Menu
Assert features work as intended - general assertions, architecture conformance, and frontend UI validation.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Detect the current project's state and open a hub of project actions - understand the project, set up or refresh the memory bank, or continue the AIDD development journey. Silently inspects the project, the AIDD setup, and which AIDD plugins are installed, then adapts the menu to that context. Use when the user says "where do I start", "onboard me", "onboard me to this project", "what should I run next", "what should I work on next", "what's the state of this project", "guide me through aidd", "guide me through aidd-context", or invokes `aidd-context:00-onboard`. Do NOT use to enumerate every installed surface from raw user intent (the discovery skill in this plugin handles that).
Imagine and validate the technical architecture of a new SaaS through interactive Q&A, candidate-stack comparison, multi-agent audit, and an INSTALL.md output. Use when starting a new SaaS project, choosing a stack, designing the architecture pattern (monolith vs microservices vs serverless), or producing a project's INSTALL.md. Do NOT use for editing an existing project's stack, database schema design, or scaffolding actual files (this skill produces docs only, no code).
Initialize or refresh the project memory bank and ensure AI context files contain the project memory block. Use when running `aidd init` for the first time, bootstrapping a new project, or re-running the init flow on an existing project. Do NOT use for updating individual memory files after they exist - use `aidd-context:05-learn` instead; do NOT use for editing a single rule - edit the file directly.
Generate context artifacts (skills, agents, rules, commands, hooks, plugins, marketplaces) across the host AI tool(s) the project uses. Use when the user wants to create, refactor, add or remove actions in a skill, migrate a legacy slash command into a router-based skill, or generate a new agent, rule, command, hook, plugin, or marketplace. Do NOT use for editing a single action inside an existing skill (edit directly), writing MCP servers, or modifying project-level files.
Generate high-quality Mermaid diagrams from markdown content using a structured plan-validate workflow.
Capture and store project-level learnings, conventions, and decisions surfaced during work into memory, decisions, or rules. Use proactively when the user states a durable project rule or convention ("for next", "always do X", "from now on", "going forward", "rule:", "convention:"), records a technical decision and its rationale, deprecates something, or notes an insight that should outlive the current task. Do NOT use for personal or AI-preference reminders (those belong to user memory), routine code edits, minor fixes, or anything already captured.
| name | 03-assert |
| description | Assert features work as intended - general assertions, architecture conformance, and frontend UI validation. |
| model | sonnet |
Validates correctness of implementations through iterative assertion loops, architecture checks, and browser-based frontend verification.
| # | Action | When to use |
|---|---|---|
| 01 | assert | Iterate until a feature works by running the project's coding assertions |
| 02 | assert-architecture | Verify the codebase conforms to documented architecture (C4, ADRs, tree) |
| 03 | assert-frontend | Iterate until a frontend feature works by inspecting the running UI |
These actions are complementary facets, not mutually exclusive. This skill is run-one-OR-run-all:
When running all applicable: 01-assert is the baseline (project coding assertions); add 03-assert-frontend when the feature has a UI and a running frontend URL; add 02-assert-architecture when architecture conformance is in scope. A facet whose precondition is absent (e.g. no running URL) is skipped with a noted reason, never forced. Run the selected actions in order (01, then 03, then 02). Read and follow each selected action file.
@actions/01-assert.md@actions/02-assert-architecture.md@actions/03-assert-frontend.md