← ClaudeAtlas

ark-placelisted

Where does new code go? Names the folder from the rules file and writes the file there.
pedroknigge/arkgate · ★ 1 · AI & Automation · score 67
Install: claude install-skill pedroknigge/arkgate
# /ark-place — Where does this code go? **Contener · Guiar · Ordenar.** In plain words: contain the write, guide the next step, order leftover mess. This door is **Contener**: write the new file in the right house. Skills never enforce — CLI / hooks / CI do. **When:** you are adding a new file or artifact and need the layer, folder, and name. **Not when:** session 0 / config is missing or lying (`/ark-adopt`) or an existing violation cluster (`/ark-autopilot`). ## Steps 1. CLI-first: if the local CLI already resolved the root, skip waiting on MCP. Identity is optional then. 2. Place with **filePath required** (`ark_place` or read `ark.config.json` + `.ark/golden-pattern.json`). Fail-closed without a path — never invent `components/*.tsx` or default to Presentation. 3. Write it there. Then `arkgate-check`. ## Checklist - `filePath` is known before the call. Description alone is not a path. - Host write gate: prefer the installed pre-hook. MCP `ark_prepare_write` is fallback when that hook is missing or fail-open. Skills never enforce. - Golden pattern is load-bearing when present. Adopt generates it. - An included file that matches no layer is not a pass. The write gate denies it (`CONFIG_UNCLASSIFIED_FILES`). Place it in a layer folder, or send include/layer drift to `/ark-adopt`. Do not write into a loose include gap. - Do not default a repository to Presentation. - When doctor JSON has `noDomainFrontend`, the new file is a Domain rule — not another UI helper.