Agent skill

Logo Semantic Fusion

by ZSeven-W in ZSeven-W/craft-skills

Develop and evaluate logo concepts when the explicit design problem is semantic fusion: two or more brand meanings must share a contour, stroke, negative space, glyph skeleton, or shape system.

Apache-2.0Auto-check passedMedia & Creative

Install Logo Semantic Fusion

skills CLI
$ npx skills add ZSeven-W/craft-skills --skill logo-semantic-fusion -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install ZSeven-W/craft-skills logo-semantic-fusion --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/ZSeven-W/craft-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/logo-semantic-fusion .claude/skills/logo-semantic-fusion && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
logo-semantic-fusion
GitHub stars
225
Used in
1 other repo
Token cost
~1.7k tokens
SKILL.md length
832 words
Files
7 (incl. references)
Skills in repo
5
Repo updated
First seen
Licence
Apache-2.0

At a glance

Develop and evaluate logo concepts when the explicit design problem is semantic fusion: two or more brand meanings must share a contour, stroke, negative space, glyph skeleton, or shape system.

  • Works in 3 steps: At least two distinct brand signals are… → A plausible shared contour, stroke,… → Fusion improves the brand idea without…
  • Fusion-focused design
  • SKILL.md covers Route the references, Choose one mode, Run the applicability gate and Establish the brief, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Logo Semantic Fusion is an agent skill from ZSeven-W/craft-skills. Develop and evaluate logo concepts when the explicit design problem is semantic fusion: two or more brand meanings must share a contour, stroke, negative space, glyph skeleton, or shape system. Use for fusion-focused design or redesign, critique, comparison, or prompt-only work on a logo, symbol, app icon, monogram, or wordmark. Do not use for generic logo creation, general identity systems, illustration, packaging, or type selection unless semantic fusion is a stated or clearly central requirement.

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including reference files (for example `README.en.md`, `README.md` and `agents/openai.yaml`).

It sits in Media & Creative, covering Logo and visual identity. The repository describes itself as: Research-backed, eval-driven skills for AI agents. The licence is Apache-2.0.

When your agent uses it

  • Fusion-focused design
  • Prompt-only work on a logo
  • Generic logo creation
  • General identity systems

Example prompts

  • “/logo-semantic-fusion”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. At least two distinct brand signals are worth encoding.
  2. A plausible shared contour, stroke, void, glyph skeleton, or module system can carry them.
  3. Fusion improves the brand idea without sacrificing required-script legibility, category trust, or recognition at the intended scale.

What it can do on your machine

Read from SKILL.md and the folder at commit 01c8ffe. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Logo Semantic Fusion loads about 1.7k tokens when it runs, and up to ~4.8k if it reads all its reference files. Until then it costs about 131 tokens; SKILL.md has 832 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~131
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from ZSeven-W/craft-skills at commit 01c8ffe, republished under its Apache-2.0 licence (© ZSeven-W). 832 words, ~1,681 tokens.

Download SKILL.mdSave it as .claude/skills/logo-semantic-fusion/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.
name
logo-semantic-fusion
description
Develop and evaluate logo concepts when the explicit design problem is semantic fusion: two or more brand meanings must share a contour, stroke, negative space, glyph skeleton, or shape system. Use for fusion-focused design or redesign, critique, comparison, or prompt-only work on a logo, symbol, app icon, monogram, or wordmark. Do not use for generic logo creation, general identity systems, illustration, packaging, or type selection unless semantic fusion is a stated or clearly central requirement.

Logo Semantic Fusion

Build one structurally shared idea. Do not force fusion when a simpler wordmark, single symbol, or broader identity system serves the brand better.

Route the references

Choose one mode

  • Design or redesign: Run the full workflow. Preserve stated redesign invariants before exploring.
  • Critique: Inspect the supplied artifact and report evidence, hard-gate failures, and the smallest useful revisions. Do not redesign unless asked.
  • Compare: Apply the same brief, scales, and hard gates to every candidate. Allow reject all; do not invent a new candidate unless asked.
  • Prompt-only: Produce a production prompt, constraints, and future acceptance tests. Do not generate an artifact or claim visual QA, similarity screening, or production readiness.

Run the applicability gate

Proceed with fusion concepting only when all are true:

  1. At least two distinct brand signals are worth encoding.
  2. A plausible shared contour, stroke, void, glyph skeleton, or module system can carry them.
  3. Fusion improves the brand idea without sacrificing required-script legibility, category trust, or recognition at the intended scale.

If any condition fails, state why and recommend a pure wordmark, single symbol, abstract mark, or identity-system route. In critique or compare mode, treat forced fusion as a finding instead of ending the review.

Establish the brief

Extract or reasonably infer:

  • name, pronunciation, audience, category, promise, and personality;
  • target contexts and smallest committed size;
  • required scripts, must-keep elements, and forbidden motifs;
  • color, background, accessibility, and delivery constraints.

State consequential assumptions. Do not improvise unfamiliar letterforms or characters: consult authoritative form references and require a fluent reader or native reviewer before calling the result production-ready.

Inventory semantics and screen prior art

Map up to three primary signals to visual structures and language structures. Describe geometry, not only nouns.

During early ideation, list provisional category clichés and mark the avoid map not screened; do not block concept generation on open-ended research. Before advancing a direction or claiming distinctiveness, review a bounded current sample of relevant-category marks and the closest structural analogues. Record sources, dates, recurring silhouettes, distinctive constructions, and unresolved gaps without implying an exhaustive search. If current screening is unavailable, keep the work not screened and make no originality claim. Treat this as design-direction screening, never trademark clearance.

Generate distinct concept families

Create at least six thumbnails across at least three families and three fusion methods. Make every family change both:

  • the semantic pairing or interpretation; and
  • the dominant silhouette or visual skeleton.

Count a change of method alone as a variant, not a new family. Name the shared structural move for every thumbnail. Reject pasted icons, complete-symbol overlaps, generic containers, explanation-dependent readings, and close imitation.

Prefer two signals in the core mark. Add a third only when the same geometry carries it.

Show full SKILL.md (352 more words)Show less

Select before polishing

Score candidates from 1 to 5 on brand fit, fusion integrity, screened distinctiveness, smallest-size legibility, one-color reproducibility, and cultural/category safety. Use higher scores for better or safer outcomes.

Advance only when no score is below 3, fusion integrity and cultural/category safety are at least 4, and the mean is at least 3.8. A hard-gate failure in the review checklist overrides the score. Lock silhouette, fusion relationship, dominant angle, stroke or fill logic, and essential negative space before rendering.

Render in controlled passes

  1. Draw in black and white.
  2. Normalize weight, corners, curves, spacing, and optical balance.
  3. Remove or responsively replace details that fail at the smallest committed size.
  4. Add color only after monochrome works.
  5. Solve the wordmark lockup separately unless it is the fused mark.

Use image generation for isolated flat concept sheets, not precision masters. Rebuild selected geometry as clean vector paths when production precision matters.

Verify the actual artifact

Run the review checklist on the rendered output. Test required sizes, one color, reverse, grayscale, and silhouette. If the full mark fails at small sizes, create a responsive micro mark and define the switch point.

Do not report visual QA from a prompt, source file, or intention. If no artifact was inspected, state visual QA not run. Preserve locked invariants during local fixes, then rerun every applicable check.

Hand off proportionately

For production delivery, define clear space, minimum sizes, responsive variants, lockups, color variants, and basic vector/export requirements. Mark non-applicable items explicitly. For concept-only or prompt-only work, list these checks as pending rather than implying completion.

Deliver by mode

  • Design or redesign: Return the brief, applicability result, semantic inventory, avoid map, family matrix, scores, selected principle, artifact, QA result, and handoff status.
  • Critique: Return evidence-linked findings, hard-gate status, pass, revise, or reject, and minimal revisions.
  • Compare: Return a normalized score table, hard-gate status, and a winner or reject all.
  • Prompt-only: Return the prompt, negative constraints, and future acceptance tests. State that no artifact was inspected and visual QA and production readiness remain unverified.

Always distinguish design-direction similarity screening from jurisdiction- and class-specific trademark clearance.

© ZSeven-W, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 6 other files (references) in skills/logo-semantic-fusion of ZSeven-W/craft-skills.

  • SKILL.md
  • README.en.md
  • README.md
  • agents/openai.yaml
  • references/concept-methods.md
  • references/review-checklist.md
  • references/source-notes.md

Open the folder on GitHubat commit 01c8ffe

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in ZSeven-W/craft-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Logo Semantic Fusion next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Logo Semantic Fusion compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Logo Semantic Fusion this skillZSeven-W/craft-skills2251 repos~1.7kAutomated safety check: PassApache-2.0
Brand and Design Toolkitnextlevelbuilder/ui-ux-pro-max-skill135k1 repos~3.5kAutomated safety check: PassMIT
Anthropic Brand Stylinganthropics/skills180k30 repos~559Automated safety check: PassApache-2.0
Logo Designkaankiziltug/logo-design-skill2.5k—~4.4kAutomated safety check: PassMIT
Logo Generatorop7418/logo-generator-skill2.2k—~1.8kAutomated safety check: NotesNone
Web Asset Generatoralonw0/web-asset-generator5141 repos~6.6kAutomated safety check: PassMIT

Similar skills

  • Brand and Design Toolkit

    nextlevelbuilder/ui-ux-pro-max-skill

    Bundles design tasks behind one skill: brand identity, tokens, UI styling, logos, corporate identity mockups, slides, banners, icons and social images.

    135k GitHub starsUsed in 1 repo~3.5k tokens
    Media & CreativeAuto-check passed
  • Anthropic Brand Styling

    anthropics/skills

    Official

    Applies Anthropic's brand colors and fonts to artifacts such as PowerPoint slides, using fixed hex values for text and accents, Poppins headings and Lora body text.

    180k GitHub starsUsed in 30 repos~559 tokens
    Media & CreativeAuto-check passed
  • Logo Design

    kaankiziltug/logo-design-skill

    Professional logo and brand-mark design, from brief to production files.

    2.5k GitHub stars~4.4k tokensUpdated 10 days ago
    Media & CreativeAuto-check passed
  • Logo Generator

    op7418/logo-generator-skill

    Generate professional SVG logos and high-end showcase images.

    2.2k GitHub stars~1.8k tokensUpdated 5 mo ago
    Media & CreativeAuto-check: notes
  • Web Asset Generator

    alonw0/web-asset-generator

    Generate web assets including favicons, app icons (PWA), and social media meta images (Open Graph) for Facebook, Twitter, WhatsApp, and LinkedIn.

    514 GitHub starsUsed in 1 repo~6.6k tokens
    Media & CreativeAuto-check passed
  • Image Generation

    onyx-dot-app/onyx

    Generate or edit raster images (photos, illustrations, textures, sprites, mockups, logos, infographics) using the workspace's configured image-generation provider via onyx-cli image.

    32k GitHub starsUsed in 1 repo~1.7k tokens
    Media & CreativeAuto-check passed

More from ZSeven-W/craft-skills

  • Native Transparent Imagegen

    ZSeven-W/craft-skills

    Generate new raster assets that must contain native pixel transparency, then verify the untouched PNG or WebP before delivery.

    225 GitHub starsUsed in 1 repo~1.1k tokens
    Auto-check passed
  • Recurring Character Diary Comic

    ZSeven-W/craft-skills

    Create, audit, and repair short page-native diary comics around an existing authorized recurring character, with story-directed page rhythm, exact dialogue, directional-surface proof, and…

    225 GitHub starsUsed in 1 repo~2.8k tokens
    Auto-check passed
  • Qwen Image Gen

    ZSeven-W/craft-skills

    为 Qwen-Image 编写和改写生图提示词,区分局部编辑与参考主体创作,处理同人物系列、画幅及原图验收;用户要求生成时连接其已有的 Qwen 图像工作流。不用于下载权重、通用模型运维或其他图像模型。

    225 GitHub stars~478 tokensUpdated 18 days ago
    Auto-check passed
  • Single Path Process Diorama

    ZSeven-W/craft-skills

    将 3–5 步线性流程制作成单张完整、非宫格的微缩剧场成品。适用于流程故事封面、制作过程图、软件交付旅程与科普式微缩场景;以单一路径、可追踪载体、可辨识动作和题材匹配的材质表达顺序。不用于需要精确分支和数据尺度的流程图、实际操作规程或普通城市微缩景观。

    225 GitHub stars~824 tokensUpdated 18 days ago
    Auto-check passed

Questions about Logo Semantic Fusion

What does Logo Semantic Fusion do?

Develop and evaluate logo concepts when the explicit design problem is semantic fusion: two or more brand meanings must share a contour, stroke, negative space, glyph skeleton, or shape system. Logo Semantic Fusion is an agent skill from ZSeven-W/craft-skills. Develop and evaluate logo concepts when the explicit design problem is semantic fusion: two or more brand meanings must share a contour, stroke, negative space, glyph skeleton, or shape system.

When should I use Logo Semantic Fusion?

Logo Semantic Fusion fits situations like: fusion-focused design; prompt-only work on a logo; generic logo creation; general identity systems.

How do I install Logo Semantic Fusion in Claude Code?

Run `npx skills add ZSeven-W/craft-skills --skill logo-semantic-fusion -a claude-code`. Or copy the skill folder (skills/logo-semantic-fusion in ZSeven-W/craft-skills) into .claude/skills/logo-semantic-fusion in your project. Claude Code loads it when a task matches its description.

How do I install Logo Semantic Fusion in Codex?

Run `npx skills add ZSeven-W/craft-skills --skill logo-semantic-fusion -a codex`. Or copy the skill folder (skills/logo-semantic-fusion in ZSeven-W/craft-skills) into .agents/skills/logo-semantic-fusion in your project. Codex loads it when a task matches its description.

Can I use Logo Semantic Fusion in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ZSeven-W/craft-skills --skill logo-semantic-fusion -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/logo-semantic-fusion, .gemini/skills/logo-semantic-fusion, .github/skills/logo-semantic-fusion and .opencode/skills/logo-semantic-fusion in your project.

What does Logo Semantic Fusion need to run?

SKILL.md names no scripts, command-line tools or credentials: Logo Semantic Fusion is instructions for the agent only.

Does Logo Semantic Fusion access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Logo Semantic Fusion safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Logo Semantic Fusion use?

Logo Semantic Fusion is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Logo Semantic Fusion use?

About 1.7k tokens (SKILL.md is roughly 6.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.1k tokens, read only when the agent opens those files.

What are the alternatives to Logo Semantic Fusion?

Skills that share tags, products or a category with Logo Semantic Fusion: Brand and Design Toolkit (nextlevelbuilder/ui-ux-pro-max-skill, 135k stars), Anthropic Brand Styling (anthropics/skills, 180k stars), Logo Design (kaankiziltug/logo-design-skill, 2.5k stars) and Logo Generator (op7418/logo-generator-skill, 2.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Logo Semantic Fusion?

ZSeven-W (a GitHub organization) maintains it in ZSeven-W/craft-skills, which has 225 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on September 22, 2026.

Source: ZSeven-W/craft-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.