javascript-testing
JavaScript Testing Best Practices
Overview
Comprehensive guidance for writing high-quality JavaScript/Node.js tests using Vitest with 100% code coverage.
Testing Framework: Vitest
Why Vitest:
- Native ESM support (no experimental flags)
- Seamless JSDOM integration
- Faster than Jest
- Jest-compatible API
- Built-in coverage with v8
Test structure:
More from shino369/claude-code-personal-workspace
translation-expertise
Expert translation methodology and best practices for English-Japanese-Chinese (Traditional) trilingual translation. Use when translating any content between these languages, including handling idioms, cultural nuances, and language-specific expressions. Provides translation workflows and quality assurance methods.
458document-writing
Expert knowledge in document and essay writing conventions for English, Japanese, and Chinese (Traditional). Use when writing or translating formal documents, essays, articles, reports, or professional communications. Provides language-specific writing styles, formatting conventions, and rhetorical patterns.
153web-content-fetcher
Expert guidance for fetching and parsing web content from URLs, handling various content sizes, JavaScript-rendered sites, and working around tool limitations. Use when fetching articles, documentation, social media posts, or any web content for translation, analysis, or archiving.
64engineering-terminology
Expert knowledge in engineering, technical, and scientific terminology across English, Japanese, and Chinese (Traditional). Use when translating technical documents, engineering specifications, API documentation, or scientific papers. Provides accurate technical term translations and domain-specific vocabulary.
29code-review
Software engineering best practices for code review. Use when reviewing code, analyzing code quality, checking for bugs, security vulnerabilities, or providing feedback on code changes.
21claude-code-development
Expert knowledge in creating and configuring Claude Code components (subagents, skills, slash commands, hooks, MCP integrations). Use when the user asks to create, modify, or extend .claude/ directory components. Follows official best practices and documentation standards.
17