4,042 件 ・ 関連度順
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Construa sistemas de ML em produção com PyTorch 2.x, TensorFlow e frameworks modernos de ML. Implementa model serving, feature engineering, A/B testing e monitoramento.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Audit and fix common accessibility issues in Angular templates and Angular Material components. Use when the user mentions Lighthouse, axe, screen readers, keyboard navigation, ARIA, asks to fix a11y issues in Angular HTML templates, or after any feature, bug fix, or refactor that changed Angular templates.
日本語の概要は準備中です。原文の説明を表示しています。
Load this skill whenever you are planning, executing, or reviewing manual accessibility testing. Manual testing with real assistive technologies is essential — automated tools catch only ~30–40 % of WCAG issues. Absolutely always include keyboard-only testing and at least one screen reader test before marking a feature accessible. Under no circumstances skip forced colors mode testing for UI components.
日本語の概要は準備中です。原文の説明を表示しています。
[Workflow] Use when activating the Spec to PBI Backlog workflow to convert canonical tech-free Feature Specs into complete, prioritized, dependency-aware PBIs and stories.
日本語の概要は準備中です。原文の説明を表示しています。
[Workflow] Use when activating the Integration Test Green workflow — drive an integration-test suite to fully green with a bounded convergence loop: verify the whole system (or the named target), adjudicate every failure with /debug-investigate + /integration-test-review before any edit, fix at the owning layer, /changes-review each round's fix diff, re-verify from scratch, then sync spec TCs, the integration-test reference doc, and feature docs.
日本語の概要は準備中です。原文の説明を表示しています。
[Workflow] Use when activating the Test Spec Update (Post-Change) workflow for update test specs and feature docs after code changes, bug fixes, or pr reviews.
日本語の概要は準備中です。原文の説明を表示しています。
[Workflow] Use when activating the Idea-to-Spec workflow — turn a raw idea/vision/problem into ONE canonical (provisional) Feature Spec. STOPS at the reviewed spec; chain workflow-spec-to-pbi for a backlog. For code→spec use workflow-code-to-spec.
日本語の概要は準備中です。原文の説明を表示しています。
[Architecture] Use when scaffolding reusable OOP/SOLID project foundations before feature implementation.
日本語の概要は準備中です。原文の説明を表示しています。
[Code Quality] Use to validate a spec artifact's decisions with the user across three contexts — a freshly-authored Feature Spec (idea-to-spec), an existing canonical spec before PBI decomposition (spec-to-pbi), or a refined idea + §8 test-specs (idea-to-pbi deep mode). Detects the context, walks every applicable validation category, and runs an exhaustive but budget-bounded blocking clarification gate so every non-obvious or conflicting decision is confirmed before the artifact drives downstream work.
日本語の概要は準備中です。原文の説明を表示しています。
[General] Use when you need to (re)generate a DERIVED navigation index, cross-capability ERD, or reimplementation guide assembled FROM the canonical Feature Specs under docs/specs/**. Never extracts a separate A-E engineering tree.
日本語の概要は準備中です。原文の説明を表示しています。
[Project Management] Use when creating user stories from PBIs, slicing features, or breaking down requirements.
日本語の概要は準備中です。原文の説明を表示しています。
[Workflow] Use when activating code-to-spec development — author/maintain the single canonical Feature Spec FROM existing code, keeping spec, implementation, and tests synchronized. For idea→spec (no code yet) use workflow-idea-to-spec.
日本語の概要は準備中です。原文の説明を表示しています。
[Documentation] Use when scanning the codebase to (re)generate ONE project-reference doc. Parameterized by `--target=<key>`: project-structure | backend-patterns | frontend-patterns | scss-styling | design-system | code-review-rules | domain-entities | feature-spec | docs-index | e2e-tests | integration-tests | seed-test-data | ui-system. Shared 4-phase scan engine; per-target detail lives in references/targets.md. `ui-system` is an orchestrator meta-target (`kind: orchestrator`) that runs the 3 UI child scans in parallel instead of the 4-phase engine.
日本語の概要は準備中です。原文の説明を表示しています。
[Project Management] Use when capturing new ideas, feature requests, or concepts for future refinement.
日本語の概要は準備中です。原文の説明を表示しています。
[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.
日本語の概要は準備中です。原文の説明を表示しています。
[Utilities] Use when you need Claude Code CLI setup, configuration, troubleshooting, and feature guidance.
日本語の概要は準備中です。原文の説明を表示しています。
[Project Management] Use when you need to map and visualize feature dependencies between modules, services, and work items.
日本語の概要は準備中です。原文の説明を表示しています。
[Documentation] Use when you need to synthesize all generated specs, PBIs, ideas and mockups into one standalone HTML slide presentation for stakeholders (PO/BA/Dev/QC).
日本語の概要は準備中です。原文の説明を表示しています。
[Content] Use when you need to brainstorm as a PO/BA — structured ideation for problem-solving, new product creation, or feature enhancement.
日本語の概要は準備中です。原文の説明を表示しています。