ragnarwestad
UserSpec-driven development for AI coding assistants (Claude Code, Codex, OpenCode, Copilot) — specs, skills and a dashboard that runs them.
Categories
Indexed Skills (25)
aide-wiki
Build the project's wiki: a map of how its parts hang together, kept in the project's folder of the specs repository and read first by /aide-analyze. One page per part, an index and a schema, each generated page naming the files and the commit it was written from. Use when: the run is a wiki build (the runner starts it with --command wiki), the wiki is missing or stale. Do NOT use for: a spec's analysis (use aide-analyze), documentation for readers of the project (use the project's own docs).
aide-repo-maintenance
How to add a new skill, update a shared rule, or change the 4-file spec structure in the Aide repo itself, and how install.sh/uninstall.sh must stay mirrored. Use when: adding or editing a skill or rule under core/, changing spec-structure.md, or touching install.sh/uninstall.sh. Do NOT use for: ordinary spec work (create/analyze/implement/archive) in any project Aide is installed into — this is about maintaining Aide's own source.
aide-analyze
Analyze the codebase for a spec. Detects complexity (LOW/MEDIUM/HIGH), maps affected files with file:line references, and creates an implementation plan with TDD. Use when: analyzing the codebase for an existing task, filling in 2-analysis.md and 3-solution.md, needing an overview of affected files and API impact. Do NOT use for: creating a new task (use aide-create), implementation (use aide-implement).
aide-archive
Archive a finished spec and feed its durable knowledge back into the project's living documentation — resolving the branch's merge conflict with the default branch first, if there is one. Use when: a spec is done, closing it out, cleaning up the specs root, a spec's branch conflicts with the default branch. Do NOT use for: creating specs (use aide-create), unfinished work, deleting specs.
aide-close
Close a spec that is not going to work: record the reason, move it to archive/, and delete its code branch without merging it — resolving the specs branch's merge conflict with the default branch first, if there is one. Use when: a spec's idea does not hold, its description asked for something that cannot be built, a work round needs to end without being finished. Do NOT use for: finished work (use aide-archive), another round on the same spec (change an acceptance criterion and run analyze again), unfinished work that is still worth finishing.
aide-create
Create a spec — a title and a description — as the 4-file spec structure (description, analysis, solution, status). Use when: creating a new spec, starting new work that needs documentation. Do NOT use for: analysis (use aide-analyze), implementation (use aide-implement), code review.
aide-implement
Implement the solution for a spec with Test-Driven Development (RED → GREEN → REFACTOR). Reads the existing analysis and plan, writes tests first, implements, and runs the quality check. Use when: implementing a solution with TDD, having a completed analysis and implementation plan, coding based on 3-solution.md. Do NOT use for: creation (use aide-create), analysis (use aide-analyze).
aide-manifest
Draft or refresh the project's .aide/project.yaml manifest — what the project IS: stack, dependencies, deployment, logging, statistics, reports, docs. Drafts from the codebase, ASKS about what it cannot derive, never guesses. Use when: setting up Aide in a project, the manifest is stale, an analysis needs project context that is missing. Do NOT use for: per-user settings (.aide/config), creating specs (use aide-create), analyzing a task (use aide-analyze).
aide-reopen
Take an archived spec back into the active list for another round, keeping every file as it is, or, when asked, resetting the analysis, the plan and the status as well. Keeps the description and the archive trail, and marks the point after which nothing counts as having run. Use when: archived work has to be done again, a spec was archived too early, a shipped change has to be redone from its own description. Do NOT use for: creating a new spec (use aide-create), analysis (use aide-analyze), archiving (use aide-archive).
aide-to-pdf
Generate PDF from a spec. Use when: exporting documentation to PDF, generating a print-friendly spec. Do NOT use for: creating documentation (use aide-create)
documentation
The documentation standard for markdown documents: title, table of contents, headings, separators, code blocks, numbered lists, emojis, and the practices that make a document useful to an AI assistant. Use when: writing or restructuring any markdown document, adding a table of contents, formatting code examples, referencing files or screenshots in a document. Do NOT use for: linter errors specifically (use the markdown-linting skill), the 4-file spec layout (use the spec-structure skill).
markdown-linting
Markdown linting for this workspace: MD029 list numbering, MD040 code block language tags, MD051 anchor links, and the closing-fence mistake that breaks HTML generation. Use when: writing or editing any .md file, running markdownlint-cli2, fixing MD029/MD040/MD051 errors, generating HTML or PDF from markdown. Do NOT use for: the general documentation standard (use the documentation skill) — this is the linter-specific subset.
playwright-e2e
Prosjekt-uavhengige Playwright E2E-regler: detekter prosjektets egne konvensjoner, rolle-baserte locators, auto-waiting, test-isolasjon, mocking og soft assertions. Use when: skriver eller endrer Playwright E2E-tester i et hvilket som helst prosjekt. Do NOT use for: enhetstester (Vitest/Jest), manuell testing, backend-tester.
spec-structure
The 4-file spec structure (1-description, 2-analysis, 3-solution, 4-status): what belongs in each file, the required sections, and the Tracking info fields. Use when: creating, analyzing, reviewing, implementing or archiving a spec; deciding which of the four files a piece of content belongs in. Do NOT use for: general documentation formatting (use the documentation skill), the workflow around the files (use the workflows skill).
task-workflow-assistant
Structured analysis and planning of a spec. Use when: analyzing a spec, planning its solution, identifying affected files. Do NOT use for: pure code implementation, TDD cycle, code review
tdd-coach
Test-Driven Development methodology. Use when: implementing new functionality, refactoring existing code, ensuring high test coverage. Do NOT use for: task analysis and planning (use task-workflow-assistant), codebase exploration without implementation
tools-and-scripts
Aide's skills, the per-project .aide/config keys, how a project's own test/lint/build commands are detected, and where specs are stored. Use when: running a project's test, lint or build command; looking up which Aide skill does what; reading or writing .aide/config; deciding where a spec belongs. Do NOT use for: how to run tests correctly (that is the testing rule), the spec files' own layout (use the spec-structure skill).
unit-tests
Prosjekt-uavhengig: analyser en fil og opprett manglende enhetstester. Detekter prosjektets test-oppsett (runner, kommando, stil), skriv happy/edge/error-tester som matcher eksisterende stil, kjør dem og rapporter dekning. Use when: skal generere manglende enhetstester for en fil, skal øke testdekning i et hvilket som helst prosjekt. Do NOT use for: TDD-implementering av ny funksjonalitet (egen flyt), E2E-tester (bruk `playwright-e2e`), ren kode-review.
workflows
The workflow for AI-assisted development: complexity detection (LOW/MEDIUM/HIGH), problem-type routing, branch strategy across repositories, and the create - analyze - implement - archive flow for a spec. Use when: starting work on a spec, deciding how much analysis a task needs, planning a change that spans several projects, checking which branch belongs where. Do NOT use for: the spec files' own layout (use the spec-structure skill), how to run tests (that is the testing rule).
install-all
Install Aide for all AI tools (Claude Code, Copilot, Codex). Runs install-all.sh, which calls each implementations/<ai>/install.sh. Use when: installing or updating Aide for all tools, having changed skills or rules and wanting to reinstall. Do NOT use for: uninstalling (use /uninstall-all). Just one AI? Run implementations/<ai>/install.sh directly.
aide-explore
No-stakes thinking partner before /aide-create: explore a problem or idea, weigh approaches, sharpen the scope — without creating any files. Use when: an idea is not ready for a spec yet, weighing whether/how to do something, unclear scope, "what would it take to ...". Do NOT use for: creating specs (use aide-create), analysis of an existing spec (use aide-analyze), implementation.
ai-tools-reference
Verified configuration reference for the three AI tools Aide supports: Claude Code, GitHub Copilot and OpenAI Codex. Covers instruction files, skill discovery paths, frontmatter field support, rules, agents, hooks, MCP and config formats, with a comparison matrix and source links. Use when: answering which tool reads which path, changing an installer, adding or moving a skill, checking frontmatter field support, updating the support matrix. Do NOT use for: news about new releases (use check-news), general web questions about the tools.
check-news
Check AI tool news from Anthropic, GitHub and OpenAI. Fetches changelogs and news from official sources, assesses relevance for Aide, and updates the news log. Use when: checking AI news, wanting to know what's new in Claude Code/Copilot/Codex, updating the news log. Do NOT use for: general questions about AI tools (use web search directly).
uninstall-all
Uninstall Aide for all AI tools (Claude Code, Copilot, Codex). Runs uninstall-all.sh, which calls each implementations/<ai>/uninstall.sh. Use when: removing Aide from the machine, cleaning up before a fresh install. Do NOT use for: installing (use /install-all). Just one AI? Run implementations/<ai>/uninstall.sh directly.
ai-tools-upgrade
How the Copilot and Codex CLIs are kept up to date on a machine, and how to install the daily upgrade job — plain cron on an always-on machine, a launchd agent on a laptop (cron silently skips runs the machine sleeps through). Use when: setting Aide up on a new machine, the AI tools have gone stale, choosing between cron and launchd, editing core/scripts/upgrade-ai-tools. Do NOT use for: updating Claude Code itself (it auto-updates), checking for news (use check-news).
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.