clodbridge: Skill for Cursor

Verify Before Proceeding

The Golden Rule

Don't assume correctness. Verify every time you're about to move to the next feature.

Verification Checklist

After writing code, before committing:

Mandatory Checks

• TypeScript compiles — npm run typecheck or bun run typecheck (zero errors)
• No syntax errors — The parser can open the file
• Tests pass — npm test if you wrote tests (100% pass rate)
• Imports resolve — All from statements find their targets
• No unused variables — TypeScript strict mode catches these

Conditional Checks

• Integration test — If adding an MCP tool, call it and verify the response
• Glob matching test — If using micromatch, test with real file paths
• File fixtures exist — If parsing logic, do test files exist?

What to Do When Verification Fails

❌ DON'T

• Skip the failing check
• Assume it will work later
• Proceed to the next feature anyway
• Disable type checking or warnings

✅ DO

1. Read the error message carefully
2. Identify the root cause (typo, wrong import, logic error, missing file)
3. Fix the code (or the test, if the test is wrong)
4. Re-run verification
5. Confirm it passes before proceeding

Common Errors and Fixes

Type Error: "Property 'globs' does not exist"

// Error: Property 'globs' does not exist on type 'RuleFrontmatter'

// Fix: Check types.ts — is 'globs' defined in the interface?
interface RuleFrontmatter {
  description?: string;
  globs?: string;  // ← Add this if missing
}

Import Error: "Cannot find module './parse.js'"

// Error at src/reader/rules.ts:3
import { parseRuleFile } from './parse.js';  // Error

// Fix: Check that parse.ts exists in src/reader/
// If it exists, verify the import is using .js (for ESM)

Test Failure: "Expected ['src//.ts', '.md'], got ['src//*.ts ', ' *.md']"

// Bug: parseGlobs() is not trimming whitespace

// Fix:
function parseGlobs(raw: string) {
  return raw
    .split(',')
    .map(s => s.trim())  // ← Add trim()
    .filter(Boolean);
}