2,300 件 ・ 関連度順
概要と使いどころ
Clarify ambiguous requirements through focused dialogue before implementation. Use when requirements are unclear, features are complex (>2 days), or involve cross-team coordination. Ask two core questions - Why? (YAGNI check) and Simpler? (KISS check) - to ensure clarity before coding.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when building React components with TypeScript, typing hooks, handling events, or when React TypeScript, React 19, Server Components are mentioned. Covers type-safe patterns for React 18-19 including generic components, proper event typing, and routing integration (TanStack Router, React Router).
日本語の概要は準備中です。原文の説明を表示しています。
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.
日本語の概要は準備中です。原文の説明を表示しています。
Create a minimalist marketing plan focused on building an audience through free, authentic content. Use when someone has product-market fit (~100 customers) and wants to scale through marketing or needs a content strategy.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when creating a Claude Code slash command. Use when users ask to "create a command", "make a slash command", "add a command", or want to document a workflow as a reusable command. Essential for creating optimized, agent-executable slash commands with proper structure and best practices.
日本語の概要は準備中です。原文の説明を表示しています。
Expert in building products that wrap AI APIs (OpenAI, Anthropic, etc. ) into focused tools people will pay for. Not just "ChatGPT but different" - products that solve specific problems with AI.
日本語の概要は準備中です。原文の説明を表示しています。
Use when authoring Litestar skill content, Python/TypeScript examples, PEP 604, async I/O, Google docstrings, ruff/mypy/pyright, pytest, or CI rules. Not for focused Litestar APIs.
日本語の概要は準備中です。原文の説明を表示しています。
6-lens diagnostic slop audit — unused imports, dead private fns, duplicate signatures, abandoned TODOs, lint bypass markers, stale refs.
日本語の概要は準備中です。原文の説明を表示しています。
Used by the Reviewer agent during Phase 9 (DesignVerify) and Phase 11 (Quality) to evaluate frontend code. Assesses visual hierarchy, spacing consistency, accessibility, and detects formulaic 'AI slop' design patterns, providing actionable feedback to the Developer.
日本語の概要は準備中です。原文の説明を表示しています。
Used by the Developer agent during Phase 8 (Implement) when building web components, pages, or UI features. Provides strict aesthetic guidelines to create distinctive, production-grade frontend interfaces that avoid generic 'AI slop' aesthetics.
日本語の概要は準備中です。原文の説明を表示しています。
Used by the Lead agent during Phase 6 (Brainstorm) to collaboratively explore user intent, requirements, and alternative approaches before locking in the architecture. Helps turn raw ideas into fully formed specs through natural dialogue.
日本語の概要は準備中です。原文の説明を表示しています。
Generate a conversion-focused landing page that compares offers, pricing cues, and trust signals for a family law practice. Use when handling offer...
日本語の概要は準備中です。原文の説明を表示しています。
Zod schema validation and React Hook Form integration for TypeScript frontends. This skill should be used when creating forms, defining API schemas, validating form data, implementing type-safe validation, using ZodResolver with React Hook Form, or migrating legacy forms to the Zod + React Hook Form pattern.
日本語の概要は準備中です。原文の説明を表示しています。
Django Redis caching with django-cacheops. This skill should be used when implementing caching, adding cache invalidation, optimizing API performance, modifying models that affect cached data, or debugging cache-related issues in the Django backend.
日本語の概要は準備中です。原文の説明を表示しています。
DraftForge test infrastructure for writing backend unit tests, Playwright E2E tests, and managing test data population. This skill should be used when writing new tests, adding test fixtures, creating populate functions for new features, adding Playwright E2E specs, using login/auth fixtures, creating test users/orgs/leagues/tournaments, or understanding the test data architecture. Covers backend Django tests via Docker, Playwright config (projects, workers, sharding), test auth endpoints that expose backend login to frontend, and feature-isolated test data patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Python Invoke task automation for DTX website. This skill should be used when running repo commands, backend tests via Docker, database migrations, updating invoke tasks, Docker operations, or workflow automation. Supports dev/test/prod environments with run, exec, up, down commands. References docs/development/invoke-tasks.md for complete command reference.
日本語の概要は準備中です。原文の説明を表示しています。
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
日本語の概要は準備中です。原文の説明を表示しています。
Structured logging conventions for DraftForge backend (Django/Celery/Daphne) and frontend (React). This skill should be used when adding log statements, creating new modules, debugging with logs, or reviewing logging patterns. Covers structlog usage, system/subsystem taxonomy, required fields, log levels, and Grafana query patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Auto-detect project context and optimize harness — deactivate unused agents/skills, suggest missing experts, generate project profile
日本語の概要は準備中です。原文の説明を表示しています。
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
日本語の概要は準備中です。原文の説明を表示しています。
Query the witness-anchored ruLake cache — search, verify, explain, or refresh. Returns ranked results plus a decision_trace block with cost, latency, witness match, and substrates used.
日本語の概要は準備中です。原文の説明を表示しています。
Document-driven workflow for implementing, reviewing, and verifying Chisel processor and memory-subsystem RTL. Use when Codex must work from maintained Architecture and Design, trace a complete integration surface, reason in synthesized-hardware terms, keep source-adjacent _codex.md summaries current, avoid redundant or overprotective logic, or run focused functional verification.
日本語の概要は準備中です。原文の説明を表示しています。
Generate realistic product-in-use lifestyle scenes. Places the product in believable contexts of use (who, where, when, doing what) with natural lighting and real texture, for lifestyle/editorial/ecommerce. Use when the user says "lifestyle shot", "product in use", "scene", "show it being used", "in-context photography", or needs people/environment around the product. Part of the Creative Production set.
日本語の概要は準備中です。原文の説明を表示しています。
Apply or adapt a dual-theme neo-glow control board for UI kits, design-system previews, settings surfaces, admin panels, control rooms, and dense operational interfaces. Use when Codex should build or restyle interface work with bright white or dark control surfaces, compact neumorphic cards, vertical icon rails, blue/cyan halo accents, glowing active states, luminous toggles, and a board focused on control states, inputs, and specification details.
日本語の概要は準備中です。原文の説明を表示しています。