Turn approved identity assets into exact brand rules, accessibility decisions, file manifests, and a release-ready handoff without inventing missing specifications.
A polished brand board can still leave everyone guessing. Which logo file is the master? Is the web font licensed for self-hosting? Which blue is approved? Can the gray be used for body text? What does the printer need, and who has authority to release it?
Brand Guidelines Builder turns supplied identity material into controlled production rules. It inventories logo masters, colors, typography, imagery, icons, templates, and channel exports. Every material rule stays tied to an observed, reported, derived, proposed, approved, or unknown source state. Conflicting files and missing authority remain visible instead of being smoothed into a plausible-looking guide.
The workflow covers logo use, color spaces, contrast checks, font rights and fallbacks, digital and print applications, editable masters, exports, change control, release gates, and acceptance evidence. It returns the guideline structure, asset and export manifests, conflicts, owners, limitations, next actions, and the narrowest supported verdict. A bundled checker validates the canonical JSON handoff and prevents a record from claiming release when approval, hashes, conflicts, or deliverables do not support it.
This package does not generate a new identity, replace a designer or legal reviewer, clear trademarks, grant font rights, inspect files the agent cannot access, or certify accessibility from one color pair. It is built for teams that already have identity material and need rules other people can apply without guessing.
Version 1.0.0 was reviewed on 2026-07-22 and evaluated through Codex CLI with gpt-5.6-sol in 12 fresh read-only contexts. The candidate scored 100 across three cases, compared with 78.33 for the same agent without the skill and 81.67 for the exact free upstream. It led the upstream by 5 points on an incomplete identity release, 18.75 points on a cross-channel accessibility and production revision, and 31.25 points on the strict JSON handoff. All three cases passed. The evaluation covers those supplied cases; it does not prove a real brand asset, license, approval, accessibility state, print package, trademark position, or production release.
The reviewed package SHA-256 is 00f2597ca3511402965b8ea090c923d0400d7c133fb82b51e365a6f9dd82523e. Maintenance and install support are handled by the platform-operated publisher for this listing.
Input
We have a raster logo, two different blues, an older brochure lockup, and font files with no license record. Web, social, and print work starts next week. Produce the safest useful handoff without inventing rules.
Output
A controlled asset register, source and authority ledger, unresolved logo and color conflicts, provisional guideline structure, channel requirements, release blockers, owners, and a bounded request for the missing masters and rights.
Input
The current Figma library conflicts with the old PDF. Body gray may fail at 16 px, our font license may not allow web hosting, and the printer supplied an unapproved CMYK conversion.
Provide the current logo and identity assets, existing guides, design-source links or exports, colors, fonts and license evidence, target channels, production requirements, owners, and approval boundaries. Ask to assess, build, revise, release, or return the canonical JSON handoff. The skill keeps unsupported specifications and approvals visibly unresolved.
Current logo files, color and type sources, existing guidelines, design-system files, templates, examples, or an explicit note that an item is missing.
The web, product, social, email, presentation, print, packaging, signage, or partner uses that the package must support, plus required file formats.
Owners, approvers, evidence dates, licensing records, trademark or legal boundaries, accessibility requirements, printer specifications, and release constraints.
SKILL.md; controlled brand-guidelines workflow; production framework for assets, logos, colors, typography, channels, conflicts, and release gates; canonical JSON handoff contract; read-only record checker
No reviews yet.
Output
A precedence-based change plan with exact conflicting values, scoped contrast checks, font-rights gate, channel impact matrix, print acceptance evidence, owners, and a blocked or conditional verdict.
Input
Return strict JSON for release 1.0.0. The vector logo is observed, the web-font license is unknown, two primary colors conflict, no approver is assigned, and no deliverable files exist.
Output
A contract-valid blocked record with exact sources, asset states, conflicts, open decisions, limitations, empty deliverables, authority status, and one evidence-producing next action.
Creator
Uulvane1
