seed-conventionslisted

# Seed Conventions > **HARD GATE** — **HARD GATE** — Before any new code lands, confirm the project conventions are understood. Ask: 'What does a good commit message look like in this project?' Bootstrap a new project with the AI agent conventions it needs. Run this once at the start of a greenfield project. ## What this creates - `CLAUDE.md` — Claude Code session config (project-specific) - `CONVENTIONS.md` — shared rules for all AI agents - `specs/` — the specs directory where all planning output will live - `AGENTS.md` — for OpenCode and other agents (optional) - `GEMINI.md` — for Gemini CLI (optional) ## Interview Ask the user these questions (one at a time, wait for each answer): 1. **Project name and one-sentence description** — "What is this project? One sentence." 2. **Stack** — "What language, framework, and runtime? (e.g. TypeScript / Next.js / Node 22)" 2b. **Stack profile (optional)** — Offer: `swift`, `typescript-vue`, `node-service`, or none. If chosen, merge the matching fragment from `profiles/<name>.md` into generated `CONVENTIONS.md` (commands, architecture, never-do). 3. **Commands** — "What commands do you use for: run, test, build, lint? I'll document them so agents know how to verify their work." 4. **Architecture** — "Describe the key modules and their relationships in 1–2 sentences. What are the main moving parts?" 5. **Conventions** — "Any naming conventions, file organization rules, or patterns that every contributor (human or agent) must