菜单
Use when writing, reviewing, or refactoring code for maintainability and readability. Triggers on code reviews, naming discussions, function design, error handling, and test writing. Based on Robert C. Martin's Clean Code handbook with modern corrections.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/pproenca/dot-skills --skill clean-code命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Drizzle ORM against PostgreSQL inside a Next.js App Router app. Covers client construction (globalThis singleton across HMR, serverless pool sizing, `prepare:false` behind PgBouncer/Supavisor, driver choice when you need interactive transactions, `server-only`), reads in Server Components under Next.js 16 Cache Components (`use cache` superseding `unstable_cache` and the `revalidate`/`dynamic` segment configs, Suspense boundaries, React `cache()` dedupe), Server Actions (authorization inside the action, `updateTag` vs `revalidateTag`, `after()`), Postgres schema types (timestamptz, identity vs serial, jsonb, numeric-as-string, bigint modes), drizzle-kit migrations (generate vs push, CONCURRENTLY outside the migrator, NOT VALID constraints, rename prompts), transactions and pooled connections, and Postgres query traps (keyset pagination, count cost, driver-dependent `db.execute()` shape, NOT IN nulls, prepared statements). Use when writing or reviewing Drizzle + Postgres code in Next.js.
Corrects the wrong defaults a model has when designing a relational schema — the DDL decisions an experienced engineer makes differently. Use when creating or reviewing tables, migrations, ER models, or ORM schema definitions. Covers identity and keys (surrogate vs natural, identity vs serial, uuidv7, composite keys that make cross-tenant references impossible), relationships (polymorphic foreign keys the database cannot enforce, referential actions, unindexed FK columns, disjoint subtypes), invariants the engine can prove instead of application code (EXCLUDE, partial unique indexes, CHECK limits, deferrable cycles, NOT VALID), types (timestamptz, exact money, range types, enum vs lookup table), derived and encoded data (generated columns, JSONB as an escape hatch), and time (events vs in-place updates, soft-delete flags that silently disable constraints, temporal keys). NOT for query tuning, index selection for read paths, or connection pooling.
Distills a logical relational-database design methodology into rules an agent applies while designing or reviewing a schema. Covers the design sequence (mission → tables → fields → keys → relationships → business rules → views → integrity review), one-subject-per-table decomposition, atomic single-valued fields, candidate/primary/foreign keys, relationship types with deletion rules and participation, the four levels of data integrity, database-vs-application business rules, validation tables, views for derived data, and the flat-file / spreadsheet / RDBMS-driven antipatterns to avoid. The structure is logical and RDBMS-agnostic, and normalized by construction. Use when designing a new relational schema, reviewing or refactoring an existing one, resolving redundant or repeating data, choosing keys, modeling relationships, or deciding where a constraint belongs.
正在显示 SKILL.md
基于 SOC 职业分类
| name | clean-code |
| description | Use when writing, reviewing, or refactoring code for maintainability and readability. Triggers on code reviews, naming discussions, function design, error handling, and test writing. Based on Robert C. Martin's Clean Code handbook with modern corrections. |
Comprehensive software craftsmanship guide based on Robert C. Martin's "Clean Code: A Handbook of Agile Software Craftsmanship", updated with modern corrections where the original 2008 advice has been superseded. Contains 48 rules across 10 categories, prioritized by impact to guide code reviews, refactoring decisions, and new development. Examples are primarily in Java but principles are language-agnostic.
Reference these guidelines when:
| Priority | Category | Impact | Prefix |
|---|---|---|---|
| 1 | Meaningful Names | CRITICAL | name- |
| 2 | Functions | CRITICAL | func- |
| 3 | Comments | HIGH | cmt- |
| 4 | Formatting | HIGH | fmt- |
| 5 | Error Handling | HIGH | err- |
| 6 | Objects and Data Structures | MEDIUM-HIGH | obj- |
| 7 | Boundaries | MEDIUM-HIGH | bound- |
| 8 | Classes and Systems | MEDIUM-HIGH | class- |
| 9 | Unit Tests | MEDIUM | test- |
| 10 | Emergence and Simple Design | MEDIUM | emerge- |
name-intention-revealing - Use names that reveal intentname-avoid-disinformation - Avoid misleading namesname-meaningful-distinctions - Make meaningful distinctionsname-pronounceable - Use pronounceable namesname-searchable - Use searchable namesname-avoid-encodings - Avoid encodings in namesname-class-noun - Use noun phrases for class namesname-method-verb - Use verb phrases for method namesfunc-small - Keep functions smallfunc-one-thing - Functions should do one thingfunc-abstraction-level - Maintain one level of abstractionfunc-minimize-arguments - Minimize function argumentsfunc-no-side-effects - Avoid side effectsfunc-command-query-separation - Separate commands from queriesfunc-dry - Do not repeat yourselfcmt-express-in-code - Express yourself in code, not commentscmt-explain-intent - Use comments to explain intentcmt-avoid-redundant - Avoid redundant commentscmt-avoid-commented-out-code - Delete commented-out codecmt-warning-consequences - Use warning comments for consequencesfmt-vertical-formatting - Use vertical formatting for readabilityfmt-horizontal-alignment - Avoid horizontal alignmentfmt-team-rules - Follow team formatting rulesfmt-indentation - Respect indentation ruleserr-use-exceptions - Separate error handling from happy patherr-write-try-catch-first - Write try-catch-finally firsterr-provide-context - Provide context with exceptionserr-define-by-caller-needs - Define exceptions by caller needserr-avoid-null - Avoid returning and passing nullobj-data-abstraction - Hide data behind abstractionsobj-data-object-asymmetry - Understand data/object anti-symmetryobj-law-of-demeter - Follow the Law of Demeterobj-avoid-hybrids - Avoid hybrid data-object structuresobj-dto - Use DTOs for data transferbound-wrap-third-party - Wrap third-party APIsbound-learning-tests - Write learning tests for third-party codeclass-small - Keep classes smallclass-cohesion - Maintain class cohesionclass-organize-for-change - Organize classes for changeclass-isolate-from-change - Isolate classes from changeclass-separate-concerns - Separate construction from usetest-first-law - Follow the three laws of TDDtest-keep-clean - Keep tests cleantest-one-assert - One concept per testtest-first-principles - Follow FIRST principlestest-build-operate-check - Use Build-Operate-Check patternemerge-simple-design - Follow the four rules of simple designemerge-expressiveness - Maximize expressivenessRead individual reference files for detailed explanations and code examples:
| File | Description |
|---|---|
| references/_sections.md | Category definitions and ordering |
| assets/templates/_template.md | Template for new rules |
| metadata.json | Version and reference information |