Identify unnecessary structure and hidden complexity in software designs.
npx skills add https://github.com/nmnmcc/skills --skill simplicity-nmnmcc
Please help me install this Agent Skill. Skill: simplicity Source: https://github.com/nmnmcc/skills/tree/main/skills/simplicity Command: npx skills add https://github.com/nmnmcc/skills --skill simplicity-nmnmcc
This Skill helps you judge and shape software so it stays as simple as possible while still meeting its real need, keeping its promises, and remaining safe enough for its use.
Use the simplicity skill to analyze this codebase and recommend the smallest faithful design that still satisfies the real requirements.
High-intent search queries and answers about installing and using this skill.
Software complexity analysis identifies unnecessary wrappers, layers, and mismatched abstractions by evaluating whether each structure carries required meaning. This process removes distinctions that add noise without providing real risk protection, resulting in a smaller faithful design that preserves the system contract.
Simplifying software architecture requires treating implementations as the smallest faithful model of inputs, outputs, state, and failures. You must preserve the original contract, minimize the proof surface, and keep only the safeguards justified by real risk to ensure safe refactoring.
Architectural boundaries are needed where meaning or trust changes within the system. You should add safeguards only when real risk justifies them, avoiding extra layers that do not carry required protection or meaning during software design and refactoring.
Refactoring a tangled service involves analyzing whether each wrapper or abstraction carries required meaning or protection. If the layer adds noise without justifying real risk, it should be removed to minimize proof surface and reduce unnecessary software design complexity.
Simplifying software design does not remove all failure handling; it keeps only the protections justified by real risk. The implementation must remain the smallest faithful model of failures and effects while preserving the contract and ensuring safe operation.
xlsamaAnalyze project files and user answers to write a Design Context section for CLAUDE.md.
Ankurjain1121Plan standardized end-to-end testing patterns for multi-agent frameworks.
huangzidaCoordinate multi-file feature changes through incremental slices with test and verify steps.
JSai23Evaluate code architecture to surface misdesigns, coupling, and unsuitable abstractions.
