一键导入
typescript-engineer
Use when writing TypeScript code - covers types, error handling, style, and patterns
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Use when writing TypeScript code - covers types, error handling, style, and patterns
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
Use when producing product artifacts - epics, user stories, acceptance criteria, or analytics specs.
Use when defining product direction, vision document sections, or roadmap. Triggers on strategic product planning, vision creation, or vision document quality review.
Use when designing UI, choosing colors, typography, spacing, creating visual hierarchy, or making design decisions. Based on Refactoring UI by Wathan & Schoger.
Use when someone needs a plain-language explanation of how an existing feature or edge case behaves in the codebase. Triggers - non-technical stakeholder asks how something works, need code-informed functional explanation, need to understand rules or edge cases without implementation planning.
Use when a developer wants to go from rough idea to working code autonomously. Triggers - imperfect prompt, solo dev wants full pipeline, "just build it", idea to implementation without manual steps.
Use when creating a new agentic workflow skill. Triggers - need new multi-step orchestrated process, want to add workflow to agentic framework, building spec-driven pipeline.
基于 SOC 职业分类
| name | typescript-engineer |
| description | Use when writing TypeScript code - covers types, error handling, style, and patterns |
Rules for writing production-grade TypeScript. Covers type safety, error handling, code style, and patterns.
.ts or .tsx| Priority | Category | Rules |
|---|---|---|
| CRITICAL | Core Principles | core-principles.md |
| CRITICAL | Typing | typing.md |
| CRITICAL | Switch Exhaustiveness | switch-exhaustiveness.md |
| HIGH | Error Handling | error-handling.md |
| HIGH | Code Style | code-style.md |
| MEDIUM | Imports | imports.md |
| MEDIUM | Strategy Pattern | strategy-pattern.md |
| Red Flag | Fix |
|---|---|
type for object shapes | Use interface |
Missing readonly on properties | Add readonly everywhere |
readonly inside z.object({}) | Remove - runtime JS, not type syntax |
any or as casts | unknown + narrowing or type guards |
| Explicit return types | Inference + as const / satisfies |
| Function overloads | Union returns instead |
| Throwing in domain logic | Result<T, E> |
Switch without satisfies never | Add default with satisfies never |
| Nesting > 3 levels | Extract functions |
| Abbreviated variable names | Full names |
| Mixed type/value imports | Separate import type from values |
Rules are in the rules/ folder. Each follows rules/_template.md format.
When writing TypeScript, check rules by priority (CRITICAL first). Apply all applicable rules.