本文へ移動
cccskills
無料GitHub で公開

logo-generation

Generate a logo or brand mark — structured prompt, provider routing, and a true-vector path. Use for logo or brand mark generation.

インストール方法を見る

含まれるファイル(2)

  • SKILL.md5.2 KB
  • evals/triggers.json1.7 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

logo-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.

When to use

  • User asks to generate, create, or design a logo or brand mark.
  • End-to-end logo production (path selection + routing + prompting + governance).
  • When a simple geometric mark can be authored directly as SVG without a raster model.

Procedure

  1. Capture the brand brief — extract: business name, style intent (wordmark / icon mark / combination), colour palette, do/don't constraints (e.g. "no gradients", "must be legible at 16 px").
  2. Choose the path — raster concept (text-in-mark → Ideogram for legible type) vs. true vector (a vector-native provider for editable marks, or a hand-authored one for simple geometric marks — authored under svg-authoring, never free-hand). Raster output is a concept only — not a shippable logo asset.
  3. Inject brand tokens when a brand layer is present (pack-brand) — pull the registered palette, typeface, and spacing tokens. When no brand layer exists, use the brief's palette and type choices directly.
  4. Route + prompt via 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).
  5. Dry-run + validate — invoke the adapter (scaffold-tier; returns a dry-run plan). If the vector path is taken, the vector verdict comes from 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.
  6. Rights check — never reproduce a mark that resembles an existing trademarked logo. Run image-likeness-and-rights when the brief names a brand, references a known mark style, or targets a regulated sector.

Output format

  1. Chosen path — raster concept or true vector, with rationale.
  2. Prompt or SVG — the prompt string ready to copy (raster/vector provider), or the authored SVG markup (LLM-authored geometric mark path).
  3. Governance note — rights check outcome and the adapter dry-run caveat: "adapter is experimental (scaffold-tier) — dry-run plan only; no rendered asset until promotion per provider-lifecycle-discipline."

Gotcha

  • Raster models cannot emit usable editable logos — general-purpose image models garble text and produce no <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.
  • Scaffold-tier adapters produce plans, not pixels — all adapters are 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.

Do NOT

  • Do NOT ship a raster PNG as a "logo" when an editable vector mark is needed — surface the vector path and the raster-model limitation explicitly.
  • Do NOT generate a mark resembling an existing trademarked logo — run image-likeness-and-rights when the brief references a known brand or mark.
  • Do NOT claim a live render at scaffold tier — the dry-run caveat is mandatory every time.

See also

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

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'.

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

event4u-app/agent-config112026年10月12日 更新

Use when defining or auditing the activation event — aha-moment selection, retention correlation, falsifiable definition. Triggers on 'what is our aha moment', 'redefine activation'.

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

event4u-app/agent-config112026年10月12日 更新

Use when capturing an architectural decision — file naming, next ADR number, Status / Context / Decision / Consequences, index regen; fires even without saying 'ADR'.

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

event4u-app/agent-config112026年10月12日 更新

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.

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

event4u-app/agent-config112026年10月12日 更新

Use when reading, creating, or updating agent documentation, module docs, roadmaps, or AGENTS.md. Understands the full .augment/, agents/, and copilot-instructions structure.

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

event4u-app/agent-config112026年10月12日 更新

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.

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

event4u-app/agent-config112026年10月12日 更新

event4u-app のスキルをすべて見る

このスキルの問題を報告する