Use when reviewing UI for accessibility — WCAG 2.2 AA, keyboard nav, focus, ARIA, contrast, screen-reader semantics — even on 'is this a11y-OK?' or 'mach das barrierefrei'.
日本語の概要は準備中です。原文の説明を表示しています。
Generate a logo or brand mark — structured prompt, provider routing, and a true-vector path. Use for logo or brand mark generation.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Generate a logo or brand mark end-to-end: capture the brand brief, choose raster
vs. true-vector path, inject brand tokens when available, route to the right
provider, author a provider-specific prompt, dry-run the adapter, and apply rights
governance. All adapters are scaffold-tier (dry-run) until promoted to stable.
svg-authoring, never free-hand). Raster output
is a concept only — not a shippable logo asset.pack-brand) — pull the
registered palette, typeface, and spacing tokens. When no brand layer exists,
use the brief's palette and type choices directly.image-provider-routing
and prompt-engineering-image — apply
provider-specific grammar (text-literal first for Ideogram, style: vector param
for a vector-native provider, direct SVG authoring for simple geometric shapes).lint_svg_asset's vector-honesty family plus the render witness, not from
counting <path> elements: a raster embedded beside one dummy path passes
that count and is not a vector, and a mark built from rect/circle fails
it and is one. See svg-authoring.image-likeness-and-rights
when the brief names a brand, references a known mark style, or targets a
regulated sector.provider-lifecycle-discipline."<path> geometry. A PNG concept is useful
for direction-setting, but it is not a logo asset. Use the vector path for any
mark that must scale, be modified, or be handed to a designer.experimental (dry-run only). Claiming a rendered asset exists while no adapter
is stable misleads the caller.Good example: Brief for a wordmark → route to a vector-native provider with
style: vector, run lint_svg_asset over the output and confirm it carries no
embedded raster, note "experimental — dry-run plan only."
Bad example: Routing a logo brief to a photoreal raster model and delivering the PNG as the final logo file.
image-likeness-and-rights when the brief references a known brand or mark.image-generation — general-purpose image generation (non-logo briefs).image-provider-routing — select the right provider before writing the prompt.prompt-engineering-image — translate the brief into provider-specific prompt grammar.image-likeness-and-rights — rights check before generating brand marks or likenesses.まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Use when reviewing UI for accessibility — WCAG 2.2 AA, keyboard nav, focus, ARIA, contrast, screen-reader semantics — even on 'is this a11y-OK?' or 'mach das barrierefrei'.
日本語の概要は準備中です。原文の説明を表示しています。
Use when defining or auditing the activation event — aha-moment selection, retention correlation, falsifiable definition. Triggers on 'what is our aha moment', 'redefine activation'.
日本語の概要は準備中です。原文の説明を表示しています。
Use when capturing an architectural decision — file naming, next ADR number, Status / Context / Decision / Consequences, index regen; fires even without saying 'ADR'.
日本語の概要は準備中です。原文の説明を表示しています。
Adversarial critique — devil's advocate, stress-test, honest teardown ('poke holes', 'be brutal', 'was hältst du davon'); explicit request only. Routine code or design review → code-review.
日本語の概要は準備中です。原文の説明を表示しています。
Use when reading, creating, or updating agent documentation, module docs, roadmaps, or AGENTS.md. Understands the full .augment/, agents/, and copilot-instructions structure.
日本語の概要は準備中です。原文の説明を表示しています。
Use for an adversarial red-team / blue-team / auditor review of an AI agent's CONFIG + behaviour (rules, skills, MCP, hooks, permissions) — attack-chain → defensive-gap list, not a code audit.
日本語の概要は準備中です。原文の説明を表示しています。