1,581 件 ・ 関連度順
概要と使いどころ
Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
日本語の概要は準備中です。原文の説明を表示しています。
Manages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when deciding whether to maintain or sunset existing code.
日本語の概要は準備中です。原文の説明を表示しています。
Generates complete features from natural language — components, API routes, migrations, types, and tests.
日本語の概要は準備中です。原文の説明を表示しています。
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
日本語の概要は準備中です。原文の説明を表示しています。
Turn an idea into a Conventional Docs Decision, then a Plan: classify the request, explore options and risks through dialogue, then commit a numbered Decision that review, prototypes, and acceptance move through. Use PROACTIVELY before any creative work — new features, new subsystems, interface or dependency changes, or any open-ended design question ("what are the options", "how should I approach", "should I use X or Y", "help me decide", "write a decision", "ADR").
日本語の概要は準備中です。原文の説明を表示しています。
Add strategic color to features that are too monochromatic or lack visual interest, making interfaces more engaging and expressive. Use when the user mentions the design looking gray, dull, lacking warmth, needing more color, or wanting a more vibrant or expressive palette.
日本語の概要は準備中です。原文の説明を表示しています。
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
日本語の概要は準備中です。原文の説明を表示しています。
Generate end to end automated tests for existing features. Use when the user says "create qa automated tests for [feature]"
日本語の概要は準備中です。原文の説明を表示しています。
Run a full project health diagnostic — checks structure, agents, features, scripts, extensions, and git status.
日本語の概要は準備中です。原文の説明を表示しています。
Run a full project health diagnostic — checks structure, agents, features, scripts, extensions, and git status.
日本語の概要は準備中です。原文の説明を表示しています。
Expert SwiftUI guidance for macOS apps — covers writing and reviewing code with runtime-level understanding of observation, concurrency, performance, and platform integration. Use when user asks to "build a SwiftUI view", "review my SwiftUI code", "fix observation issues", "bridge AppKit", "architect state management", "debug view updates", or works on any macOS SwiftUI project — building features, reviewing existing code, debugging view updates or performance, fixing concurrency issues, architecting state management, bridging AppKit, or making design decisions. Do NOT use for iOS/iPadOS-only SwiftUI, UIKit bridging, or basic Swift language questions. Focuses on non-obvious traps and deep patterns, not basics.
日本語の概要は準備中です。原文の説明を表示しています。
Take a guided tour of Open SaaS — walks you through step-by-step through the project structure, features, and customization checklist.
日本語の概要は準備中です。原文の説明を表示しています。
Use when ranking competing initiatives for a roadmap, breaking a tie between two features, or auditing a backlog for hidden low-value work via Reach × Impact × Confidence ÷ Effort.
日本語の概要は準備中です。原文の説明を表示しています。
Use when building Laravel real-time features — Broadcasting events, ShouldBroadcast, private/presence channels, Echo client. For non-Laravel WebSockets, use the stack-native skill.
日本語の概要は準備中です。原文の説明を表示しています。
Wire up DevContainers / GitHub Codespaces — `devcontainer.json`, container images, secrets, VS Code features, port forwarding. NOT for tuning Copilot itself (use `copilot-config`).
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features. Provides comprehensive security checklist and patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Você DEVE usar isto antes de qualquer trabalho criativo - criar features, construir componentes, adicionar funcionalidade ou modificar comportamento. Explora a intenção do usuário, requisitos e design antes da implementação.
日本語の概要は準備中です。原文の説明を表示しています。
Kit de ferramentas completo para gerentes de produto, incluindo priorização RICE, análise de entrevistas com clientes, templates de PRD, frameworks de descoberta e estratégias de go-to-market. Use para priorização de features, síntese de pesquisa com usuários, documentação de requisitos e desenvolvimento de estratégia de produto.
日本語の概要は準備中です。原文の説明を表示しています。
Quando o usuário quer otimizar, melhorar ou aumentar conversões em qualquer página de marketing — incluindo homepage, landing pages, páginas de preços, páginas de features ou posts de blog. Também use quando o usuário menciona "CRO," "otimização de taxa de conversão," "essa página não está convertendo," "melhorar conversões," ou "por que essa página não funciona." Para fluxos de signup/registro, veja signup-flow-cro. Para ativação pós-signup, veja onboarding-cro. Para formulários fora de signup, veja form-cro. Para popups/modals, veja popup-cro.
日本語の概要は準備中です。原文の説明を表示しています。
Cria planos de implementação detalhados e segmentados através de pesquisa, entrevistas com stakeholders e revisão multi-LLM. Use quando planejar features que precisam de análise pré-implementação aprofundada.
日本語の概要は準備中です。原文の説明を表示しています。
Load this skill whenever the project has personalization features, user preference controls, theme selectors, font size adjusters, motion toggles, contrast settings, or any user-configurable accessibility accommodations. Under no circumstances override or ignore user OS-level accessibility preferences without explicit user consent. Absolutely always persist user preferences, apply them immediately, and respect prefers-reduced-motion, prefers-contrast, and similar media queries.
日本語の概要は準備中です。原文の説明を表示しています。
[Project Management] Use when creating user stories from PBIs, slicing features, or breaking down requirements.
日本語の概要は準備中です。原文の説明を表示しています。
[Investigation] Use when about to author a new Feature Spec from an idea — investigate all existing Feature Specs AND related code logic first to surface related/overlapping/affected specs, missing features, missing test cases/user stories, system unknowns, and the invariant landscape, before any spec is drafted.
日本語の概要は準備中です。原文の説明を表示しています。
[Fix & Debug] Use when you need to investigate and explain how existing features or logic work. Flag: --mode=explain produces a one-way developer-narrative explanation (Purpose → How → Why → Impact) tuned by coding level; use /understand for the standalone prompt-driven explainer.
日本語の概要は準備中です。原文の説明を表示しています。