COMMON-PATTERNS

Common Patterns Reference

When to apply: Understanding shared concepts used across all rule files.

---

Core Shared Concepts

This file consolidates patterns used across VALIDATION-GATES, COMMUNICATION-PROTOCOL, RESEARCH-DEPTH, WORKTREE-ENFORCEMENT, FACT-VERIFICATION, INVESTIGATION-METHODS, ITERATION-GATES, SATISFACTORY-CRITERIA, and WRITING-STYLE.

---

1. Evidence Requirements

File:Line Reference Format

Standard format:

file.js:42                    # Single line
file.js:42-45                 # Line range
src/migrations/index.ts:137   # Absolute from project root

When required:

• All factual claims about code
• Bug locations
• Implementation references
• Configuration changes

Example:

✅ "Migration fails at readMigrationFiles (payload.config.ts:137)"
❌ "Migration fails in the config file"

Evidence Components

Every claim needs these 4 elements:

1. Source: Where the information comes from

   • File path with line numbers
   • URL to documentation
   • Command output

2. Evidence: Actual proof

   • Code snippet
   • Documentation quote
   • Test result
   • Screenshot (rare)

3. Verification method: How you confirmed it

   • "Code inspection"
   • "WebFetch of documentation"
   • "Tested on clean database"
   • "Used Explore agent"

4. Context: Version/date when relevant

   • Package version
   • Commit hash
   • Date of check
   • Platform version

---

2. Checklist Usage Pattern

Standard Checkbox Format

- [ ] Item to verify
- [ ] Another item to check
- [ ] Third verification point

How to Use Checklists

Before proceeding:

1. Read each checkbox item
2. Verify it's complete/true
3. Mentally check it off
4. If ANY fails, stop and fix it

Common mistake:

• Skipping checklist items
• Assuming items pass without checking
• Proceeding when checkboxes fail

Correct approach:

• Actually verify each item
• Fix failures before proceeding
• Document why skipped (if approved)