Assessment Output

What's in each agent

Every generated agent file follows the same structure: an instruction header that tells Claude how to use the rules, a per-file implementation loop, and a numbered list of project-specific patterns. The numbering is deliberate — agents reference rules by number ("Apply rule 14: tests live next to components") so plans and reviews can call out exactly which conventions a change exercises.

# Frontend Agent Implementation Rules

## Per-File Implementation Loop
1. Pattern Check
2. Similar Files Analysis
3. Implement File
4. Verify Pattern Match
...

## Frontend Patterns - <project>

### Aspect 1: Component Structure and Naming
1. UI primitives use shadcn/ui pattern with React.forwardRef and displayName.
2. Feature components are plain named function exports.
...

Frontend agent example

Output of /hypr:assess-frontend on a React + Tailwind project. Captures 17 aspects: component structure, file organization, styling, state, props, imports, types, error handling, testing, forms, data fetching, routing, permissions, performance, configuration, documentation, and tooling.

Sample patterns extracted (numbered exactly as they appear in the file):

• "UI primitives use shadcn/ui pattern with React.forwardRef and displayName." (#1)
• "Feature components are plain named function exports — no forwardRef, no default export." (#2)
• "State is managed entirely with React useState and useEffect hooks — no external state library." (#16)
• "Tests use Vitest + Testing Library + happy-dom, co-located as *.test.tsx files." (#37)

Full file: real-frontend-agent-example.md on GitHub (258 lines).

Backend agent example

Output of /hypr:assess-backend on a NestJS + TypeORM project. Covers 21 aspects across API conventions, database patterns, auth, migrations, testing, validation, and error handling.

Sample patterns:

• "Each domain has a controller / service / module trio."
• "Entities use @Entity(), @PrimaryGeneratedColumn('uuid'), and CreateDateColumn/UpdateDateColumn for timestamps."
• "Migrations use the project's npm run migration:generate script — never hand-edited."

Full file: real-backend-agent-example.md on GitHub (268 lines).

Planning agent example

Output of /hypr:assess-planning on a full-stack project. The planning agent decides how features get decomposed: chunk size, dependency ordering, test strategy, rollback approach.

Sample patterns:

• "Each chunk is sized to be completable in a single implementation session (< 2 hrs)."
• "Frontend tests live alongside components as .test.tsx." (#14)
• "Frontend rollback is straightforward: re-deploy a previous git commit's build to S3 with cache invalidation." (#41)

Full file: real-planning-agent-example.md on GitHub (404 lines).