菜单
Use when implementing small or low-complexity changes with minimal ceremony — modular, domain-centered behavior, clear separation from infrastructure, and practical SOLID guardrails without full hex/DDD layering
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | lightweight-software-principles |
| description | Use when implementing small or low-complexity changes with minimal ceremony — modular, domain-centered behavior, clear separation from infrastructure, and practical SOLID guardrails without full hex/DDD layering |
Prefer superpowers:hex-infra when complexity, integrations, or long-term change pressure are high (see superpowers:selecting-implementation-architecture).
services/ soup).UserRow, OrderDto) driving domain flowAlways pair with superpowers:test-driven-development. Lightweight does not mean untested — it means fewer structural layers, not fewer tests.
Use when you have a written implementation plan and need to execute it directly in the current session on main/master
Use when implementation is complete to verify and finalize work directly on main/master
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Use before writing an implementation plan — recommend lightweight vs heavyweight (hex-infra, DDD depth) from signals, confirm with the user, and record the decision for execution
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
Use when you have a spec or requirements for a multi-step task, before touching code