Agent skill
TypeScript Tooling
Development tools, linting, and build configuration for TypeScript projects.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/tooling-hoangnguyen0403-agent-skills-standar-9
Metadata
Additional technical details for this skill
- labels
-
tooling typescript eslint prettier testing
- triggers
-
{ "files": [ "tsconfig.json", ".eslintrc.*", "jest.config.*", "package.json" ], "keywords": [ "eslint", "prettier", "jest", "vitest", "build", "compile", "lint" ] }
SKILL.md
TypeScript Tooling
Priority: P1 (OPERATIONAL)
Essential tooling for TypeScript development and maintenance.
Implementation Guidelines
- Compiler:
tscfor CI.ts-node/esbuildfor dev. - Lint: ESLint +
@typescript-eslint. Strict type checking. - Format: Prettier (on save + commit).
- Test: Jest/Vitest > 80% coverage.
- Build:
tsup(libs), Vite/Webpack (apps). - Check:
tsc --noEmitin CI.
Anti-Patterns
- No Disable: Avoid
// eslint-disable. - No Skip: Avoid
skipLibCheck: trueif possible. - No Ignore: Use
@ts-expect-error>@ts-ignore.
ESLint Configuration
Strict Mode Requirement
CRITICAL: Every file in the project, including tests (.spec.ts), must adhere to strict type-checked rules. NEVER turn off @typescript-eslint/no-explicit-any or no-unsafe-* rules.
Common Linting Issues & Solutions
Request Object Typing
Problem: Using any for Express request objects or creating duplicate inline interfaces.
Solution: Use the centralized interfaces in src/common/interfaces/request.interface.ts.
import { RequestWithUser } from 'src/common/interfaces/request.interface';
Unused Parameters
Problem: Function parameters marked as unused by linter.
Solution: Prefix the parameter with an underscore (e.g., _data) or remove it. NEVER use eslint-disable.
Test Mock Typing
Problem: Jest mocks triggering unsafe type warnings when expect.any() or custom mocks are used.
Solution: Cast the mock or expectation using as unknown as TargetType.
mockRepo.save.mockResolvedValue(result as unknown as User);
Configuration
// tsconfig.json
{
"compilerOptions": {
"strict": true,
"noImplicitReturns": true,
"noUnusedLocals": true
}
}
Reference & Examples
For testing configuration and CI/CD setup: See references/REFERENCE.md.
Related Topics
best-practices | language
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?