agentleFS
Sign inStart free
LIDR-academyLIDR-academy/AI4Devs-LTI-extended/.cursor/rules/use-base-rules.mdc

AI4Devs-LTI-extended / rules

Cursor rule278 starsChanged 6 months agoMITView on GitHub

Directs all AI agents to use the consolidated rules in base-standards.md

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

7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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. Distinctive:

    All AI agents working on this project must follow the comprehensive development rules and guidelines defined in:

    line 9
  2. Very specific:

    Single Source of Truth: All development rules, coding standards, testing practices, and workflow requirements are maintained in …

    line 15
  3. Very specific:

    No Rule Duplication: Do not reference or follow other rule files - base-standards.md contains the complete and authoritative rule set

    line 16
  4. Distinctive:

    Before starting any development work, agents must:

    line 30
  5. Very specific:

    Read and understand all rules in base-standards.md

    line 31
  6. Distinctive:

    Follow the TDD process and core principles defined there

    line 32
  7. Distinctive:

    Use the specified tools, testing frameworks, and standards

    line 33

≈ “Common” is an estimate: at least 1 in 5 of the 6,350 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
use-base-rules.mdc
---
description: Directs all AI agents to use the consolidated rules in base-standards.md
globs: 
alwaysApply: true
---

# Use Base Development Rules

All AI agents working on this project must follow the comprehensive development rules and guidelines defined in:

**📋 [docs/base-standards.md](docs/base-standards.md)**

## Key Directive

- **Single Source of Truth**: All development rules, coding standards, testing practices, and workflow requirements are maintained in `base-standards.md`
- **No Rule Duplication**: Do not reference or follow other rule files - `base-standards.md` contains the complete and authoritative rule set
- **Always Current**: `base-standards.md` is the actively maintained configuration - other rule files may be outdated

## What's Included in base-standards.md

- **Core Principles**: Small tasks one at a time, Test-Driven Development (TDD), type safety, clear naming, incremental changes
- **Language Standards**: English-only requirement for all technical artifacts
- **Specific Standards**: Links to detailed standards for:
  - Backend development (API, database patterns, testing, security)
  - Frontend development (React components, UI/UX guidelines)
  - Documentation (structure, formatting, maintenance)

## Compliance

Before starting any development work, agents must:
1. Read and understand all rules in `base-standards.md`
2. Follow the TDD process and core principles defined there
3. Use the specified tools, testing frameworks, and standards
4. Maintain the required code quality and type safety standards
5. Refer to specific standards documents (backend, frontend, documentation) for detailed guidelines

**Remember**: `base-standards.md` is the complete development rulebook for this project.

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