claude-piv-skeleton / rules
Cursor rule4 starsChanged 10 months agoMITView on GitHub
PIV API design rules for controllers and routes
Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.
Of the Cursor rule files we read, the 4,243 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- .cursor/rules/piv-general.mdcCursor rule
- .cursor/rules/piv-security.mdcCursor rule
- .cursor/rules/piv-tdd.mdcCursor rule
- adaptive-learningSkill
- api-designSkill
- code-reviewSkill
- securitySkill
- test-driven-developmentSkill
- test-writingSkill
The file
We split this piv-api.mdc into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 25
Use proper HTTP status codes (200, 201, 400, 404, 500)
≈ “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.
Files
---
description: PIV API design rules for controllers and routes
globs: ["*Controller*", "*Router*", "*Route*", "routes/*", "controllers/*", "*Handler*"]
alwaysApply: false
---
# API Design Rules
## RESTful Principles
- **Nouns over verbs**: `/users` not `/getUsers`
- **Plural nouns**: `/users` not `/user`
- **HTTP verbs**: GET (read), POST (create), PUT (update), DELETE (remove)
- **Resource hierarchy**: `/users/{id}/posts`
## Response Format
```json
// Success
{ "data": {...}, "meta": {...} }
// Error
{ "error": "ErrorCode", "message": "Human-readable description" }
```
## Best Practices
- Use proper HTTP status codes (200, 201, 400, 404, 500)
- Validate all input
- Version your API (`/v1/users`)
- Return consistent response structures
<!-- PIV v1.0.0 -->
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.

