agents-templated 1.2.2 → 1.2.3

package/README.md

@@ -120,7 +120,7 @@ When you run `agents-templated init`, you get:
 ```
 your-project/
 ├── agent-docs/                      # 📚 Comprehensive documentation
-│   ├── AI_INSTRUCTIONS.md          # Primary AI assistant guide
+│   ├── AGENTS.md                   # AI assistant guide
 │   ├── ARCHITECTURE.md             # Project architecture & tech stack
 │   ├── AGENTS.MD                   # Agent delegation patterns
 │   └── README.md                   # Human-readable setup guide
@@ -226,9 +226,9 @@ Open your AI assistant and it will automatically load the appropriate config:
 
 ### 3. Read the Documentation
 
-- **[agent-docs/AI_INSTRUCTIONS.md](agent-docs/AI_INSTRUCTIONS.md)** – Primary AI assistant guide
+- **[AGENTS.md](AGENTS.md)** – AI assistant guide
 - **[agent-docs/ARCHITECTURE.md](agent-docs/ARCHITECTURE.md)** – Project architecture & tech stack guidance
-- **[agent-docs/AGENTS.MD](agent-docs/AGENTS.MD)** – Agent delegation patterns
+- **[AGENTS.md](AGENTS.md)** – AI assistant guide
 - **[agents/rules/security.mdc](agents/rules/security.mdc)** – Security patterns (CRITICAL)
 - **[agents/rules/testing.mdc](agents/rules/testing.mdc)** – Testing strategy
 
@@ -276,7 +276,7 @@ Your AI will follow the enterprise patterns automatically!
 | **TestAgent** | Unit, integration, E2E, accessibility testing |
 | **SecurityAgent** | Input validation, authentication, OWASP compliance |
 
-**Reference**: [agent-docs/AGENTS.MD](agent-docs/AGENTS.MD)
+**Reference**: [AGENTS.md](AGENTS.md)
 
 ---
 

package/bin/cli.js

@@ -162,27 +162,27 @@ program
         );
       }
 
-      // Install AI Agent instructions (Cursor, Copilot, VSCode, Gemini)
+      // Install AI Agent instructions (Cursor, Copilot, Claude, Gemini)
       if (installAll || choices.includes('github')) {
         console.log(chalk.yellow('Installing AI agent instructions...'));
         await fs.ensureDir(path.join(targetDir, '.github'));
         await copyFiles(templateDir, targetDir, [
           '.cursorrules',
           '.github/copilot-instructions.md',
-          '.vscode-ai-rules.md',
-          '.gemini-instructions.md'
+          'CLAUDE.md',
+          'GEMINI.md'
         ], options.force);
         console.log(chalk.gray('  ✓ Cursor (.cursorrules)'));
         console.log(chalk.gray('  ✓ GitHub Copilot (.github/copilot-instructions.md)'));
-        console.log(chalk.gray('  ✓ VSCode (.vscode-ai-rules.md)'));
-        console.log(chalk.gray('  ✓ Google Gemini (.gemini-instructions.md)'));
+        console.log(chalk.gray('  ✓ Claude (CLAUDE.md)'));
+        console.log(chalk.gray('  ✓ Google Gemini (GEMINI.md)'));
       }
 
       console.log(chalk.green.bold('\nInstallation complete!\n'));
       console.log(chalk.cyan('Next steps:'));
-          console.log(chalk.white('  1. Review agent-docs/AI_INSTRUCTIONS.md for AI assistance guide'));
+      console.log(chalk.white('  1. Review AGENTS.md for generic AI assistant guide'));
       console.log(chalk.white('  2. Review agent-docs/ARCHITECTURE.md for project guidelines'));
-      console.log(chalk.white('  3. Review agent-docs/AGENTS.MD for agent patterns'));
+      console.log(chalk.white('  3. Review AGENTS.md for AI assistant guide'));
       console.log(chalk.white('  4. Configure your AI assistant (Cursor, Copilot, etc.)'));
       console.log(chalk.white('  5. Adapt the rules to your technology stack\n'));
 
@@ -353,13 +353,15 @@ program
         await copyFiles(templateDir, targetDir, [
           '.cursorrules',
           '.github/copilot-instructions.md',
-          '.vscode-ai-rules.md',
-          '.gemini-instructions.md'
+          'AGENTS.md',
+          'CLAUDE.md',
+          'GEMINI.md'
         ], options.force);
         console.log(chalk.gray('  ✓ Cursor (.cursorrules)'));
         console.log(chalk.gray('  ✓ GitHub Copilot (.github/copilot-instructions.md)'));
-        console.log(chalk.gray('  ✓ VSCode (.vscode-ai-rules.md)'));
-        console.log(chalk.gray('  ✓ Google Gemini (.gemini-instructions.md)'));
+        console.log(chalk.gray('  ✓ Generic AI (AGENTS.md)'));
+        console.log(chalk.gray('  ✓ Claude (CLAUDE.md)'));
+        console.log(chalk.gray('  ✓ Google Gemini (GEMINI.md)'));
       }
 
       // Step 4: Show recommendations
@@ -371,9 +373,9 @@ program
       if (techStack.database) console.log(chalk.white(`   Database: ${techStack.database}`));
       
       console.log(chalk.cyan('\n📚 Next Steps:\n'));
-      console.log(chalk.white('   1. Review agent-docs/AI_INSTRUCTIONS.md for AI assistance guide'));
+      console.log(chalk.white('   1. Review AGENTS.md for AI assistant guide'));
       console.log(chalk.white('   2. Review agent-docs/ARCHITECTURE.md for project guidelines'));
-      console.log(chalk.white('   3. Review agent-docs/AGENTS.MD for agent patterns'));
+      console.log(chalk.white('   3. Review AGENTS.md for AI assistant guide'));
       console.log(chalk.white('   3. Customize agents/rules/*.mdc for your tech stack'));
       
       if (techStack.frontend || techStack.backend) {
@@ -452,7 +454,13 @@ program
       let passed = [];
 
       // Check documentation files
-      const docFiles = ['AGENTS.MD', 'ARCHITECTURE.md', 'AI_INSTRUCTIONS.md'];
+      if (await fs.pathExists(path.join(targetDir, 'AGENTS.md'))) {
+        passed.push(`✓ AGENTS.md found`);
+      } else {
+        warnings.push(`⚠ AGENTS.md missing - run 'agents-templated init --docs'`);
+      }
+
+      const docFiles = ['ARCHITECTURE.md'];
       const docsDir = path.join(targetDir, 'agent-docs');
       
       if (await fs.pathExists(docsDir)) {
@@ -655,9 +663,9 @@ program
       // List potential updates
       const updates = [];
       const checkFiles = [
-        { file: 'agent-docs/AGENTS.MD', component: 'docs' },
+        { file: 'AGENTS.md', component: 'root' },
         { file: 'agent-docs/ARCHITECTURE.md', component: 'docs' },
-        { file: 'agent-docs/AI_INSTRUCTIONS.md', component: 'docs' },
+        { file: 'AGENTS.md', component: 'root' },
         { file: 'agents/rules/security.mdc', component: 'rules' },
         { file: 'agents/rules/testing.mdc', component: 'rules' },
         { file: 'agents/rules/core.mdc', component: 'rules' },

package/index.js

@@ -26,9 +26,8 @@ async function install(targetDir, options = {}) {
   // Documentation files
   if (installAll || options.docs) {
     files.push(
-      'agent-docs/AGENTS.MD',
+      'AGENTS.md',
       'agent-docs/ARCHITECTURE.md',
-      'agent-docs/AI_INSTRUCTIONS.md',
       'agent-docs/README.md'
     );
   }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agents-templated",
-  "version": "1.2.2",
+  "version": "1.2.3",
   "description": "Technology-agnostic development template with multi-AI agent support (Cursor, Copilot, VSCode, Gemini), security-first patterns, and comprehensive testing guidelines",
   "main": "index.js",
   "bin": {

package/templates/.cursorrules

@@ -35,7 +35,7 @@
 - **Performance**: Monitor bundle/binary size, implement lazy loading patterns
 - **Accessibility**: WCAG 2.1 AA compliance for user-facing components
 - **Testing**: All business logic and user flows must have appropriate tests
-- **Documentation**: Keep README, agent-docs/ARCHITECTURE.md, and agent-docs/AGENTS.md updated
+- **Documentation**: Keep README, agent-docs/ARCHITECTURE.md, and AGENTS.md updated
 
 ## Technology Stack Adaptation
 Choose your stack and apply these patterns consistently:
@@ -55,7 +55,7 @@ Choose your stack and apply these patterns consistently:
 - **NoSQL**: MongoDB, DynamoDB with ODM patterns
 - **Cloud**: Supabase, Firebase, managed database services
 
-## Agent Delegation (See agent-docs/AGENTS.md for details)
+## Agent Delegation (See AGENTS.md for details)
 - **UI/Design work** → FrontendAgent
 - **API/Business logic** → BackendAgent  
 - **Database/Schema** → DatabaseAgent

package/templates/{agent-docs/AI_INSTRUCTIONS.md → AGENTS.MD}

@@ -4,8 +4,8 @@ This project follows enterprise-grade, technology-agnostic development patterns.
 
 ## Primary Documentation (Always Reference)
 
-- **`ARCHITECTURE.md`** - Overall project guidelines, architecture principles, and technology stack selection
-- **`AGENTS.md`** - Agent delegation patterns, responsibilities, and when to use each agent
+- **`AGENTS.md`** - This file! AI instructions for working with AI assistants
+- **`agent-docs/ARCHITECTURE.md`** - Overall project guidelines, architecture principles, and technology stack selection
 
 ## Detailed Rules (Reference When Relevant)
 
@@ -23,11 +23,10 @@ When implementing features, always check the relevant rule file:
 
 When implementing any feature:
 
-1. **Check `AGENTS.md`** to determine which agent pattern applies (FrontendAgent, BackendAgent, DatabaseAgent, etc.)
-2. **Reference `ARCHITECTURE.md`** for overall architecture and technology stack guidance
-3. **Apply relevant rules** from `agents/rules/*.mdc` files based on the task
-4. **Always apply security patterns** from `agents/rules/security.mdc`
-5. **Always apply testing patterns** from `agents/rules/testing.mdc`
+1. **Reference `agent-docs/ARCHITECTURE.md`** for overall architecture and technology stack guidance
+2. **Apply relevant rules** from `agents/rules/*.mdc` files based on the task
+3. **Always apply security patterns** from `agents/rules/security.mdc`
+4. **Always apply testing patterns** from `agents/rules/testing.mdc`
 
 ## Critical Rules (Always Apply)
 
@@ -48,7 +47,7 @@ When implementing any feature:
 - **Type safety**: Use strong typing, validate at boundaries
 - **Performance**: Monitor bundle/binary size, implement lazy loading
 - **Accessibility**: WCAG 2.1 AA compliance for user-facing components
-- **Documentation**: Keep README, ARCHITECTURE.md, and AGENTS.md updated
+- **Documentation**: Keep README, agent-docs/ARCHITECTURE.md, and AGENTS.md updated
 
 ## Architecture Principles
 
@@ -61,31 +60,26 @@ When implementing any feature:
 ## Quick Reference
 
 ### For UI/Design Work
-→ Reference `AGENTS.md` → FrontendAgent section
 → Apply `agents/rules/frontend.mdc` patterns
 → Ensure accessibility compliance
 
 ### For API/Business Logic
-→ Reference `AGENTS.md` → BackendAgent section
 → Apply `agents/rules/security.mdc` for authentication/validation
 → Apply `agents/rules/testing.mdc` for test coverage
 
 ### For Database Work
-→ Reference `AGENTS.md` → DatabaseAgent section
 → Apply `agents/rules/database.mdc` patterns
 → Use ORM/ODM patterns, avoid raw queries
 
 ### For Security Reviews
-→ Reference `AGENTS.md` → SecurityAgent section
 → Apply `agents/rules/security.mdc` comprehensively
 → Check OWASP Top 10 compliance
 
 ## When in Doubt
 
-1. Check `AGENTS.md` for agent delegation guidance
-2. Review `ARCHITECTURE.md` for architecture decisions
-3. Reference the specific `agents/rules/*.mdc` file for detailed patterns
-4. Always prioritize security and testing requirements
+1. Review `agent-docs/ARCHITECTURE.md` for architecture decisions
+2. Reference the specific `agents/rules/*.mdc` file for detailed patterns
+3. Always prioritize security and testing requirements
 
 ---
 

package/templates/CLAUDE.md

@@ -4,9 +4,9 @@ This project uses enterprise-grade, technology-agnostic development patterns for
 
 ## Quick Start
 
-- **AI Guide**: See `agent-docs/AI_INSTRUCTIONS.md` for comprehensive instructions
+- **AI Guide**: See `AGENTS.md` for comprehensive instructions
 - **Architecture**: See `agent-docs/ARCHITECTURE.md` for project guidelines
-- **Agent Patterns**: See `agent-docs/AGENTS.md` for delegation patterns
+- **AI Guide**: See `AGENTS.md` for AI assistant patterns
 - **Detailed Rules**: See `agents/rules/*.mdc` files
 
 ## Always Apply
@@ -22,7 +22,7 @@ This project uses enterprise-grade, technology-agnostic development patterns for
 
 ## Agent Delegation
 
-When implementing features, follow agent patterns from `agent-docs/AGENTS.md`:
+When implementing features, reference `AGENTS.md`:
 - **UI/Design** → FrontendAgent patterns (`agents/rules/frontend.mdc`)
 - **API/Logic** → BackendAgent patterns (`agents/rules/security.mdc`)
 - **Database** → DatabaseAgent patterns (`agents/rules/database.mdc`)
@@ -41,9 +41,9 @@ When implementing features, follow agent patterns from `agent-docs/AGENTS.md`:
 
 ## Reference Files
 
-- `agent-docs/AI_INSTRUCTIONS.md` - Primary AI assistant guide
+- `AGENTS.md` - Primary AI assistant guide
 - `agent-docs/ARCHITECTURE.md` - Architecture and technology stack guidance
-- `agent-docs/AGENTS.md` - Agent responsibilities and delegation
+- `AGENTS.md` - AI assistant guide and patterns
 - `agents/rules/core.mdc` - Core principles
 - `agents/rules/security.mdc` - Security patterns (CRITICAL)
 - `agents/rules/testing.mdc` - Testing strategy (CRITICAL)

package/templates/GEMINI.md

@@ -8,9 +8,9 @@ This project uses enterprise-grade, technology-agnostic development patterns for
 
 ## Quick Start
 
-- **AI Guide**: See `agent-docs/AI_INSTRUCTIONS.md` for comprehensive instructions
+- **AI Guide**: See `AGENTS.md` for comprehensive instructions
 - **Architecture**: See `agent-docs/ARCHITECTURE.md` for project guidelines
-- **Agent Patterns**: See `agent-docs/AGENTS.md` for delegation patterns
+- **AI Guide**: See `AGENTS.md` for AI assistant patterns
 - **Detailed Rules**: See `agents/rules/*.mdc` files
 - **Available Skills**: See `agents/skills/` directory
 
@@ -100,9 +100,9 @@ These patterns apply regardless of your tech stack. Adapt them to your chosen fr
 
 | File | Purpose | When to Use |
 |------|---------|------------|
-| `agent-docs/AI_INSTRUCTIONS.md` | Primary AI assistant guide | Always start here |
+| `AGENTS.md` | Primary AI assistant guide | Always start here |
 | `agent-docs/ARCHITECTURE.md` | Architecture and technology stack decisions | Need architectural guidance |
-| `agent-docs/AGENTS.md` | Agent responsibilities and delegation | Deciding who should implement a feature |
+| `AGENTS.md` | AI assistant guide and patterns | How to work effectively with AI |
 | `agents/rules/core.mdc` | Core development principles | General development questions |
 | `agents/rules/security.mdc` | Security patterns and implementations | Building secure features |
 | `agents/rules/testing.mdc` | Testing strategy and best practices | Writing tests or test strategy |
@@ -113,9 +113,9 @@ These patterns apply regardless of your tech stack. Adapt them to your chosen fr
 
 ## Workflow Recommendations
 
-1. **Read agent-docs/AI_INSTRUCTIONS.md** for comprehensive AI assistance guidance
+1. **Read AGENTS.md** for comprehensive AI assistance guidance
 2. **Read agent-docs/ARCHITECTURE.md** to understand the overall architecture
-3. **Check agent-docs/AGENTS.md** to identify which agent should lead the implementation
+3. **Reference AGENTS.md** for AI working patterns and guidance
 3. **Reference the appropriate rule file** for implementation patterns
 4. **Look in agents/skills/** for domain-specific guidance
 5. **Follow all critical rules** without exception
@@ -130,4 +130,4 @@ These patterns apply regardless of your tech stack. Adapt them to your chosen fr
 
 ---
 
-For best results with Gemini AI assistance, reference the appropriate rules files and provide the relevant context from `agent-docs/AI_INSTRUCTIONS.md`, `agent-docs/ARCHITECTURE.md`, and `agent-docs/AGENTS.md` in your prompts.
+For best results with Gemini AI assistance, reference the appropriate context from `AGENTS.md`, `agent-docs/ARCHITECTURE.md`, and the relevant `agents/rules/*.mdc` files in your prompts.

package/templates/README.md

@@ -116,7 +116,7 @@ When you run `agents-templated init`, you get:
 ```
 your-project/
 ├── agent-docs/                      # 📚 Comprehensive documentation
-│   ├── AI_INSTRUCTIONS.md          # Primary AI assistant guide
+│   ├── AGENTS.md                   # AI assistant guide
 │   ├── ARCHITECTURE.md             # Project architecture & tech stack
 │   ├── AGENTS.MD                   # Agent delegation patterns
 │   └── README.md                   # Human-readable setup guide
@@ -222,9 +222,9 @@ Open your AI assistant and it will automatically load the appropriate config:
 
 ### 3. Read the Documentation
 
-- **[agent-docs/AI_INSTRUCTIONS.md](agent-docs/AI_INSTRUCTIONS.md)** – Primary AI assistant guide
+- **[AGENTS.md](AGENTS.md)** – AI assistant guide
 - **[agent-docs/ARCHITECTURE.md](agent-docs/ARCHITECTURE.md)** – Project architecture & tech stack guidance
-- **[agent-docs/AGENTS.MD](agent-docs/AGENTS.MD)** – Agent delegation patterns
+- **[AGENTS.md](AGENTS.md)** – Working with AI assistants guide
 - **[agents/rules/security.mdc](agents/rules/security.mdc)** – Security patterns (CRITICAL)
 - **[agents/rules/testing.mdc](agents/rules/testing.mdc)** – Testing strategy
 
@@ -272,7 +272,7 @@ Your AI will follow the enterprise patterns automatically!
 | **TestAgent** | Unit, integration, E2E, accessibility testing |
 | **SecurityAgent** | Input validation, authentication, OWASP compliance |
 
-**Reference**: [agent-docs/AGENTS.MD](agent-docs/AGENTS.MD)
+**Reference**: [AGENTS.md](AGENTS.md)
 
 ---
 

package/templates/agent-docs/README.md

@@ -8,7 +8,7 @@ Depending on what you installed, you may have:
 
 - **AGENTS.MD**: Agent patterns and delegation guide
 - **ARCHITECTURE.md**: Project guidelines and architecture
-- **AI_INSTRUCTIONS.md**: Instructions for AI assistants
+- **AGENTS.md**: Instructions for AI assistants
 - **agents/rules/**: Development rules and patterns (6 files)
 - **agents/skills/**: Reusable agent skills
 - **CLAUDE.md**: Claude AI configuration
@@ -41,7 +41,7 @@ agents-templated list
 
 ## Getting Started
 
-1. Review AI_INSTRUCTIONS.md for AI assistance guidance
+1. Review AGENTS.md for AI assistance guidance
 2. Review ARCHITECTURE.md for overall project guidelines
 3. Review AGENTS.MD for agent patterns
 4. Adapt the rules to your specific technology stack

package/templates/agent-docs/AGENTS.MD

@@ -1,336 +0,0 @@
-## Agents
-
-This file defines the different agents (MCP helpers) available in this **technology-agnostic development template** and when to use each one.
-
-- See `CLAUDE.md` for overall project guidelines.
-- Use this file as a quick reference for **which agent to call for which task**.
-- All agents support **security-first development** with comprehensive validation patterns.
-- Adapt the specific technologies and tools mentioned to match your chosen tech stack.
-
----
-
-### FrontendAgent (UI/UX Developer)
-
-**FrontendAgent is your frontend developer.** For all UI/design work, use this MCP. Adapt tool descriptions to your chosen frontend framework.
-
-#### When to use FrontendAgent
-
-- New visual component (popup, card, section, etc.) → `snippet_frontend` or `create_frontend`
-- Redesign/restyle of existing UI → `modify_frontend`
-- Design system implementation → follow design integration patterns
-- Component library and design system work
-- Accessibility improvements and WCAG compliance
-- Pure logic or trivial tweaks → handle directly without delegating
-
-#### Enhanced Capabilities
-
-- **Security-aware components**: Automatically includes proper input sanitization
-- **Accessibility-first**: Components include ARIA attributes and keyboard navigation
-- **Performance-optimized**: Uses framework-specific optimization patterns
-- **Type-safe**: All components include proper type definitions (TypeScript/PropTypes/etc.)
-
-#### Framework Adaptations
-
-**React/Next.js/Vue/Svelte:**
-- Component-based architecture with proper state management
-- Framework-specific image optimization and lazy loading
-- CSS-in-JS, Tailwind, or styled-components patterns
-
-**Angular:**
-- Component + service architecture
-- RxJS reactive patterns
-- Angular Material or custom design system
-
-#### Critical Rules
-
-1. If UI already exists and you need to redesign/restyle it → use `modify_frontend`, **not** `snippet_frontend`.
-2. Tasks can be mixed (logic + UI). Handle logic yourself, delegate UI to FrontendAgent.
-3. **Always include accessibility testing** patterns for new components.
-4. **Follow security patterns** from `agents/rules/security.mdc` for user inputs.
-
----
-
-### BackendAgent (API & Business Logic)
-
-#### Scope
-
-- Owns **API routes**, **business logic layers**, and **service functions**
-- **Authentication & Authorization** implementation
-- **Rate limiting** and **security middleware**
-- **Input validation** with schema validation libraries
-
-#### Enhanced Responsibilities
-
-- Implement secure API endpoints with comprehensive validation
-- Add authentication middleware and role-based access control
-- Integrate rate limiting for DoS protection
-- Create type-safe API responses and data fetching
-- Handle errors gracefully with proper logging
-- Move business logic into dedicated service functions (not in controllers/handlers)
-- Keep responses typed and consistent with shared interfaces
-
-#### Security Requirements
-
-- **Always validate input** at API boundaries using schema validation
-- **Implement rate limiting** for all public endpoints
-- **Apply OWASP Top 10** protection patterns
-- **Log security events** appropriately without exposing sensitive data
-- **Handle errors** gracefully with proper error responses
-
-#### Technology Adaptations
-
-**Node.js (Express/Fastify/Next.js API):**
-- RESTful or GraphQL API patterns
-- Middleware-based authentication and validation
-- Schema validation with Zod, Joi, or similar
-
-**Python (Django/FastAPI/Flask):**
-- Django REST Framework or FastAPI patterns
-- Pydantic models for validation
-- SQLAlchemy or Django ORM patterns
-
-**Other Stacks:**
-- Adapt patterns to your chosen backend framework
-- Maintain consistent validation, authentication, and error handling
-
----
-
-### DatabaseAgent (Data Layer & Schema Management)
-
-#### Scope
-
-- Owns **database schema, migrations, and data access patterns**
-- **Technology-agnostic**: Supports various database and ORM approaches
-
-#### Enhanced Responsibilities
-
-- **Schema Design**: Create optimized, scalable database schemas
-- **Migration Management**: Handle schema evolution safely
-- **Query Optimization**: Prevent N+1 queries and performance issues
-- **Data Access Patterns**: Implement consistent, type-safe data access
-- **Security**: Access controls, input sanitization, and audit logging
-
-#### Database Strategy Support
-
-**SQL Databases (PostgreSQL/MySQL/SQLite):**
-- Schema design with proper relationships and constraints
-- Migration strategies with version control
-- ORM integration (Prisma, TypeORM, Sequelize, SQLAlchemy, etc.)
-- Connection pooling and optimization
-
-**NoSQL Databases (MongoDB/DynamoDB/Firestore):**
-- Document schema design and validation
-- Index optimization and query patterns
-- ODM integration (Mongoose, etc.)
-
-**Cloud-Native Solutions:**
-- Supabase, Firebase, AWS RDS, Azure SQL, etc.
-- Built-in authentication and real-time features
-- Row-level security policies
-
-#### Security Requirements
-
-- **Input validation**: All database inputs must be validated
-- **Access control**: Implement proper authorization checks
-- **Injection prevention**: Use ORM/ODM-only access, avoid raw queries
-- **Audit logging**: Track important data changes
-- **Data encryption**: Handle sensitive data appropriately
-
-#### Must
-
-- **Choose one approach** and maintain consistency throughout the project
-- Never run manual destructive queries in production code
-- Always keep schema + migrations in sync
-- **Test database operations** with appropriate test patterns
-- **Document schema decisions** and migration strategies
-
----
-
-### TestAgent (Comprehensive Testing)
-
-#### Scope
-
-- Owns **complete testing strategy**: unit, integration, E2E, and accessibility testing
-- **Framework-agnostic**: Adapts to chosen testing tools and frameworks
-
-#### Enhanced Responsibilities
-
-- **Unit Testing**: Components, functions, utilities with >80% coverage
-- **Integration Testing**: API endpoints, database operations, authentication flows
-- **E2E Testing**: Critical user journeys across browsers/devices
-- **Accessibility Testing**: Automated WCAG compliance checking
-- **Performance Testing**: Load times, Core Web Vitals, and performance budgets
-- **Security Testing**: Input validation and authentication testing
-
-#### Testing Patterns
-
-- **Component/Unit Testing**: Framework-appropriate testing utilities
-- **API Testing**: Mock dependencies, test authentication and validation
-- **E2E Testing**: Page Object Model with stable selectors and user scenarios
-- **Accessibility Testing**: Automated scanning and keyboard navigation
-- **Visual Regression**: Screenshot comparison for critical UI components
-
-#### Quality Gates
-
-- **Code Coverage**: Maintain >80% coverage for business logic
-- **E2E Coverage**: All critical user flows must have E2E tests
-- **Accessibility**: All public interfaces must pass WCAG 2.1 AA standards
-- **Performance**: Meet performance thresholds for your platform
-- **Security**: Authentication and authorization flows fully tested
-
-#### Technology Adaptations
-
-**JavaScript/TypeScript:**
-- Jest, Vitest, or framework-specific test runners
-- Testing Library, Enzyme, or component testing utilities
-- Playwright, Cypress, or Selenium for E2E testing
-
-**Python:**
-- pytest, unittest with appropriate fixtures and mocking
-- Selenium or Playwright for browser testing
-
-**Other Languages:**
-- Adapt to language-specific testing frameworks
-- Maintain consistent testing patterns and quality gates
-
----
-
-### SecurityAgent (Security & Compliance)
-
-#### Scope
-
-- **Security-first development** across all application layers
-- **OWASP Top 10** protection implementation
-- **Authentication & authorization** security patterns
-- **Input validation** and **output sanitization**
-- **Security monitoring** and **audit logging**
-
-#### Responsibilities
-
-- **Input Validation**: Implement schema validation for all user inputs
-- **Authentication Security**: Secure session management and multi-factor authentication
-- **Authorization**: Role-based access control (RBAC) implementation
-- **Rate Limiting**: DoS protection with appropriate algorithms
-- **Security Headers**: CSP, HSTS, and comprehensive security header configuration
-- **Data Protection**: Encryption, sanitization, and secure data handling
-- **Audit Logging**: Security event logging without exposing sensitive data
-- **Vulnerability Assessment**: Regular security pattern reviews
-
-#### Security Patterns
-
-- **Authentication**: Multi-provider authentication with secure session management
-- **Authorization**: Middleware-based route protection with role validation
-- **Input Validation**: Schema validation at every boundary
-- **Rate Limiting**: Technology-appropriate rate limiting implementation
-- **Error Handling**: Secure error responses that don't leak sensitive information
-- **Database Security**: ORM/ODM-only access with parameterized queries
-- **File Upload Security**: Content type validation and secure storage
-
-#### Technology Adaptations
-
-**Web Applications:**
-- JWT tokens with proper expiration and refresh patterns
-- HTTPS enforcement and security headers
-- CORS configuration and CSRF protection
-
-**API Security:**
-- API key management and OAuth2/OpenID Connect
-- Request signing and payload validation
-- Rate limiting per API consumer
-
-#### Must
-
-- **Validate all inputs** with appropriate schema validation
-- **Implement rate limiting** on authentication and public endpoints
-- **Apply security headers** to all responses
-- **Log security events** appropriately
-- **Never expose sensitive data** in error messages or logs
-
----
-
-### ReviewerAgent (Code Review & Quality)
-
-#### Enhanced Scope
-
-- Reviews changes for **correctness, security, performance, and readability**
-- **Security vulnerability assessment** using OWASP guidelines
-- **Performance impact analysis** and optimization recommendations
-- **Test coverage verification** and quality assessment
-- **Accessibility compliance** checking
-- **Code quality standards** enforcement
-
-#### Security Review Focus
-
-- **Input validation**: Ensure all user inputs are properly validated
-- **Authentication flows**: Verify secure authentication implementation
-- **Authorization checks**: Validate role-based access controls
-- **Data exposure**: Check for sensitive data leaks in responses
-- **Error handling**: Ensure secure error message patterns
-- **Dependencies**: Review third-party package security
-
-#### Quality Standards
-
-- **Type Safety**: Strict typing without loose type usage
-- **Testing**: Appropriate test coverage for new functionality
-- **Performance**: Bundle/binary size impact and performance considerations
-- **Accessibility**: WCAG 2.1 AA compliance for user-facing features
-- **Security**: OWASP Top 10 protection patterns
-- **Documentation**: Clear code documentation and README updates
-
-#### Must
-
-- **Flag missing tests** for important logic and security flows
-- **Ensure security patterns** from `agents/rules/security.mdc` are followed
-- **Validate accessibility** for all user-facing components
-- **Check performance impact** of new dependencies and code changes
-- **Verify documentation** is updated for significant changes
-- **Ensure conventions** in `CLAUDE.md` are followed throughout
-
----
-
-## Design Integration Patterns
-
-These rules define how to translate design inputs into code and must be followed for design-driven development.
-
-#### Required Design-to-Code Flow
-
-1. **Analyze Design**: Extract design tokens, components, and interaction patterns
-2. **Create Design System**: Establish consistent color, typography, and spacing tokens
-3. **Component Architecture**: Break down designs into reusable components
-4. **Responsive Patterns**: Ensure designs work across device sizes
-5. **Accessibility Integration**: Include ARIA attributes and keyboard navigation
-6. **Performance Optimization**: Implement lazy loading and efficient rendering
-
-#### Implementation Rules
-
-- **Design System First**: Create consistent tokens and reusable components
-- **Accessibility by Default**: Include ARIA labels, focus management, and keyboard navigation
-- **Performance Conscious**: Optimize images, fonts, and rendering patterns
-- **Responsive Design**: Mobile-first approach with appropriate breakpoints
-- **Type Safety**: Define proper interfaces for component props and data
-- **Testing Integration**: Include visual regression and accessibility testing
-
-#### Framework-Specific Patterns
-
-**Component-Based (React/Vue/Svelte):**
-- Atomic design principles with proper component hierarchy
-- Consistent prop interfaces and state management
-- Style composition with CSS modules, styled-components, or utility classes
-
-**Template-Based (Django/Rails/PHP):**
-- Consistent partial/template structure
-- Server-side rendering with progressive enhancement
-- Asset optimization and caching strategies
-
----
-
-## Usage Guidelines
-
-1. **Start with Security**: Always consider security implications first
-2. **Choose Your Stack**: Adapt the specific technologies to your project needs
-3. **Maintain Consistency**: Once you choose patterns, apply them consistently
-4. **Test Everything**: Implement comprehensive testing at all levels
-5. **Document Decisions**: Keep architectural decisions and patterns documented
-6. **Review Regularly**: Use ReviewerAgent to maintain code quality
-
-This template provides the agent structure while remaining flexible for any technology stack you choose to implement.