Bita71Bita71/Agent-Workflow-Kit/.cursor/rules/main.mdc

Agent-Workflow-Kit / rules

Cursor rule1 starsChanged 4 months agoMITView on GitHub

docs/ai is the source of truth for rules, skills, commands, agent roles, and artifacts. Before working, read: - .agent-workflow-kit/config.conf — project settings and active profiles. - docs/ai/README.md — map of the AI surface. - docs/ai/rules/project.md — tool-agnostic invariants (scope, clarify, safety, verification). - docs/ai/rules/coding-rules.md — this stack's conventions. - docs/ai/rules/commit-message.md — Conventional Commits. <check> means CHECK_COMMAND from the config. Run it after substantive changes unless it is none. Do not commit or push without an explicit request. Cursor slash commands…

In this repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- skill-ai-auditSkill
- skill-buildSkill
- skill-choose-modelSkill
- skill-deps-auditSkill
- skill-learnSkill
- skill-planSkill
- skill-review-correctnessSkill
- skill-review-designSkill
- skill-review-securitySkill

The file

Create a free account to mount

Files

main.mdc

---
alwaysApply: true
---

# Cursor Adapter

`docs/ai` is the source of truth for rules, skills, commands, agent roles, and
artifacts. Before working, read:

- `.agent-workflow-kit/config.conf` — project settings and active profiles.
- `docs/ai/README.md` — map of the AI surface.
- `docs/ai/rules/project.md` — tool-agnostic invariants (scope, clarify, safety,
  verification).
- `docs/ai/rules/coding-rules.md` — this stack's conventions.
- `docs/ai/rules/commit-message.md` — Conventional Commits.

`<check>` means `CHECK_COMMAND` from the config. Run it after substantive changes
unless it is `none`. Do not commit or push without an explicit request.

## Commands

Cursor slash commands live in `.cursor/commands/*` as thin adapters that point
into `docs/ai/commands/*`. Available: `symphony`, `codex-plan`, `build`,
`review-full`, `review-design`, `choose-model`, `ai-audit`, `deps-audit`,
`learn`, `apply-worktree`.

## Roles

- Planning and correctness/security review run through Codex
  (`docs/ai/agents/cli.md`, `docs/ai/agents/codex-plan.md`,
  `docs/ai/agents/review-correctness.md`, `docs/ai/agents/review-security.md`).
- Implementation and design review use the tracked Cursor agents `build` and
  `review-design` (`docs/ai/agents/build.md`,
  `docs/ai/agents/review-design.md`).

Resolve model roles and effort through config and
`docs/ai/commands/choose-model.md`. Do not restate rules in replies; follow the
referenced files.

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