typescript-rules
TypeScript Development Rules (Frontend)
Basic Principles
- Aggressive Refactoring - Prevent technical debt and maintain health
- Delete code when no current caller exists - YAGNI principle (Kent Beck)
Comment Writing Rules
- Function Description Focus: Describe what the code "does"
- Timeless content only: Record decisions and rationale; leave chronological history to version control
- Conciseness: Keep explanations to necessary minimum
Type Safety
Absolute Rule: Replace every any with unknown, generics, or union types. any disables type checking and causes runtime errors.
More from shinpr/claude-code-workflows
coding-principles
Language-agnostic coding principles for maintainability, readability, and quality. Use when implementing features, refactoring code, or reviewing code quality.
49testing-principles
Language-agnostic testing principles including TDD, test quality, coverage standards, and test design patterns. Use when writing tests, designing test strategies, or reviewing test quality.
48integration-e2e-testing
Integration and E2E test design principles, ROI calculation, test skeleton specification, and review criteria. Use when designing integration tests, E2E tests, or reviewing test quality.
47subagents-orchestration-guide
Guides subagent coordination through implementation workflows. Use when orchestrating multiple agents, managing workflow phases, or determining autonomous execution mode.
46task-analyzer
Performs metacognitive task analysis and skill selection. Use when determining task complexity, selecting appropriate skills, or estimating work scale.
42ai-development-guide
Technical decision criteria, anti-pattern detection, debugging techniques, and quality check workflow. Use when making technical decisions, detecting code smells, or performing quality assurance.
41