agents-templated 2.2.5 → 2.2.6

package/bin/cli.js

@@ -122,7 +122,7 @@ program
             choices: [
               { name: 'All components', value: 'all' },
               { name: 'Documentation files (agent-docs/)', value: 'docs' },
-              { name: 'Agent rules (.claude/rules/*.mdc)', value: 'rules' },
+              { name: 'Agent rules (.claude/rules/*.md)', value: 'rules' },
               { name: 'Skills (.github/skills/*)', value: 'skills' },
               { name: 'AI Agent instructions (Cursor, Copilot, Claude, Generic AGENTS)', value: 'github' },
               { name: 'Agent subagents (.claude/agents/*.md)', value: 'subagents' }
@@ -383,10 +383,10 @@ program
       console.log(chalk.white('   1. Review CLAUDE.md (canonical AI policy — edit this directly)'));
       console.log(chalk.white('   2. Review agent-docs/ARCHITECTURE.md for project guidelines'));
       console.log(chalk.white('   3. AGENTS.MD and .github/copilot-instructions.md are thin pointers to CLAUDE.md'));
-      console.log(chalk.white('   4. Customize agents/rules/*.mdc for your tech stack'));
+      console.log(chalk.white('   4. Customize agents/rules/*.md for your tech stack'));
       
       console.log(chalk.cyan('\n🔒 Security Reminder:\n'));
-      console.log(chalk.white('   • Review agents/rules/security.mdc'));
+      console.log(chalk.white('   • Review agents/rules/security.md'));
       console.log(chalk.white('   • Validate all inputs with schema validation'));
       console.log(chalk.white('   • Implement rate limiting on public endpoints'));
       console.log(chalk.white('   • Never expose sensitive data in errors\n'));
@@ -403,7 +403,7 @@ program
   .action(() => {
     console.log(chalk.blue.bold('\nAvailable Components:\n'));
     console.log(chalk.yellow('docs') + '    - Documentation files (agent-docs/ directory)');
-    console.log(chalk.yellow('rules') + '   - Agent rules (.claude/rules/*.mdc)');
+    console.log(chalk.yellow('rules') + '   - Agent rules (.claude/rules/*.md)');
     console.log(chalk.yellow('skills') + '  - Agent skills (.github/skills/*)');
     console.log(chalk.yellow('github') + '  - AI Agent instructions (Cursor, Copilot, Claude, Generic AGENTS)');
     console.log(chalk.yellow('subagents') + ' - Agent subagents (.claude/agents/*.md)');
@@ -455,7 +455,7 @@ program
       }
 
       // Check agent rules
-      const ruleFiles = ['core.mdc', 'security.mdc', 'testing.mdc', 'frontend.mdc', 'database.mdc', 'style.mdc'];
+      const ruleFiles = ['core.md', 'security.md', 'testing.md', 'frontend.md', 'database.md', 'style.md'];
       const canonicalRulesDir = path.join(targetDir, LAYOUT.canonical.rulesDir);
       const legacyRulesDir = path.join(targetDir, LAYOUT.legacy.rulesDirs[0]);
       const rulesDir = path.join(targetDir, resolveRulesDir(targetDir));
@@ -829,9 +829,9 @@ program
       const checkFiles = [
         { targetFile: CANONICAL_INSTRUCTION_FILE, templateFile: CANONICAL_INSTRUCTION_FILE, component: 'root' },
         { targetFile: 'agent-docs/ARCHITECTURE.md', templateFile: 'agent-docs/ARCHITECTURE.md', component: 'docs' },
-        { targetFile: `${LAYOUT.canonical.rulesDir}/security.mdc`, templateFile: 'agents/rules/security.mdc', component: 'rules' },
-        { targetFile: `${LAYOUT.canonical.rulesDir}/testing.mdc`, templateFile: 'agents/rules/testing.mdc', component: 'rules' },
-        { targetFile: `${LAYOUT.canonical.rulesDir}/core.mdc`, templateFile: 'agents/rules/core.mdc', component: 'rules' },
+        { targetFile: `${LAYOUT.canonical.rulesDir}/security.md`, templateFile: 'agents/rules/security.md', component: 'rules' },
+        { targetFile: `${LAYOUT.canonical.rulesDir}/testing.md`, templateFile: 'agents/rules/testing.md', component: 'rules' },
+        { targetFile: `${LAYOUT.canonical.rulesDir}/core.md`, templateFile: 'agents/rules/core.md', component: 'rules' },
         { targetFile: `${LAYOUT.canonical.skillsDir}/README.md`, templateFile: 'agents/skills/README.md', component: 'skills' },
         { targetFile: `${LAYOUT.canonical.skillsDir}/find-skills/SKILL.md`, templateFile: 'agents/skills/find-skills/SKILL.md', component: 'skills' },
         { targetFile: `${LAYOUT.canonical.skillsDir}/ui-ux-pro-max/SKILL.md`, templateFile: 'agents/skills/ui-ux-pro-max/SKILL.md', component: 'skills' }
@@ -989,7 +989,7 @@ program
       console.log(chalk.blue('\n📚 Quick Tips:\n'));
       console.log(chalk.white('  • Run "agents-templated validate" to check setup'));
       console.log(chalk.white('  • Run "agents-templated wizard" for guided setup'));
-      console.log(chalk.white('  • Review agents/rules/security.mdc for security patterns\n'));
+      console.log(chalk.white('  • Review agents/rules/security.md for security patterns\n'));
 
     } catch (error) {
       console.error(chalk.red('Error:'), error.message);
@@ -1015,7 +1015,7 @@ program
 
 program
   .command('new-rule <name>')
-  .description('Scaffold a new rule in agents/rules/<name>.mdc')
+  .description('Scaffold a new rule in agents/rules/<name>.md')
   .action(async (name) => {
     try {
       const targetDir = process.cwd();

package/lib/instructions.js

@@ -137,10 +137,10 @@ async function scaffoldSkill(targetDir, skillName) {
 
 async function scaffoldRule(targetDir, ruleName) {
   const rulesDir = path.join(targetDir, 'agents', 'rules');
-  const ruleFile = path.join(rulesDir, `${ruleName}.mdc`);
+  const ruleFile = path.join(rulesDir, `${ruleName}.md`);
 
   if (await fs.pathExists(ruleFile)) {
-    throw new Error(`Rule already exists: agents/rules/${ruleName}.mdc`);
+    throw new Error(`Rule already exists: agents/rules/${ruleName}.md`);
   }
 
   const content = [
@@ -168,7 +168,7 @@ async function scaffoldRule(targetDir, ruleName) {
 
   await fs.ensureDir(rulesDir);
   await fs.writeFile(ruleFile, content, 'utf8');
-  return `agents/rules/${ruleName}.mdc`;
+  return `agents/rules/${ruleName}.md`;
 }
 
 async function scaffoldSubagent(targetDir, name) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agents-templated",
-  "version": "2.2.5",
+  "version": "2.2.6",
   "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/.claude/rules/{ai-integration.mdc → ai-integration.md}

@@ -5,12 +5,6 @@ version: "1.0.0"
 tags: ["ai", "llm", "openai", "anthropic", "rag", "prompt-engineering", "safety"]
 alwaysApply: false
 globs: ["**/*llm*", "**/*openai*", "**/*anthropic*", "**/*langchain*", "**/*rag*", "**/ai/**"]
-triggers:
-  - "Integrating OpenAI, Claude, or other LLM APIs"
-  - "Building RAG (Retrieval-Augmented Generation) pipeline"
-  - "Engineering prompts or prompt chains"
-  - "Implementing LLM-powered features"
-  - "Evaluating LLM outputs or quality"
 ---
 
 ## Purpose

package/templates/.claude/rules/{core.mdc → core.md}

@@ -6,13 +6,6 @@ version: "3.0.0"
 tags: ["architecture", "core", "enterprise", "technology-agnostic"]
 globs:
   - "*"
-triggers:
-  - "Designing application architecture"
-  - "Setting up new project or module"
-  - "Defining type systems and validation"
-  - "Organizing code structure"
-  - "Improving code quality standards"
-  - "Making testing or performance decisions"
 ---
 
 ## Developer Identity

package/templates/.claude/rules/{database.mdc → database.md}

@@ -7,13 +7,6 @@ tags: ["database", "backend", "data", "orm", "schema"]
 globs:
   - "src/models/**/*"
   - "src/data/**/*"
-triggers:
-  - "Designing database schema or tables"
-  - "Creating/updating ORM models or queries"
-  - "Running database migrations"
-  - "Optimizing slow queries"
-  - "Selecting database technology"
-  - "Implementing access control for data"
 ---
 
 # Database and Data Layer Guidelines

package/templates/.claude/rules/{frontend.mdc → frontend.md}

@@ -8,13 +8,6 @@ globs:
   - "src/**/*"
   - "components/**/*"
   - "public/**/*"
-triggers:
-  - "Building user interfaces or components"
-  - "Designing responsive layouts"
-  - "Creating forms and validations"
-  - "Implementing accessibility features"
-  - "Working on user-facing features"
-  - "Optimizing performance for frontend"
 ---
 
 # Frontend Development Guidelines

package/templates/.claude/rules/{guardrails.mdc → guardrails.md}

@@ -4,14 +4,6 @@ title: "AI Agent Guardrails"
 description: "Enforce hard behavioral limits on all agents. Apply when any destructive, irreversible, or dangerous action is requested"
 version: "1.0.0"
 tags: ["guardrails", "safety", "scope", "reversibility", "agent-behavior"]
-triggers:
-  - "User requests file/folder/branch deletion"
-  - "Force pushing or hard-resetting git history"
-  - "Deploying to production"
-  - "Dropping database tables"
-  - "Disabling tests to make build pass"
-  - "Bypassing security controls"
-  - "Any action that cannot be easily undone"
 ---
 
 ## Purpose

package/templates/.claude/rules/{hardening.mdc → hardening.md}

@@ -3,12 +3,6 @@ title: "Application Hardening & Obfuscation"
 description: "Apply when building client-distributed apps, protecting IP logic, or preparing releases with anti-tamper requirements"
 version: "1.0.0"
 tags: ["hardening", "obfuscation", "anti-tamper", "security"]
-triggers:
-  - "Building mobile or desktop app for distribution"
-  - "Protecting high-value or proprietary logic"
-  - "Increasing tamper detection or anti-hooking"
-  - "Preparing production release with security concerns"
-  - "Performance and integrity validation needed"
 ---
 
 ## Purpose

package/templates/.claude/rules/{intent-routing.mdc → intent-routing.md}

@@ -3,11 +3,6 @@ title: "Intent Routing & Command Selection"
 description: "Apply when determining which rule or workflow applies to the user's request. Ensures correct execution pathway"
 version: "1.0.0"
 tags: ["routing", "deterministic", "workflow", "commands"]
-triggers:
-  - "Ambiguous or multi-intent user request"
-  - "Need to route to correct rule or workflow"
-  - "Destructive action requested"
-  - "Scope expansion detected"
 ---
 
 ## Purpose

package/templates/.claude/rules/{planning.mdc → planning.md}

@@ -4,12 +4,6 @@ description: "Apply when implementing features, designing systems, or making arc
 version: "1.0.0"
 tags: ["planning", "workflow", "documentation", "prompts"]
 alwaysApply: true
-triggers:
-  - "User asks to implement a new feature"
-  - "Making design or architecture decisions"
-  - "Planning a significant refactor"
-  - "Fixing bugs that require investigation"
-  - "Discussion produces decisions affecting architecture"
 ---
 
 ## Purpose

package/templates/.claude/rules/{security.mdc → security.md}

@@ -4,14 +4,6 @@ description: "Apply when implementing authentication, authorization, API validat
 alwaysApply: true
 version: "3.0.0"
 tags: ["security", "auth", "validation", "secrets", "owasp"]
-triggers:
-  - "User adds login/authentication to project"
-  - "Building API endpoints or handling user input"
-  - "Storing passwords, tokens, or sensitive data"
-  - "Validating form inputs or API requests"
-  - "Protecting against injection, XSS, CSRF"
-  - "Adding authorization/permissions to endpoints"
-  - "Integrating third-party APIs or external services"
 ---
 
 # Security Rules & Best Practices

package/templates/.claude/rules/{style.mdc → style.md}

@@ -6,12 +6,6 @@ version: "3.0.0"
 tags: ["style", "formatting", "naming", "quality"]
 globs:
   - "**/*"
-triggers:
-  - "Writing or reviewing code"
-  - "Setting up code formatting rules"
-  - "Naming variables, functions, or files"
-  - "Organizing module structure"
-  - "Refactoring or improving readability"
 ---
 
 # Code Style and Standards

package/templates/.claude/rules/{system-workflow.mdc → system-workflow.md}

@@ -3,12 +3,6 @@ title: "System Workflow Orchestration"
 description: "Apply when planning work phases, defining acceptance criteria, or establishing delivery gates and rollback strategies"
 version: "1.0.0"
 tags: ["workflow", "gates", "delivery", "governance"]
-triggers:
-  - "Starting a new feature or major change"
-  - "Planning implementation phases"
-  - "Defining acceptance criteria"
-  - "Establishing rollback procedures"
-  - "Preparing for release or deployment"
 ---
 
 ## Purpose

package/templates/.claude/rules/{testing.mdc → testing.md}

@@ -3,14 +3,6 @@ title: "Testing Guidelines & Best Practices"
 description: "Apply when adding tests, verifying coverage, or validating quality before deployment. Always required for business logic and critical flows"
 version: "3.0.0"
 tags: ["testing", "quality", "coverage", "e2e", "a11y"]
-triggers:
-  - "User requests tests for business logic"
-  - "Implementing a new feature"
-  - "Fixing a bug"
-  - "Need to verify API endpoints work"
-  - "Checking application behavior"
-  - "Hardening release artifacts"
-  - "CI/CD validation needed before deployment"
 ---
 
 # Testing Guidelines & Best Practices

package/templates/.claude/rules/{workflows.mdc → workflows.md}

@@ -6,11 +6,6 @@ version: "1.0.0"
 tags: ["workflow", "quality", "validation", "commit"]
 globs:
   - "**/*"
-triggers:
-  - "User asks about workflow or pre-commit steps"
-  - "Need to keep project validated"
-  - "Running quality gates before merge"
-  - "Post-hardening verification needed"
 ---
 
 # Development Workflow Guidelines

package/templates/CLAUDE.md

@@ -11,19 +11,19 @@ All policy, routing, and skill governance lives here — edit this file directly
 
 | Module | File | Apply when... |
 |--------|------|---------------|
-| Security | `.claude/rules/security.mdc` | Implementing authentication, validating inputs, protecting against injection attacks |
-| Testing | `.claude/rules/testing.mdc` | Adding tests, verifying coverage, validating quality before deployment |
-| Core | `.claude/rules/core.mdc` | Designing architecture, setting up projects, defining type systems |
-| Database | `.claude/rules/database.mdc` | Designing schema, building data access layers, optimizing queries |
-| Frontend | `.claude/rules/frontend.mdc` | Building UI components, designing pages, creating forms, implementing accessibility |
-| Style | `.claude/rules/style.mdc` | Organizing code, naming variables, improving clarity and maintainability |
-| System Workflow | `.claude/rules/system-workflow.mdc` | Planning delivery phases, defining acceptance criteria, establishing rollback |
-| Workflows | `.claude/rules/workflows.mdc` | Optimizing development process, running pre-commit checks, keeping project healthy |
-| Hardening | `.claude/rules/hardening.mdc` | Building distributed apps, protecting IP logic, preparing production releases |
-| Intent Routing | `.claude/rules/intent-routing.mdc` | Determining which rule applies, routing to correct execution pathway |
-| Planning | `.claude/rules/planning.mdc` | Implementing features, designing systems, making architectural decisions |
-| AI Integration | `.claude/rules/ai-integration.mdc` | Integrating LLMs, RAG pipelines, prompt engineering, AI-powered features |
-| Guardrails | `.claude/rules/guardrails.mdc` | Any destructive/irreversible action, scope expansion, dangerous requests |
+| Security | `.claude/rules/security.md` | Implementing authentication, validating inputs, protecting against injection attacks |
+| Testing | `.claude/rules/testing.md` | Adding tests, verifying coverage, validating quality before deployment |
+| Core | `.claude/rules/core.md` | Designing architecture, setting up projects, defining type systems |
+| Database | `.claude/rules/database.md` | Designing schema, building data access layers, optimizing queries |
+| Frontend | `.claude/rules/frontend.md` | Building UI components, designing pages, creating forms, implementing accessibility |
+| Style | `.claude/rules/style.md` | Organizing code, naming variables, improving clarity and maintainability |
+| System Workflow | `.claude/rules/system-workflow.md` | Planning delivery phases, defining acceptance criteria, establishing rollback |
+| Workflows | `.claude/rules/workflows.md` | Optimizing development process, running pre-commit checks, keeping project healthy |
+| Hardening | `.claude/rules/hardening.md` | Building distributed apps, protecting IP logic, preparing production releases |
+| Intent Routing | `.claude/rules/intent-routing.md` | Determining which rule applies, routing to correct execution pathway |
+| Planning | `.claude/rules/planning.md` | Implementing features, designing systems, making architectural decisions |
+| AI Integration | `.claude/rules/ai-integration.md` | Integrating LLMs, RAG pipelines, prompt engineering, AI-powered features |
+| Guardrails | `.claude/rules/guardrails.md` | Any destructive/irreversible action, scope expansion, dangerous requests |
 
 ### Skill modules (`.github/skills/`)
 
@@ -59,40 +59,40 @@ Subagents are bounded agents with limited tool access. They inherit all policy f
 
 ## Always Enforce
 
-1. **Security-first (non-overrideable)** — `.claude/rules/security.mdc`
+1. **Security-first (non-overrideable)** — `.claude/rules/security.md`
    - Validate all external inputs at boundaries.
    - Require authentication and role-based authorization for protected operations.
    - Rate-limit public APIs.
    - Never expose secrets, credentials, or PII in logs/errors/responses.
 
-2. **Testing discipline (non-overrideable)** — `.claude/rules/testing.mdc`
+2. **Testing discipline (non-overrideable)** — `.claude/rules/testing.md`
    - Coverage mix target: Unit 80% / Integration 15% / E2E 5%.
    - Business logic must have tests; critical flows need integration coverage.
    - Never disable/remove tests to pass builds.
 
-3. **Type safety and runtime boundaries** — `.claude/rules/core.mdc`
+3. **Type safety and runtime boundaries** — `.claude/rules/core.md`
    - Strong internal typing, runtime validation at boundaries, explicit error models.
 
-4. **Database integrity** — `.claude/rules/database.mdc`
+4. **Database integrity** — `.claude/rules/database.md`
    - Prefer ORM/ODM, justify raw queries, enforce DB constraints, prevent N+1, reversible migrations.
 
-5. **Frontend standards** — `.claude/rules/frontend.mdc`
+5. **Frontend standards** — `.claude/rules/frontend.md`
    - WCAG 2.1 AA, responsive defaults, clear loading/error states, no unsafe client trust.
 
-6. **Style and consistency** — `.claude/rules/style.mdc`
+6. **Style and consistency** — `.claude/rules/style.md`
    - Consistent naming, small composable modules, explicit contracts, no magic values.
 
-7. **Workflow discipline** — `.claude/rules/system-workflow.mdc`, `.claude/rules/workflows.mdc`
+7. **Workflow discipline** — `.claude/rules/system-workflow.md`, `.claude/rules/workflows.md`
    - Feature branches only, no direct main edits, deterministic PR structure, review gates.
 
-8. **Hardening mode** — `.claude/rules/hardening.mdc`
+8. **Hardening mode** — `.claude/rules/hardening.md`
    - In hardening/audit contexts: assume hostile input, threat-model, validate config safety, strict rate limits, dependency audit.
 
-9. **Planning discipline** — `.claude/rules/planning.mdc`
+9. **Planning discipline** — `.claude/rules/planning.md`
    - Every feature discussion or implementation produces a `.github/prompts/` plan file.
    - Plans are updated as work progresses, not discarded.
 
-10. **Guardrails (non-overrideable)** — `.claude/rules/guardrails.mdc`
+10. **Guardrails (non-overrideable)** — `.claude/rules/guardrails.md`
    - Require `CONFIRM-DESTRUCTIVE:<target>` token before any destructive/irreversible action.
    - Work only within the defined task scope; no silent expansion.
    - Classify every action by reversibility before executing.
@@ -106,7 +106,7 @@ All items above are policy-level requirements; skills and command modes cannot w
 
 ## Intent Routing
 
-Use `.github/instructions/rules/intent-routing.mdc` and route each task to one primary module:
+Use `.claude/rules/intent-routing.md` and route each task to one primary module:
 
 - UI/Design → Frontend
 - API/Logic → Security + Core

package/templates/agents/rules/{ai-integration.mdc → ai-integration.md}

@@ -5,14 +5,6 @@ version: "3.0.0"
 tags: ["ai", "llm", "openai", "anthropic", "rag", "prompt-engineering", "safety"]
 alwaysApply: false
 globs: ["**/*llm*", "**/*openai*", "**/*anthropic*", "**/*langchain*", "**/*rag*", "**/ai/**"]
-triggers:
-  - "Integrating OpenAI or other LLM API"
-  - "Building RAG pipeline or semantic search"
-  - "Implementing prompt template or engineering"
-  - "Adding AI-powered feature to application"
-  - "Evaluating LLM responses or quality"
-  - "Optimizing LLM API costs"
-  - "Implementing AI moderation or safety controls"
 ---
 
 ## Purpose

package/templates/agents/rules/{core.mdc → core.md}

@@ -6,13 +6,6 @@ version: "3.0.0"
 tags: ["architecture", "core", "enterprise", "technology-agnostic"]
 globs:
   - "*"
-triggers:
-  - "Designing application architecture"
-  - "Setting up new project or module"
-  - "Defining type systems and validation"
-  - "Organizing code structure"
-  - "Improving code quality standards"
-  - "Making testing or performance decisions"
 ---
 
 ## Developer Identity

package/templates/agents/rules/{database.mdc → database.md}

@@ -1,4 +1,4 @@
----
+---
 title: "Database and Data Layer Guidelines"
 description: "Apply when designing schema, building data access layers, optimizing queries, or managing database operations"
 alwaysApply: true
@@ -7,14 +7,6 @@ tags: ["database", "backend", "data", "orm", "schema"]
 globs:
   - "src/models/**/*"
   - "src/data/**/*"
-triggers:
-  - "Designing database schema"
-  - "Adding database migrations"
-  - "Building data access layer"
-  - "Querying or filtering data"
-  - "Optimizing slow queries"
-  - "Managing relationships between entities"
-  - "Handling data validation in models"
 ---
 
 # Database and Data Layer Guidelines

package/templates/agents/rules/{frontend.mdc → frontend.md}

@@ -1,4 +1,4 @@
----
+---
 title: "Frontend Development Guidelines"
 description: "Apply when building UI components, designing pages, creating forms, or implementing accessibility and responsive interfaces"
 alwaysApply: true
@@ -8,14 +8,6 @@ globs:
   - "src/**/*"
   - "components/**/*"
   - "public/**/*"
-triggers:
-  - "Building UI components or pages"
-  - "Creating forms and handling user input"
-  - "Designing responsive layouts"
-  - "Implementing accessibility features"
-  - "Styling and theming interfaces"
-  - "Building navigation and routing"
-  - "Implementing client-side state management"
 ---
 
 # Frontend Development Guidelines

package/templates/agents/rules/{guardrails.mdc → guardrails.md}

@@ -4,14 +4,6 @@ title: "AI Agent Guardrails"
 description: "Apply before any irreversible action, scope expansion, dangerous request, or system change. Safety constraints that cannot be weakened"
 version: "3.0.0"
 tags: ["guardrails", "safety", "scope", "reversibility", "agent-behavior"]
-triggers:
-  - "Planning destructive or irreversible action"
-  - "Deleting files, databases, or deployment"
-  - "Modifying security or authentication"
-  - "Making scope expansion decisions"
-  - "Evaluating request safety and reversibility"
-  - "Handling secrets or sensitive data"
-  - "Making agent behavioral decisions"
 ---
 
 ## Purpose

package/templates/agents/rules/{hardening.mdc → hardening.md}

@@ -3,14 +3,6 @@ title: "Application Hardening & Obfuscation"
 description: "Apply when building distributed apps, protecting IP logic, preparing production releases, or hardening against reverse engineering"
 version: "3.0.0"
 tags: ["hardening", "obfuscation", "anti-tamper", "security"]
-triggers:
-  - "Preparing mobile or desktop app for release"
-  - "Protecting proprietary business logic"
-  - "Hardening against reverse engineering"
-  - "Building distributed client applications"
-  - "Preparing production release with hardening"
-  - "Implementing tamper detection"
-  - "Adding integrity checks to release"
 ---
 
 ## Purpose

package/templates/agents/rules/{intent-routing.mdc → intent-routing.md}

@@ -3,14 +3,6 @@ title: "Intent Routing & Command Selection"
 description: "Apply when determining which rule applies, routing to correct execution pathway, or making command selection decisions"
 version: "3.0.0"
 tags: ["routing", "deterministic", "workflow", "commands"]
-triggers:
-  - "User makes natural language request"
-  - "Determining which rule applies"
-  - "Routing to correct execution pathway"
-  - "Selecting command or agent to invoke"
-  - "Handling ambiguous user intent"
-  - "Making safety behavior decisions"
-  - "Validating action scope and appropriateness"
 ---
 
 ## Purpose

package/templates/agents/rules/{planning.mdc → planning.md}

@@ -4,14 +4,6 @@ description: "Apply when implementing features, designing systems, discussing ar
 version: "3.0.0"
 tags: ["planning", "workflow", "documentation", "prompts"]
 alwaysApply: true
-triggers:
-  - "User requests a new feature"
-  - "Planning implementation approach"
-  - "Discussing architectural changes"
-  - "Breaking down user stories"
-  - "Creating acceptance criteria"
-  - "Designing database schema"
-  - "Planning deployment phases"
 ---
 
 ## Purpose

package/templates/agents/rules/{security.mdc → security.md}

@@ -1,17 +1,9 @@
----
+---
 title: "Security Rules & Best Practices"
 description: "Apply when implementing authentication, authorization, API validation, secrets management, or protecting against OWASP Top 10 vulnerabilities"
 alwaysApply: true
 version: "3.0.0"
 tags: ["security", "auth", "validation", "secrets", "owasp"]
-triggers:
-  - "User adds login/authentication to project"
-  - "Building API endpoints or handling user input"
-  - "Storing passwords, tokens, or sensitive data"
-  - "Validating form inputs or API requests"
-  - "Protecting against injection, XSS, CSRF"
-  - "Adding authorization/permissions to endpoints"
-  - "Integrating third-party APIs or external services"
 ---
 
 # Security Rules & Best Practices

package/templates/agents/rules/{style.mdc → style.md}

@@ -1,4 +1,4 @@
----
+---
 title: "Code Style and Standards"
 description: "Apply when organizing code, naming variables/functions, improving clarity, formatting with consistency, and maintaining code quality"
 alwaysApply: true
@@ -6,14 +6,6 @@ version: "3.0.0"
 tags: ["style", "formatting", "naming", "quality"]
 globs:
   - "**/*"
-triggers:
-  - "Writing new code or functions"
-  - "Organizing code structure"
-  - "Naming variables, functions, or classes"
-  - "Formatting code for readability"
-  - "Improving code documentation"
-  - "Refactoring for clarity"
-  - "Following project conventions"
 ---
 
 # Code Style and Standards

package/templates/agents/rules/{system-workflow.mdc → system-workflow.md}

@@ -3,14 +3,6 @@ title: "System Workflow Orchestration"
 description: "Apply when planning delivery phases, defining acceptance criteria, establishing rollback procedures, or orchestrating multi-step workflows"
 version: "3.0.0"
 tags: ["workflow", "gates", "delivery", "governance"]
-triggers:
-  - "Implementing feature with multiple phases"
-  - "Defining deployment gates and approval"
-  - "Planning rollback strategy"
-  - "Creating acceptance criteria"
-  - "Coordinating deployment across services"
-  - "Planning database migration"
-  - "Managing breaking API changes"
 ---
 
 ## Purpose

package/templates/agents/rules/{testing.mdc → testing.md}

@@ -1,16 +1,8 @@
----
+---
 title: "Testing Guidelines & Best Practices"
 description: "Apply when adding tests, verifying coverage, or validating quality before deployment. Always required for business logic and critical flows"
 version: "3.0.0"
 tags: ["testing", "quality", "coverage", "e2e", "a11y"]
-triggers:
-  - "User requests tests for business logic"
-  - "Implementing a new feature"
-  - "Fixing a bug"
-  - "Need to verify API endpoints work"
-  - "Checking application behavior"
-  - "Hardening release artifacts"
-  - "CI/CD validation needed before deployment"
 ---
 
 # Testing Guidelines & Best Practices

package/templates/agents/rules/{workflows.mdc → workflows.md}

@@ -6,14 +6,6 @@ version: "3.0.0"
 tags: ["workflow", "quality", "validation", "commit"]
 globs:
   - "**/*"
-triggers:
-  - "Running pre-commit hooks"
-  - "Validating code quality gates"
-  - "Setting up CI/CD pipeline"
-  - "Checking code before commit"
-  - "Running linting or formatting"
-  - "Executing test suites automatically"
-  - "Maintaining project health and standards"
 ---
 
 # Development Workflow Guidelines