ワンクリックで
project-principles
Core architectural and code quality principles that guide all development decisions in the vm0 project
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Core architectural and code quality principles that guide all development decisions in the vm0 project
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Patterns and best practices for using ccstate state management in the vm0 platform
Deep code review and quality analysis for vm0 project
Database migrations and Drizzle ORM guidelines for the vm0 project
Feature switch system guide for gating new user-facing features behind feature flags
Technical debt management - scan codebase for bad smells and create tracking issues
Comprehensive testing patterns and anti-patterns for writing and reviewing tests
| name | project-principles |
| description | Core architectural and code quality principles that guide all development decisions in the vm0 project |
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.
Don't add functionality until it's actually needed.
Quick rules:
When coding: Ask "Do we need this NOW?" If not, don't add it.
→ For detailed guidelines and examples, read yagni.md
Let exceptions propagate naturally. Don't wrap everything in try/catch.
Quick rules:
When coding: Only use try/catch when you have specific error recovery logic.
→ For detailed guidelines and examples, read no-defensive.md
Maintain type safety throughout the codebase. Never compromise on type checking.
Quick rules:
any typeWhen coding: If you see any, fix it. If types are missing, add them.
→ For detailed guidelines and examples, read type-safety.md
All code must pass linting without exceptions.
Quick rules:
When coding: If lint fails, fix the code, not the linter.
→ For detailed guidelines and examples, read zero-lint.md
Before writing any code, verify:
yagni.md firstno-defensive.mdtype-safety.mdzero-lint.mdThese principles should be applied:
These principles exist to:
They may feel restrictive at first, but they lead to cleaner, more maintainable code.
If principles seem to conflict: