code-review
Code Review Best Practices
Core Principles
Review Mindset:
- Be constructive, explain the "why"
- Prioritize by severity (critical vs nice-to-have)
- Suggest alternatives, not just problems
- Acknowledge good work
Goals:
- Catch bugs before production
- Improve code quality
- Share knowledge
- Prevent security vulnerabilities
- Ensure consistency
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.
460document-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.
154web-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.
29javascript-testing
JavaScript/Node.js testing best practices with Vitest. Use when writing tests, achieving test coverage, or working with JavaScript/TypeScript test files.
19claude-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