Typescript Discipline
Write or review TypeScript production code, shared domain types, schemas, API/client contracts, exported functions, typed React, casts, any/unknown, ts-ignore, narrowing, and package-script verification.
Install
$ agentstack add skill-jesse-merhi-skills-typescript-discipline ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-jesse-merhi-skills-typescript-discipline) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
TypeScript Discipline
Use TypeScript to model the real contract. Prefer named types, validated boundaries, and compiler-checked narrowing over casts or informal object shapes.
Workflow
- Reuse existing exported domain, schema, API/client, route, and module
contract types before creating local ones.
- Place types at the boundary where the concept belongs.
- Apply the boundary and data-shape rules in
[type-boundaries.md](references/type-boundaries.md).
- Avoid unsafe typing using [unsafe-types.md](references/unsafe-types.md).
- Before writing library/framework code, check installed versions and use
current docs for that version.
- Verify with repo scripts using [verification.md](references/verification.md).
Required Discipline
- Do not use
anywithout asking the user first. - Do not add
@ts-ignoreor@ts-expect-errorunless the user asks, and explain
why in the comment.
- Model structured data first. Serialize strings, cache keys, and protocol
values only at an explicit boundary.
Context Pointers
- Use [type-boundaries.md](references/type-boundaries.md) for shared/local type
placement and data modeling.
- Use [unsafe-types.md](references/unsafe-types.md) for
any,unknown,
non-null assertions, casts, and TS comments.
- Use [verification.md](references/verification.md) for return types, package
scripts, and monorepo checks.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: jesse-merhi
- Source: jesse-merhi/skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.