cursor-mishka-builder

Audit repositories and plan PRD-aligned vertical slices for Project Mishka.

Updated Nov 13, 2025
One-click install
npx skills add https://github.com/ransomeye/ransomeye --skill cursor-mishka-builder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cursor-mishka-builder
Source: https://github.com/ransomeye/ransomeye/tree/main/cursor-mishka-builder
Command: npx skills add https://github.com/ransomeye/ransomeye --skill cursor-mishka-builder

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

It solves the problem of safely implementing the Project Mishka prototype inside Cursor without drifting from the PRD authority model or creating conflicting edits across a growing codebase.

Core Features & Use Cases

  • Deterministic repo auditing before major changes: runs scripts/audit_repo.py to detect drift, duplicates, dead code candidates, and port/service collisions before planning implementation work.
  • PRD authority-guided development workflow: uses references/mishka-authority-map.md as the control plane and produces slice-based work to keep authoritative boundaries intact.
  • Acceptance-driven response structure for reliable delivery: enforces the sectioned reporting format from references/acceptance-pattern.md so each slice includes plan, applied changes, and deterministic verification.

Use case: You need to implement or refactor a single Mishka phase-1 vertical slice (e.g., storage authority touchpoints or pipeline wiring) while ensuring no AI/heuristics leak into authoritative execution paths and no direct state mutation occurs outside the PRD commit path.

Quick Start

Ask ChatGPT to use cursor-mishka-builder to audit the repo, follow the authority map, then implement the requested Mishka phase-1 slice with a Cursor-friendly multi-file plan and the required acceptance output sections.

Frequently Asked Questions about cursor-mishka-builder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit a codebase for drift before implementing vertical slices in Cursor?

To audit a codebase for drift before implementing vertical slices in Cursor, run `scripts/audit_repo.py` to detect duplicates, dead code candidates, and port collisions. This deterministic repo auditing establishes a clean baseline for planning PRD-aligned development work.

How do I enforce PRD compliance during AI-assisted coding in Cursor?

Enforce PRD compliance during AI-assisted coding in Cursor by using `references/mishka-authority-map.md` as the control plane. This authority-guided workflow keeps authoritative boundaries intact and prevents AI or heuristics from leaking into execution paths.

What's the best way to plan deterministic vertical slices for a prototype project?

The best way to plan deterministic vertical slices for a prototype project is to combine repo auditing with an authority map. This approach produces slice-based work that includes a plan, applied changes, and deterministic verification for reliable delivery.

Can I detect port conflicts and service collisions in my repository before deployment?

Yes, you can detect port conflicts and service collisions in your repository before deployment. Running `scripts/audit_repo.py` identifies port and service collisions alongside codebase drift, ensuring safe implementation without conflicting edits.

How do I structure acceptance reports for phased coding tasks?

Structure acceptance reports for phased coding tasks by following the sectioned format in `references/acceptance-pattern.md`. This acceptance-driven response structure requires each slice to include plan, applied changes, and deterministic verification sections.

Why does my codebase drift from the PRD authority model during multi-file edits?

Your codebase drifts from the PRD authority model during multi-file edits when direct state mutation occurs outside the PRD commit path. Applying deterministic, PRD-aligned vertical slices with an authority map prevents conflicting edits across the growing codebase.