kamehadb: Skill for Claude Code

Setup Codebase

Create context with repository-reading, not a static file template. Existing context belongs to the project: never overwrite or shorten it.

Pick the mode before step 1; this guard runs before any write.

1. Check the exact status of AGENTS.md, CLAUDE.md, CONVENTIONS.md, docs/llm/, and .gitignore. Read every existing context or conventions file before writing anything. If the repository has no application source and an approved design exists as design.md in a docs/agent-devkit/changes/ folder (or a legacy spec under docs/agent-devkit/specs/), read it before writing context.
2. If context is missing, inspect only enough evidence to ground it: README*, root/workspace manifests, task scripts, environment examples, CI/config, top-level source layout, and any approved design from the previous step. Do not install dependencies, start services, or infer facts from filenames alone.
3. Write only missing files from that evidence:

   • AGENTS.md: concise purpose, relevant layout, verified commands, explicit conventions/gotchas, and verification. Omit unknown sections. For a source-less new project, the approved design establishes intended purpose and planned layout only; do not claim unimplemented behavior or commands as verified. If a skills/ or .agents/skills folder exists in the repository, add a ## Skills section listing each skill by name with its SKILL.md path so every agent platform can discover them. If docs/llm/ exists or is created, add a ## Documentation section:

     ## Documentation
     
     The verified codebase wiki is at `docs/llm/INDEX.md`.
     
     For behavior, workflow, or domain questions:
     
     1. Read `docs/llm/INDEX.md`.
     2. Open the relevant wiki page.
     3. Verify important claims against current source and tests.
     
     The wiki describes verified behavior only; source and tests remain authoritative.
     

   • CLAUDE.md: a short repository-specific pointer to AGENTS.md; include extra instructions only when local evidence establishes them.

   • docs/llm/: for direct setup or wiki-only inline calls, create the wiki skeleton with AGENTS.md and INDEX.md; skip for a code-task call without an explicit wiki-setup request. The generated AGENTS.md must match document-wiki's current-source verification rules, distinguish verification limits from confirmed content gaps, and state that any existing log is legacy, not read or written and not used for freshness. It must also state that feature pages use document-wiki's requirement format and the ## Requirement prefixes registry in INDEX.md, without restating the format. Do not create LOG.md. If a legacy LOG.md already exists, preserve it byte-for-byte without reading or updating it. Create wiki category folders (architecture/, domains/, workflows/, integrations/, operations/, or decisions/) only when document-wiki has a real page to place there; do not add placeholder pages just to preserve empty directories.