「structured」の検索結果

Use when planning or building a SaaS MVP from scratch. Provides a structured roadmap covering tech stack, architecture, auth, payments, and launch checklist.

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

Get reliable JSON, enums, and typed objects from LLMs using response_format, tool_use, and schema-constrained decoding across OpenAI, Anthropic, and Google APIs.

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

Deep research with structured reports and charts. ONLY use when the user explicitly requests research/analysis, or needs data visualization with charts, or quantitative/comparative analysis across multiple sources. Do NOT use for simple questions or quick lookups.

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

Generate structured changelogs from git history. Use when user asks "what changed recently", "generate a changelog", "summarize commits" or user wants to understand recent development activity.

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

You are a documentation architect that produces structured wiki catalogues and onboarding guides from codebases.

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

Annotate and map the anatomy of any design. Identify visual hierarchy, spacing systems, color roles, and tension points through clinical analysis. Use when doing formal design audits, teaching design analysis, or building structured observation skills.

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

Structured taste breakdowns of real products. The format for making taste observations legible and shareable. Use when analyzing products, writing case studies, documenting design observations, or teaching through example.

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

Structured exposure habits for building taste through relentless, intentional consumption. Not passive scrolling. Active intake across design, architecture, film, music, food, and culture. Use when building a taste practice, advising on professional development, or diagnosing why someone's design range feels narrow.

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

Write a structured design review that someone can act on without follow-up questions. Use when giving async design feedback, writing portfolio case studies, or documenting design decisions.

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

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.

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

Survey one surface of tdmcp (artist controls, library/packaging, CLI/DX, AI/LLM, or TouchDesigner depth) for candidate NEW features — inventory what exists, cross-check the roadmap, apply the gap-finding lenses, vet each idea, and emit a structured, novelty- and confidence-labelled candidate list to _workspace/discovery/. Use when a td-surveyor agent is scouting a surface during the feature-discovery harness.

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

Design, validate, and optimize schema.org structured data for eligibility, correctness, and measurable SEO impact.

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

Audit technical SEO across crawlability, indexability, security, URLs, mobile, Core Web Vitals, structured data, JavaScript rendering, and related platform signals like robots.txt and AI crawler access.

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

Design and evaluate programmatic SEO strategies for creating SEO-driven pages at scale using templates and structured data.

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

Get reliable JSON, enums, and typed objects from LLMs using response_format, tool_use, and schema-constrained decoding across OpenAI, Anthropic, and Google APIs.

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

Generate a concise and structured PR description from commit history with minimal token usage

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

Multi-agent brainstorming: async opinion collision with expert personas. Mixed Codex/Claude Code engine. Use when multiple AI agents need to collaboratively discuss, debate, and converge on solutions through structured dialog. Triggers: brainstorm, multi-perspective discussion, opinion collision, expert debate, war room, collective intelligence, 头脑风暴, 多视角讨论, 集思广益.

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

Resolve Swift concurrency compiler errors, adopt approachable concurrency (SE-0466), and write data-race-safe async code. Use when fixing Sendable conformance errors, actor isolation warnings, or strict concurrency diagnostics; when adopting default MainActor isolation, @concurrent, nonisolated(nonsending), or Task.immediate; when designing actor-based architectures, structured concurrency with TaskGroup, or background work offloading; or when migrating from @preconcurrency to full Swift 6 strict concurrency.

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

Integrate on-device AI using Foundation Models framework, Core ML, and open-source LLM runtimes on Apple Silicon. Covers Foundation Models (LanguageModelSession, @Generable, @Guide, SystemLanguageModel, structured output, tool calling), Core ML (coremltools, model conversion, quantization, palettization, pruning, Neural Engine, MLTensor), MLX Swift (transformer inference, unified memory), and llama.cpp (GGUF, cross-platform LLM). Use when building tool-calling AI features, working with guided generation schemas, converting models, or running on-device inference.

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

Build, review, or improve networking code in iOS/macOS apps using URLSession with async/await, structured concurrency, and modern Swift patterns. Use when working with REST APIs, downloading files, uploading data, WebSocket connections, pagination, retry logic, request middleware, caching, background transfers, or network reachability monitoring. Also use when handling HTTP requests, API clients, network error handling, or data fetching in Swift apps.

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

Ground rules for an effective subagent in a loop, workflow, or graph run. Stay in scope, escalate when stuck, return structured results. Use when acting as a subagent, writing subagent prompts, or reviewing delegated agent behavior.

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

Craft a single, high-quality GitHub issue from a developer's description of a bug, unexpected behavior, or desired enhancement. Walks through reproduction, codebase exploration, and structured drafting so the issue is actionable on arrival. Use when user wants to file an issue, report a bug, request a feature, or document a problem they've encountered.

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

Structured 3-phase peer review of a diff or PR — intent, issues by severity, then pointed merge-readiness questions and a verdict. Use for general code review. Not for AI workflow self-fix-and-edit (ai-systems-review) or no-edit devil's-advocate threat models (adversarial-challenge). Phase 3 asks questions only; it is not the adversarial-challenge skill.

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

This skill should be used when the user asks to "analyze a lawsuit", "訴訟分析", "事件分析", "書面分析", "case analysis", "判決分析", "訴訟書類の整理", or wants to extract structured information from litigation documents.

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