infrastructure-setuplisted

# Infrastructure Setup ## Gathering Project Context Read project-knowledge references: - `.claude/skills/project-knowledge/references/architecture.md` — tech stack, framework - `.claude/skills/project-knowledge/references/patterns.md` — code conventions, branching strategy, testing - `.claude/skills/project-knowledge/references/deployment.md` — deployment strategy If files lack needed info, search other project-knowledge references — info may exist under different names. If missing entirely, ask the user and immediately update the relevant doc. **Autonomous decisions** (based on project-knowledge): - Framework init commands, folder structure, test framework, .gitignore patterns **Ask user:** - Docker: needed? Local dev, production, or both? - Pre-commit strictness: gitleaks only, or add lint/format? ## Phase 1: Framework Initialization Init framework from `architecture.md`. Use Context7 for up-to-date init commands and flags. Verify it starts. **Checkpoint:** dev server starts successfully. ## Phase 2: Folder Structure Convention — separate concerns by purpose: - **Web Apps:** `src/{components, services, lib, config}` + `tests/{unit, integration, e2e}` - **APIs:** `src/{routes, services, models, middleware, config}` + `tests/{unit, integration}` - **CLI tools:** `src/{commands, services, config}` + `tests/{unit, integration}` Add `src/prompts/` if project uses LLM prompts. Add `src/messages/` if project uses i18n. **Checkpoint:** structure created, matches projec