菜单
Use when writing or reviewing TypeScript — getting value from the type system (unknown over any, discriminated unions, narrowing, satisfies, readonly) and avoiding the escape hatches (any, unchecked as casts, non-null !) that silently defeat it.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when designing memory or persistent context for an agent — deciding what to persist vs. recompute, how to retrieve only what's relevant, and how to summarize/compact history to fit the context window. Use when an agent forgets, bloats its context, or repeats work.
Interactive installer for Rosetta. Guides users through selecting and installing skills and language-specific rules at user-level or project-level, verifies paths, and optionally optimizes installed files.
Instinct-based learning system that observes sessions via hooks, creates atomic instincts with confidence scoring, and evolves them into skills, commands, and agents.
Use when building or reviewing an evaluation for an LLM feature — assembling a representative test set, choosing pass criteria (exact match, programmatic checks, rubric, or LLM-as-judge), and catching regressions. Use when asking "how do I know this prompt or model change is better?"
Use when writing or reviewing a prompt for an LLM — making it specific, structured, and testable (clear task, role/context, examples, an explicit output contract, decomposition, room to reason) and avoiding the anti-patterns that make prompts brittle. Provider-agnostic.
Pattern for progressively refining context retrieval to solve the subagent context problem.
| name | writing-idiomatic-typescript |
| description | Use when writing or reviewing TypeScript — getting value from the type system (unknown over any, discriminated unions, narrowing, satisfies, readonly) and avoiding the escape hatches (any, unchecked as casts, non-null !) that silently defeat it. |
The point of TypeScript is to make illegal states unrepresentable and let the compiler catch
mistakes. Idiomatic TS works with the type system instead of around it. Assume strict: true.
{ kind: "ok"; value } | { kind: "err"; error }),
then switch on the tag — the compiler checks exhaustiveness.type aliases for unions/functions/mapped types; interface for object shapes that may be
extended or merged. Be consistent.type Mode = "r" | "w") over enum.readonly where it shouldn't mutate; use as const for literal tuples/objects.Pick, Omit, Partial, Record, ReturnType) before restating shapes.unknown, not any, at boundaries (JSON, catch) — then narrow with type guards.as casts; when unavoidable, cast to the narrowest type and comment why. Never
double-cast through unknown to silence an error.!; narrow instead (if (x == null) return).satisfies to check a value against a type without widening it.x is T) and in/typeof/instanceof narrowing over manual casts.async/await over raw .then chains; never leave a promise unawaited (handle or void it).map/filter/reduce) over mutation when it reads clearly.any (especially implicit), unchecked as, !, @ts-ignore without a justification.enum where a string-literal union would do; Function/Object/{} as types.American English in identifiers and comments.