mattamior Brand Design System
Create a brand identity that remains traceable and faithful from the initial evidence through the approved production assets. Treat source material and approved artwork—not verbal recollection—as the source of truth.
Invoke the skill
In Codex, invoke the skill from any repository by starting the request with $brand-design-system; a user-scoped installation does not need to be copied into each project. In ChatGPT desktop, select Brand Design System from the Skills picker. Both products may also select it automatically when the request matches the skill description.
$brand-design-system audit this project's existing logo, favicon, and PWA assets. Start read-only and report evidence, gaps, and required decisions.
Establish the assignment
Determine whether the request is exploration, refinement, historical reconstruction, production, integration, or review. Inspect existing assets, implementation, repository history, and prior records before asking questions they can answer.
Establish the brand or product name, audience, intended surfaces, required languages, visual constraints, target markets, available source material, and approval authority. Keep evidence, inference, and unknowns separate. Never invent missing design history.
Keep a durable process record
Read process record guidance for new identity work, historical reconstruction, or any task expected to produce a reusable handoff. Use the supplied process log and handoff templates when the project lacks an equivalent record; adapt an established project convention instead of creating a duplicate system.
Record materially distinct concept directions, the evidence behind them, selection and rejection reasons, approval checkpoints, and unresolved questions. A transient ideation request does not require a full dossier unless the user asks for one.
Explore and approve
For new identity exploration, create a small set of materially distinct, vector-friendly directions. Explain the visual idea, likely category associations, and important tradeoffs. Image generation is suitable for exploration, not as an automatic substitute for editable production artwork.
Do not treat aesthetic preference as approval. Once the user or named approver selects a direction, record that checkpoint before producing derivatives. Similarity review may flag visual or naming risk, but it is not legal or trademark clearance.
Lock the approved master
Record the master artwork location and visible invariants: geometry and proportions, palette, stroke behavior, typography and casing, backgrounds, negative space, and lockup relationships. Do not silently simplify, redraw, reinterpret, or substitute those decisions while producing derivatives.
Use editable SVG or another vector-native source for production logo work. Pathify final wordmarks when portability matters and licensing permits it. If only raster or incomplete evidence exists, report the fidelity limit before rebuilding anything.
Produce only what the delivery needs
Read production asset guidance when producing production assets, application icons, social images, or a web-ready pack. Generate the minimum useful asset set and keep concept previews separate from approved production files.
Website integration requires explicit authorization. When authorized, inspect the project and follow its existing asset conventions. Update only the approved branding surface and required metadata; do not change product behavior or information architecture.
Verify visible output
Read visual QA guidance whenever finalizing production assets or reviewing an implementation. Validate rendered output rather than SVG source alone, including transparency, color application, small-size readability, lockup proportions, and actual favicon or manifest delivery.
Finish by updating the process log and handoff with generated assets, integration changes, validation evidence, known limits, and unresolved work. Report evidence and inference separately.