메뉴
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에서 현재 제공할 수 있는 파일을 다운로드하세요.
SOC 직업 분류 기준
SKILL.md 표시 중
| 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 |
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.