← ClaudeAtlas

groundworklisted

Sets up or audits a project for AI work: CLAUDE.md contract, docs layout, agents. Use when starting a new project, there is no CLAUDE.md, or the user asks to set up or audit the repo. Writes only after your ok.
t8jwscc7qy-sketch/foma-skills · ★ 2 · AI & Automation · score 78
Install: claude install-skill t8jwscc7qy-sketch/foma-skills
Sets up or audits the project layout and the CLAUDE.md contract the other foma-skills read. Explore, present, confirm, write. Hand-offs (by message, never called): rule content (stale, duplicate, contradicting rules) to `/foma-skills:learning`; junk files, stray `*.md`, unarchived plans to `/foma-skills:tidying`. ## Steps 1. Explore, read-only. Read with Read (HTML comments are invisible in context): root and nested `CLAUDE.md`, `AGENTS.md`, `.claude/` (settings, rules, agents, skills), `.gitignore`, `docs/`, manifests. Mode: no CLAUDE.md and no AGENTS.md, or an empty repo, is setup; otherwise audit. `$ARGUMENTS` is only a hint of the mode. 2. Safety first, both modes: list hooks, `env` (esp. `ANTHROPIC_BASE_URL`), `enableAllProjectMcpServers` and `.mcp.json` servers from `.claude/settings*.json`, and tell the user before anything else. Change none of them. 3. Setup: if the repo is empty, ask what the project is for first. Ask the choices in rounds of 4 or fewer, recommended answer first. 4. Branch per mode (below). 5. Present findings and the exact proposed diffs, grouped (contract, docs skeleton, agents, `.gitignore`, optional lines). Write a group only after the user's ok on that group. 6. Write. Own content goes in one block, `<!-- foma-skills:start -->` ... `<!-- foma-skills:end -->`. On rerun, Read the file and replace the text between the markers; never append a second block. If the markers are missing but the headings exist, edit those sections in place. 7. Agents: