type-safety-rules
/type-safety-rules
20 rules across 7 categories, each with detection and fix guidance. TRIGGER WHEN: reviewing or hardening TypeScript against type-system erosion: `any` leakage, unsound casts, missing boundary validation, assertion abuse, tsconfig strictness, exhaustiveness and generics soundness. DO NOT TRIGGER WHEN: style and naming review (use typescript-write), or dead-code detection (use knip).
- Author
- acaprino ↗
- Repository
- alfio-claude-plugins ↗
- Licence
- MIT
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 25
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 1
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
20 rules across 7 categories, each with detection and fix guidance. TRIGGER WHEN: reviewing or hardening TypeScript against type-system erosion: `any` leakage, unsound casts, missing boundary validation, assertion abuse, tsconfig strictness, exhaustiveness and generics soundness. DO NOT TRIGGER WHEN: style and naming review (use typescript-write), or dead-code detection (use knip).
Original author description
20 rules across 7 categories, each with detection and fix guidance. TRIGGER WHEN: reviewing or hardening TypeScript against type-system erosion: `any` leakage, unsound casts, missing boundary validation, assertion abuse, tsconfig strictness, exhaustiveness and generics soundness. DO NOT TRIGGER WHEN: style and naming review (use typescript-write), or dead-code detection (use knip).
How it works
- Review evidence
- Rule Categories by Priority
- Quick Reference
- How to Use
- Load map
SKILL.md preview
--- name: type-safety-rules description: > 20 rules across 7 categories, each with detection and fix guidance. TRIGGER WHEN: reviewing or hardening TypeScript against type-system erosion: `any` leakage, unsound casts, missing boundary validation, assertion abuse, tsconfig strictness, exhaustiveness and generics soundness. DO NOT TRIGGER WHEN: style and naming review (use typescript-write), or dead-code detection (use knip). --- <daodan_host_binding host="claude"> This binding governs execution of this package and its loaded references. It takes precedence over executable examples written for another host. Use only registered tools and their actual input schema; an example never creates a tool, argument, permission, model alias or nested worker capability. Preserve the generated worker allowlist, dependency closure, scope and delivery contracts. Claude binding: repository tools are Read/Glob/Grep and Write/Edit; shell execution uses Bash and network fetch uses WebFetch. Pass the executable string in Bash's command field, and use its registered timeout/background schema. Worker dispatch uses the available native Agent mechanism and its registered agent-selection and prompt fields. Do not turn a prose role label into an invented role argument. Inherit the session model unless the declared workflow and active schema permit an override. Load installed skills by qualified ID; named roles use their owning plugin's agent identity, while workflow entries use /<plugin>:<workflow>. Required foreign providers use Claude's marketplace/install commands: claude plugin marketplace add <source>, then claude plugin install <provider>@<marketplace>. A provider that is installed but disabled is enabled with claude plugin enable <provider>@<marketplace>; check `claude plugin list --json` before the first phase, and stop with that command when any plugin of this package's dependency closure, direct or transitive, is off. A declared package MCP server is configured through the generated MCP manifest; still check its tools are actually available in the active session. The executing agent and its coordinator own continuation, recovery, verification and delivery. Skills supply knowledge and method instructions; they are not executors or a runtime persistence mechanism. Resolve each component by kind and exact installed identity. A role is dispatched as a worker, a skill loads instructions, and a workflow starts its declared method. Kernel owner-qualified skill references are logical provider identities: resolve them to the actual host registry name and verified installed provider path. Do not invent a registry string by adding an owner's prefix when the host does not use it. Do not load an agent identity as a skill or execute a workflow name as a shell command. Declared required foreign providers remain mandatory. If a required provider or capability (including required MCP access or isolation) is unavailable, stop its dependent phase and report the missing capability. Optional external providers follow the method's declared selection and absence behavior; their absence alone does not block the base workflow. Report any explicitly requested but unavailable provider contribution as unfulfilled and continue independent work. Do not install a different host's plugin or substitute unrelated skills to claim coverage. Shell execution alone does not establish interactive stdin. Before a capture or checkpoint, use an available session-control mechanism. When stdin is unavailable, keep user-driven capture in a supported background process with bounded output and an explicit stop signal controlled by the coordinator after the user's completion message. Close owned browser/process resources on completion or cancellation. Continue working within the current authorization while the requested result is achievable. After a tool error, inspect its cause, correct the relevant input or implementation, retry when justified and verify the outcome; never repeat a failing action blindly. Do not close the turn with a promise or a partial result when an authorized next step can still produce or verify the requested result. Stop only for a documented real impediment, a missing required capability, an unresolved human decision or the caller's stop request. At that boundary, report completed results, remaining work and the concrete prerequisite for continuation; continue any independent work that the blocker does not prevent. A tool's successful exit, a worker stop or an idle session is not the deliverable. Return final text naming observed findings, artifact paths, executed checks and blockers. An empty worker result is missing delivery: inspect or resume that worker when permitted, or record failure. Verify required artifacts and candidate gates before marking the requested outcome complete. This is an execution binding, not a rewrite of source examples. Preserve programming language fences, domain code and host APIs that are the subject of marketplace-ops or agent-sdk-builder. A host-as-subject API is not a tool provided to this session. Compiled binding and static checks do not prove an installed host executed a run. </daodan_host_binding> # TypeScript Type-Safety Rules Review-oriented rule set for hunting type-system erosion in TypeScript codebases. 20 rules across 7 categories, prioritized by blast radius. Used as the audit checklist by the `type-safety-auditor` agent and usable standalone while writing or hardening TypeScript. ## Review evidence Rule examples, grep hits and priority labels nominate candidates. Promote only a reachable type/runtime mismatch or a violated explicit project contract, after checking equivalent guards and effective inherited configuration. Missing preferred syntax, schema library or config flag alone is not a defect. Use impact-based severity and the caller’s report; no universal score. See [TypeScript configuration inheritance](https://www.typescriptlang.org/tsconfig/#extends). ## Rule Categories by Priority | Priority | Category | Impact | Prefix | |----------|----------|--------|--------| | 1 | Any Erosion | CRITICAL | `any-` | | 2 | Unsound Casts | CRITICAL | `cast-` | | 3 | Boundary Validation | CRITICAL | `boundary-` | | 4 | Assertion Abuse | HIGH | `assert-` | | 5 | Compiler Configuration | HIGH | `config-` | | 6 | Exhaustiveness | MEDIUM-HIGH | `exhaust-` | | 7 | Generics Soundness | MEDIUM | `generics-` | ## Quick Reference ### 1. Any Erosion (CRITICAL) - `any-explicit` - Replace explicit `any` with `unknown` plus narrowing - `any-implicit-boundary` - Type the results of `JSON.parse`, `response.json()`, and `catch` immediately - `any-generic-default` - Never default a type parameter to `any` ### 2. Unsound Casts (CRITICAL) - `cast-as-unsound` - An `as` cast that changes the shape needs a runtime check instead - `cast-double` - `as unknown as X` is a type-system bypass; write a guard or converter - `cast-const-assertion` - Use `as const` for literal narrowing instead of widening annotations ### 3. Boundary Validation (CRITICAL) - `boundary-http` - Parse HTTP payloads with a schema at the edge - `boundary-queue` - Validate queue and event messages before processing - `boundary-storage` - Validate and version storage reads (localStorage, files, DB JSON) - `boundary-env` - Access environment variables through one validated config module ### 4. Assertion Abuse (HIGH) - `assert-non-null` - `!` needs an adjacent invariant justification or a fail-fast check - `assert-ts-expect-error` - Use `@ts-expect-error` with a reason, never `@ts-ignore` ### 5. Compiler Configuration (HIGH) - `config-strict` - `"strict": true` is the baseline - `config-unchecked-index` - Enable `noUncheckedIndexedAccess` - `config-exact-optional` - Enable `exactOptionalPropertyTypes` - `config-skiplibcheck` - `skipLibCheck` may speed up third-party types, never hide first-party errors ### 6. Exhaustiveness (MEDIUM-HIGH) - `exhaust-switch-never` - Discriminated unions get a `never` assertion in the default branch - `exhaust-satisfies-record` - Use `satisfies Record<K, V>` for complete lookup tables ### 7. Generics Soundness (MEDIUM) - `generics-constraint` - Constrain type parameters on public APIs - `generics-type-guards` - A type predicate must verify the whole shape it claims ## How to Use Read individual rule files in the `rules/` directory for detailed explanations and code examples. Each rule file contains a brief explanation, an incorrect example, a correct example, and a detection hint for reviewers. ## Load map | Read | When | |------|------| | `rules/<rule-id>.md` | Confirming or fixing one rule's violation | | `references/audit.md` | Running the type-safety audit as a procedure (the TypeScript stack audit of `/daodan:check-health`): scope detection, tsc and ESLint ground truth, the isolated `type-safety-auditor` review and the scored report under the run directory |
Files in this package (25)
- SKILL.md 9 KB
- SKILL.toml 1 KB
- references/audit.md 10 KB
- rules/_sections.md 5 KB
- rules/_template.md 5 KB
- rules/any-explicit.md 6 KB
- rules/any-generic-default.md 6 KB
- rules/any-implicit-boundary.md 6 KB
- rules/assert-non-null.md 6 KB
- rules/assert-ts-expect-error.md 6 KB
- rules/boundary-env.md 6 KB
- rules/boundary-http.md 6 KB
- rules/boundary-queue.md 6 KB
- rules/boundary-storage.md 6 KB
- rules/cast-as-unsound.md 6 KB
- rules/cast-const-assertion.md 6 KB
- rules/cast-double.md 6 KB
- rules/config-exact-optional.md 6 KB
- rules/config-skiplibcheck.md 6 KB
- rules/config-strict.md 6 KB
- rules/config-unchecked-index.md 6 KB
- rules/exhaust-satisfies-record.md 6 KB
- rules/exhaust-switch-never.md 6 KB
- rules/generics-constraint.md 6 KB
- rules/generics-type-guards.md 6 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · acaprino/alfio-claude-plugins | 100 | MIT |
| acaprino/alfio-claude-plugins | 100 | MIT |
| acaprino/alfio-claude-plugins | 100 | MIT |
| acaprino/alfio-claude-plugins | 100 | MIT |
| acaprino/alfio-claude-plugins | 100 | MIT |
| acaprino/alfio-claude-plugins | 100 | MIT |
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 1116d7e98033 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100typescript-rules
Applies type safety and error handling rules. Enforces no-any policy and type guards. Use when implementing TypeScript or reviewing types. - 100typescript
Enforces modern TypeScript best practices for type-safe code, strict configuration, runtime validation, and clear type contracts. Use when writing or reviewing TypeScript/JavaScript code, configuring tsconfig.json, or when the user asks for TypeScript style guidance. - 100typescript-patterns
TypeScript discipline for any JavaScript/TypeScript project (frontend + backend): strict mode, type design, generics, narrowing, error types, module resolution, tsconfig hygiene. Apply when the project has `tsconfig.json` and `typescript` in devDependencies. Stack-agnostic —… - 100typescript-best-practices
TypeScript coding guidelines with dos and don'ts for type design and patterns. Use when writing, reviewing, or refactoring TypeScript code in projects with tsconfig.json or .ts/.tsx files. Trigger when the user asks to "review TypeScript code", "check my TS code", "write… - 100frontend-typescript-rules
Applies React/TypeScript type safety, component design, and state management rules. Use when implementing React components. - 100typescript-type-safety
TypeScript type safety patterns - unknown vs any, generics golden rule, null narrowing, inference discipline, import type, discriminated unions, error typing. Use when writing or reviewing TypeScript code for type correctness.