agentleFS
Sign inStart free
phmatrayphmatray/tagout/.cursor/rules/tagout.mdc

tagout / rules

Cursor rule4 starsChanged 59 days agoMITView on GitHub

Tagout — which kit skill to use, how to load it, and its MCP servers

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 1

    1. phmatray/ai-migration-kit★ 4100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.

    Of the Cursor rule files we read, the 4,183 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository15 other files it gives its agents.

The file

We split this tagout.mdc into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When a request matches a row above, read that SKILL.md and follow it step by step.

    line 26

≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
tagout.mdc
---
description: Tagout — which kit skill to use, how to load it, and its MCP servers
alwaysApply: true
---

# Tagout

Agent skills for two loops: a gate-verified pipeline that takes a legacy .NET application to
verified production, with RoselineMCP doing every C# analysis and edit, and a hands-off GitHub
issue → pull request lifecycle. Guide: https://phmatray.github.io/tagout/

## Which kit skill, for what

Reach for the kit's own skills first, before any third-party plugin's equivalent (`superpowers`):
`<kit>/skills/_shared/` is the one home of their doctrine (#324), `<kit>` being the kit root — the
plugin's install directory, or a clone at `~/.tagout`. Full guide:
`<kit>/docs/methodology.md`. Short form — broken/flaky → `debug-issue`; a new idea →
`create-issue` (`--seed #N` plans a raw issue); a planned issue → `implement-issue #N`; a finished branch → `create-pr`; a ready PR →
`merge-pr #N`; many issues hands-off → `auto-dev`; the queue → `triage-backlog`;
profile/labels → `init` (typed `/tagout:init`); a legacy .NET app → `/migrate-assess` then `/migrate`; a missing
skill → write it with `skill-creator`, then register it (*Adding a skill* in `<kit>/.claude/CLAUDE.md`).

## Loading a skill

Each skill is a folder under `<kit>/skills/` whose `SKILL.md` says when it applies and what to do.
When a request matches a row above, read that `SKILL.md` and follow it step by step; the files it
links resolve relative to it. A `/migrate…` command is the `migrate-legacy` skill run at a given
scope (`<kit>/commands/`).

`<kit>` is the kit root — the directory holding `skills/`, `scripts/` and `requirements.json`:

- **installed as a plugin** — two directories above the skill's own `SKILL.md`;
- **this text is a rule file in your own project** — a clone at `~/.tagout`
  (`git clone https://github.com/phmatray/tagout ~/.tagout`).

Skill scripts need bash, python3 with PyYAML, git and an authenticated `gh`;
`<kit>/requirements.json` lists every prerequisite and `<kit>/scripts/preflight.sh` checks them.

## MCP servers

The migration pipeline runs on **RoselineMCP** (required: every C# analysis and edit goes through
it) and consults **AdrMcp** (recommended: the architectural decisions under `docs/adr/`). Both start
with `dnx` from the .NET 10 SDK — `dnx RoselineMCP --yes` and `dnx AdrMcp --yes`. A plugin install
starts them from the kit's own manifest; anywhere else, register both in your host's MCP settings.
Without RoselineMCP, `/migrate` stops at its phase-0 preflight; without AdrMcp, the skills grep
`docs/adr/` instead and say so. The issue → pull request skills need neither.

`auto-dev` and `deliver-issue` dispatch sub-agents and need a host that has them. The gates under
`<kit>/hooks/` are Claude Code hooks; elsewhere the skills run without them.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free