@nockdev/awf 6.2.0

package/.agent/rules/modules/quality.yaml

@@ -0,0 +1,185 @@
+# Quality Rule v6.0
+# Modular rule for code quality standards
+
+---
+name: quality
+version: "6.1.2"
+rule_id: "MOD-QLT-001"
+
+# =============================================================================
+# RULE METADATA
+# =============================================================================
+
+description: |
+  Code quality standards and best practices for all generated code.
+
+category: "quality"
+
+# =============================================================================
+# CONTEXT APPLICATION
+# =============================================================================
+
+context:
+  always_apply: true
+  personas: ["developer", "debugger", "tester", "auditor"]
+  workflows: ["/code", "/refactor", "/review"]
+
+# =============================================================================
+# CODE QUALITY PRINCIPLES
+# =============================================================================
+
+principles:
+  naming:
+    description: "Use clear, descriptive names"
+    rules:
+      - "Variables describe content (userEmail, not e)"
+      - "Functions describe action (validateUser, not check)"
+      - "Constants in UPPER_SNAKE_CASE"
+      - "Classes in PascalCase"
+
+  error_handling:
+    description: "Always handle errors properly"
+    rules:
+      - "Never swallow errors silently"
+      - "Provide meaningful error messages"
+      - "Log errors with context"
+      - "Use appropriate error types"
+
+  type_safety:
+    description: "Use types effectively"
+    rules:
+      - "Avoid 'any' type without reason"
+      - "Define proper interfaces"
+      - "Use generics where appropriate"
+      - "Document complex types"
+
+  documentation:
+    description: "Document the 'why', not the 'what'"
+    rules:
+      - "Comment on non-obvious logic"
+      - "Explain business rules"
+      - "Skip obvious comments"
+      - "Keep comments updated"
+
+  dry_principle:
+    description: "Don't Repeat Yourself"
+    rules:
+      - "Extract repeated logic"
+      - "Use shared utilities"
+      - "Avoid copy-paste code"
+      - "Create reusable components"
+
+# =============================================================================
+# FUNCTION GUIDELINES
+# =============================================================================
+
+functions:
+  size_limits:
+    max_lines: 50
+    max_parameters: 4
+    max_nesting: 3
+
+  rules:
+    - "Single responsibility principle"
+    - "Pure functions where possible"
+    - "Early returns for guard clauses"
+    - "Avoid side effects"
+
+# =============================================================================
+# ANTI-PATTERNS
+# =============================================================================
+
+anti_patterns:
+  never_do:
+    - pattern: "Magic numbers/strings"
+      fix: "Use named constants"
+    - pattern: "Catch-all error handling"
+      fix: "Handle specific errors"
+    - pattern: "Overly clever one-liners"
+      fix: "Readable multi-line code"
+    - pattern: "Deep nesting (>3 levels)"
+      fix: "Early returns or extraction"
+    - pattern: "God functions (>50 lines)"
+      fix: "Break into smaller functions"
+    - pattern: "Hardcoded secrets"
+      fix: "Use environment variables"
+
+# =============================================================================
+# SECURITY DEFAULTS
+# =============================================================================
+
+security_defaults:
+  input_validation:
+    - "Validate all user input"
+    - "Sanitize before use"
+    - "Type coercion checks"
+
+  output_encoding:
+    - "Context-aware encoding"
+    - "XSS prevention"
+    - "SQL parameterization"
+
+  error_handling:
+    - "Non-revealing errors"
+    - "Structured logging"
+    - "No stack traces in prod"
+
+  secrets:
+    - "Environment variables only"
+    - "No hardcoded secrets"
+    - "Rotation support"
+
+# =============================================================================
+# TESTING REQUIREMENTS
+# =============================================================================
+
+testing:
+  minimum_coverage: 80
+  required_test_types:
+    - unit: "All public functions"
+    - integration: "API endpoints"
+    - edge_cases: "Boundary conditions"
+
+  test_quality:
+    - "Meaningful test names"
+    - "Arrange-Act-Assert pattern"
+    - "One assertion per test (preferable)"
+    - "No test interdependencies"
+
+# =============================================================================
+# CHECKLIST
+# =============================================================================
+
+checklist:
+  - "Clear naming?"
+  - "Error handling complete?"
+  - "Types defined?"
+  - "No anti-patterns?"
+  - "Security considered?"
+  - "Tests added?"
+
+# =============================================================================
+# INTEGRATION
+# =============================================================================
+
+integration:
+  tier: 2 # Execution tier
+  related_modules:
+    - edit-verification
+    - evidence
+
+  hsa_tools:
+    hsa_search_patterns:
+      purpose: "Retrieve language-specific best practices and anti-patterns"
+      usage: "hsa_search_patterns query=[pattern] domain=[lang] → quality guidance from 730+ patterns"
+    hsa_detect_stack:
+      purpose: "Auto-detect correct lint/format tools for quality gates"
+      usage: "hsa_detect_stack → determines lint_check, format_check commands"
+
+  reflection:
+    enabled: true
+    check_before: "output"
+    question: "Does this code meet quality standards?"
+
+---
+_DOMYH Awesome Code • Quality Rule_

package/.agent/rules/modules/reflection.yaml

@@ -0,0 +1,209 @@
+# 🔧 Modular Rule: Reflection Integration
+
+> Self-improvement through reflection patterns
+> Version: 6.1.2
+
+---
+
+## Overview
+
+This modular rule integrates reflection capabilities into the agent's workflow,
+enabling learning from both successes and failures.
+
+---
+
+## Configuration
+
+```yaml
+name: reflection
+version: "6.1.2"
+category: improvement
+priority: 2
+
+# Dependencies
+dependencies:
+  requires:
+    - evidence  # Need evidence to reflect on
+  enhances:
+    - quality
+    - context-management
+  conflicts_with: []
+
+# Applicability
+context:
+  always_apply: false  # Activated on triggers
+  personas: ["*"]
+  workflows: ["*"]
+```
+
+---
+
+## Reflection Triggers
+
+```yaml
+triggers:
+  # Automatic reflection
+  auto:
+    on_error:
+      condition: "user_correction OR task_failure"
+      action: "analyze_error"
+      template: "templates/reflection/error_analysis.md"
+      
+    on_success:
+      condition: "user_satisfaction OR task_complete"
+      action: "analyze_success"
+      template: "templates/reflection/success_analysis.md"
+      
+    on_uncertainty:
+      condition: "confidence < 70%"
+      action: "self_critique"
+      template: "templates/reflection/critic.md"
+
+  # Manual reflection
+  manual:
+    command: "/reflect"
+    action: "full_reflection_cycle"
+```
+
+---
+
+## Reflection Process
+
+```yaml
+process:
+  pre_output:
+    name: "Self-Critique"
+    when: "Before delivering significant output"
+    template: "templates/reflection/critic.md"
+    questions:
+      - "Does this address the user's actual request?"
+      - "Is the information accurate and verified?"
+      - "Are there missing edge cases?"
+      - "Could this cause unintended consequences?"
+    action_on_fail: "revise_before_output"
+
+  post_error:
+    name: "Error Analysis"
+    when: "User corrects or task fails"
+    template: "templates/reflection/error_analysis.md"
+    steps:
+      1_identify: "What specifically went wrong?"
+      2_cause: "Why did it happen? (5 Whys)"
+      3_classify: "What type of error?"
+      4_learn: "What pattern to avoid?"
+      5_store: "Save to patterns/errors.json"
+
+  post_success:
+    name: "Success Reinforcement"
+    when: "User satisfied or task succeeds"
+    template: "templates/reflection/success_analysis.md"
+    steps:
+      1_identify: "What worked well?"
+      2_extract: "What pattern to replicate?"
+      3_generalize: "How to apply elsewhere?"
+      4_store: "Save to patterns/successes.json"
+```
+
+---
+
+## Pattern Storage
+
+```yaml
+storage:
+  errors:
+    file: "patterns/errors.json"
+    schema:
+      id: "ERR-XXX"
+      name: "descriptive_name"
+      trigger: "What situation triggers this"
+      wrong_action: "What was done incorrectly"
+      correct_action: "What should be done"
+      detection_rule: "How to recognize this"
+      severity: "P0-P3"
+      occurrences: 0
+      last_seen: "ISO8601"
+
+  successes:
+    file: "patterns/successes.json"
+    schema:
+      id: "SUC-XXX"
+      name: "descriptive_name"
+      context: "When this applies"
+      approach: "Steps that worked"
+      key_elements: "Critical factors"
+      success_rate: 0.0
+      uses: 0
+      last_used: "ISO8601"
+```
+
+---
+
+## Integration Points
+
+```yaml
+integration:
+  # Load patterns at task start
+  on_task_start:
+    - "Load patterns/errors.json"
+    - "Load patterns/successes.json"
+    - "Match context to known patterns"
+    - "Apply relevant learnings"
+
+  # Check patterns during execution
+  during_execution:
+    - "Compare current approach to error patterns"
+    - "If match found, apply prevention"
+    - "Compare to success patterns"
+    - "If match found, follow proven approach"
+
+  # Update patterns at end
+  on_task_end:
+    - "Analyze outcome"
+    - "Update relevant patterns"
+    - "Save to storage"
+```
+
+---
+
+## Confidence Thresholds
+
+```yaml
+confidence:
+  thresholds:
+    high: 90  # Very confident, proceed
+    medium: 70  # Mostly confident, note caveats
+    low: 50  # Uncertain, request verification
+    critical: 30  # Very uncertain, stop and research
+
+  actions:
+    below_critical:
+      - "Stop current approach"
+      - "Request more information"
+      - "Research before continuing"
+      
+    below_low:
+      - "Add uncertainty markers"
+      - "Suggest verification steps"
+      - "Offer alternatives"
+```
+
+---
+
+## Metrics
+
+```yaml
+metrics:
+  track:
+    - reflections_performed_per_session
+    - errors_caught_by_self_critique
+    - patterns_learned_and_applied
+    - success_rate_improvement_over_time
+
+  report:
+    frequency: "weekly"
+    format: "summary_table"
+```
+
+---
+
+# DOMYH Awesome Code  • Reflection Module

package/.agent/rules/modules/stop-conditions.yaml

@@ -0,0 +1,196 @@
+# Stop Conditions Rule v6.0
+# Modular rule for knowing when to pause and ask
+
+---
+name: stop-conditions
+version: "6.1.2"
+rule_id: "MOD-STP-001"
+
+# =============================================================================
+# RULE METADATA
+# =============================================================================
+
+description: |
+  Rules for identifying conditions that require pausing and consulting
+  the user before proceeding. Critical for safety and alignment.
+
+category: "safety"
+
+# =============================================================================
+# CONTEXT APPLICATION
+# =============================================================================
+
+context:
+  always_apply: true
+  personas: ["*"]
+  workflows: ["*"]
+
+# =============================================================================
+# STOP CONDITIONS
+# =============================================================================
+
+conditions:
+  # ==========================================================================
+  # CRITICAL STOPS (Always stop, no exceptions)
+  # ==========================================================================
+
+  critical:
+    destructive_actions:
+      trigger: "About to delete files, drop tables, or remove data"
+      action: "STOP and confirm"
+      message: |
+        ⛔ **Destructive Action Required**
+
+        I'm about to: {action}
+        This will: {impact}
+
+        Proceed? (yes/no)
+
+    security_sensitive:
+      trigger: "About to modify auth, permissions, or security config"
+      action: "STOP and confirm"
+      message: |
+        🔒 **Security Change Detected**
+
+        Changing: {what}
+        Impact: {impact}
+
+        Please confirm this is intended.
+
+    production_actions:
+      trigger: "Any action targeting production environment"
+      action: "STOP and confirm"
+      message: |
+        🚀 **Production Action**
+
+        Action: {action}
+        Environment: PRODUCTION
+
+        This affects live users. Confirm? (yes/no)
+
+  # ==========================================================================
+  # HIGH PRIORITY STOPS (Stop in most cases)
+  # ==========================================================================
+
+  high:
+    scope_expansion:
+      trigger: "Task requires changes outside original scope"
+      action: "STOP and confirm scope expansion"
+      message: |
+        📏 **Scope Expansion**
+
+        Original scope: {original}
+        New requirement: {expanded}
+
+        Should I expand the scope?
+
+    ambiguous_request:
+      trigger: "Request has multiple valid interpretations"
+      action: "STOP and clarify"
+      message: |
+        ❓ **Clarification Needed**
+
+        I could interpret this as:
+        1. {interpretation_1}
+        2. {interpretation_2}
+
+        Which do you mean?
+
+    missing_information:
+      trigger: "Cannot proceed without information I don't have"
+      action: "STOP and ask"
+      message: |
+        📋 **Information Needed**
+
+        To proceed, I need to know: {what}
+
+    large_change:
+      trigger: "Change affects > 100 lines or > 5 files"
+      action: "STOP and confirm plan"
+      threshold:
+        lines: 100
+        files: 5
+      message: |
+        📦 **Large Change**
+
+        This will modify: {files} files, ~{lines} lines
+
+        Review plan before proceeding?
+
+  # ==========================================================================
+  # MEDIUM PRIORITY STOPS (Stop if uncertain)
+  # ==========================================================================
+
+  medium:
+    external_dependencies:
+      trigger: "Need to add new external dependency"
+      action: "Confirm before adding"
+      message: |
+        📦 **New Dependency**
+
+        Package: {package}
+        Version: {version}
+        Purpose: {purpose}
+
+        Add this dependency?
+
+    pattern_deviation:
+      trigger: "Proposed solution differs from project patterns"
+      action: "Note deviation and optionally confirm"
+      message: |
+        🔄 **Pattern Deviation**
+
+        Project uses: {existing_pattern}
+        Proposed: {new_pattern}
+        Reason: {reason}
+
+        Proceed with deviation?
+
+    test_failures:
+      trigger: "Existing tests fail after changes"
+      action: "STOP and report"
+      max_retries: 3
+      message: |
+        ❌ **Tests Failing**
+
+        Failed: {test_count} tests
+        After: {change_description}
+
+        Options:
+        1. Review and fix
+        2. Revert changes
+        3. Mark as known issue
+
+# =============================================================================
+# OVERRIDE PROTOCOL
+# =============================================================================
+
+override:
+  critical:
+    allow: false # Cannot be overridden
+
+  high:
+    allow: true
+    requires: "Explicit user confirmation"
+    log: true
+
+  medium:
+    allow: true
+    requires: "User preference or explicit request"
+    log: true
+
+# =============================================================================
+# INTEGRATION
+# =============================================================================
+
+integration:
+  constitutional:
+    tier: 1 # Inherits from safety tier
+
+  reflection:
+    enabled: true
+    check_before: "action"
+    question: "Should I pause and confirm this with the user?"
+
+---
+_DOMYH Awesome Code • Stop Conditions Rule_