# 03 Assert

Assert the work behaves by iterating the project's coding assertions until they pass...

- Repository: https://github.com/ai-driven-dev/framework (542 stars)
- Category: Design
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add ai-driven-dev/framework --skill 03-assert -g -a claude-code -y`
Codex: `npx skills add ai-driven-dev/framework --skill 03-assert -g -a codex -y`
Cursor: `npx skills add ai-driven-dev/framework --skill 03-assert -g -a cursor -y`
Gemini CLI: `npx skills add ai-driven-dev/framework --skill 03-assert -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add ai-driven-dev/framework`

## Description

Assert the work behaves by iterating the project's coding assertions until they pass, plus optional architecture and frontend facets. Use to validate an implementation. Not for reviewing or writing tests.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Skill: assert

Validate that the work behaves as intended: run the project's assertions, iterating and fixing until they pass.

## Actions

| #   | Action                | Facet                                                       |
| --- | --------------------- | ----------------------------------------------------------- |
| 01  | `assert`              | Run the project's coding assertions, fixing until they pass |
| 02  | `assert-architecture` | Report where the code breaks the documented architecture    |
| 03  | `assert-frontend`     | Inspect the running UI, fixing until the behavior is right   |

Run every applicable facet by default, or one when named. Coding (`01`) always applies; add `03` when the work has a UI and a frontend is running, the facet resolving the URL itself; run `02` only when architecture conformance is asked for. Skip a facet whose precondition is absent, with a noted reason. Ask only when the intent is genuinely ambiguous.
Before running an action, read its file in `actions/`, not only the table or assets.

## Transversal rules

- Gate: it returns a pass or fail verdict on the work.
- Fix loop: the coding and frontend facets fix and re-run until they pass. The architecture facet only reports, never fixes.
- Stop only when every selected assertion passes a final clean sweep.
- On supplied CI failures, fixing facets collect all failed checks, repair each reproducible failure locally, and rerun every applicable command in the final sweep; the caller pushes once after green if authorized, with CI-only checks unverified.

## Assets

- `assets/task-template.md`: the tracking file the frontend facet fills across its fix loop.