agentleFS
20030419zhanghongyi20030419zhanghongyi/AI-Software-Engineering-Workflow-Template/.cursor/rules/project-rules.mdc

AI-Software-Engineering-Workflow-Template / rules

Cursor rule0 starsChanged 6 months agoMITView on GitHub

Project rules for AI Software Engineering Workflow Template

The file

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

10 rules. About 0 are common, 9 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    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:

    DO NOT create React/Vue/Electron apps, backend services, or CLI tools as part of this template.

    line 13
  2. Distinctive:

    Before editing any code, read in order:

    line 25
  3. Distinctive:

    Do NOT code from vague requirements.

    line 37
  4. Distinctive:

    Do NOT expand task scope without permission.

    line 38
  5. Distinctive:

    Do NOT refactor unrelated code.

    line 39
  6. Distinctive:

    Do NOT introduce new dependencies without justification.

    line 40
  7. Distinctive:

    Do NOT bypass tests.

    line 41
  8. Distinctive:

    Do NOT modify files outside the task scope.

    line 42
  9. Distinctive:

    STOP and ask when uncertain.

    line 43
  10. Distinctive:

    After changes, always report: what files changed, why, test results, risks.

    line 44

≈ “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
project-rules.mdc
---
description: Project rules for AI Software Engineering Workflow Template
globs:
alwaysApply: true
---

# Project Rules

## Project Type

This is a template repository for solo developers using AI coding tools. It is NOT a business application.

DO NOT create React/Vue/Electron apps, backend services, or CLI tools as part of this template.

## Core Philosophy

```
Repository manages state, AI manages execution, CI manages quality, Human manages decisions.
```

The goal is NOT to make AI write more code, but to make AI write more maintainable code within clear boundaries and quality rules.

## Required Reading

Before editing any code, read in order:

1. README.md
2. docs/00_project_brief.md
3. docs/04_architecture.md
4. docs/05_module_boundaries.md
5. docs/06_coding_standards.md
6. docs/07_testing_strategy.md
7. Current Issue or task description

## Rules

1. Do NOT code from vague requirements. Output a plan first.
2. Do NOT expand task scope without permission.
3. Do NOT refactor unrelated code.
4. Do NOT introduce new dependencies without justification.
5. Do NOT bypass tests.
6. Do NOT modify files outside the task scope.
7. STOP and ask when uncertain.
8. After changes, always report: what files changed, why, test results, risks.

## Language

Documentation and comments should be primarily in Chinese, with technical terms in English where appropriate.

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.