tech-stack:add-typescript-best-practices
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
0
total installs
0
this week
765
GitHub stars
0
upvotes
Install Skill
Run in your terminal
0
installs
0
this week
765
stars
Installation Guide
How to use tech-stack:add-typescript-best-practices on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your machine
- ›Node.js 16+ with npm — verify with
node --version - ›Active project directory where you want to add
tech-stack:add-typescript-best-practices
Run the install command
Execute 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.
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Verify installation
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.
Security Notice
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.
Documentation
Setup TypeScript Best Practices
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
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases
Task Automation & Efficiency
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Knowledge Enhancement
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Quality Improvement
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Implementation Guide
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Steps
- 1Install skill using provided installation command
- 2Test with simple use case relevant to your work
- 3Evaluate output quality and relevance
- 4Iterate on prompts to improve results
- 5Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This
✓ 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.
Learning Path
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Related Skills
typescript-best-practices
96jwynia/agent-skills
python-expert-best-practices-code-review
34wispbit-ai/skills
nestjs-best-practices
51kadajett/agent-nestjs-skills
react-vite-best-practices
35asyrafhussin/agent-skills
svelte5-best-practices
23ejirocodes/agent-skills
angular-best-practices-primeng
19alfredoperez/angular-best-practices
Reviews
- JJames Smith★★★★★Dec 28, 2024
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.
- AAdvait Diallo★★★★★Dec 24, 2024
tech-stack:add-typescript-best-practices is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- AAnaya Malhotra★★★★★Dec 20, 2024
tech-stack:add-typescript-best-practices reduced setup friction for our internal harness; good balance of opinion and flexibility.
- CChaitanya Patil★★★★★Dec 12, 2024
tech-stack:add-typescript-best-practices fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- NNikhil Harris★★★★★Nov 19, 2024
tech-stack:add-typescript-best-practices has been reliable in day-to-day use. Documentation quality is above average for community skills.
- YYuki Menon★★★★★Nov 15, 2024
Solid pick for teams standardizing on skills: tech-stack:add-typescript-best-practices is focused, and the summary matches what you get after install.
- NNikhil Taylor★★★★★Nov 11, 2024
We added tech-stack:add-typescript-best-practices from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- PPiyush G★★★★★Nov 3, 2024
Registry listing for tech-stack:add-typescript-best-practices matched our evaluation — installs cleanly and behaves as described in the markdown.
- SShikha Mishra★★★★★Oct 22, 2024
tech-stack:add-typescript-best-practices reduced setup friction for our internal harness; good balance of opinion and flexibility.
- NNikhil Zhang★★★★★Oct 10, 2024
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
Discussion
Comments — not star reviews- No comments yet — start the thread.