1,751 件 ・ 関連度順
概要と使いどころ
Apply best practices for managing URL, server, and client state in Next.js applications. Use when choosing between URL params, SWR/TanStack Query, Zustand, or Context for state, or when fixing hydration mismatches from localStorage.
日本語の概要は準備中です。原文の説明を表示しています。
Write PHP following PSR coding standards, SOLID principles, and code-quality guidelines. Use for PHP style, design, refactoring, naming, and guard clauses—not Composer/PSR-4 project configuration.
日本語の概要は準備中です。原文の説明を表示しています。
Write maintainable Python with small functions, explicit boundaries, guard clauses, and readable state flow. Use when refactoring Python services, helpers, modules, or async logic for clarity—not generic test writing, tooling setup, or database transaction implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Best practices for multi-language handling, locale routing, and detection strategies across App and Pages Router. Use when adding i18n, locale routing, or language detection in Next.js.
日本語の概要は準備中です。原文の説明を表示しています。
Apply core Effective Java patterns for robust, maintainable code. Use when applying SOLID principles, choosing between inheritance and composition, refactoring Java code smells, or reviewing class design.
日本語の概要は準備中です。原文の説明を表示しています。
Idiomatic JavaScript patterns and conventions for maintainable existing code. Use when reviewing or refactoring JavaScript language patterns; defer project scaffolding, dependency setup, and tool configuration.
日本語の概要は準備中です。原文の説明を表示しています。
Core Kotlin patterns for scope functions, backing properties, and read-only collection interfaces. Use for let/apply/run/also/with choices or encapsulating mutable state; defer general language constructs, extension functions, coroutines/runCatching, Android/Room recipes, and testing/tooling setup.
日本語の概要は準備中です。原文の説明を表示しています。
Core idioms, style guides, and best practices for writing idiomatic Go code. Use when writing Go code following official style guides and idiomatic patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Enforce version control best practices for commits, branching, pull requests, and repository security. Use when writing commits, creating branches, merging, or opening pull requests.
日本語の概要は準備中です。原文の説明を表示しています。
Dart code quality conventions: naming, const/final/var hierarchy, single quotes, trailing commas, collection idioms, tear-offs, and import organization. Use only for Dart style-focused changes or reviews; never activate for configuration-only lint setup, unrelated feature work, or widget tests.
日本語の概要は準備中です。原文の説明を表示しています。
Enforce SOLID principles, guard-clause style, function size limits, and intention-revealing naming across all languages. Use when refactoring for readability, applying clean-code patterns, reviewing naming conventions, or reducing function complexity.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "create a plugin", "scaffold a plugin", "understand plugin structure", "organize plugin components", "set up plugin.json", "use ${CLAUDE_PLUGIN_ROOT}", "add commands/agents/skills/hooks", "configure auto-discovery", or needs guidance on plugin directory layout, manifest configuration, component organization, file naming conventions, or Claude Code plugin architecture best practices.
日本語の概要は準備中です。原文の説明を表示しています。
Best practices for writing R package tests with testthat version 3+. Use this skill when writing or organizing tests for an R package or when improving existing tests that use testthat. It covers test structure and expectations, self-sufficient test design, proper cleanup with withr, fixtures, mocking external dependencies, snapshot testing, and BDD-style describe/it patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive guide for writing modern Neo4j Cypher queries. Essential for text2cypher MCP tools and LLMs generating Cypher queries. Covers removed/deprecated syntax, modern replacements, CALL subqueries for reads, COLLECT patterns, sorting best practices, set-based writes, and Quantified Path Patterns (QPP) for efficient graph traversal.
日本語の概要は準備中です。原文の説明を表示しています。
Module composition, state management, workspace strategy, provider versioning, and infrastructure-as-code best practices.
日本語の概要は準備中です。原文の説明を表示しています。
Validation agent that validates plan tech choices against current best practices
日本語の概要は準備中です。原文の説明を表示しています。
Spring Security best practices for authn/authz, validation, CSRF, secrets, headers, rate limiting, and dependency security in Java Spring Boot services.
日本語の概要は準備中です。原文の説明を表示しています。
Research agent for external documentation, best practices, and library APIs via MCP tools
日本語の概要は準備中です。原文の説明を表示しています。
Pythonic idioms, PEP 8 standards, type hints, and best practices for building robust, efficient, and maintainable Python applications.
日本語の概要は準備中です。原文の説明を表示しています。
PostgreSQL database patterns for query optimization, schema design, indexing, and security. Based on Supabase best practices.
日本語の概要は準備中です。原文の説明を表示しています。
Cloud Run deployment, BigQuery optimization, Pub/Sub patterns, IAM best practices
日本語の概要は準備中です。原文の説明を表示しています。
Idiomatic Go patterns, best practices, and conventions for building robust, efficient, and maintainable Go applications.
日本語の概要は準備中です。原文の説明を表示しています。