Individual skill
logo-semantic-fusion
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.
skills/logo-semantic-fusion/SKILL.md
Source commit 01c8ffe0bc94cfe1dbfc7e1de537399253d04f39
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 241
- Repository last updated
- Sep 22, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
README.en.mddoc · 687 bytesREADME.mddoc · 854 bytesSKILL.mdcore · 6,723 bytesSKILL.mdcore · 6,723 bytesagents/openai.yamlasset · 289 bytesreferences/concept-methods.mddoc · 5,143 bytesreferences/review-checklist.mddoc · 5,924 bytesreferences/source-notes.mddoc · 1,364 bytes
Read excerpt
# 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
- Read [references/concept-methods.md](references/concept-methods.md) before designing or substantially redesigning a mark.
- Read [references/review-checklist.md](references/review-checklist.md) before scoring, comparing, or accepting a visual result.
- Read [references/source-notes.md](references/source-notes.md) only to explain provenance or resolve an ambiguous method.
## 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.