agentleFS
sagarchauhan005sagarchauhan005/agent-sage/.cursor/rules/sage-system.mdc

agent-sage / rules

Cursor rule0 starsChanged 5 months agoMITView on GitHub

Sage agent system — always load root Agents.md and route through SDLC agents.

The file

We split this sage-system.mdc into the rules it gives an agent

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

  • 3

    Very specific

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

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

    Always read Agents.md first.

    line 10
  2. Very specific:

    When doing SDLC work, use /sage-* slash commands.

    line 12
  3. Very specific:

    Do not skip phases except those listed in manifest.skipped_phases.

    line 14

≈ “Common” is an estimate: at least 1 in 5 of the 6,809 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
sage-system.mdc
---
description: Sage agent system — always load root Agents.md and route through SDLC agents.
alwaysApply: true
---

# Sage system

This project uses the **Sage** SDLC agent system.

Always read [Agents.md](../../Agents.md) first. It is the root contract linked to all phase agents in `agents/`.

When doing SDLC work, use `/sage-*` slash commands. Set `workflow_profile` in manifest per [workflows/profiles.md](../../workflows/profiles.md).

Do not skip phases except those listed in `manifest.skipped_phases`. Never skip plan, build, qa, or release.

Agent registry, skills mirror, and flow: see the top of Agents.md. Keep `.cursor/skills/` aligned with the Skills mirror table when adding or removing agents.

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.