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.
npx skills add https://github.com/ZSeven-W/craft-skills --skill 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.
reject all; do not invent a new candidate unless asked.Proceed with fusion concepting only when all are true:
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.
Extract or reasonably infer:
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.
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.
Create at least six thumbnails across at least three families and three fusion methods. Make every family change both:
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.
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.
Use image generation for isolated flat concept sheets, not precision masters. Rebuild selected geometry as clean vector paths when production precision matters.
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.
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.
pass, revise, or reject, and minimal revisions.reject all.Always distinguish design-direction similarity screening from jurisdiction- and class-specific trademark clearance.
Take zseven-w/logo-semantic-fusion from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.