How do I install the Busirocket Typescript Standards skill?

Run npx skillmds@latest add busirocket/busirocket-typescript-standards in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Busirocket Typescript Standards safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Busirocket Typescript Standards?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Busirocket Typescript Standards free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Busirocket Typescript Standards?

busirocket (@busirocket) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Busirocket Typescript Standards by busirocket

Name: Busirocket Typescript Standards
Author: busirocket

File contents

TypeScript + React Standards

Strict, reusable standards for TypeScript/React projects.

When to Use

Use this skill when:

Writing or refactoring .ts / .tsx
Moving inline types into types/
Enforcing consistent type naming and result shapes
Working in Next.js where special files allow extra exports

Non-Negotiables (MUST)

One exported symbol per file for your own modules.
No inline interface/type in components/hooks/utils/services/route handlers.
Put shared shapes under types/<area>/... (one type per file).
Avoid barrel files (index.ts) that hide dependencies.
After meaningful changes: run the project's standard checks (e.g. yarn check:all).

Next.js Special-file Exceptions

app/**/page.tsx, app/**/layout.tsx: allow default export + metadata/generateMetadata/viewport (etc.).
app/api/**/route.ts: allow multiple HTTP method exports and route config exports.

Rules

TypeScript Standards

ts-language-style - Language & style (interface vs type, const vs let, English-only)
ts-one-thing-per-file - One thing per file (STRICT)
ts-nextjs-exceptions - Next.js special-file exceptions
ts-types-strict - Types (STRICT) - no inline types
ts-helpers-strict - Helpers (STRICT) - no helpers in components/hooks
ts-nextjs-hygiene - Next.js TS hygiene (docs-aligned)
ts-validation - Validation (run checks after changes)

Types Conventions

types-one-type-per-file - One type per file (STRICT)
types-naming-patterns - Naming patterns (Params, Result, Error, Props)
types-result-shape - Result shape for boundaries that can fail
types-where-allowed - Where types are allowed

Related Skills

busirocket-core-conventions - General file structure (one-thing-per-file, boundaries)
busirocket-react - Component and hook structure
busirocket-refactor-workflow - Refactoring workflow for TypeScript/React

How to Use

Read individual rule files for detailed explanations and code examples:

rules/ts-one-thing-per-file.md
rules/ts-types-strict.md
rules/types-one-type-per-file.md

Each rule file contains:

Brief explanation of why it matters
Code examples (correct and incorrect patterns)
Additional context and best practices

---name: busirocket-typescript-standardsdescription: Enforces TypeScript standards for maintainable codebases. Use when creating or refactoring TS/TSX to enforce one-thing-per-file, type conventions, and Next.js special-file export exceptions.---# TypeScript + React StandardsStrict, reusable standards for TypeScript/React projects.## When to UseUse this skill when:- Writing or refactoring `.ts` / `.tsx`- Moving inline types into `types/`- Enforcing consistent type naming and result shapes- Working in Next.js where special files allow extra exports## Non-Negotiables (MUST)- **One exported symbol per file** for your own modules.- **No inline `interface`/`type`** in components/hooks/utils/services/route handlers.- Put shared shapes under `types/<area>/...` (**one type per file**).- Avoid barrel files (`index.ts`) that hide dependencies.- After meaningful changes: run the project's standard checks (e.g. `yarn check:all`).## Next.js Special-file Exceptions- `app/**/page.tsx`, `app/**/layout.tsx`: allow `default export` + `metadata/generateMetadata/viewport` (etc.).- `app/api/**/route.ts`: allow multiple HTTP method exports and route config exports.## Rules### TypeScript Standards- `ts-language-style` - Language & style (interface vs type, const vs let, English-only)- `ts-one-thing-per-file` - One thing per file (STRICT)- `ts-nextjs-exceptions` - Next.js special-file exceptions- `ts-types-strict` - Types (STRICT) - no inline types- `ts-helpers-strict` - Helpers (STRICT) - no helpers in components/hooks- `ts-nextjs-hygiene` - Next.js TS hygiene (docs-aligned)- `ts-validation` - Validation (run checks after changes)### Types Conventions- `types-one-type-per-file` - One type per file (STRICT)- `types-naming-patterns` - Naming patterns (Params, Result, Error, Props)- `types-result-shape` - Result shape for boundaries that can fail- `types-where-allowed` - Where types are allowed## Related Skills- `busirocket-core-conventions` - General file structure (one-thing-per-file, boundaries)- `busirocket-react` - Component and hook structure- `busirocket-refactor-workflow` - Refactoring workflow for TypeScript/React## How to UseRead individual rule files for detailed explanations and code examples:```rules/ts-one-thing-per-file.mdrules/ts-types-strict.mdrules/types-one-type-per-file.md```Each rule file contains:- Brief explanation of why it matters- Code examples (correct and incorrect patterns)- Additional context and best practices

Frequently asked questions

Busirocket Typescript Standards