From pds
Grounds in core development principles: understand before act, small reversible steps, tests as spec, explicit over implicit. Use when starting significant work, feeling stuck, or resetting clarity.
npx claudepluginhub rmzi/portable-dev-system --plugin pdsThis skill uses the workspace's default tool permissions.
> Understand · Build · Validate
Provides development principles, safety guidelines, diff-aware editing rules, repo context reading instructions, and VibeCoder guidance via referenced files. Use for principle application, not implementation or reviews.
Generates tailored Development Principles for CLAUDE.md by auto-detecting project structure, monorepo setup, tech stack including TypeScript, React, Python, Django, and user preferences via interactive questions.
Applies Pragmatic Programmer principles like DRY, orthogonality, tracer bullets, and design by contract to score and improve software designs, architecture, code, and engineering decisions.
Share bugs, ideas, or general feedback.
Understand · Build · Validate
When invoked, remind of these principles. Use as grounding before significant work.
Read existing code before modifying. Map the territory before changing it.
"Weeks of coding can save hours of planning."
Atomic commits. Small PRs. Refactor before adding.
"Make the change easy, then make the easy change." — Kent Beck
Tests document intent. Code documents implementation.
Declare dependencies. Name things for what they do. Configuration over invisible convention.
Code is read 10x more than written. Coupling is the enemy. Delete freely.
Validate at boundaries. Crash on programmer errors. Handle user errors.
Scripts encode knowledge. CI runs what developers run. Automate the repeated.
Mutually Exclusive (no overlap) + Collectively Exhaustive (no gaps). Apply everywhere:
| Domain | MECE means |
|---|---|
| Skills | Each skill has one clear purpose, no overlap |
| Functions | Each function does one thing, responsibilities don't overlap |
| Architecture | Components have clear, non-overlapping responsibilities |
| Documentation | Each topic in one place |