Skip to content

Latest commit

 

History

History
76 lines (47 loc) · 3.16 KB

AGENTS.md

File metadata and controls

76 lines (47 loc) · 3.16 KB

AGENTS.md

Cross-agent behavioral constraints. See AGENT-STRATEGY.md for ecosystem docs.

Prime Directive

TypeScript + Next.js 14+ App Router codebase. Follow CLAUDE.md (architecture, quality gates) and copilot-instructions.md (always-on rules).

Universal Agent Protocol

  1. Always use /ultrathink. Think deeply and critically about every task before acting.
  2. Read before writing — match existing patterns.
  3. Co-locate tests next to source.
  4. No any, @ts-ignore, as unknown as — see typescript.instructions.md.
  5. Validate all external input at runtime.
  6. Server Components by default — 'use client' only when needed.
  7. @/ imports, group order: external → internal → relative.
  8. Never suppress linting. Fix root cause.
  9. Quality gate compliance — see copilot-instructions.md § Non-Negotiables.
  10. Handoff, don't duplicate — if a task is outside your domain, hand off to the right specialist.
  11. Every agent has an escape route — when stuck, report findings and hand off with context.

Architecture

Pages → Components → Hyperdex (src/lib/queries/) → Prisma → PostgreSQL

  • Hyperdex is the only DB access path
  • Three shapes per entity — see prisma-queries.instructions.md
  • Cross-link everything — no dead ends

Agent Handoff Protocol

Every handoff must include:

  1. What was accomplished — summary of completed work
  2. What remains — with specific file paths
  3. Blockers — anything preventing progress
  4. Quality gate status — did the work pass lint/test/build?

All handoffs use send: false — user confirms before the next agent begins.

Agent Roster (23 Agents)

Core (12)

Orchestrator, Architect, Implement, Review, TDD, Debug, Document, Refactor, Research, Perf, Verifier, Security

Specialist (5)

Specialist-Backend, Specialist-Data, Specialist-Infra, Specialist-SEO, Specialist-UI

Read-Only Reviewers (3)

Copy-Editor — user-facing text quality, naming consistency, SEO copy. Data-Analyst — database coverage audits, gap analysis, integrity checks. Designer — Tier 0 design principles, visual hierarchy, UX flow critiques.

Dispatch (1)

Operator — takes continuation prompts, reads branch context, routes to the correct specialist agent.

Peripheral (1)

Chaos — surprise audit agent. Not part of standard workflows. Triggered manually or on timer. Inspects only in-flight files. Maximum 3 inspections per session. Reports findings but doesn't block unless critical.

Autonomous (1)

Autoloop — fully autonomous work cycle: select task, implement, pipeline, PR, review, merge, loop. Operates independently of the standard agent roster.

Ecosystem

See AGENT-STRATEGY.md for the full three-layer architecture, workflows, and agent selection guide.

Continue work: Say "Continue the work" → Orchestrator reads WORK-QUEUE.md → selects tasks → delegates → updates state.

Pipeline: /00-intake → /10-plan → /20-implement → /30-verify → /40-docs → /90-release-notes