agents-templated 2.2.1 → 2.2.2

package/templates/agents/rules/style.mdc

@@ -1,11 +1,19 @@
 ---
 title: "Code Style and Standards"
-description: "Language-agnostic naming conventions, formatting rules, and code quality standards"
+description: "Apply when organizing code, naming variables/functions, improving clarity, formatting with consistency, and maintaining code quality"
 alwaysApply: true
 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
@@ -341,4 +349,4 @@ Test names describe what is being tested:
 ---
 
 Remember: **Write code for humans first, computers second.**
-Clean code is maintainable code, and maintainable code is more secure, performant, and bug-free.
+Clean code is maintainable code, and maintainable code is more secure, performant, and bug-free.

package/templates/agents/rules/system-workflow.mdc

@@ -1,8 +1,16 @@
 ---
 title: "System Workflow Orchestration"
-description: "Lifecycle gates and required artifacts for systematic delivery"
-version: "1.0.0"
+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

@@ -1,8 +1,16 @@
 ---
 title: "Testing Guidelines & Best Practices"
-description: "Framework and language-agnostic testing strategy for enterprise applications"
+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

@@ -1,11 +1,19 @@
 ---
 title: "Development Workflow Guidelines"
-description: "Optional development workflow: project health checks and pre-commit quality gates"
+description: "Apply to optimize development process, running pre-commit checks, enforcing quality gates, and keeping project healthy"
 alwaysApply: false
-version: "1.0.0"
+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