Create or update CLAUDE.md in with following content, write it strictly as it is, do not summaraise or introduce and new additional information:
Works with
Create or update CLAUDE.md in with following content, write it strictly as it is, 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
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiontech-stack:add-typescript-best-practicesExecute the skills CLI command in your project's root directory to begin installation:
Fetches tech-stack:add-typescript-best-practices from neolabhq/context-engineering-kit and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate tech-stack:add-typescript-best-practices. Access via /tech-stack:add-typescript-best-practices in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
765
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
765
stars
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
jwynia/agent-skills
wispbit-ai/skills
kadajett/agent-nestjs-skills
asyrafhussin/agent-skills
vercel-labs/next-skills
ejirocodes/agent-skills
Keeps context tight: tech-stack:add-typescript-best-practices is the kind of skill you can hand to a new teammate without a long onboarding doc.
tech-stack:add-typescript-best-practices is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
tech-stack:add-typescript-best-practices reduced setup friction for our internal harness; good balance of opinion and flexibility.
tech-stack:add-typescript-best-practices fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
tech-stack:add-typescript-best-practices has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: tech-stack:add-typescript-best-practices is focused, and the summary matches what you get after install.
We added tech-stack:add-typescript-best-practices from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Registry listing for tech-stack:add-typescript-best-practices matched our evaluation — installs cleanly and behaves as described in the markdown.
tech-stack:add-typescript-best-practices reduced setup friction for our internal harness; good balance of opinion and flexibility.
Solid pick for teams standardizing on skills: tech-stack:add-typescript-best-practices is focused, and the summary matches what you get after install.
showing 1-10 of 49