claudeloop-docslisted

Explains where different kinds of content belong in this repo (CLAUDE.md vs .claude/skills/ vs docs/), how to build and strict-check the MkDocs Material site, and the writing conventions used throughout (Roadmap admonitions, relative links, ADR format). Use this whenever writing or editing any file under docs/, whenever deciding whether new content belongs in CLAUDE.md, a skill, or docs/, whenever the user asks about documentation structure, or before adding a page to mkdocs.yml's nav. Make sure to consult this before adding procedural, multi-step content to CLAUDE.md directly — CLAUDE.md is deliberately kept short and holds only facts; procedures belong in a skill instead, and getting this wrong bloats the context every single session pays for.
the-vibey-project/vibey · ★ 2 · AI & Automation · score 68

Install: claude install-skill the-vibey-project/vibey

# claudeloop documentation > **Codex skill mirror** of `.claude/skills/claudeloop-docs/SKILL.md`. When this guidance changes, update Claude skill, Cursor rule, and `.agents/skills/` in the same PR. ## Where content belongs — the decision table | Content | Goes in | |---|---| | An always-true fact, cheap to state, every session needs | `CLAUDE.md` **and** `AGENTS.md` — kept deliberately SHORT, routers not manuals | | A procedure for working on a specific part of this codebase | `.claude/skills/<name>/SKILL.md` **and** mirrored to `.cursor/rules/<name>.mdc` **and** `.agents/skills/<name>/SKILL.md` | | User-facing "how do I..." | `docs/getting-started/` or `docs/guides/` | | System design — what exists, how pieces fit | `docs/architecture/` | | The reasoning behind ONE specific hard decision | `docs/architecture/decisions/` — an ADR | | Generated API docs | `docs/reference/api.md` via `mkdocstrings` — never hand-write signatures that already exist as docstrings | | Contributor process | `docs/contributing/` | | Historical plans, preserved verbatim once superseded | `docs/plans/` | **The CLAUDE.md / AGENTS.md / skill dividing line:** routers hold facts; skills/rules hold procedures. If you're about to add a multi-step "when doing X, do Y then Z" instruction to `CLAUDE.md` or `AGENTS.md`, it belongs in a skill instead — skills load into context only when relevant. ### Three agent surfaces (must stay in sync) | Surface | Paths | |---|---| | Claude Code | `CLAUDE.md` + `.clau