Cursor plugin for AI Dev OS — Rules (.mdc) for guideline-driven development
yunbow/ai-dev-os-plugin-cursor
Cursor rule
Audits the health of the AI Dev OS 4-layer structure. Detects dependency rule violations, expiration, and coverage gaps. Used for monthly or quarterly periodic maintenance.
yunbow/ai-dev-os-plugin-cursor
Cursor rule
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.
yunbow/ai-dev-os-plugin-cursor
Cursor rule
Supports the spiral evolution of AI Dev OS. Analyzes recent AI coding practices (commit history, review records) and generates update proposals for L1 philosophy and L2 principles. Used in monthly retrospectives or quarterly reviews.
yunbow/ai-dev-os-plugin-cursor
Cursor rule
Extracts rules from the gap between AI-generated code and ideal code. Used after code review to add new rules to AI Dev OS guidelines. A Rule Harvesting approach to rule discovery.
yunbow/ai-dev-os-plugin-cursor
Cursor rule
AI Dev OS initial setup wizard. Use when starting a new project or introducing AI Dev OS. Asks about the project's tech stack and scale, then generates an optimal 4-layer structure from templates.
yunbow/ai-dev-os-plugin-cursor
Cursor rule
Creates an implementation plan with relevant AI Dev OS guideline checklists before writing any code. Analyzes the request, identifies affected files and applicable guidelines, then presents a plan with embedded checklist for user approval. Implementation begins only after approval.
yunbow/ai-dev-os-plugin-cursor
Cursor rule
Generates an AI Dev OS compliance report for teams and stakeholders. Includes compliance rate trends, major violations, and improvement proposals for a specified period. Used for weekly or monthly reporting.
yunbow/ai-dev-os-plugin-cursor
Cursor rule
Performs a comprehensive self-review before creating a PR. Combines guideline compliance checking (L3) with design-level review (L2) and philosophical alignment (L1). Unlike @ai-dev-os-check which only checks rules, this also evaluates architecture decisions and code design quality.
yunbow/ai-dev-os-plugin-cursor
Cursor rule
Scans ALL source files in the project against AI Dev OS guidelines. Unlike @ai-dev-os-check (which only checks git diff), this performs a full project-wide compliance scan. Use for initial audits, periodic full reviews, or after introducing new guidelines.
yunbow/ai-dev-os-plugin-cursor
Cursor rule
Generates a ticket (local file or GitHub Issue) with implementation summary and checklist candidates derived from AI Dev OS guidelines. Used to create structured implementation tasks.
yunbow/ai-dev-os-plugin-cursor
Cursor rule
Explains the "why" behind a specific AI Dev OS rule or guideline. Traces the path from L3 guideline → L2 principle → L1 philosophy. Used when team members question a rule.
yunbow/ai-dev-os-plugin-cursor
Cursor rule
Audits the coverage, consistency, and freshness of AI Dev OS L3 guidelines. Used during periodic maintenance or when introducing a new framework.
yunbow/ai-dev-os-plugin-cursor
Cursor rule
Lightweight AI Dev OS guideline compliance guidance for code files. Automatically active when editing code files.
yunbow/ai-dev-os-plugin-cursor
Cursor rule
Warns about dependency rule violations when L1-L2 files are edited. L1 philosophy files must not contain tool-specific terms. L2 principle files must not contain framework-specific implementation details.
yunbow/ai-dev-os-plugin-cursor
Cursor rule
Provides architecture judgment based on AI Dev OS L1 philosophy. When facing technology choices or design decisions, offers recommendations grounded in philosophical values.
yunbow/ai-dev-os-plugin-cursor
Cursor rule
Verifies that code changes align with AI Dev OS L2 principles. Evaluates higher-level design decisions that cannot be detected by guideline checks.