디자인 스킬

Add runtime UI options (select/checkbox/switch/input) to MaaFramework option surfaces such as `assets/interface.json` or `assets/resource/tasks/**/*.json`. Use when adding a user-facing toggle, selector, checkbox, or input; wiring options to `pipeline_override`; aligning option paths with Python `context.get_node_data()` or CustomAction params; or reviewing option behavior across Pipeline JSON and Python.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generate MaaFramework Pipeline nodes and recognition snippets from screenshots or observed UI state. Use for OCR node generation, ROI sweep, choosing TemplateMatch/OCR/ColorMatch/CustomRecognition, preserving target-file schema style, and designing `next`/`[JumpBack]` links before merging generated nodes into pipeline JSON.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review a design artifact (spec, plan, PR packet) with fresh, memoryless subagents. Invoke when the user asks — "goldfish this", "fresh eyes", "tear this apart" — or after suggesting it for a spec that has grown load-bearing and the user agrees.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Runs a deliberative two-model committee of GPT-6 Astra and Claude Opus under a selectable chair, Fable by default, with `/model-committee-astra`, `/model-committee-opus`, and `/model-committee-sol` selecting the others. Use when a consequential decision has several defensible options and two model families should propose, critique, revise, and cross-rank them against a predeclared rubric before converging, as in research design, interpretation, architecture, manuscript strategy, or evaluation design. Not for factual lookups, independent-coder reliability, brainstorming, routine implementation, or final professional judgment.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Designs survey instruments, covering question wording, scale construction and index reliability, flow and treatment placement, pretesting and soft launches, respondent burden with attention and speeding rules, sensitive questions and social-desirability bias, and treatment delivery. Use when the user writes or revises survey questions, chooses a scale, orders blocks, plans a pilot, or worries respondents will not answer honestly. Indirect measurement goes to list-experiment, multi-country instruments to cross-national-design, and live-survey operations to qualtrics-ops.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Reviews an existing conjoint study for threats to inference and returns severity-ranked findings on design integrity, estimation, measurement error, external validity, and interpretation, including the guardrail against reading an AMCE as majority preference. Use when the user asks whether a conjoint design or analysis holds up, has referee comments on a conjoint, or wants a second opinion on estimation or interpretation. New designs go to conjoint-design, reshaping to conjoint-cleaning.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Designs multi-country survey experiments, covering case selection with a stated comparative logic, instrument localization and TRAPD translation, stimulus calibration, per-country power, and pooled versus per-country analysis with measurement-equivalence checks. Use when the user fields the same experiment in several countries, asks which countries to include, how to adapt an instrument without breaking comparability, whether to pool, or how large each country sample must be. Question wording goes to survey-design, reporting to methods-reporting, the study plan to pre-registration-writing.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Designs conjoint and factorial-vignette experiments: attributes and restrictions, effective-N power, estimand choice among AMCE, marginal means, and AMIE, forced choice versus rating, and PAP tiers. Use when planning a conjoint, critiquing an attribute table, sizing respondents and tasks, or testing interactions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Designs conjoint and factorial-vignette experiments, covering attribute architecture and randomization restrictions, effective-N power, treatment realism, the choice among AMCE, marginal-mean, and AMIE estimands, forced-choice versus rating designs, and PAP tiers. Use when the user is planning a conjoint, drafting or critiquing an attribute table, asking how many respondents or tasks are needed, whether to report AMCEs or marginal means, or how to test interactions. Reviewing an existing design goes to conjoint-diagnostics, cleaning the export to conjoint-cleaning.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Designs multi-country survey experiments: case selection, localization and TRAPD translation, stimulus calibration, per-country power, and pooled versus per-country analysis with measurement-equivalence checks. Use when fielding the same experiment in several countries.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Designs survey instruments: question wording, scales and index reliability, flow and treatment placement, pretesting, attention and speeding rules, and sensitive questions. Use when writing or revising survey questions, choosing scales, ordering blocks, or planning a pilot.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

DRAFT. Design and harden a standing Luma registration/unsubscribe webhook that enriches guests and writes to CRM or customer DB — with backfill and versioning. Not installed by deepline skills.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design RESTful APIs with best practices for consistency and usability

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Write YouTube community-tab posts: text updates, polls, image-caption posts, and questions that drive comments and bring subscribers back between video uploads. Tuned to the community tab's role as a low-friction touchpoint that keeps a channel warm and feeds session signals. Returns a copy-paste block (community posts have no publishing API, so this is always manual by design). Use to write a community post or poll. Not for video titles or descriptions (use yt-title-optimizer and yt-description-writer).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Script the spoken opening that decides retention: the first 30 seconds of a long-form YouTube video or the first 3 seconds of a YouTube Short. Uses 2026 patterns (restate-and-raise, cold-open payoff tease, question-and-contract, and the 3-second frame-one Shorts hook with a designed loop) to confirm the title's promise, open a loop, and earn the next 30 seconds with no intro. Use to write or fix a video opening. Not for the title (use yt-title-optimizer) or description (use yt-description-writer).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Open a ready-to-use local 3D model composition workbench for GLB or GLTF files. Use when the user says "打开模型工作台", asks to place, rotate, scale, arrange, or frame one or more 3D models, or needs a clean composition screenshot before website or Image 2 design. If the user has not supplied a model, request GLB/GLTF files first; after models are available, generate the workspace, start its localhost server, and open it automatically.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design, build, evaluate, or teach graph-based systems. Use for knowledge graphs, ontology/schema design, entity/relation/event extraction, entity resolution and fusion, GraphRAG or graph memory, and agent/task dependency graphs with concurrency, joins, failure handling, verification, or human gates.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design and run controlled experiments using the experiment-registry MCP server — domain-agnostic, pluggable, mechanically enforced. Use when you need evidence that a change actually improves behaviour.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use before any CLI/TUI display code is written, modified, or audited — runs the 7-stage discipline (Context, Register, Shape brief, Implement, Critique, Audit, Polish) for Typer, Rich, Textual, and Questionary work, grounded in per-project PRODUCT.md and DESIGN.TUI.md/DESIGN.md. Triggers on output formatting, display design, interactive prompts, visual consistency, TUI layout, progress display, dashboard design, design audit, design polish, design critique, shape brief, register decision (brand-cli vs product-cli), and AI-slop checks.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when independently assessing how bounded Python code could accomplish the same behavior with less maintained code, more Pythonic design, newer language/stdlib capabilities, or well-maintained ecosystem libraries.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when facing unknowns, debugging without a clear cause, or making architecture decisions — enforces hypothesis-driven scientific reasoning through observation, hypothesis formulation, prediction, experiment design, and evidence-based conclusion. Use when previous attempts have failed or the problem space involves uncertainty.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when independently hunting Python code smells, deviations from engineering standards, maintenance hazards, or suspicious design choices in a bounded review surface.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Orchestrate the full plugin development lifecycle from blank canvas to marketplace-ready. Use when creating a new plugin, improving an existing plugin, fixing validation errors, or taking a plugin through assessment, research, design, creation, debugging, optimization, and verification. Complements /plugin-creator:plugin-creator which provides the detailed new-plugin creation workflow with discussion capture, parallel research, and atomic implementation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Assess a plugin and produce an executable refactoring design, task plan, and context manifest. Use when preparing systematic plugin refactoring.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.