053-design-simple-rules — Claude Code skill
053-design-simple-rules is a Claude skill that checks Java design and refactoring decisions against Kent Beck's four rules, in order.
Apache-2.0 172 installs ★ 465 updated 2026-10-21
npx skills add jabrena/plinth --skill 053-design-simple-rules -a claude-codeWhat 053-design-simple-rules does
The four rules run in a set order: tests pass first, then intent reads clearly, then duplication goes, and the count of elements comes last. The skill is built so an agent cannot trade an earlier rule away for a later one.
The run is interactive. The agent opens references/053-design-simple-rules.md, pins down what evidence shows the code behaves correctly, then looks at names, types, responsibilities and API shape. Repeated knowledge gets pulled together only if the result stays readable. Trimming classes, methods, parameters and layers waits until the end. The wrap-up compares the options on the table and names the rejected tradeoffs, the signal that will confirm the change, and the risk left over.
That reference file sits with the skill and has to be there: without it the skill stops at the first step. Expect questions about your code rather than a verdict handed down.
What it helps with
- review a contested class design against Kent Beck's rules
- pick one of two refactoring options and see the tradeoffs
- find duplication that hides what the domain means
- strip extra layers and parameters once the tests are green
- explain to the team why one variant is simpler than the other
Example prompts for the agent
- Review
OrderServiceagainst Kent Beck's simple design rules - Pick between these two refactoring options for
PricingPolicyand list the tradeoffs - Is this design simple enough, or is there duplication I should remove first?
How to install 053-design-simple-rules
1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 053-design-simple-rules -a claude-code2Manually: put the files in place
~/.claude/skills/053-design-simple-rules/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/053-design-simple-rules/
1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 053-design-simple-rules -a codex2Manually: put the files in place
.agents/skills/053-design-simple-rules/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 053-design-simple-rules -a cursor2Manually: put the files in place
.cursor/skills/053-design-simple-rules/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install jabrena/plinth skills/053-design-simple-rules2Manually: put the files in place
.github/skills/053-design-simple-rules/SKILL.md1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 053-design-simple-rules -a gemini-cli2Platform CLI
gemini skills install https://github.com/jabrena/plinth --path skills/053-design-simple-rulesManually: put the files in place
.devin/skills/053-design-simple-rules/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 053-design-simple-rules -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about 053-design-simple-rules
How do I install 053-design-simple-rules in Claude Code?
Run npx skills add jabrena/plinth --skill 053-design-simple-rules -a claude-code. The skill lands at ~/.claude/skills/053-design-simple-rules/SKILL.md.
What does 053-design-simple-rules do?
It walks through Java design and refactoring choices using Kent Beck's four rules in order, then compares the options and reports the tradeoffs, the check that confirms the change, and the remaining risk.
What has to be in place before it runs?
The skill reads references/053-design-simple-rules.md as a mandatory first step, so that file needs to be present. It also asks for whatever evidence shows the code works, such as tests or a build check.
Source text
SKILL.md · Apache-2.0
--- name: 053-design-simple-rules description: Use when Java design, refactoring, or implementation tradeoffs should be evaluated with Kent Beck's simple design rules, including passes the tests, reveals intention, has no duplication, and has the fewest elements. This should trigger for requests such as Apply simple design rules; Review this design with Beck's rules; Choose between these refactoring options; Keep this Java design simple. Part of Plinth Toolkit license: Apache-2.0 metadata: author: Juan Antonio Breña Moral version: 0.19.0 --- # Simple Design Rules Guide Java developers through Kent Beck's simple design rules when evaluating design and refactoring choices. **This is an interactive SKILL**. **What is covered in this Skill?** - Using tests as the first correctness boundary before design cleanup - Revealing intention and maximizing clarity before abstraction pressure - Reducing duplication without hiding domain meaning or worsening readability - Treating fewer elements as the final simplification pressure after correctness, clarity, and duplication - Comparing Java design and refactoring options with the ordered rules - Reporting the chosen option, tradeoffs, validation signal, and remaining risk ## Constraints Apply simple design rules in priority order, and do not optimize later rules by weakening earlier rules. - **MUST** read `references/053-design-simple-rules.md` before applying the rules - **MUST** evaluate the rules in this order: passes the tests, reveals intention, has no duplication, has the fewest elements - **MUST** treat passing tests as the correctness boundary before design cleanup - **MUST** prefer clear intention over abstraction for its own sake - **MUST** reduce duplication only when the result preserves or improves clarity - **MUST** consider fewer elements only after correctness, clarity, and duplication have been addressed ## When to use this skill - Apply simple design rules - Use Beck's simple design rules - Review this design with simple design rules - Choose between these refactoring options - Keep this Java design simple - Does this design pass the simple design rules? ## Workflow 1. **Anchor Correctness** Read `references/053-design-simple-rules.md`, then identify the behavior under discussion and the tests, characterization checks, build checks, or manual evidence that define whether the code works. 2. **Reveal Intention** Evaluate whether names, types, responsibilities, control flow, API shape, and test descriptions make the domain decision clear to a future maintainer. 3. **Reduce Duplication Carefully** Find repeated knowledge, policy, mappings, validation, queries, or workflow decisions. Remove duplication only when the abstraction keeps the intent easier to understand. 4. **Minimize Elements Last** After correctness, clarity, and duplication are handled, remove unnecessary classes, methods, parameters, branches, layers, configuration, or indirection that no longer pay for themselves. 5. **Compare Options and Report** Compare available design or refactoring options against the ordered rules. Recommend the option that satisfies the earlier rules best, describe rejected tradeoffs, and name the verification signal. ## Reference For detailed guidance, examples, and constraints, see [references/053-design-simple-rules.md](references/053-design-simple-rules.md).
© Juan Antonio Breña Moral · Apache-2.0 · jabrena/plinth