brand-alignment

name	brand-alignment
description	Ensures every website element — layout, messaging, navigation, imagery, CTAs — reflects the client's brand identity and speaks clearly to their ideal customer. Use before and during page building to validate that the site feels intentional, cohesive, and trustworthy.

Brand Alignment

Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, [phone].

Use when

• The task matches this domain: Ensures every website element — layout, messaging, navigation, imagery, CTAs — reflects the client's brand identity and speaks clearly to their ideal customer. Use before and during page building to validate that the site feels intentional, cohesive, and trustworthy.
• The work needs a quality gate or standard applied across other outputs.

Do not use when

• The task is unrelated to this standard or quality lens.
• A more specific execution skill should own the work instead.

Required inputs

• The content, interface, or artifact being reviewed or improved.
• Any brand, audience, regional, or conversion context that affects the judgment.

Workflow

1. Read the artifact and the decision context before applying rules.
2. Use only the parts of the preserved guidance that matter to the current task.
3. Review or revise the work using this skill as a focused quality lens.
4. Return actionable changes or acceptance criteria instead of abstract theory.

Quality standards

• Recommendations must be concrete enough to apply immediately.
• Changes should improve consistency, usability, or credibility without flattening the brand.
• The standard should support downstream implementation rather than slow it down.

Anti-patterns

• Do not apply every rule mechanically when only a subset is relevant.
• Do not give generic critique with no change implications.
• Do not override project reality with taste-based preferences alone.

Outputs

• Revisions, review findings, acceptance criteria, or quality guidance tied to the artifact under review.

References

• Start with references/legacy-guidance.md when you need the preserved detailed instructions from the previous skill version.
• Use references/trust-architecture-checklist.md when validating proof, legitimacy, and credibility requirements across a site's strategy or pages.
• Read only the specific files under references/ that match the current task instead of loading the whole directory.
• This skill has no bundled scripts by default; keep execution focused on the documented workflow and any existing project files.

Notes

• Treat this SKILL.md as the portable execution layer for both Codex and Codex.
• Preserve existing project behavior unless the current task explicitly requires a change.