agentleFS
kensauruskensaurus/cursor-kenji/.cursor/rules/skill-workflows.mdc

cursor-kenji / rules

Cursor rule9 starsChanged 42 days agoMITView on GitHub

Skill routing where a name alone misleads: multi-phase requests, closure modes (complete-everything, burndown-full), and look-alike skills.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

Files
skill-workflows.mdc
---
description: >-
  Skill routing where a name alone misleads: multi-phase requests, closure
  modes (complete-everything, burndown-full), and look-alike skills.
globs:
alwaysApply: false
---

# Skill Routing Index

A request that spans phases (spec, build, test, ship) goes to a bundled
workflow skill, not a chain of single-phase skills. Where a name misleads:

- An approved plan with open items or deferrals → `complete-everything`; a
  mechanical change stopped short of 100% → `burndown-full`; list parked work
  in BACKLOG.md without doing it → `housekeep-backlog`.
- Raw feedback (reports, reviews, Sentry, QA, audits) → deduplicated tickets,
  each closed → `workflow-feedback-to-closure`; a ranked fix loop on a live
  app's signals → `iterate-post-launch`.
- Prove tools, installs, services, and verify commands before a long run →
  `workflow-environment-ready`; checks run but fail → `workflow-green-repo`.
- Agent stopped early, claimed false completion, or gamed a check → a guard
  with a regression test → `iterate-agent-harness`.
- Working tree → merge-ready PR, never merges → `workflow-release-prep`.
- Orient in an unfamiliar codebase → `workflow-onboard` (product user
  onboarding → `enhance-onboarding`).
- Is a lint or ratchet rule right → `audit-doctrine`; is it enforced →
  `audit-gate-logic`.
- The agent or the machine is slow (hooks, status line, CPU) →
  `audit-agent-speed`; the product is slow → `audit-performance`.
- These `audit-*` skills fix after reporting, not present-then-stop:
  `audit-responsive`, `audit-code-quality`, `audit-performance`,
  `audit-security`, `audit-i18n`, `audit-bundle-size`, `audit-agent-speed`.

Rules hold always-on policy and routing; procedures stay in skills.

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.