About typescript-coding-standards
A TypeScript coding skill for applying and reviewing repository-aware conventions across frontend, backend, worker, and shared-library changes. It prioritizes local instructions and relevant guides without requiring adoption of new tooling.
Key features
- 01Repository-specific instruction checks
- 02Guides for common coding tasks
- 03Frontend and backend conventions
- 04Scope-conscious change guidance
Use cases
- 01Writing or reviewing TypeScript
- 02Refactoring functions and types
- 03Changing dependencies or modules
- 04Verifying code and tests
Install
Copy the command and run it in a terminal.
npx skills add https:/After installing, type/typescript-coding-standardsin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
rules/comments.mddependencies.mdfile-naming-and-size.mdmodules.mdreact.mdruntime.mdtesting.mdtooling.mdtypescript.mdDetails
From the project READMETypeScript Coding Standards
Apply these conventions when writing, reviewing, or refactoring TypeScript in frontend apps, backend services, workers, and shared libraries.
Read the target repository's AGENTS.md, package scripts, and lint/test
configuration first. Explicit local requirements take precedence over these
shared defaults. Keep changes within the requested scope; existing violations
do not justify an unrelated repository-wide migration.
Guides
Read the guides relevant to the change before editing.
| Guide | Read when |
|---|---|
| TypeScript contracts | Writing or reviewing functions, arguments, types, or constants. |
| File naming and size | Creating, renaming, or splitting files. |
| Comments and JSDoc | Documenting functions, types, or non-obvious logic. |
| Modules and organization | Choosing exports, import boundaries, or where code belongs. |
| Dependencies and catalogs | Adding or updating dependencies, package manifests, catalogs, or lockfiles. |
| Runtime behavior | Handling errors, external data, service dependencies, or backend import boundaries. |
| React and Next.js | Changing components, callbacks, or hooks; read the Next.js section only in Next.js apps. |
| Testing | Deciding whether a test is useful, adding coverage, or reviewing assertions. |
| Tooling and verification | Selecting tools or validating a code change. |
For backend-only work, skip the React guide. Use the consumer's existing tooling and runtime conventions; the skill does not require adopting another repo's framework, formatter, or dependencies.