agentleFS
Sign inStart free
Luis85Luis85/agentic-workflow/.cursor/rules/agents.mdc

agentic-workflow / rules

Cursor rule0 starsChanged 6 months agoMITView on GitHub

Specorator project conventions and workflow rules for Cursor and editor-agents

The file

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

2 rules. About 0 are common, 0 are distinctive, and 2 are 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.

  • 2

    Very specific

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

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

    All implementation derives from specs under specs/<slug>/.

    line 23
  2. Very specific:

    Commit messages: imperative, reference task IDs — feat(area): add T-AREA-NNN description.

    line 24

≈ “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
agents.mdc
---
description: Specorator project conventions and workflow rules for Cursor and editor-agents
alwaysApply: true
---

# Specorator — project context

This repository is **Specorator**, a template for spec-driven, agentic software development. The workflow itself is the deliverable.

## Source of truth

[`AGENTS.md`](../../AGENTS.md) is the single source of truth for workflow rules, agent roles, operating conventions, and repository layout. Read it first for any non-trivial change.

Supporting context (in load order):

1. `AGENTS.md` — project conventions, agent classes, operating rules
2. `memory/constitution.md` — governing principles
3. `docs/specorator.md` — full lifecycle workflow definition
4. `specs/<feature>/workflow-state.md` — active feature state

## Key conventions

- All implementation derives from specs under `specs/<slug>/`. Read the relevant spec before writing code.
- Commit messages: imperative, reference task IDs — `feat(area): add T-AREA-NNN description`.
- One concern per branch; `npm run verify` green before push; no direct commits to `main` or `develop`.

## Adapter note

This rule is a thin pointer. It does not duplicate `AGENTS.md`. When `AGENTS.md` *Tool-specific notes* changes, sync this file. See [`docs/adapters.md`](../../docs/adapters.md).

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