rulebook-typescript
TypeScript development with strict mode, Vitest testing, ESLint linting, and CI/CD best practices. Use when working on TypeScript projects, writing tests, configuring linting, or setting up build pipelines.
Best use case
rulebook-typescript is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
TypeScript development with strict mode, Vitest testing, ESLint linting, and CI/CD best practices. Use when working on TypeScript projects, writing tests, configuring linting, or setting up build pipelines.
Teams using rulebook-typescript should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/rulebook-typescript/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How rulebook-typescript Compares
| Feature / Agent | rulebook-typescript | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
TypeScript development with strict mode, Vitest testing, ESLint linting, and CI/CD best practices. Use when working on TypeScript projects, writing tests, configuring linting, or setting up build pipelines.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# TypeScript Development Standards
## Quality Check Commands
Run these commands after every implementation:
```bash
npm run type-check # TypeScript type checking
npm run lint # ESLint (0 warnings required)
npm run format # Prettier formatting
npm test # Run all tests
npm run test:coverage # Coverage check (95%+ required)
npm run build # Build verification
```
## TypeScript Configuration
Use TypeScript 5.3+ with strict mode:
```json
{
"compilerOptions": {
"target": "ES2022",
"module": "ESNext",
"moduleResolution": "node",
"strict": true,
"esModuleInterop": true,
"noUnusedLocals": true,
"noUnusedParameters": true,
"noImplicitReturns": true
}
}
```
## Code Quality Rules
1. **No `any` type** - Use `unknown` with type guards
2. **Strict null checks** - Handle null/undefined explicitly
3. **Type guards over assertions** - Avoid `as` keyword
4. **95%+ test coverage** - Required for all new code
## Testing with Vitest
```typescript
import { describe, it, expect } from 'vitest';
describe('myFunction', () => {
it('should handle valid input', () => {
expect(myFunction('input')).toBe('expected');
});
});
```
## ESLint Setup
```json
{
"extends": ["eslint:recommended", "plugin:@typescript-eslint/recommended"],
"parser": "@typescript-eslint/parser",
"rules": {
"@typescript-eslint/no-unused-vars": ["error", { "argsIgnorePattern": "^_" }],
"@typescript-eslint/no-explicit-any": "warn"
}
}
```