CAP-SKILL-015
Skill100 starsChanged 2 months agoMITView on GitHub
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- harness/AGENTS.mdAGENTS.md
- i-test-target/AGENTS.mdAGENTS.md
- anti-overengineeringSkill
- app-type-classifierSkill
- auth-permission-securitySkill
- backend-api-designSkill
- CAP-SKILL-004Skill
- CAP-SKILL-013Skill
- CAP-SKILL-014Skill
- database-schema-designSkill
- frontend-ui-systemSkill
- mobile-miniapp-patternsSkill
- product-architectureSkill
- webapp-preview-testingSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 34
If .cursorrules and AGENTS.md conflict on code style, AGENTS.md takes precedence
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill 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.
Files
Project Rules Ecosystem Skill
Trigger
This skill activates when a project contains rule files beyond AGENTS.md — including .cursorrules, .coderules, project-rules.md, CONVENTIONS.md, .githooks/, or similar.
Purpose
Parse and apply project-level rule files that define coding conventions, architecture constraints, and agent behavior boundaries. Extends CAP-SKILL-004 (AGENTS.md) to cover the broader project rules ecosystem.
Core Rules
1. Rule File Discovery
Walk the project directory tree and identify rule files:
.cursorrules— Cursor IDE project rules.coderules— Generic code rulesproject-rules.md— Explicit project rule documentationCONVENTIONS.md— Coding conventions document.github/workflows/— CI/CD rules.githooks/— Git hook rules
2. Rule Extraction
Parse each file and extract:
| Category | Pattern | Output |
| File naming | *.tsx, *.module.css patterns | Naming convention rules |
| Directory structure | src/components/, src/pages/ | Directory layout rules |
| Import rules | import order, no default exports | Import convention rules |
| Type rules | no any, strict null checks | TypeScript strictness rules |
| CI/CD rules | workflow triggers, required checks | Pipeline rules |
| Git rules | commit message format, branch naming | VCS rules |
3. Integration with AGENTS.md
- AGENTS.md (CAP-SKILL-004) has precedence for agent behavior
- Project rule files provide supplementary conventions
- If
.cursorrulesand AGENTS.md conflict on code style, AGENTS.md takes precedence - Report all conflicts
4. Tool Restrictions
- This skill READS project rule files
- This skill does NOT modify rule files
- This skill does NOT enforce rules — it surfaces them to agents
Output Format
{
"ruleFilesFound": [".cursorrules", "CONVENTIONS.md"],
"namingRules": ["Component files: PascalCase.tsx", "Utils: camelCase.ts"],
"directoryRules": ["Components in src/components/", "Pages in src/pages/"],
"importRules": ["No default exports", "Type imports separate"],
"typeRules": ["Strict mode on", "No implicit any"],
"gitRules": ["Conventional commits", "Feature branches"],
"ciRules": ["Lint on PR", "Build on push to main"],
"conflicts": []
}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
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.

