← ClaudeAtlas

devialisted

Project memory and engineering standard. Use at the START of any work on a repository: initialise or read .devia/, follow the rules it pins, and update it in the same change. Triggers on starting work in an unfamiliar repo, "init devia", memory or standard questions, and before claiming anything is done or production ready.
schneiderjoseph/devia · ★ 1 · AI & Automation · score 69
Install: claude install-skill schneiderjoseph/devia
# devia A repository worth working on has a memory. `.devia/` is that memory, and this skill is how you use it. ## Step 1 — is there a memory? ```bash ls .devia ``` **No `.devia/`** → initialise before writing any code: ```bash npm i -D @schneiderjoseph/devia # the package is scoped, the command is not npx devia init ``` Install first: `npx devia` only resolves once the package is a dependency of the project. Then fill `.devia/00_OVERVIEW.md` from what the repository actually contains — stack, modules, where the truth lives. Read the code to fill it; do not invent it. This is not paperwork: it is the difference between a task and a guess (`AGT-002`). **`.devia/` exists** → read, in this order: 1. `.devia/AGENTS.md` — the contract for this repository 2. `.devia/10_NEVER_ALWAYS.md` — what this project has already banned 3. `.devia/00_OVERVIEW.md` — what this project is 4. The memory file for the surface you are about to touch (`.devia/14_INDEX.md`) ## Step 1b — what has this project NOT decided? ```bash npx devia decide pending ``` **A `pending` decision is not permission to choose one.** The register names the questions this kind of project always owes an answer to — its purpose, its stack versions, its brand, whether search engines and AI crawlers may have it — and a slot that has not been ruled on is a question with an owner, not a blank for you to fill (`DEC-001`). | Status | What you may do | |---|---| | `decided` | Implement it. Never reverse it quietly. |