claude-piv-skeleton
CLAUDE.md4 starsChanged 10 months agoMITView on GitHub
PIV (Prime-Implement-Validate) methodology for AI-assisted development RED → GREEN → REFACTOR - No exceptions. ❌ Code before tests = DELETE IT Backend: Spring Boot • Node/Express • FastAPI Frontend: React/TS Database: PostgreSQL PIV Version: 2.0 | Claude Code Plugin Available
In this repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/piv-api.mdcCursor rule
- .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 CLAUDE.md into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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 9
RED → GREEN → REFACTOR: - No exceptions.
- Distinctive: line 11
RED: Write failing test FIRST
≈ “Common” is an estimate: at least 1 in 5 of the 27,641 CLAUDE.md 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
PIV Spec-Kit
PIV (Prime-Implement-Validate) methodology for AI-assisted development
🚨 TDD MANDATORY
RED → GREEN → REFACTOR - No exceptions.
- RED: Write failing test FIRST
- GREEN: Minimal code to pass
- REFACTOR: Improve while green
❌ Code before tests = DELETE IT
Quick Commands
| Command | Purpose |
/piv-speckit:constitution | Create project principles (one-time) |
/piv-speckit:prime | Load context |
/piv-speckit:plan-feature "X" | Plan feature X |
/piv-speckit:execute | Implement plan |
/piv-speckit:validate | Run validation |
/piv-speckit:code-review | Review code |
/piv-speckit:learn | Capture learnings |
/commit | Commit changes |
Supported Stack
Backend: Spring Boot • Node/Express • FastAPI Frontend: React/TS Database: PostgreSQL
Workflow
PRIME → Load context
PLAN → Design approach (complex features only)
IMPLEMENT → Write tests first, then code
VALIDATE → Runs automaticallyFor Full Details
- Methodology:
Read .claude/reference/methodology/PIV-METHODOLOGY.md - Rules:
Read .claude/rules/(compressed) or.claude/reference/rules-full/(complete) - Execution:
Read .claude/reference/execution/[command].md
PIV Version: 2.0 | Claude Code Plugin Available
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.

