| name | project-principles |
| description | Core architectural and code quality principles that guide all development decisions in the vm0 project |
Project Principles Skill
This skill defines the fundamental design principles and coding standards for the vm0 project. These principles are MANDATORY for all code written in this project and should guide every development decision.
The Four Core Principles
1. YAGNI (You Aren't Gonna Need It) ⭐ CORE PRINCIPLE
Don't add functionality until it's actually needed.
Quick rules:
- Start with the simplest solution that works
- Avoid premature abstractions
- Delete unused code aggressively
- No "just in case" features
When coding: Ask "Do we need this NOW?" If not, don't add it.
→ For detailed guidelines and examples, read yagni.md
2. Avoid Defensive Programming
Let exceptions propagate naturally. Don't wrap everything in try/catch.
Quick rules:
- Only catch exceptions when you can meaningfully handle them
- Let errors bubble up to where they can be properly addressed
- Avoid defensive try/catch blocks that just log and re-throw
- Trust the runtime and framework error handling
When coding: Only use try/catch when you have specific error recovery logic.
→ For detailed guidelines and examples, read no-defensive.md
3. Strict Type Checking
Maintain type safety throughout the codebase. Never compromise on type checking.
Quick rules:
- Absolutely NO use of
any type
- Always provide explicit types where TypeScript can't infer
- Use proper type narrowing instead of type assertions
