797 件 ・ 関連度順
概要と使いどころ
Use when writing or running Unreal Engine tests - which test type fits (simple/complex automation tests, Automation Specs, functional tests, CQTest, Low-Level Tests, Gauntlet), naming and filters, latent tests, and the headless UnrealEditor-Cmd run with report export, exit handling and screenshot captures.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a web/frontend app needs a cloud deploy - GitHub Actions to Cloud Run/ECS for SSR or GCS+CDN/Firebase and S3+CloudFront for static, with build-time env and cache invalidation
日本語の概要は準備中です。原文の説明を表示しています。
Use when a backend or worker service needs a cloud deploy - container-first GitHub Actions deploys to Google Cloud Run (WIF) or AWS ECS/App Runner (OIDC), with migrate-before-deploy and a health-check gate
日本語の概要は準備中です。原文の説明を表示しています。
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks for Superloopy clone or asks to clone, rebuild, reverse-engineer, replicate, or copy a website or page into a Superloopy-governed implementation. Triggers on "loopy clone", target URLs plus requests such as "clone this site", "rebuild this page", "make a copy of this website", "pixel-perfect clone", or "AI website clone". Requires browser automation and records component specs, assets, implementation, build output, and visual QA as Superloopy evidence.
日本語の概要は準備中です。原文の説明を表示しています。
Automated iterative agent runner for spec-based development in Kiro. Wraps kiro-cli in a self-correcting bash loop that picks up tasks from a Kiro spec, implements them one at a time, verifies against exit criteria, and accumulates corrections and codebase patterns across iterations. Use this skill when the user mentions "ralph loop", "ralph", "spec loop", "iterative spec runner", "run my spec tasks automatically", "kiro spec automation", "self-correcting agent loop", "implement spec tasks in a loop", "run kiro-cli in a loop", "automated task implementation", or wants to drive a Kiro spec to completion through repeated agent iterations. Also use when the user wants to set up, configure, troubleshoot, or understand the Ralph Loop workflow — including progress tracking, corrections, codebase patterns, timing logs, and the summary dashboard.
日本語の概要は準備中です。原文の説明を表示しています。
Create comprehensive design systems, brand identities, and UI component libraries. Use when the user says "create design system", "build brand identity", "design UI components", "generate design tokens", "create figma specs", "review my design", "analyze design trends", "audit accessibility", "convert design to code", or "create presentation deck". Covers 10 specialized roles from system architecture to executive presentations.
日本語の概要は準備中です。原文の説明を表示しています。
Product Hunt launch optimization with specific specs, timing, and gallery strategy. Covers taglines, gallery images, maker comments, and launch day tactics. Use for: product launches, startup launches, side project launches, Product Hunt optimization. Triggers: product hunt, ph launch, product hunt launch, launch strategy, product launch, startup launch, product hunt tips, product hunt gallery, ph optimization, launch day, product hunt maker
日本語の概要は準備中です。原文の説明を表示しています。
Writes implementation plans before coding: phases, plan files, specs, definition of done. Use when planning a multi-step feature or breaking a large refactor into phases.
日本語の概要は準備中です。原文の説明を表示しています。
Proves protocols and agent workflows with TLA+, P, Alloy, Z3, Dafny, or Lean. Use when proving protocols correct, writing TLA+ specs, or verifying LLM proofs.
日本語の概要は準備中です。原文の説明を表示しています。
Writes PRDs and specs optimized for coding assistants. Use when authoring requirements or project context for Claude Code, Cursor, Copilot, or Codex.
日本語の概要は準備中です。原文の説明を表示しています。
Brainstorming interactively to deepen ideas via four modes (Expand/Propose/Evaluate/Subtract). Does not write code. Not for decisions (Magi), feature specs (Spark), or one-shot reframing (Flux).
日本語の概要は準備中です。原文の説明を表示しています。
Converting document formats (Markdown/Word/Excel/PDF/HTML) and generating reusable conversion scripts. Use for distributable specs, accessibility-compliant PDFs, or Pandoc/LibreOffice pipelines.
日本語の概要は準備中です。原文の説明を表示しています。
Authoring tech blog/article series for note/Zenn/Qiita/dev.to. Not for specs (Scribe) or microcopy (Prose).
日本語の概要は準備中です。原文の説明を表示しています。
Authoring unified specification packages across Business/Development/Design teams via staged elaboration (L0 Vision, L1 Requirements, L2 Team Detail, L3 Acceptance Criteria). Use for cross-team specs.
日本語の概要は準備中です。原文の説明を表示しています。
Navigating delivery status read-only: reconciles planned scope (specs/roadmap/PRD) against implemented code for what's built vs left. Not for priority scoring (Rank) or AC conformance (Attest).
日本語の概要は準備中です。原文の説明を表示しています。
Visualizing code, specs, or context as Mermaid, ASCII, or draw.io diagrams: flowcharts, sequence/state/class/ER, Journey Maps, personas, coverage heatmaps. Use to reverse-document systems visually.
日本語の概要は準備中です。原文の説明を表示しています。
Verifying spec compliance: extracts ACs from specs, adversarially checks conformance, generates BDD scenarios and traceability matrices. Use when impl must be proven to match a PRD/SRS/AC.
日本語の概要は準備中です。原文の説明を表示しています。
Designing and reviewing APIs: OpenAPI spec generation, versioning strategy, breaking change detection, REST/GraphQL best practices. Use for API design or OpenAPI specs.
日本語の概要は準備中です。原文の説明を表示しています。
Scan a repo for mixed ADRs, PRDs, SPECs, and DOCs and bootstrap or merge the full .planning/ setup from them. Classifies each doc in parallel, synthesizes a consolidated context with a conflicts report, and routes to new-project or merge-milestone depending on whether .planning/ already exists.
日本語の概要は準備中です。原文の説明を表示しています。
Condense any input — an idea, brief, PRD, transcript, or mixed notes — into a short spec: one kernel file plus supporting files that downstream skills build from. Also updates and validates existing specs. Use when the user says "create a spec", "distill this into a spec", "validate this spec", or "update the spec"
日本語の概要は準備中です。原文の説明を表示しています。
Audit the decisions in .ank/ against the current code and report what no longer holds. Use when asked whether ADRs, specs, or tasks are still accurate, after a milestone, or when the corpus and the code seem to disagree.
日本語の概要は準備中です。原文の説明を表示しています。
Publish, read, comment on, or edit markdown in Proof. Use for Proof links, sharing specs/plans/drafts, or publish handoffs from planning workflows; avoid proofread, math, evidence, or proof-of-concept meanings.
日本語の概要は準備中です。原文の説明を表示しています。
Review requirements, plans, or specs with role-specific lenses. Use when the user wants to improve an existing planning document.
日本語の概要は準備中です。原文の説明を表示しています。