- Home
- Skills
- Wesleysmits
- Agent Skills
- Brand Identity Template
brand-identity-template_skill
2
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill wesleysmits/agent-skills --skill brand-identity-template- SKILL.md2.0 KB
Overview
This skill provides a single source of truth for brand guidelines, design tokens, technology choices, and voice/tone. Use it as the canonical reference when generating UI components, styling applications, writing copy, or creating user-facing assets. It is a template you customize with your brand specifics to enforce consistency across teams and automation. Follow the included resource files instead of guessing brand details.
How this skill works
The skill bundles three resource files: design tokens for visual styling, a tech-stack document for implementation constraints, and a voice/tone guide for copy. When asked to produce UI, code, or content, the agent reads the relevant resource file and applies the specified values and rules. You must copy the template into your project and replace placeholders with your brand’s actual tokens and guidelines.
When to use it
- Generating UI components or design assets that must match brand visuals
- Writing user-facing copy, messages, or marketing content
- Choosing libraries, patterns, or build tools to align with approved tech choices
- Creating automated flows that output branded documents or emails
- Reviewing or auditing design and implementation for brand compliance
Best practices
- Always read the specific resource file for the task instead of guessing values
- Keep design tokens authoritative and update them centrally when brand changes
- Document any deviations and get approval before implementing exceptions
- Version the resources alongside your application to track changes
- Embed the skill in CI/linting checks to surface inconsistencies early
Example use cases
- Generate a React component styled with exact color, font, and spacing from design-tokens.json
- Produce marketing headings and microcopy that match the voice-tone.md guidelines
- Select frontend libraries and folder structure that adhere to tech-stack.md constraints
- Automate email templates using approved brand colors and tone for customer communications
- Audit a new feature’s UI and content against the brand resources and report mismatches
FAQ
Copy the template folder into your project, rename it, and update resources/design-tokens.json, resources/tech-stack.md, and resources/voice-tone.md with your brand specifics.
Which file do I consult for exact colors or spacing?
Consult resources/design-tokens.json for authoritative color values, fonts, spacing, and other tokens.
What if a requested design element isn’t covered in the files?
Treat missing items as out-of-scope: add the new token to design-tokens.json and version the change, or request approval before making assumptions.