菜单
Google TypeScript style guide for writing clean, consistent, type-safe code. This skill should be used when writing, reviewing, or refactoring TypeScript code. Triggers on TypeScript files, type annotations, module imports, class design, and code style decisions.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/pproenca/dot-skills --skill ts-google命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
基于 SOC 职业分类
| name | ts-google |
| description | Google TypeScript style guide for writing clean, consistent, type-safe code. This skill should be used when writing, reviewing, or refactoring TypeScript code. Triggers on TypeScript files, type annotations, module imports, class design, and code style decisions. |
Comprehensive TypeScript style guide based on Google's internal standards, designed for AI agents and LLMs. Contains 45 rules across 8 categories, prioritized by impact to guide automated refactoring and code generation.
Reference these guidelines when:
| Priority | Category | Impact | Prefix |
|---|---|---|---|
| 1 | Module Organization | CRITICAL | module- |
| 2 | Type Safety | CRITICAL | types- |
| 3 | Class Design | HIGH | class- |
| 4 | Function Patterns | HIGH | func- |
| 5 | Control Flow | MEDIUM-HIGH | control- |
| 6 | Error Handling | MEDIUM | error- |
| 7 | Naming & Style | MEDIUM | naming- |
| 8 | Literals & Coercion | LOW-MEDIUM | literal- |
module-named-exports - Use named exports over default exportsmodule-no-mutable-exports - Avoid mutable exportsmodule-es6-modules - Use ES6 modules exclusivelymodule-no-namespaces - Avoid TypeScript namespacesmodule-import-paths - Use relative paths for project importsmodule-import-type - Use import type for type-only importsmodule-export-api-surface - Minimize exported API surfacetypes-no-any - Never use the any typetypes-prefer-interfaces - Prefer interfaces over type aliases for objectstypes-explicit-structural - Explicitly annotate structural typestypes-nullable-patterns - Handle nullable types correctlytypes-array-syntax - Use consistent array type syntaxtypes-no-wrapper-types - Never use wrapper object typestypes-prefer-map-set - Prefer Map and Set over index signaturestypes-no-empty-object - Avoid empty object typeclass-parameter-properties - Use parameter properties for constructor assignmentclass-readonly-properties - Mark properties readonly when never reassignedclass-no-private-fields - Use TypeScript private over private fieldsclass-no-static-containers - Avoid container classes with only static membersclass-constructor-parens - Always use parentheses in constructor callsclass-no-prototype-manipulation - Never manipulate prototypes directlyfunc-declarations-over-expressions - Prefer function declarations over expressionsfunc-arrow-concise-bodies - Use concise arrow function bodies appropriatelyfunc-avoid-this-rebinding - Avoid rebinding thisfunc-rest-parameters - Use rest parameters over argumentsfunc-generator-syntax - Use correct generator function syntaxfunc-default-parameters - Use default parameters sparinglycontrol-always-use-braces - Always use braces for control structurescontrol-triple-equals - Always use triple equalscontrol-for-of-iteration - Prefer for-of over for-in for arrayscontrol-switch-default - Always include default case in switchcontrol-no-assignment-in-condition - Avoid assignment in conditional expressionserror-throw-errors - Always throw Error instanceserror-catch-unknown - Type catch clause variables as unknownerror-empty-catch-comments - Document empty catch blockserror-avoid-assertions - Avoid type and non-null assertionsnaming-identifier-styles - Use correct identifier naming stylesnaming-descriptive-names - Use descriptive namesnaming-no-decorative-underscores - Avoid decorative underscoresnaming-no-interface-prefix - No I prefix for interfacesnaming-constants - Use CONSTANT_CASE for true constantsliteral-single-quotes - Use single quotes for stringsliteral-number-formats - Use correct number literal formatsliteral-explicit-coercion - Use explicit type coercionliteral-array-constructor - Avoid Array constructorRead individual reference files for detailed explanations and code examples:
| File | Description |
|---|---|
| AGENTS.md | Complete compiled guide with all rules |
| 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.