> tech-stack:add-typescript-best-practices
Setup TypeScript best practices and code style rules in CLAUDE.md
curl "https://skillshub.wtf/NeoLabHQ/context-engineering-kit/add-typescript-best-practices?format=md"Setup TypeScript Best Practices
Create or update CLAUDE.md in with following content, <critical>write it strictly as it is<critical>, do not summaraise or introduce and new additional information:
## Code Style Rules
### General Principles
- **TypeScript**: All code must be strictly typed, leverage TypeScript's type safety features
### Code style rules
- Interfaces over types - use interfaces for object types
- Use enum for constant values, prefer them over string literals
- Export all types by default
- Use type guards instead of type assertions
### Best Practices
#### Library-First Approach
- Common areas where libraries should be preferred:
- Date/time manipulation → date-fns, dayjs
- Form validation → joi, yup, zod
- HTTP requests → axios, got
- State management → Redux, MobX, Zustand
- Utility functions → lodash, ramda
#### Code Quality
- Use destructuring of objects where possible:
- Instead of `const name = user.name` use `const { name } = user`
- Instead of `const result = await getUser(userId)` use `const { data: user } = await getUser(userId)`
- Instead of `const parseData = (data) => data.name` use `const parseData = ({ name }) => name`
- Use `ms` package for time related configuration and environment variables, instead of multiplying numbers by 1000
> related_skills --same-repo
> tdd:write-tests
Systematically add test coverage for all local code changes using specialized review and development agents. Add tests for uncommitted changes (including untracked files), or if everything is commited, then will cover latest commit.
> tdd:test-driven-development
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first
> tdd:fix-tests
Systematically fix all failing tests after business logic changes or refactoring
> sdd:plan
Refine, parallelize, and verify a draft task specification into a fully planned implementation-ready task