tools-and-scriptslisted

# Tools and scripts ## Table of contents - [Skills](#skills) - [Project commands](#project-commands) - [Per-project configuration (.aide/config)](#per-project-configuration-aideconfig) - [Spec storage](#spec-storage) --- ## Skills Skills are loaded from `~/.claude/skills/` — use the `/` syntax. Available skills: - `/aide-explore` - No-stakes thinking partner before a spec exists (creates nothing) - `/aide-create` - Create a spec - `/aide-analyze` - Analyze the codebase, then review the plan (feasibility, scope, coherence) - `/aide-manifest` - Draft or refresh the project manifest (.aide/project.yaml) - `/aide-wiki` - Build the project's wiki of how its parts hang together (run by the dashboard's Wiki tab) - `/aide-implement` - Implement with TDD - `/aide-archive` - Resolve any merge conflict on the branch, then archive the spec and feed durable knowledge back into the docs - `/aide-to-pdf` - Render the specs to PDF - `/tdd-coach` - Test-Driven Development methodology --- ## Project commands Run the project's own test/lint/build commands **automatically** without asking the user. **The test command is `AIDE_TEST_CMD` in `.aide/project.yaml`, and nothing else.** Committed with the project, so every checkout runs the same one. One command that runs the project's whole suite — a step, the landing and `/aide-implement` all run exactly it, through `aide-resolve-test-cmd --project-dir <path>`. It is never guessed: a project without the key has no test command, and the das