distill-rules
Review routing corrections and propose updates to vault CLAUDE.md routing rules.
What this skill does
# Distill Rules
Review accumulated routing corrections in `.routing-memory.md` and propose updates to the vault's CLAUDE.md routing rules.
See `references/routing-memory.md` for correction format and learning loop.
## Process
1. Read `.routing-memory.md` from vault root
2. Read vault CLAUDE.md
3. Analyze corrections for patterns:
- Group corrections by destination
- Identify repeated corrections (same type of note going to same destination)
- Look for corrections that contradict existing CLAUDE.md rules
4. Propose updates:
- New edge case mappings for disambiguation sections
- New category table entries
- New learned patterns for `.routing-memory.md`
- Corrections to existing rules that have been consistently overridden
5. Present proposals to user:
```
Found {n} patterns in {m} corrections:
1. Add edge case: "{scenario}" -> {destination}
Based on: {n} corrections over {date range}
2. Add to category table: "{tool}" under {area}
Based on: {n} corrections
3. Update rule: "{old rule}" -> "{new rule}"
Based on: consistently overridden {n} times
Apply these updates?
(A) Apply all
(B) Review individually
(C) Skip for now
```
6. Apply selected updates:
- Edit vault CLAUDE.md with new rules
- Move applied corrections to an `## Archived` section in `.routing-memory.md`
- Promote stable patterns to `## Patterns Learned`
## Constraints
- Never auto-apply. Always present proposals for approval.
- Preserve existing CLAUDE.md structure and formatting
- Archive corrections, don't delete them (audit trail)
- Only propose rules backed by multiple corrections (minimum 2)
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.