7,232 件 ・ 関連度順
概要と使いどころ
Use this skill instead of WebSearch for ANY question requiring web research. Trigger on queries like "what is X", "explain X", "compare X and Y", "research X", or before content generation tasks. Provides systematic multi-angle research methodology instead of single superficial searches. Use this proactively when the user's question needs online information.
日本語の概要は準備中です。原文の説明を表示しています。
Replicate and validate a GitHub issue by spinning up Archon, analyzing the issue, and systematically testing all described symptoms using browser automation. Use when: User wants to reproduce a bug, validate a GitHub issue, confirm a reported problem, or investigate whether an issue is real before working on a fix. Triggers: "replicate issue", "reproduce issue", "validate issue", "confirm bug", "test issue", "can you reproduce", "try to replicate", "verify the bug". Capability: Checks out main, pulls latest, starts Archon, reads the GitHub issue, then uses agent-browser to systematically test every symptom and produce a findings report. NOT for: Fixing issues (use /archon or /exp-piv-loop:fix-issue), general UI testing (use /validate-ui).
日本語の概要は準備中です。原文の説明を表示しています。
Create a detailed, phased implementation plan with documentation discovery. Use when asked to plan a feature, task, or multi-step implementation — especially before executing with do.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze blast radius before making code changes
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: "Is it safe to change X?", "What depends on this?", "What will break?"
日本語の概要は準備中です。原文の説明を表示しています。
Swiss 网格 / 系统派社交卡 — 精确 / 系统化 / 技术感 / 方法论调性。卡角色含 system 封面 / numbered method / 对比 before-after / KPI tower / 横条 mini-chart / 截图解释 / 证据墙 / 收尾 checklist。用于 framework / checklist / 工具说明 / AI workflow / 产品更新 / KPI 总结。触发："做个方法卡 / 框架卡 / 工具拆解卡 / AI 工具卡 / 系统派结构卡"。NOT 情绪 / 文学 / 图主导卡，NOT 软生活 pastel 风。
日本語の概要は準備中です。原文の説明を表示しています。
Audit of existing Vue components in the project. Use when reviewing Vue design system consistency, identifying duplicate patterns, evaluating legacy components (Options API), or before implementing something new.
日本語の概要は準備中です。原文の説明を表示しています。
Bidirectional Figma skill — read designs and write back to Figma. READ: extract tokens, map Vue/Reka UI components, translate Auto Layout to Tailwind. WRITE: push components, screens, and design tokens from code to Figma. Requires /figma:figma-use skill before every use_figma call.
日本語の概要は準備中です。原文の説明を表示しています。
Create or revise the SDD Composy technical specification (tasks/prd-SLUG/techspec.md) from the approved PRD, resolved stories, and mapped codebase, with DEC/RISK and TU/TI/E2E traceability and a human gate. Use when the product contracts are approved and architecture is needed — 'criar a spec técnica', 'techspec do prd-SLUG', 'design the solution for…'. Do NOT use to change product scope, before PRD and stories approval, or for design notes outside SDD.
日本語の概要は準備中です。原文の説明を表示しています。
Produce a deterministic, read-only evidence map of the repository for SDD Composy (languages, manifests, commands, modules, boundaries, staleness) and publish the context bundle only on request. Use before a PRD or TechSpec, or when the map is stale — 'mapear o repositório', 'atualizar o contexto do código', 'what does this codebase look like for SDD'. Do NOT use for architecture decisions, code review, or repository exploration without an SDD workspace.
日本語の概要は準備中です。原文の説明を表示しています。
Create, revise, or resolve applicability for SDD Composy user stories (US/SC) from an approved PRD and domain evidence, stopping at the human gate. Use after the PRD is approved — 'gerar as histórias de usuário', 'cenários de aceite', 'stories for prd-SLUG', 'is stories NOT_APPLICABLE here'. Do NOT use before the PRD is approved, for the TechSpec, or for user-story writing outside SDD.
日本語の概要は準備中です。原文の説明を表示しています。
Use when starting any conversation in a repository that uses PWDEV Power - establishes how to find and apply Power skills before any response, including clarifying questions
日本語の概要は準備中です。原文の説明を表示しています。
Use when about to claim work is complete, fixed, or passing, and when a finished feature needs adversarial verification before integration
日本語の概要は準備中です。原文の説明を表示しています。
Use when starting feature work that needs isolation from the current workspace, or before executing an implementation plan
日本語の概要は準備中です。原文の説明を表示しています。
Use when a design or set of requirements exists and work needs decomposing into tasks, before touching any code
日本語の概要は準備中です。原文の説明を表示しています。
Analyze a completed phase diff for high-confidence behavior-preserving simplifications and apply only explicitly approved proposals. Use after execution and before review to reduce duplication, dead code, needless complexity, or avoidable inefficiency.
日本語の概要は準備中です。原文の説明を表示しています。
Use when implementing any feature or fixing any bug, before writing implementation code
日本語の概要は準備中です。原文の説明を表示しています。
Discover and approve feature requirements through focused interviewing and repository research. Use when the user has a feature idea, unclear scope, conflicting requirements, or needs Flow context artifacts before design.
日本語の概要は準備中です。原文の説明を表示しています。
Use when encountering any bug, test failure, or unexpected behavior, before proposing any fix
日本語の概要は準備中です。原文の説明を表示しています。
Use when an existing skill must be refactored to cut context and ambiguity without losing behavior, safety or fallbacks — 'refatorar a skill', 'reduzir esta SKILL.md', 'revisar skill com métricas' — with before/after metrics, preserved invariants and three review rounds.
日本語の概要は準備中です。原文の説明を表示しています。
Use when work needs reviewing before it is merged, and when review feedback has arrived and needs acting on
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants a full feature action plan (backend + frontend + tests) with the PWDEVIA 7-question method before any code is written — 'planejar a feature X', 'criar plano de feature', 'plan the user CRUD'. Interviews the human (max 2 rounds) and writes .planning/feat/features/{slug}/plan.md. Do NOT use to write code (feat-exec), for small 1–3 file changes (feat-quick), backend-only or UI-only scope (feat-backend / feat-frontend), tests for existing code (feat-test) or code review (feat-review).
日本語の概要は準備中です。原文の説明を表示しています。
Audit a GTK4/libadwaita app for GNOME HIG compliance across 12 categories (text, icons, layout, shortcuts, accessibility, color, dialogs, responsiveness, CSS, GSettings, i18n), then fix violations category by category. Use when asked to audit, review, polish, or "make HIG-compliant" a GNOME app, or before a release/Flathub submission.
日本語の概要は準備中です。原文の説明を表示しています。
Perform a final quality pass fixing alignment, spacing, consistency, and micro-detail issues before shipping. Use when the work is functionally complete and needs finishing touches—not when the hierarchy, structure, tone, or technical foundation still need major changes.
日本語の概要は準備中です。原文の説明を表示しています。