typescript-dev
Build Safer TypeScript Projects
TypeScript projects often develop inconsistent types, documentation, and validation workflows. This skill applies strict conventions and practical review checks for safer, maintainable code.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "typescript-dev" from https://skillstore.io/skills/cain96-typescript-dev.md and its manifest at https://skillstore.io/api/skills/cain96-typescript-dev/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "typescript-dev". Review a service that returns untyped data and catches every error as unknown.
Expected outcome:
- Define the service response with a validated UserData type.
- Return a discriminated result for success and failure.
- Narrow unknown errors before exposing an error message.
- Add tests for malformed responses and request failures.
Using "typescript-dev". Suggest a quality checklist for a small TypeScript library.
Expected outcome:
- Enable strict compiler checks and use ES modules.
- Document public exports when intent is not clear.
- Run formatting, linting, type checks, and tests through pnpm.
- Keep coverage above the agreed project threshold.
Using "typescript-dev". Review a React component with repeated renders and broad type assertions.
Expected outcome:
Replace broad assertions with narrowed props and type guards. Measure render cost before adding memoization, then test loading and error states.
Security Audit
SafeAll 33 static findings are false positives caused by Markdown prose, code fences, routine pnpm commands, or illustrative TypeScript. No hidden execution, data exfiltration, system reconnaissance, or prompt injection was found.
Risk Factors
⚡ Contains scripts (2)
⚙️ External commands (26)
🌐 Network access (1)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/cain96-typescript-dev/audits/12?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/cain96-typescript-dev?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/cain96-typescript-dev?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/cain96-typescript-dev/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/cain96-typescript-dev.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
Cain96. (2026). typescript-dev security audit report (audit version 12) [Author version unspecified]. Skillstore. https://skillstore.io/skills/cain96-typescript-dev/audits/12BibTeX citation
@techreport{cain96-cain96-typescript-dev-2026,
author = {Cain96},
title = {typescript-dev security audit report (audit version 12)},
institution = {Skillstore},
year = {2026},
number = {12},
url = {https://skillstore.io/skills/cain96-typescript-dev/audits/12},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "typescript-dev security audit report (audit version 12)"
version: "unspecified"
type: report
authors:
- name: "Cain96"
date-released: "2026-07-13"
url: "https://skillstore.io/skills/cain96-typescript-dev/audits/12"
identifiers:
- type: other
value: "skillstore:cain96-typescript-dev:audit:12"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Start a Strict TypeScript Project
Establish strict compiler settings, pnpm commands, module conventions, and documentation rules for a new codebase.
Review a TypeScript Change
Check a pull request for unsafe types, weak error handling, missing tests, and unclear public API documentation.
Improve React Type Safety
Refine React components with type-only imports, careful memoization, lazy loading, and reusable generic types.
Try These Prompts
Review this TypeScript file for strict typing, clear errors, ES module usage, and appropriate TSDoc. Explain each recommended change.
Create a TypeScript quality workflow for this project using pnpm. Include formatting, linting, type checking, tests, coverage, and a review checklist.
Refactor these TypeScript modules to remove any, reduce assertions, add type guards, and preserve behavior. Describe important type design decisions.
Audit this React TypeScript feature for API types, asynchronous errors, render performance, lazy loading, tests, and maintainability. Prioritize findings by impact.
Best Practices
- Share relevant project configuration, package scripts, and code so recommendations match the existing toolchain.
- Ask for prioritized findings when reviewing large changes, then address type correctness before performance tuning.
- Run the project formatter, linter, type checker, and tests after applying recommendations.
Avoid
- Do not request a broad rewrite without defining behavior, compatibility, and testing constraints.
- Do not apply memoization or type assertions automatically without evidence that they solve a real problem.
- Do not treat the suggested coverage percentage as proof of meaningful test quality.