project-initlisted

# project-init Configure the current project directory. `AGENTS.md` is the cross-tool context file (read by Claude Code, Codex, Antigravity, Cursor, opencode, Windsurf); `GEMINI.md` holds Antigravity-specific overrides. ## Flow 1. **Confirm the dir.** It's the project cwd. If it's `~` or a tool config dir, WARN before continuing. 2. **ALWAYS ask the user what the project is about — before generating anything.** What it is, its goal, the **domain** (e.g. networking/Fortinet, fintech, RAG app), and preferred stack. Ask even if a README or code already exists — **do NOT silently infer from the folder name or README**; confirm with the user (you may propose a draft from the README and ask them to correct it). **Wait for their answer.** It becomes `--about` and drives BOTH the context files AND which experts to discover in step 5. A vague `--about` = a weak setup. 3. **Generate** by running the bundled script: ``` node "<this-skill-dir>/project-init.js" . --about "<what it is>" # Codex node "<this-skill-dir>/project-init.js" . --gemini --about "<what it is>" # Antigravity (also writes GEMINI.md) ``` It detects language/frameworks/real commands and writes `AGENTS.md` (+ `GEMINI.md`) and `STATE.md`. Keeps existing files unless `--force`. 4. **Fill the high-value sections** (best practice): the files ship with placeholders for **Structure** and **Non-obvious patterns**. Inspect the repo and fill them — structure high-level; patterns ONLY the counterintui