TypeScript Style Guide skill
An agent skill with TypeScript conventions: types, discriminated unions, functions, naming, source layout, React and tests, loaded per topic
- 786 ★ on the repository
- Last commit
- MIT
Minimal access
Why this level
- The skill is only conventions and reference text; it runs no code
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/typescript-style-guideDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- The skill is only conventions and reference text; it runs no code
This is third-party code. Review the repository files before installing.
What it does
The skill brings an opinionated TypeScript guide into a format for a coding agent so it applies a consistent style while writing and reviewing code. The complete skill routes by topic and reads only the reference the task needs, so it does not take extra context. Focused single-topic skills are available too: types, discriminated unions, functions, variables, naming, source organization, React and tests. It does not duplicate rules that TypeScript, linters and formatters already enforce, and it puts the repository's own conventions above its recommendations. It installs through npx skills add with a choice of which skill to add.
Who it is for. For TypeScript and React developers who want a consistent code style without style debates in review.
Good fit when
- You want the agent to apply a consistent TypeScript style while writing and reviewing code
- You need guidance on a single topic: types, functions, naming, React or tests
- You want to remove code-style debates from review
Not a fit when
- You only need a linter or formatter; the skill deliberately does not duplicate their rules
- The project is not written in TypeScript
Example request
Review this module against our TypeScript guideLimitations
The guide is opinionated, and the repository's own conventions take precedence. The skill applies only to TypeScript tasks, not to layout or styling. Installation runs through npx, so Node is required.
How to disable. Remove the installed skill folder from your agent's skills directory.
FAQ
Does it replace ESLint and Prettier?
No. It deliberately avoids duplicating what a linter and formatter enforce and covers conventions that cannot be expressed as a tool rule.
Can I install just one topic?
Yes, each topic has its own skill added with the --skill flag, for example typescript-react or typescript-tests.
Discussion
No questions or reviews yet.
Related
SkillsA code review skill across many languages and frameworks: architecture, performance, security, anti-patterns and common bugs
An Effect v4 skill for TypeScript: schemas, services and layers, config, retries, caches, streams, the HTTP client and tests with virtual time
A skill that installs a set of Oxlint rules catching low-quality TypeScript and JavaScript patterns often left by code generation
Five skills for TypeScript: Effect 3 and 4 code review, service and layer rules, tech debt cleanup and a plan-to-merge PR loop
Two skills for the tsdown bundler: setting up TypeScript library builds and migrating a project from tsup
Agent Skills (AsyrafHussin)
Agent Skills
24 skills for Laravel, PHP, React and TypeScript: code rules, testing, security, technical debt and documentation.
README in short
The README presents the project as a TypeScript style guide and, at the same time, a set of skills for a coding agent. Skills install via npx skills add with an interactive choice or a flag for a specific topic. The complete skill loads only the sections relevant to the task, while focused skills provide individual topics independently. The rationale section argues that a shared approach to code speeds up development and removes style debates from review. The full guide text is on the project site, MIT licensed.
README badge
Original SKILL.md
--- name: typescript-style-guide description: Apply, review, and explain the opinionated conventions in the TypeScript Style Guide. Use automatically only when TypeScript conventions are part of the requested task, including type modelling, discriminated unions, function APIs, variables and state, naming, source organization, React props, component APIs, state management, data flow, or tests. Do not use for styling or layout alone. --- # TypeScript Style Guide Apply only the conventions relevant to the current task. Keep TypeScript, linters, and formatters responsible for rules they can enforce automatically. ## Workflow 1. Inspect the consuming repository's conventions and configuration. 2. Let explicit repository conventions take precedence over this opinionated guide. 3. Identify which guide topic applies. 4. Read only the reference for the task's primary guide topic. Read multiple references only when the task substantively spans multiple topics. 5. Apply, review, or explain the conventions in the context of the current task. 6. State important tradeoffs when a convention depends on context or judgment.