2,814 件 ・ 関連度順
概要と使いどころ
Use when a feature begins or specs are checked in: author or update behavioral specs and keep them current with what ships. Not for producing the initial approved spec and plan: use spec-driven.
日本語の概要は準備中です。原文の説明を表示しています。
Investigate a bounded Proto UI Contract, Prototype, Module, Host Capability, Adapter, schema, or ownership question and turn a genuinely unresolved direction into one semantic decision packet. Use for spec brainstorming, admission questions, competing semantic models, uncataloged behavior, or unresolved cross-layer boundaries.
日本語の概要は準備中です。原文の説明を表示しています。
Inspect one bounded Proto UI Issue queue slice and route ready governed work toward claim and implementation. Use for intake health, readiness, ownership, claim conflicts, stale state, or a candidate task search. This evidence leaf is read-only; authorized claim and implementation continue in their registered leaves.
日本語の概要は準備中です。原文の説明を表示しています。
Reproduce and repair a bounded Proto UI regression whose expected behavior and owning layer are already governed. Use this before domain implementation skills whenever work starts from a reproducible failure, including bug fixes, drift repairs, broken exports, Runtime failures, Adapter parity defects, Prototype defects, or public-projection regressions. Do not use when expected semantics or ownership is unresolved.
日本語の概要は準備中です。原文の説明を表示しています。
Maintain an existing Proto UI Prototype or implement a governed Base or design-language component slice. Use for governed component behavior, anatomy, inheritance, exports, CLI registration, style projection, demos, or public preview work. Do not use to admit a new semantic subject or invent Base ownership from a component name.
日本語の概要は準備中です。原文の説明を表示しています。
Create or revise a governed Proto UI spec entity after identity, ownership, lifecycle intent, semantic scope, relations, and evidence plan are fixed by current authority. Use for Contract, Prototype, Module, Adapter profile, Decision, Host Capability, Test, Version, or Knowledge entity work. Do not use to decide an unresolved admission or lifecycle promotion.
日本語の概要は準備中です。原文の説明を表示しています。
Plan Odylith delegation ownership, bounded fanout, and merge-safe orchestration.
日本語の概要は準備中です。原文の説明を表示しています。
Speed up Rust development iteration when `cargo build --release` takes 10+ minutes even for one-line edits. Use when: (1) every release rebuild takes minutes despite tiny edits, (2) Cargo.toml has `lto = "fat"` and/or `codegen-units = 1` in `[profile.release]`, (3) you want a production- shaped build for testing without paying the LTO cost on every iteration, (4) you suspect cargo is re-linking the whole binary instead of doing incremental work, (5) developing rfdb/grafema-orchestrator/large Rust binaries where full LTO is enabled for shipped builds. Adds a `fast` profile that inherits release but disables LTO, raises codegen-units, enables incremental compilation — first build still slow because it populates a fresh `target/fast/` dep cache, but every subsequent rebuild drops from ~13 min to ~13 s (≈60×).
日本語の概要は準備中です。原文の説明を表示しています。
Build and deploy full-stack web and mobile apps with AWS Amplify Gen2 (TypeScript code-first). Covers auth (Cognito), data (AppSync/DynamoDB including schema modeling, enum types, relationships, authorization rules), storage (S3), functions, APIs, and AI (Amplify AI Kit with Bedrock). Supports React, Next.js, Vue, Angular, React Native, Flutter, Swift, and Android. Always use this skill for Amplify Gen2 topics — even for questions you think you know — it contains validated, version-specific patterns that prevent common mistakes. TRIGGER when: user mentions Amplify Gen2; project has amplify/ directory or amplify_outputs; code imports @aws-amplify packages; user asks about defineBackend, defineAuth, defineData, defineStorage, or npx ampx. SKIP: Amplify Gen1 (amplify CLI v6), standalone SAM/CDK without Amplify (use aws-serverless), direct Bedrock without Amplify AI Kit (use bedrock).
日本語の概要は準備中です。原文の説明を表示しています。
Run the Codex Optimized Development, Evaluation, and Remediation (CODER) Loop with an orchestration-only coordinator, non-overlapping task-family owners, fresh independent reviewers, evidence-scoped remediation, and final coordinator acceptance. Discover and compose optional MSW, Timebox, MSL, and Codex Voice Optimizer companions as the Slopware Dev Stack without making them dependencies. Use in Codex when the user invokes the CODER Loop, asks to divide a complex change into bounded implementation families with independent reviewers, requests multi-agent implementation without overlapping ownership, requires review and repair until every blocking gap is independently rechecked, asks for the CODER tutorial or Slopware Dev Stack, or wants CODER to install or use its companions. Do not trigger for an ordinary single-agent change, a review-only request, or a non-Codex host.
日本語の概要は準備中です。原文の説明を表示しています。
Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas. Use when asked to "weekly retro", "what did we ship", or "engineering retrospective".
日本語の概要は準備中です。原文の説明を表示しています。
Before committing any non-trivial change, dispatch the diff to a reviewer runtime via ATO (`ato dispatch <reviewer> --session <id>`), parse the numbered/severity-tagged findings, apply or defer each one with a recorded justification, then commit. Fights the "build passes therefore ship it" failure mode — what Garry Tan calls the AI agent complexity ratchet. Place in the v2.16 stack: this skill is the LAST gate. `ato-warroom` decides the design; `ato-mission` runs the multi-step work and produces the diff; `ato-review` checks the diff before commit. When the review is part of a Mission, dispatch the review with `--require-tools read_file,grep,git_diff,git_log` so the reviewer can walk the source itself instead of reasoning from a paraphrase (PR-1.5 tool surface). Receipts land in `execution_logs` and the Mission narrative. Fires automatically before commits touching public surface (CLI subcommands, Tauri commands, MCP tools, schema migrations, security boundaries) or whenever a diff exceeds ~50 LOC of behavior change.
日本語の概要は準備中です。原文の説明を表示しています。
Systematically QA test a web application and fix bugs found. Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs", "test and fix", or "fix what's broken". Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix evidence, and a ship-readiness summary. For report-only mode, use /qa-only.
日本語の概要は準備中です。原文の説明を表示しています。
Review or polish a product UI for accessibility, brand fidelity, hierarchy, rhythm, responsive behavior, themes, interaction states, and generic AI-template patterns. Use for visual audits, accessibility checks, UX polish, UI critique, or pre-ship design review. Do not use for generic code review, backend review, or API design.
日本語の概要は準備中です。原文の説明を表示しています。
Reads, searches and counts Claude Code session transcripts (the .jsonl files under ~/.claude/projects, subagents too) with the csift command-line tool, and ships hooks that re-inject compacted turns or record pending questions. Use when asked what a past or running session said, did, edited, spent or is doing now; when about to grep, jq or script over a transcript jsonl (a type=="user" filter overcounts the person's messages), count how many messages the person typed, tool calls or tokens, or claim something was never done or decided; to rebuild a lost file or plan from what a session wrote, extract pasted images, restore turns a compaction summary lost, find a subagent's own id when CLAUDE_CODE_SESSION_ID names the parent, wait on or message another session or subagent; or when csift prints "unknown label selector", "show needs an address", "looks like a session/agent id, not a project path" or "0 matches — a DEFINITIVE absence". Not for semantic or embedding search: csift matches regular expressions only.
日本語の概要は準備中です。原文の説明を表示しています。
当用户是管理者/创始人/领导者，面临企业增长停滞、文化僵化、战略转型困难、或在问"如何推动组织变革""企业文化怎么改""使命愿景怎么定"时激活。 核心信号：用户在描述组织层面的问题，且已经意识到"不是业务问题而是底层问题"。 不适用于：个人成长问题（除非明确映射到组织场景）、纯战术层面的业务调整。
日本語の概要は準備中です。原文の説明を表示しています。
当用户是创业者/管理者/领导者，遇到企业增长瓶颈、转型困难、或者在问"为什么公司越大越创新不了""为什么我们总是错过新机会""公司的问题到底出在哪"时激活。 核心信号：用户在描述组织发展困境，且问题根源指向领导者自身的认知局限而非外部环境。 不适用于：非管理者的个人发展问题、纯粹的市场/竞争分析、具体业务执行问题。
日本語の概要は準備中です。原文の説明を表示しています。
Release a NowStack Mobile Android app to Google Play production - listing, screenshots, Data safety, content rating, release notes, then promote the tested internal build to the production track with a staged rollout. Use for "release on Android", "publish to Play production", "promote to production", "ship the Android update". If no build is on a testing track yet, run ns-android-beta first.
日本語の概要は準備中です。原文の説明を表示しています。
Build an organic-traffic operating system for any site or app: a multi-phase, resumable engine that plans and ships a BATCH ROADMAP of landing pages (use-cases, playbooks, /for/ pages, roundups) on top of real keyword research, with a persistent phase tracker. Use when the user says 'SEO machine', 'build organic traffic', 'rank on Google', 'we need traffic', 'SEO roadmap', 'batch of pages', 'pages roadmap', or 'build an SEO engine'. Distinct from `seo-audit` (one-off diagnostic) and `seo-content` (single-article writer): this skill owns the multi-page roadmap, run sequencing, page generation, internal linking, and the persistent phase tracker across the whole run. For a single alternatives or vs/comparison page, see /competitor-alternatives; for programmatic SEO templates and content at scale, see /seo-content; for off-page link building, see /off-page-seo. Resumable — every invocation continues the last run.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to plan a product launch, feature announcement, release strategy, or go-to-market plan. Also use when the user mentions 'launch plan', 'go to market', 'GTM', 'Product Hunt', 'beta launch', 'how do I launch', 'pre-launch', 'launch checklist', 'distribution plan', 'release strategy', 'feature announcement', or is about to ship something and needs a distribution plan. Even vague requests like 'I'm almost done building, what now?' or 'how do I get users?' should trigger this skill. Make sure to use this whenever someone is planning ANY kind of product or feature release, even if they don't say 'launch' explicitly — if they're thinking about getting something in front of users, this is the skill. This is the STRATEGIC planner — for operational platform submissions and directory launches, see /startup-launcher instead.
日本語の概要は準備中です。原文の説明を表示しています。
Research companies, competitors, funding, news, leadership, and market context with Exa Agent and advanced search. Use when researching companies, competitor analysis, market research, or building company lists. Writes findings the caller can fold into brand/competitors.md or brand/landscape.md. Prefer this over ad-hoc web search for company deep dives. Distinct from competitive-intel (full brand competitive file methodology) - this skill is the Exa research engine those foundation skills should call.
日本語の概要は準備中です。原文の説明を表示しています。
Create high-converting free resources that capture emails and build trust. Produces complete lead magnets (ebooks, checklists, templates, toolkits, quizzes) with landing page copy, thank-you page, and follow-up email sequence. Use when someone needs a list-building asset, wants to grow their email list, needs an opt-in incentive, a content upgrade, a gated download, or top-of-funnel content. Triggers on 'lead magnet', 'ebook', 'checklist', 'template', 'free resource', 'opt-in', 'grow my list', 'email capture', 'content upgrade', 'list building', 'gated content', or 'free download'. Even if someone just says 'I need something to capture emails' or 'how do I get more subscribers', this is the skill. Every lead magnet passes a 4-gate quality test before shipping.
日本語の概要は準備中です。原文の説明を表示しています。
Turn a local talking-head / 口播 video into metadata, transcript, and an AI-composed card-based video where the agent composes cards by cloning styled templates and filling them (designing bespoke only when content needs it), then renders to MP4. Ships with the Interflow AI club sign-off ("Interflow AI 出品"). Use when the user asks for interflow-video-cut, 口播成片, talking-head repurposing, video takeaways, transcript cleanup, or turning a spoken video into a captioned card video.
日本語の概要は準備中です。原文の説明を表示しています。
Design, audit, or correct an electronic circuit from a product brief, native schematic, netlist, block diagram, or circuit description. Use for architecture and component-function review, power and logic-domain checks, reset and boot sequencing, bus ownership, ratings, timing, protection, safe states, component suitability, circuit bugs, or layout-facing electrical constraints.
日本語の概要は準備中です。原文の説明を表示しています。