القائمة
Use when TypeScript work involves naming, abstractions, classes, local reasoning, semantic centers, full cutovers, type assertions, or design cleanup.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when designing, reviewing, refactoring, or implementing code that should stay simple, testable, readable, and sustainable. Covers investigation, architecture, dependency boundaries, cohesive units, naming, and clear plans. Also use when code hides I/O or dependencies, adds unnecessary layers, mixes business and infrastructure concerns, or fragments one flow across tiny helpers.
Makes answers easier to start reading, scan, resume, and understand without losing important detail. Use when the user asks for simpler, clearer, less dense, dyslexia-friendly, step-by-step, more scannable, more natural, less robotic, less AI-sounding, or better explained answers.
Use when TypeScript code design, implementation, review, debugging, or testing needs focused guidance on coding standards, boundaries, composition, configs, async control, error handling, observability, security, or testing. Do not use for prose-only, formatting-only, or history requests that merely mention TypeScript.
| name | typescript-coding-standards |
| description | Use when TypeScript work involves naming, abstractions, classes, local reasoning, semantic centers, full cutovers, type assertions, or design cleanup. |
Use this skill for local design quality in owned TypeScript code: names, abstractions, classes, semantic centers, and cutovers.
| If you see... | Read |
|---|---|
| wrapper, base class, shared helper, interface, manager, adapter-like abstraction | rules/abstraction-and-local-reasoning.md |
| class proposed for stateless behavior | rules/functions-vs-classes.md |
| confusing name, leaked implementation word, hidden important branch | rules/naming-and-semantic-center.md |
| old and new implementations coexisting | rules/cutovers.md |
!, as, as unknown as, as any, @ts-ignore, non-null assertion, forced type | rules/type-narrowing-over-assertion.md |
| blank-line groups in a function, comment labels, long function, mixed levels of abstraction, extraction question, reader must jump up/down through helpers | rules/vertical-discipline.md |
| same-shape primitives mixed (UserId vs OrderId), validated value losing its proof | rules/branded-and-opaque-types.md |
switch on union without default: never, "what if a new variant is added", silent fallback | rules/exhaustive-narrowing.md |
function copy-pasted per type, generic with any, conditional/mapped type question | rules/generics-and-conditional-types.md |
Abstraction cost and local reasoning.
Function vs class defaults.
Names in owned code.
Clean cutover policy.
Type narrowing over assertion as hard gate.
Branded types and nominal typing for domain primitives.
Exhaustive narrowing of discriminated unions.
Generics, conditional types, and mapped types — when each earns itself.
Vertical discipline: comment labels first, then extraction by responsibility.
../typescript-boundaries/SKILL.md.../typescript-composition/SKILL.md.../typescript-configs/SKILL.md.../typescript-testing/SKILL.md.Preserve local reasoning. Add structure only when it removes more confusion than it creates.