メニュー
TypeScript convention lens consulted BEFORE writing code — strictness, type-at-the-boundary, discriminated unions over booleans, and no-any hygiene. Appended to impl-conventions.txt by the stack-conventions pack. Also usable standalone.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | typescript-conventions |
| description | TypeScript convention lens consulted BEFORE writing code — strictness, type-at-the-boundary, discriminated unions over booleans, and no-any hygiene. Appended to impl-conventions.txt by the stack-conventions pack. Also usable standalone. |
When: consulted by plan-writer (to record type-design decisions) and by implement-feature (to apply them while coding), in projects where the stack-conventions pack is installed and the stack is TS. Not a review lens — shapes code as written; the code-review lens still audits it after.
Scope: TS the change introduces. Advisory knowledge, makes no edits.
strict: true. No implicit any. If a value's type is unknown at a boundary, type it unknown and narrow — never any to silence the compiler.as Foo) untrusted data into a type — casting is an assertion, not a check.{ status: 'loading' } | { status: 'ok'; data } | { status: 'error'; error }, not isLoading+data?+error?). Prefer readonly fields and as const for fixed sets.voided; no floating promises. Errors propagate as typed results or thrown typed errors — never swallowed in a bare catch {}.const object, named once and imported — not the same string literal retyped across files.?? / ?. for null-vs-undefined intent; reserve || for genuine boolean-falsy defaults.plan-writer: when the plan introduces a domain state machine or an external boundary, record the union/parse-at-edge decision in Decisões Técnicas.implement-feature: match the repo's existing validation lib and type-organization convention before introducing a new one — climb the laziness ladder (reuse existing).Ingest a raw source into the project's OKF knowledge bundle — distill it into concept pages, refresh the index, and log the change. keel's compounding "LLM wiki" loop.
Use when implementation is complete, gates pass, and you need to decide how to integrate the work — presents structured options (merge, PR, keep, discard) and handles the chosen workflow, including worktree cleanup. Closes the SDD cycle after review-and-simplify.
Use when executing implementation plans with independent tasks in the current session
Orchestrates the implement-feature, evaluator, fix-runner loop for the active feature until all Criterios de Aceitacao are met and quality gates are green.
Use after the plan is approved to break the active feature's plan into a concrete task checklist, written into specs/<feature>/tasks.md from the tasks template.
Use while implementing a feature that has retries, queues, background jobs, external calls, or any critical path an on-call engineer will need to reason about in production. Invoke when adding a new endpoint, dependency, or async flow, and before considering such a feature done — instrumentation is developed alongside the code, like tests, not bolted on after.