Typescript Best Practices

TypeScript best practices. Use when reading or editing any .ts or .tsx file. Observe required inputs first; HOLD when they are missing rather than guessing.

38 stars 11 forksSoftware Development

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add jeremybrasher/grokbot-skills --skill typescript-best-practices
Manual install
git clone --depth 1 https://github.com/jeremybrasher/grokbot-skills.git /tmp/grokbot-skills
mkdir -p ~/.claude/skills
cp -r /tmp/grokbot-skills/collections/pstack/skills/typescript-best-practices ~/.claude/skills/typescript-best-practices

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# TypeScript best practices

## When to use

Reading or editing any .ts or .tsx file; apply TypeScript best practices.

**Do not use when:**
- Non-TypeScript files
- No code to read or edit
- User asked for a language migration plan, not TS practice

## Intake — before you proceed

You need all of the following. If any is missing, stop.

1. Named .ts/.tsx files or an edit task in TypeScript
2. Readable project TS config / patterns when advising project-wide norms

If any is missing, stop. Say what is missing and what you need. Do not invent inputs to keep moving.

## HOLD — stop and return this, not a polished guess

When you cannot proceed, return the gap.

| Condition | What is missing | What it needs | Return instead |
|---|---|---|---|
| No TS file in scope | A .ts/.tsx target | Path or paste | Holding. |
| Advice would fight stated project tsconfig | Alignment with project config | Read tsconfig or ask | Do not invent a rival house style. |
| Would add types that invent domain facts | Types grounded in code | Observe first | Holding speculative types. |

A HOLD is a return value, not a delay before you guess.

## Defaults: cut first

This operation defaults to less, not more.

- Prefer existing project patterns
- Do not add utility types unasked
- Smallest typing fix
- Expansion needs evidence from the request or the observed system — not from a habit of completeness.

## Will not produce

- any to silence errors without a plan
- Drive-by refactors while typing
Read the full skill on GitHub

Details

Skill name
typescript-best-practices
Path
collections/pstack/skills/typescript-best-practices/SKILL.md
Repo updated
15 September 2026

FAQ

What does the Typescript Best Practices skill do?

TypeScript best practices. Use when reading or editing any .ts or .tsx file. Observe required inputs first; HOLD when they are missing rather than guessing.

How do I install the Typescript Best Practices skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add jeremybrasher/grokbot-skills --skill typescript-best-practices. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Typescript Best Practices popular?

It lives in jeremybrasher/grokbot-skills, which has 38 GitHub stars and 11 forks.

Related skills

Anti Patterns

38

jeremybrasher/grokbot-skills

Catalogue of known SDLC anti-patterns that great_cto agents must actively reject when reviewing architecture, plans, code, or post-mortems. Used by architect (pre-impl), pm (planning), senior-dev (impl), l3-support (post-incident).

Software Development11

Anydesign

38

jeremybrasher/grokbot-skills

Analyze images, websites, and Figma files to extract their design and generate a `design.md` with token system, component inventory, and reconstruction notes. Use this skill whenever the user wants to understand, document, replicate, or audit the design of something visual: a screenshot, a URL, a Figma link, a Pinterest reference, a mockup, a competitor's site, a component, a dashboard, a landing page. Also when they ask 'extract the design system from X', 'document the style of Y', 'analyze this visually', 'convert this image into tokens', 'help me replicate this design', 'what palette does t

Frontend & Design11

Archetype Review Base

38

jeremybrasher/grokbot-skills

Shared review framework that every domain reviewer (pci, oracle, gov, edtech, healthcare, mlops, etc.) MUST follow. Defines the output artifact (TM-{slug}.md), mandatory sections, severity scale, verdict format, the workflow scaffold (when-invoked, Step-0 read-inputs, HANDOFF), and the "domain heuristic vs generic check" boundary. Eliminates duplication across the ~30 reviewer prompts.

Finance & Crypto11

Well Architected

38

jeremybrasher/grokbot-skills

6-pillar architecture review framework. Adapted from AWS Well-Architected for use by great_cto's architect agent on every non-nano ARCH document. Forces explicit answers across operational excellence, security, reliability, performance, cost, and sustainability — not just feature design.

Software Development11

Test Driven Development

38

jeremybrasher/grokbot-skills

Use when implementing any feature or bugfix, before writing implementation code. Observe the required behavior first. Do not use it to keep a green suite that encodes the wrong object, to write tests after the code, or to ship production code without a failing test.

Software Development11

Activity Program Senior

39

lionelsimai/claude-skills-collection

Design activity programs for senior engagement. TRIGGERS - Use when user needs help with activity-program-senior related tasks.

Software Development

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.