4,503 件 ・ 関連度順
概要と使いどころ
Review the product engineer's post-implementation testing notes for how thoroughly they cover the card's requirements and risk, and whether regression-worthy cases are automated at the right level of the test hierarchy
日本語の概要は準備中です。原文の説明を表示しています。
Add a new component showcase, block, or template preview page and register it everywhere it must appear (navigation, command palette, route lists, SEO, source view). Use when adding anything under /components, /blocks, or /templates.
日本語の概要は準備中です。原文の説明を表示しています。
Redesign GitHub README homepages or create project-native pure SVG, hybrid SVG-composed PNG/WebP, and opt-in animated GIF assets. Use when a user asks to beautify, redesign, rebrand, visually upgrade, simplify, or audit a GitHub README; create only a hero, section headers, diagrams, badges, motion graphics, showcase modules, or other README assets; or turn a repository homepage into a cohesive visual story. If whole-README work versus asset-only work is unclear, ask which scope the user wants. For hero-like assets where pure SVG and generated raster material are both viable, explain the tradeoffs and confirm the implementation before creating the asset.
日本語の概要は準備中です。原文の説明を表示しています。
从用户指定的本机 Codex Skill 显式派生一个项目级 Codex Flight Control Private Skill，同时不修改、移动、禁用或删除原 Skill。仅当用户直接调用 $flight-forge-local-skill 时使用；禁止隐式调用，也禁止在普通项目扫描中自动熔炼。
日本語の概要は準備中です。原文の説明を表示しています。
显式暂停、恢复或取消一个受治理 Run 的 exact Mission Controller。仅当用户使用精确命令 `$flight-control-run` 并依次提供 run_id、controller_id、expected_controller_version 与 PAUSE、RESUME 或 CANCEL 时使用；不能把自然语言意图、Lead credential、Controller 的 allowed_next_actions 或历史授权当作本次用户授权。
日本語の概要は準備中です。原文の説明を表示しています。
为一个已经创建的受治理 Run，显式批准或拒绝一个指定的 Manual Verification 条目。仅当用户本人针对明确命名的人工门禁作出决定时使用；禁止代替用户调用，也禁止用它替代可由命令验证的证据。
日本語の概要は準備中です。原文の説明を表示しています。
在用户级或项目级检查、验证、显式设置或显式重置 Codex Flight Control 的角色模型与 reasoning effort 策略。仅当用户直接调用 $flight-configure-roles 时使用；禁止隐式触发，也禁止在普通飞控开发流程中顺便修改配置。
日本語の概要は準備中です。原文の説明を表示しています。
显式启用或关闭一个受治理 Run 的本地 Codex App Server continuation。仅当用户使用精确命令 `$flight-connect-host` 并依次提供 run_id、thread_id 与 ENABLE 或 DISABLE 时使用；不能把自然语言同意、Lead 判断、UI 操作或已有 credential 当作启用授权。
日本語の概要は準備中です。原文の説明を表示しています。
从当前任务、用户指定的 Codex 任务或用户导出的结构化材料中提取可观察事实，并显式熔炼一个项目级 Codex Flight Control Private Skill。仅当用户直接调用 $flight-forge-session 时使用；禁止自动把会话总结成 Skill。
日本語の概要は準備中です。原文の説明を表示しています。
使用有界本地报告诊断 Codex Flight Control 的安装、runtime、文档、持久状态、Wave、Guidance、Private Skill、角色策略、托管工作区、Evidence、Completion Gate 和恢复状态。用户询问飞控状态、健康、支持信息、恢复分析或阻断原因时使用；禁止上传数据或执行破坏性修复。
日本語の概要は準備中です。原文の説明を表示しています。
显式授权一个已经由 Codex Flight Control 封存、用户可见且 hash 精确匹配的本地维护计划。仅当用户原样输入 `$flight-maintain` 并依次提供 plan_id 与 plan_hash 时使用；不能用自然语言同意、模型判断或 UI 点击替代。
日本語の概要は準備中です。原文の説明を表示しています。
从用户指定的 GitHub 仓库显式熔炼一个项目级 Codex Flight Control Private Skill。仅当用户直接调用 $flight-forge-github 并提供或明确指定仓库时使用；禁止根据建议隐式调用，也禁止在普通飞控开发流程中自动熔炼。
日本語の概要は準備中です。原文の説明を表示しています。
使用状态绑定的最小 Tool Surface、exact Action Gateway、来源可追踪的 MissionSpec 与 Verification Manifest、宿主无关 Flight Progression Engine、可选且无权威的 App Server continuation、顺序持久 Wave、一层原生 Agent、困难后强制战术指导、证据型 Capability Profile、显式 Manual Verification、不可变宿主 Evidence、恢复检查点和仅本地 Git，治理复杂 Codex 开发。用户要求飞控接管、继续、自主开发、修复或完成多步骤软件项目，需要有界并行子代理，或实现前必须建立文档工程时使用。
日本語の概要は準備中です。原文の説明を表示しています。
执行显式、编码前的 Product Discovery，把早期或模糊的软件想法转化为用户确认的 Intent、丰富方案卡片、对比矩阵、可编辑画布和可持续 D0 文档基线。仅当用户明确调用 $flight-brainstorm，准备在 Flight Control Run 之前探索空白、稀疏、不确定或方向发生重大变化的项目时使用；禁止因模糊请求或普通开发工作隐式触发。
日本語の概要は準備中です。原文の説明を表示しています。
Cross-reference project artifacts (WBS, meeting minutes, requirements docs) by date, participant, and action items. Extract commitments from meeting minutes and link to WBS tasks. Generate traceability reports showing which decisions were captured in which documents.
日本語の概要は準備中です。原文の説明を表示しています。
Bootstrap a new or existing project with a small, file-based documentation system so Claude Code keeps context, lessons, and decisions across session restarts instead of starting cold every time. Sets up a handful of markdown files under .claude/ (standing rules, a free-form note to your next session, a phased roadmap, a prioritized backlog, and searchable history/changelog archives) sized and split so the files read every session stay small while the archives grow without ever costing context. Use this whenever someone is starting a new project and asks how to structure it for long-running AI-assisted work, wants Claude to "remember" things between sessions without relying on chat history, asks for a CLAUDE.md + backlog + changelog setup, mentions "session continuity", "persistent context", "project memory system", or is retrofitting an existing codebase that has no such system yet. Also use to explain or extend an already-bootstrapped bottle system (add a rule, start the archival script, add a new backlog section).
日本語の概要は準備中です。原文の説明を表示しています。
Show what this repository has already decided about its vulnerabilities, read from the durable record rather than by scanning again — open versus resolved, the decision taken on each, and what is still waiting. Use when picking up triage after a break, auditing past decisions, onboarding to a repository with security history, or checking nothing high-severity is open before a release.
日本語の概要は準備中です。原文の説明を表示しています。
A six-year-old code reviewer who asks "why?" about everything. Catches over-engineering, confusing names, and unnecessary complexity. Output is a 1-2 line summary of the request as a whole: how is the file? Is the class nice? Is the function correct?
日本語の概要は準備中です。原文の説明を表示しています。
Record the statements a journal requires and a reader checks — authors with their CRediT contributions, ethics approval that names the body and the reference number, how consent was taken, funding with grant numbers, conflicts of interest, data availability with an address or a reason, and the use of generative AI — as a validated record that the submission folder prints and the manuscript never carries. Use when a run is heading for submission, when an author asks who should be listed, when consent, approval or data sharing has to be stated, or when the venue's AI policy comes up.
日本語の概要は準備中です。原文の説明を表示しています。
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze a local codebase and infer the architecture it is actually using, including repo kind, best-fit dominant architecture, directly evidenced coexisting patterns, major subsystem exceptions, confidence, docs-vs-code drift, and repo-fit hints for downstream agents. Use when prompts ask what architecture a repo uses, whether it is really hexagonal or just layered, what subtle patterns shape a repo or slice, how a target slice fits a hybrid monorepo, whether documented architecture matches implementation, or when `/tw-tk` needs a repo-dialect preflight before making a minimal change.
日本語の概要は準備中です。原文の説明を表示しています。
Generate onboarding documentation for a codebase — architecture overview, key files, local setup, and common gotchas. Use this skill whenever someone asks to onboard onto a codebase, create onboarding docs, generate a codebase overview, explain a project's architecture to newcomers, or asks "how does this codebase work". Also trigger when users say things like "document this repo for new devs", "write a getting started guide", or "help me understand this project".
日本語の概要は準備中です。原文の説明を表示しています。
Post-launch review of a shipped PRD against the brief's success metrics. Did we move the metric? What did the data actually show? Which assumptions held, which broke? Which accepted-gap decisions resolved (confirmed vs. invalidated)? What would we do differently? Triggers on "outcome review", "did it work", "post-launch review", "did we move the metric", "retro the feature", "was it worth it". Produces a Confluence outcome-review page and updates the brief + linked decisions.
日本語の概要は準備中です。原文の説明を表示しています。
Load when asked where code lives, how modules relate, what calls a symbol, what implements a feature, or for an architecture/codebase tour using the knowledge graph; not for bug diagnosis, diff review, or refactoring.
日本語の概要は準備中です。原文の説明を表示しています。