@nockdev/awf 6.2.0

package/.agent/rules/modules/evidence.yaml

@@ -0,0 +1,185 @@
+# Evidence Rule v6.0
+# Modular rule for evidence-based claims
+
+---
+name: evidence
+version: "6.1.2"
+rule_id: "MOD-EVD-001"
+
+# =============================================================================
+# RULE METADATA
+# =============================================================================
+
+description: |
+  Rules for ensuring all claims and findings are backed by evidence.
+  Critical for auditing, debugging, and code review workflows.
+
+category: "quality"
+
+# =============================================================================
+# CONTEXT APPLICATION
+# =============================================================================
+
+context:
+  always_apply: false
+  personas: ["auditor", "debugger", "security", "researcher"]
+  workflows: ["/ap", "/debug", "/review", "/security"]
+
+# =============================================================================
+# CORE PRINCIPLES
+# =============================================================================
+
+principles:
+  claim_evidence_linking:
+    description: "Every claim must have supporting evidence"
+    format: "Claim → Evidence → Location"
+
+  source_citation:
+    description: "Cite sources for external information"
+    types:
+      - "file:line for code"
+      - "URL for web sources"
+      - "command output for runtime"
+
+  confidence_levels:
+    description: "Indicate certainty of findings"
+    levels:
+      high: "Confirmed with evidence"
+      medium: "Strong indicators"
+      low: "Suspected, needs verification"
+
+# =============================================================================
+# EVIDENCE TYPES
+# =============================================================================
+
+evidence_types:
+  code_evidence:
+    format: |
+      **File:** `path/to/file:45`
+      **Code:**
+      ```language
+      // The relevant code
+      ```
+    required_for:
+      - Bug reports
+      - Security findings
+      - Refactoring suggestions
+
+  log_evidence:
+    format: |
+      **Log:** `[TIMESTAMP] [LEVEL] message`
+      **Source:** Log file or console
+    required_for:
+      - Runtime errors
+      - Performance issues
+      - Debugging
+
+  test_evidence:
+    format: |
+      **Test:** `test_name`
+      **Result:** Pass/Fail
+      **Output:** ...
+    required_for:
+      - Bug fixes
+      - Regression reports
+      - Coverage claims
+
+  metrics_evidence:
+    format: |
+      **Metric:** metric_name
+      **Value:** X
+      **Source:** tool/command
+    required_for:
+      - Performance findings
+      - Coverage reports
+      - Quality assessments
+
+# =============================================================================
+# SPECIFIC RULES
+# =============================================================================
+
+rules:
+  file_line_required:
+    rule: "All code findings must include file:line reference"
+    example: "src/auth/service.ts:45"
+    validation: "^[a-zA-Z0-9_./-]+:[0-9]+$"
+
+  code_snippet_required:
+    rule: "Include relevant code snippet for findings"
+    min_context: "3 lines"
+    max_context: "10 lines"
+
+  no_speculation:
+    rule: "Don't claim issues not confirmed by evidence"
+    allowed: "Suggest investigation areas"
+    not_allowed: "Assert bugs without proof"
+
+  source_freshness:
+    rule: "Verify sources are current"
+    for_code: "Use current file state"
+    for_docs: "Note if docs may be outdated"
+
+# =============================================================================
+# TEMPLATES
+# =============================================================================
+
+templates:
+  finding:
+    format: |
+      ## [Severity] [Title]
+
+      **File:** `{file}:{line}`
+      **Confidence:** {high|medium|low}
+
+      **Evidence:**
+      ```{language}
+      {code_snippet}
+      ```
+
+      **Issue:** {description}
+      **Impact:** {impact}
+      **Recommendation:** {fix}
+
+  claim:
+    format: |
+      {claim} (Source: `{source}`)
+
+# =============================================================================
+# VALIDATION
+# =============================================================================
+
+validation:
+  pre_output:
+    - "All findings have file:line references"
+    - "Code snippets are current (not fabricated)"
+    - "Confidence levels are appropriate"
+
+  disallow:
+    - "Findings without evidence"
+    - "Fabricated code snippets"
+    - "Unverified external claims"
+
+# =============================================================================
+# INTEGRATION
+# =============================================================================
+
+integration:
+  hsa_tools:
+    hsa_get_context:
+      purpose: "Gather code context as evidence for findings"
+      usage: "hsa_get_context files=[target] → retrieve relevant code snippets"
+    hsa_search_patterns:
+      purpose: "Find best-practice patterns to validate claims"
+      usage: "hsa_search_patterns query=[topic] → cross-reference against 730+ patterns"
+
+  reflection:
+    enabled: true
+    check_before: "output"
+    questions:
+      - "Is every claim backed by evidence?"
+      - "Are file:line references accurate?"
+      - "Are code snippets from the actual file?"
+      - "Did I use HSA context for deeper evidence?"
+
+---
+_DOMYH Awesome Code • Evidence Rule_

package/.agent/rules/modules/git-workflow.yaml

@@ -0,0 +1,165 @@
+# Git Workflow Rule v6.0
+# Modular rule for git operations
+
+---
+name: git-workflow
+version: "6.1.2"
+rule_id: "MOD-GIT-001"
+
+# =============================================================================
+# RULE METADATA
+# =============================================================================
+
+description: |
+  Rules for git operations: detection, prerequisite checks, and deployment readiness.
+
+category: "workflow"
+
+# =============================================================================
+# CONTEXT APPLICATION
+# =============================================================================
+
+context:
+  always_apply: false
+  personas: ["developer", "devops"]
+  workflows: ["/code", "/deploy", "/refactor"]
+
+# =============================================================================
+# GIT DETECTION
+# =============================================================================
+
+detection:
+  commands:
+    powershell: "Test-Path .git -PathType Container"
+    bash: "test -d .git"
+
+  on_detected:
+    - "Include git commands (commit, push, diff)"
+    - "Show git status in next steps"
+
+  on_missing:
+    - "Skip git suggestions"
+    - "Offer initialization"
+
+# =============================================================================
+# PRE-DEPLOY CHECKS
+# =============================================================================
+
+pre_deploy:
+  preconditions:
+    1_git_init:
+      check: ".git/ directory exists"
+      fail_action: "Suggest: git init"
+
+    2_remote:
+      check: "git remote -v has origin"
+      fail_action: "Suggest: git remote add origin <url>"
+
+    3_uncommitted:
+      check: "git status --porcelain is empty"
+      fail_action: "Suggest: git add .; git commit -m 'message'"
+
+  decision_flow: |
+    Before suggesting /deploy:
+        │
+        ├── No .git/? → "Initialize git: git init"
+        │
+        ├── No remote? → "Add remote: git remote add origin <url>"
+        │
+        ├── Uncommitted? → "Commit: git add .; git commit -m 'msg'"
+        │
+        └── All good → Proceed with /deploy
+
+# =============================================================================
+# OUTPUT TEMPLATES
+# =============================================================================
+
+templates:
+  with_git: |
+    Next Steps:
+    ├── ✅ Review changes: git diff
+    ├── ✅ Commit: git commit -am "{message}"
+    └── ✅ Push: git push
+
+  without_git: |
+    Next Steps:
+    ├── ✅ Changes saved successfully
+    └── 💡 Consider: git init; git add .; git commit -m 'Initial'
+
+  pre_deploy_no_git: |
+    📋 NEXT STEPS:
+    1️⃣ Initialize git: git init
+    2️⃣ Add remote: git remote add origin <your-repo-url>
+    3️⃣ First commit: git add .; git commit -m 'Initial commit'
+    4️⃣ Push: git push -u origin main
+
+    Would you like me to help set this up?
+
+# =============================================================================
+# SAFE OPERATIONS
+# =============================================================================
+
+safe_operations:
+  always_safe:
+    - "git status"
+    - "git diff"
+    - "git log"
+    - "git branch"
+    - "git remote -v"
+
+  require_confirmation:
+    - pattern: "git reset --hard"
+      reason: "Discards all uncommitted changes"
+    - pattern: "git push --force"
+      reason: "Overwrites remote history"
+    - pattern: "git clean -fd"
+      reason: "Removes untracked files"
+    - pattern: "git rebase"
+      reason: "Rewrites commit history"
+
+# =============================================================================
+# COMMIT MESSAGE GUIDELINES
+# =============================================================================
+
+commit_messages:
+  format: "type(scope): message"
+  types:
+    - feat: "New feature"
+    - fix: "Bug fix"
+    - docs: "Documentation"
+    - style: "Formatting"
+    - refactor: "Code restructure"
+    - test: "Adding tests"
+    - chore: "Maintenance"
+
+  examples:
+    - "feat(auth): add JWT authentication"
+    - "fix(payment): resolve checkout timeout"
+    - "docs(readme): update installation guide"
+
+# =============================================================================
+# CHECKLIST
+# =============================================================================
+
+checklist:
+  - "Check .git/ directory exists"
+  - "Check git remote -v has origin"
+  - "Check git status for uncommitted changes"
+  - "Only suggest /deploy if all conditions pass"
+  - "Provide helpful git setup if missing"
+
+# =============================================================================
+# INTEGRATION
+# =============================================================================
+
+integration:
+  tier: 2 # Execution tier
+  related_modules:
+    - terminal-safety
+    - edit-verification
+
+  reflection:
+    enabled: false
+
+---
+_DOMYH Awesome Code • Git Workflow Rule_

package/.agent/rules/modules/language.yaml

@@ -0,0 +1,155 @@
+# Language Rule v6.0
+# Modular rule for language and i18n
+
+---
+name: language
+version: "6.1.2"
+rule_id: "MOD-LNG-001"
+
+# =============================================================================
+# RULE METADATA
+# =============================================================================
+
+description: |
+  Language and internationalization rules for agent responses.
+  Default language: Tiếng Việt (Vietnamese)
+
+category: "communication"
+
+# =============================================================================
+# CONTEXT APPLICATION
+# =============================================================================
+
+context:
+  always_apply: true
+  personas: ["*"]
+  workflows: ["*"]
+
+# =============================================================================
+# CORE LANGUAGE SETTINGS
+# =============================================================================
+
+settings:
+  default_language: "vi"
+  supported: ["vi", "en"]
+  fallback: "en"
+
+  switch_commands:
+    vietnamese: "/lang vi"
+    english: "/lang en"
+
+# =============================================================================
+# RESPONSE RULES
+# =============================================================================
+
+response_rules:
+  vietnamese:
+    always_use:
+      - "Explanations and descriptions"
+      - "Error messages"
+      - "Questions to user"
+      - "Status updates"
+      - "Confirmations"
+
+    keep_english:
+      - "Code samples"
+      - "Technical terms"
+      - "File names and paths"
+      - "Commands"
+      - "Variable names"
+
+    examples:
+      greeting: "Chào bạn! Em có thể giúp gì?"
+      confirmation: "Em đã hoàn thành task này."
+      question: "Bạn có muốn tiếp tục không?"
+      error: "Có lỗi xảy ra: {error}"
+
+  english:
+    always_use:
+      - "All responses"
+      - "Technical explanations"
+
+    examples:
+      greeting: "Hello! How can I help?"
+      confirmation: "I've completed this task."
+      question: "Would you like to continue?"
+
+# =============================================================================
+# TONE GUIDELINES
+# =============================================================================
+
+tone:
+  characteristics:
+    - "Professional but friendly"
+    - "Clear and concise"
+    - "Helpful and supportive"
+    - "Acknowledge mistakes openly"
+
+  avoid:
+    - "Overly formal language"
+    - "Excessive apologies"
+    - "Unnecessary filler words"
+    - "Ambiguous statements"
+
+# =============================================================================
+# TECHNICAL TERM HANDLING
+# =============================================================================
+
+technical_terms:
+  keep_in_english:
+    - "API, REST, GraphQL"
+    - "JWT, OAuth, CORS"
+    - "Docker, Kubernetes"
+    - "Git, commit, push"
+    - "Build, deploy, test"
+    - "Frontend, backend"
+    - "Framework, library"
+
+  translate_when_explaining:
+    api: "giao diện lập trình ứng dụng"
+    bug: "lỗi"
+    feature: "tính năng"
+    refactor: "tái cấu trúc"
+    deploy: "triển khai"
+
+# =============================================================================
+# FORMAT LOCALIZATION
+# =============================================================================
+
+localization:
+  date_format:
+    vi: "DD/MM/YYYY"
+    en: "YYYY-MM-DD"
+
+  number_format:
+    vi: "1.000.000"
+    en: "1,000,000"
+
+  emoji_usage:
+    enabled: true
+    categories:
+      status: ["✅", "❌", "⚠️", "🔄", "⏳"]
+      files: ["📁", "📄", "📝"]
+      actions: ["🚀", "🔧", "🐛", "💻"]
+
+# =============================================================================
+# CHECKLIST
+# =============================================================================
+
+checklist:
+  - "Response in correct language?"
+  - "Technical terms kept in English?"
+  - "Tone is appropriate?"
+  - "Clear and concise?"
+
+# =============================================================================
+# INTEGRATION
+# =============================================================================
+
+integration:
+  tier: 2 # Execution tier
+  config_source: ".agent/memory/state.json"
+  config_path: "preferences.language"
+
+---
+_DOMYH Awesome Code • Language Rule_

package/.agent/rules/modules/online-research.yaml

@@ -0,0 +1,192 @@
+# Online Research Rule v6.0
+# Modular rule for web research and external sources
+
+---
+name: online-research
+version: "6.1.2"
+rule_id: "MOD-RES-001"
+
+# =============================================================================
+# RULE METADATA
+# =============================================================================
+
+description: |
+  Guidelines for conducting online research and using external sources.
+  Emphasizes source quality, citation, and information verification.
+
+category: "research"
+
+# =============================================================================
+# CONTEXT APPLICATION
+# =============================================================================
+
+context:
+  always_apply: false
+  personas: ["researcher", "developer", "architect"]
+  workflows: ["/find", "/debug", "/code"]
+  trigger: "When external information is needed"
+
+# =============================================================================
+# SOURCE HIERARCHY
+# =============================================================================
+
+source_hierarchy:
+  tier_1_primary:
+    description: "Always prefer these sources"
+    sources:
+      - "Official documentation"
+      - "GitHub repositories (official)"
+      - "Language/framework guides"
+      - "RFCs and specifications"
+    trust_level: "high"
+
+  tier_2_secondary:
+    description: "Use with verification"
+    sources:
+      - "Stack Overflow (high-voted)"
+      - "MDN Web Docs"
+      - "Framework blog posts"
+      - "Conference talks"
+    trust_level: "medium"
+
+  tier_3_tertiary:
+    description: "Cross-reference required"
+    sources:
+      - "Tutorial blogs"
+      - "Medium articles"
+      - "Forum posts"
+      - "AI-generated content"
+    trust_level: "low"
+
+# =============================================================================
+# RESEARCH WORKFLOW
+# =============================================================================
+
+workflow:
+  1_identify_need:
+    action: "Determine what information is needed"
+    questions:
+      - "What specific question needs answering?"
+      - "Can this be answered from local context?"
+      - "Is external research necessary?"
+
+  2_search_strategy:
+    action: "Plan search approach"
+    strategies:
+      - "Start with official docs"
+      - "Use specific error messages"
+      - "Include version numbers"
+      - "Target relevant platforms"
+
+  3_evaluate_sources:
+    action: "Assess source quality"
+    criteria:
+      - "Publication date (prefer recent)"
+      - "Author credibility"
+      - "Community validation"
+      - "Version compatibility"
+
+  4_synthesize:
+    action: "Combine and verify information"
+    rules:
+      - "Cross-reference multiple sources"
+      - "Test code before recommending"
+      - "Note version differences"
+
+  5_cite:
+    action: "Provide attribution"
+    format: "Source: [Title](URL) - {date}"
+
+# =============================================================================
+# CITATION REQUIREMENTS
+# =============================================================================
+
+citation:
+  always_cite:
+    - "Direct quotes"
+    - "Code snippets from external sources"
+    - "Specific techniques or patterns"
+    - "Statistics or benchmarks"
+
+  format:
+    inline: "[Source](URL)"
+    block: |
+      📚 Source: {title}
+      🔗 {url}
+      📅 {date}
+      ✅ Verified: {yes/no}
+
+# =============================================================================
+# VERIFICATION RULES
+# =============================================================================
+
+verification:
+  code_snippets:
+    action: "Test before recommending"
+    steps:
+      - "Check syntax is valid"
+      - "Verify against current version"
+      - "Test in similar environment"
+
+  claims:
+    action: "Cross-reference"
+    minimum_sources: 2
+    exceptions: ["Official documentation"]
+
+  outdated_check:
+    max_age_years: 2
+    warning: |
+      ⚠️ This information is from {year}.
+      Best practices may have changed.
+
+# =============================================================================
+# OUTPUT FORMAT
+# =============================================================================
+
+output:
+  research_summary: |
+    🔍 RESEARCH SUMMARY
+
+    Question: {question}
+
+    Findings:
+    - {finding_1}
+    - {finding_2}
+
+    Sources:
+    1. [Source 1](URL) - {reliability}
+    2. [Source 2](URL) - {reliability}
+
+    Confidence: {high/medium/low}
+    Recommendation: {action}
+
+# =============================================================================
+# CHECKLIST
+# =============================================================================
+
+checklist:
+  - "Used highest quality sources available?"
+  - "Cross-referenced information?"
+  - "Cited all external sources?"
+  - "Verified code examples work?"
+  - "Noted version/date relevance?"
+
+# =============================================================================
+# INTEGRATION
+# =============================================================================
+
+integration:
+  tier: 2 # Execution tier
+  related_modules:
+    - evidence
+
+  hsa_tools:
+    hsa_search_patterns:
+      purpose: "Check local pattern database BEFORE searching online"
+      usage: "hsa_search_patterns query=[topic] → may answer without web search"
+    hsa_get_context:
+      purpose: "Gather project context to formulate better search queries"
+      usage: "hsa_get_context files=[relevant] → understand what to search for"
+
+---
+_DOMYH Awesome Code • Online Research Rule_