053-design-simple-rules

仓库创建 2025年2月9日最近提交 3 天前SkillHot 收录 16 小时前

▸ 精选理由

适合代码审查与设计权衡，强调测试与意图揭示。

这个 Skill 做什么

按 Kent Beck 的简单设计规则评估 Java 设计与重构决策。

用 Kent Beck 的简单设计规则帮你评估 Java 的设计或重构决策：先保证 tests 通过，再把意图写清楚，去掉重复，最后追求最少的元素。选重构方案、代码评审或不确定要不要抽象时用，强调先用测试界定正确性再做清理。特点是互动式判断，偏向可读性和最小化复杂度，不鼓励过早抽象。

▸ 展开 SKILL.md 英文原文

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

开发编程Java设计规则重构通用

423

Stars

Forks

仓库内 Skill

7 日增星

安装 / 使用

给你的 Agent 一句话（通用）

帮我安装这个 skill：https://raw.githubusercontent.com/jabrena/plinth/main/skills/053-design-simple-rules/SKILL.md

或 curl 直取 SKILL.md

curl -fsSL "https://raw.githubusercontent.com/jabrena/plinth/main/skills/053-design-simple-rules/SKILL.md"

SKILL.MD 节选查看完整文件 ↗

# 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

via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有