Checks code changes against AI Dev OS guidelines and automatically fixes violations. Based on benchmark Test 011 — check+fix achieves +9.9 improvement vs report-only (+0.8). Supports git diff (default), staged changes, and branch comparison. Use --dry-run for report-only mode.
The engineering contract for this repo lives in AGENTS.md (auto-loaded). Follow it. This rule only adds Cursor-specific behavior so the contract is not duplicated token-for-token on every request.
Cursor rule "cursorrules" from wrm3/cursorrules_siliconvalley, covering assistant personality, character rotation, richard hendricks, gilfoyle and dinesh.
During you interaction with the user, if you find anything reusable in this project (e.g. version of a library, model name), especially about a fix to a mistake you made or a correction you received, you should take note in the Lessons section in the .cursorrules file so you will not make the same mistake again.
When the user asks you to generate diagrams, analyze code structure, or visualize architecture, follow this analysis pipeline. Use terminal commands (rg, find, cat) for all file operations.
Use when the user asks to create a diagram, chart, infographic, flowchart, architecture illustration, or any technical visualization. Covers flowcharts, sequence diagrams, ER diagrams, class diagrams, state machines, timelines, mind maps, git graphs, pie charts, and quadrant charts.
Meta-orchestrator that classifies tasks and routes to the right combination of installed skills across caveman (output compression), superpowers (dev workflow), anthropic-skills (business/domain expertise), and wired tactical libraries (wshobson, davila7, impeccable, anthropic-official). 26 routing categories…
Trace the impact / blast radius of a code change and prove it didn't break other features — run after a fix, before commit/PR/push. Language- and framework-agnostic; works by discovering the project's own conventions. Apply when the user asks "did this break anything", "what else does this affect", "check the impact"…
Architecture-first, reduction-first workflow for code changes, debugging, refactoring, and cleanup. Use to trace the owning path, prefer no edit and subtraction before additions, replace obsolete behavior instead of layering around it, keep scope closed, refute your own diagnosis and fix before believing them, verify…
Automatically fetch and resolve GitHub Pull Request comments. Activates when you mention PR (with or without number): 'fix PR', 'PR 2146', 'fix PR 2146', '#2146', 'PR#2146', 'pr2146', or any variation.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: