「before」の検索結果

Reads Copilot conversation history and extracts executive-ready success stories. Use when the user asks to study prior Copilot sessions, summarize what was done before, mine evidence, or quantify time, cost, risk, and priority alignment from GitHub Copilot history in any workspace or repository.

日本語の概要は準備中です。原文の説明を表示しています。

Develops an implementation plan ready for wave-orchestration to execute. Takes the user's goal or rough plan as input, mines the codebase for facts, grills the user one question at a time for the decisions, drafts the planning/ artifacts (task DAG, wave table, worker prompt template, state file), then reviews its own plan on two axes before seeking approval. Use when the user wants to turn a feature idea, master plan, or backlog into a wave-orchestration execution plan.

日本語の概要は準備中です。原文の説明を表示しています。

Structured planning workflow for any coding task. Use at the start of every new feature, bug fix, refactor, or implementation request. Analyzes the project, asks up to 5 clarifying questions, creates a TODO.md, gets user approval, then executes task by task. Never writes code before a plan is approved.

日本語の概要は準備中です。原文の説明を表示しています。

Authoritative reference for submitting tdmcp to the Anthropic Connectors Directory as a Codex Desktop Extension (MCPB). Use whenever drafting, checking, or fixing the submission — it defines the two submission paths, why tdmcp is a Desktop Extension (never a remote connector), every form field, the rejection-causing gates, and the local-only compliance story. Read this before writing any submission deliverable.

日本語の概要は準備中です。原文の説明を表示しています。

Verification methodology and gate checklist for the tdmcp Connectors Directory submission — run the docs build, build and inspect the .mcpb bundle, sweep for stale .dxt references, and cross-check the form-answer draft against the real requirements. Use to validate the submission package before a human submits, by executing commands and quoting evidence, not by trusting that work was done.

日本語の概要は準備中です。原文の説明を表示しています。

Orchestrates the dedicated Kinect wall harp implementation team. Use whenever the user asks to build, implement, continue, fix, QA, document, or ship the Kinect wall harp, Kinect v2 wall-depth harp, FreenectTD depth-blob hand tracking, projected wall strings, pluck synth harp, or this feature's Layer 1 tool/recipe/docs. Use this before the generic tdmcp-pipeline for this feature.

日本語の概要は準備中です。原文の説明を表示しています。

Design a tdmcp feature into an implementable spec before any code is written — choose the layer, define the Zod input schema, lay out the TD network topology, plan the bridge/Python approach, sketch a UI wireframe when relevant, and list probe-first risks + the test plan. Use whenever a tdmcp feature idea needs a design/wireframe/spec, or when someone asks to plan/scope/architect a new tool, generator, effect, control, or AI prompt for the TouchDesigner MCP server.

日本語の概要は準備中です。原文の説明を表示しています。

Overhaul one app's UI against an audit: UX audit and UI review of the running app, current versus proposed design tokens, a before/after visual plan, a startcycle build, point fixes, accessibility and browser tests, delivered as a PR after GO. Use for "redesign this app", "design overhaul", "audit and fix the UI", "give the app a new look".

日本語の概要は準備中です。原文の説明を表示しています。

Use when you have a spec or requirements for a multi-step task, before touching code

日本語の概要は準備中です。原文の説明を表示しています。

Use when implementing, integrating, upgrading, debugging, or answering anything involving third-party APIs, libraries, frameworks, CLIs, cloud services, model or provider SDKs, fast-moving product behavior, unfamiliar repo docs or specs, errors that may indicate API drift, or high-stakes auth, security, billing, data, migration, deployment, compliance, or privacy behavior. Forces a docs pass before coding from memory.

日本語の概要は準備中です。原文の説明を表示しています。

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

日本語の概要は準備中です。原文の説明を表示しています。

Build a throwaway prototype to answer a design question, as UI variations or a state-model walkthrough. Use when the user types /prototype, wants to sanity-check whether a state model or logic feels right, wants to explore what a UI should look like, or as the prototype step of the web design flow with brainstorm or grill before the final plan goes to plan-canvas (annotate the running prototype with the plan-canvas annotation tool).

日本語の概要は準備中です。原文の説明を表示しています。

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

日本語の概要は準備中です。原文の説明を表示しています。

Use when implementing any feature or bugfix, before writing implementation code

日本語の概要は準備中です。原文の説明を表示しています。

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

日本語の概要は準備中です。原文の説明を表示しています。

Use when a PR or git range needs a visual recap page for a reviewer, with a changed-files tree, per-file notes, a Verified vs Not verified table, risks, and optional before/after images. Local and informational; never posts to GitHub.

日本語の概要は準備中です。原文の説明を表示しています。

Use before creative or constructive work (features, architecture, behavior). Transforms vague ideas into validated designs through disciplined reasoning and collaboration.

日本語の概要は準備中です。原文の説明を表示しています。

BDB Shipping Godmode, the final gatekeeper for production releases. Use when running pre-launch checks, feature-flag rollouts, or rollback planning under Spec-Driven Development before a release ships.

日本語の概要は準備中です。原文の説明を表示しています。

Combines multi-agent brainstorming, the /grill-me slash command, and the 3 Core Godmodes (godmode-engineering, godmode-ui-ux, godmode-shipping) to force a comprehensive, multi-agent ideation and technical design workflow, ending in a plan-canvas review and a hand-off to /startcycle-graph. Use when the user asks to brainstorm, ideate, design, scope or sharpen a plan, idea or product, or when broad exploration before a build is the situation.

日本語の概要は準備中です。原文の説明を表示しています。

Analyze and improve existing Ozor.ai video prompts for better output quality. Use this skill whenever the user has an Ozor prompt that produced mediocre results, wants to improve a video prompt, needs help debugging why a video didn't turn out well, or wants expert feedback on their prompt before running it. Trigger on phrases like 'improve this prompt', 'optimize my Ozor prompt', 'why did my video look bad', 'fix this prompt', 'make this prompt better', 'review my Ozor prompt', 'the video didn't turn out right', 'prompt feedback', 'better results from Ozor', or any request to refine, debug, or enhance an existing Ozor video prompt.

日本語の概要は準備中です。原文の説明を表示しています。

When asynchronously reviewing peer code before merging into the main branch.

日本語の概要は準備中です。原文の説明を表示しています。

Scan an iOS/macOS Xcode project for common App Store rejection patterns before submission. Use when preparing an app for App Store review, after receiving a rejection from Apple, or when auditing metadata, subscriptions, privacy manifests, entitlements, or design compliance. Integrates with the asc CLI for metadata inspection.

日本語の概要は準備中です。原文の説明を表示しています。

Collect, download, and verify App Store Connect Analytics reports with asc. Use when users need to discover analytics report requests, select report instances by processing date or granularity, download every segment, or verify downloaded files against Apple's size and MD5 metadata before analysis.

日本語の概要は準備中です。原文の説明を表示しています。

Implement, review, or improve CloudKit and iCloud sync in iOS/macOS apps. Use when working with CKContainer, CKRecord, CKQuery, CKSubscription, CKSyncEngine, CKShare, NSUbiquitousKeyValueStore, or iCloud Drive file coordination; when syncing SwiftData models via ModelConfiguration with cloudKitDatabase; when handling CKError codes for conflict resolution, network failures, or quota limits; or when checking iCloud account status before performing sync operations.

日本語の概要は準備中です。原文の説明を表示しています。