# Gendosu Ccmp Key Guidelines > Key Guidelines - Skill: `tomevault-io/gendosu-ccmp-key-guidelines` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/gendosu-ccmp-key-guidelines` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/gendosu-ccmp-key-guidelines/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/gendosu-ccmp-key-guidelines --- # Key Guidelines ## Design Principles - **DRY (Don't Repeat Yourself)**: Avoid code duplication - **KISS (Keep It Simple, Stupid)**: Keep designs and code simple - **YAGNI (You Ain't Gonna Need It)**: Don't implement features until actually needed. Extract methods/functions only when there's a concrete need for reuse, not in anticipation of it - **SOLID Principles**: Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion - **SoC (Separation of Concerns)**: Separate system by concerns (UI, business logic, data access, etc.) ## Development Methodology - **TDD Approach**: Use TDD methodology (Kent Beck style) to break down tasks during execution - **Micro-commits**: One change per commit, strictly follow test-driven change cycles (Lucas Rocha's micro-commit methodology) ## Quality & Standards - **Code Quality**: Run linters and type checkers before committing - **Security**: Always follow security guidelines and scan for vulnerabilities - **Documentation**: Keep technical documentation in `docs/` directory - **Version Control**: Follow conventional commit messages and branching strategy --- > Converted and distributed by [TomeVault](https://tomevault.io/claim/gendosu) — claim your Tome and manage your conversions.