mikedev115/aetox-harness/aetox-brand

Brand

Brand identity, voice, messaging, asset management, and consistency frameworks.

When to Use

• Brand voice definition and content tone guidance
• Visual identity standards and style guide development
• Messaging framework creation
• Brand consistency review and audit
• Asset organization, naming, and approval
• Color palette management and typography specs

Quick Start

There is nothing to run. The brand lives in one file in the user's project usually docs/brand-guidelines.md, and the work is reading it before writing anything in the brand's name, and editing it when the brand changes.

Before writing anything branded: read the guidelines file whole. Voice is not a rule you can apply from a summary of itself.

Checking a piece of work: references/consistency-checklist.md and references/approval-checklist.md are the two passes, done by reading. A file name or an image size is glob and a look; a tone is a judgement, and the checklist is what keeps it from being only taste.

Colours: the palette is whatever the guidelines file says it is. Reading a colour out of an image is not something this app can do, say so rather than guessing at a hex from a description of a picture.

Brand Sync Workflow

The guidelines file is the source of truth and the tokens follow it, by hand and in that order:

1. Edit the guidelines file, the brand changed there first.
2. Carry the change into the project's design tokens. aetox-design-system is

the skill that says how the three token layers fit together.

1. Read back what you wrote. A token file that disagrees with the guidelines is

the failure this order exists to prevent, and it is silent.

When the brand changes

references/update.md is the procedure: gather the theme, colours and type in chat, then write the guidelines file and the two token files in the order above. There is no command to run; it is a checklist you follow.

The bar for anything written in the brand's name

• Read the guidelines whole first. Every sentence of voice traces to a line

in it, and a piece that cannot name its line is off-brand however good it reads.

• The two checklists in references/ are run, not remembered, and the

report says which items were checked and which could not be (a colour read from an image, a tone the guidelines do not cover).

• Logo use follows references/logo-usage-rules.md to the pixel: clear

space, minimum size, the approved colourways and nothing else.

• Same bar whichever model writes: a brand with one voice is the whole

point, and the voice does not get to vary with the model on duty.

References

Templates