New specialized agent for technical writing, documentation standards, and generating docs from code. Includes Diataxis framework, severity-based review checklists, code-to-docs patterns, and quality metrics. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Agent Profiles
This directory contains specialized AI agent profiles. Each profile defines a role, principles, constraints, and workflow for a specific domain.
Available Agents
| Agent | File | Use When |
|---|---|---|
| Frontend Architect | frontend-architect.md |
UI components, performance, accessibility, React/Next.js |
| Backend Architect | backend-architect.md |
System design, databases, APIs, scalability |
| Security Auditor | security-auditor.md |
Security review, vulnerability assessment, auth flows |
| Test Engineer | test-engineer.md |
Test strategy, automation, CI/CD, coverage |
| Code Reviewer | code-reviewer.md |
Code quality, PR review, best practices |
| Prompt Engineer | prompt-engineer.md |
LLM prompts, agent instructions, prompt optimization |
| Documentation Expert | documentation-expert.md |
Technical writing, user/admin guides, docs maintenance |
Agent Selection
See RULES.md sections 4-5 for the selection protocol and multi-agent coordination.
Using context7 (Shared Guidelines)
All agents use context7 to access up-to-date documentation. Training data may be outdated — always verify through context7 before making recommendations.
When to Use
Always query context7 before:
- Recommending specific library/framework versions
- Suggesting API patterns or method signatures
- Advising on security configurations or CVEs
- Checking for deprecated features or breaking changes
- Verifying browser support or compatibility matrices
How to Use
- Resolve library ID: Use
resolve-library-idto find the correct context7 library identifier - Query documentation: Use
query-docswith the resolved ID and a specific topic
Example
User asks about React Server Components
1. resolve-library-id: "react" → get library ID
2. query-docs: topic="Server Components patterns"
3. Base recommendations on returned documentation, not training data
What to Verify
| Category | Verify |
|---|---|
| Versions | LTS versions, deprecation timelines, migration guides |
| APIs | Current method signatures, new features, removed APIs |
| Security | CVE advisories, security best practices, auth patterns |
| Performance | Current optimization techniques, benchmarks, configuration |
| Compatibility | Version compatibility matrices, breaking changes |
Critical Rule
When context7 documentation contradicts training knowledge, trust context7. Technologies evolve rapidly — training data may reference deprecated patterns or outdated versions.
Adding a New Agent
- Create a new
.mdfile in this directory - Use consistent frontmatter:
nameanddescription - Follow the structure: Role → Core Principles → Constraints → Workflow → Responsibilities → Output Format → Pre-Response Checklist
- Reference this README for context7 usage instead of duplicating the section
- Update
DOCS.mdandREADME.mdto list the new agent