rohitg00/typescript-best-practices
packages/core/src/eval/__tests__/fixtures/good-skill/SKILL.md
Enforces TypeScript best practices and modern patterns
$ install --global
skillsauthnpx skillsauth add rohitg00/skillkit typescript-best-practicesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 12, 2026, 2:01 AM17.7s1 file scanned
SKILL.md
- name:
- typescript-best-practices
- description:
- Enforces TypeScript best practices and modern patterns
- version:
- 1.0.0
- tags:
- [typescript, best-practices, code-quality]
- globs:
- ["**/*.ts", "**/*.tsx"]
TypeScript Best Practices
When to Use
Use this skill when:
- Writing new TypeScript code
- Reviewing TypeScript pull requests
- Refactoring JavaScript to TypeScript
Triggers
Activated when editing .ts or .tsx files in the project.
Rules
Always
- Always use
constfor variables that won't be reassigned - Always use explicit return types on exported functions
- Always prefer
interfaceovertypefor object shapes
Never
- Never use
any— useunknowninstead - Never use
var— useconstorlet - Never ignore TypeScript errors with
@ts-ignore
Examples
// Good: explicit return type
export function calculateTotal(items: Item[]): number {
return items.reduce((sum, item) => sum + item.price, 0);
}
// Good: discriminated union
type Result<T> =
| { success: true; data: T }
| { success: false; error: Error };
Boundaries
- Do not modify
tsconfig.jsonwithout explicit permission - Do not add new dependencies without checking existing utilities
- Focus only on TypeScript patterns, not runtime behavior
Related Skills
rohitg00/find-skills
tools
VerifiedTrustedCommunity
Discovers, searches, and installs skills from multiple AI agent skill marketplaces (400K+ skills) using the SkillKit CLI. Supports browsing official partner collections (Anthropic, Vercel, Supabase, Stripe, and more) and community repositories, searching by domain or technology, and installing specific skills from GitHub. Use when the user wants to find, browse, or install new agent skills, plugins, extensions, or add-ons; asks 'is there a skill for X' or 'find a skill for X'; wants to explore a skill store or marketplace; needs to extend agent capabilities in areas like React, testing, DevOps, security, or APIs; or says 'browse skills', 'search skill marketplace', 'install a skill', or 'what skills are available'.
757SKILL.mdUpdated Apr 12, 2026
rohitg00/test-patterns
development
VerifiedTrustedCommunity
Applies proven testing patterns — Arrange-Act-Assert (AAA), Given-When-Then, Test Data Builders, Object Mother, parameterized tests, fixtures, spies, and test doubles — to help write maintainable, reliable, and readable test suites. Use when the user asks about writing unit tests, integration tests, or end-to-end tests; structuring test cases or test suites; applying TDD or BDD practices; working with mocks, stubs, spies, or fakes; improving test coverage or reducing flakiness; or needs guidance on test organization, naming conventions, or assertions in frameworks like Jest, Vitest, pytest, or similar.
757SKILL.mdUpdated Apr 12, 2026
rohitg00/red-green-refactor
development
VerifiedTrustedCommunity
Guides the red-green-refactor TDD workflow: write a failing test first, implement the minimum code to make it pass, then refactor while keeping tests green. Use when a user asks to practice TDD, write tests first, follow red-green-refactor, do test-driven development, write failing tests before code, or phrases like 'make the test pass', 'test coverage', or 'unit tests before implementation'.
757SKILL.mdUpdated Apr 12, 2026
rohitg00/testing-anti-patterns
development
VerifiedTrustedCommunity
Reviews test code to identify and fix common testing anti-patterns including flaky tests, over-mocking, brittle assertions, test interdependency, and hidden test logic. Flags bad patterns, explains the specific defect, and provides corrected implementations. Use when reviewing test code, debugging intermittent or unreliable test failures, or when the user mentions flaky tests, test smells, brittle tests, test isolation issues, mock overuse, slow tests, or test maintenance problems.
757SKILL.mdUpdated Apr 12, 2026