Brand Style Guidelines
Apply consistent brand standards across all aspects of the Angular project.
When to Use
Automatically invoke this skill when:
- Creating new Angular components, modules, or services
- Writing user-facing text (labels, errors, help text, notifications)
- Editing existing components for consistency
- Creating or updating documentation
- Writing TypeScript code (to follow naming and structure conventions)
- User explicitly requests brand compliance check
Instructions
Step 1: Identify Work Type
Determine what needs brand guidelines:
- UI/Visual: Angular components, templates, CSS/SCSS, styling
- Copywriting: Headings, body text, CTAs, messages
- Code: Components, services, modules, interfaces, file structure
- Documentation: README, API docs, guides, comments
Step 2: Load Relevant Guidelines
Read the appropriate reference files from reference/:
visual-ui.md - Colors, typography, spacing, components
writing-tone.md - Voice, terminology, messaging
code-conventions.md - Naming, structure, Angular patterns
documentation.md - Format, style, organization
Step 3: Apply Guidelines
For UI/Visual Work
- Use only approved brand colors from palette
- Apply correct typography hierarchy and font families
- Follow spacing system (8px grid)
- Use established component patterns
- Ensure WCAG AA accessibility compliance
For Copywriting
- Match brand tone of voice (professional yet approachable)
- Use approved terminology consistently
- Write clear, action-oriented copy
- Address users directly ("you")
- Keep language concise and specific
For Code
- Follow Angular style guide and naming conventions
- Use consistent file and folder structure
- Apply established architectural patterns (services, guards, interceptors)
- Write self-documenting code with clear intent
- Add JSDoc comments for public APIs
For Documentation
- Follow standard document structure
- Use consistent formatting and headers
- Include required sections (Purpose, Usage, Examples)
- Write for the intended audience
- Keep examples current and tested
Step 4: Use Templates
Start from templates when creating new artifacts:
templates/component-template.component.ts for Angular components
templates/service-template.service.ts for services
templates/documentation-template.md for docs
Step 5: Validate Compliance
Run through the checklist:
- ✓ Visual elements match brand system
- ✓ Copy matches tone and terminology
- ✓ Code follows Angular conventions
- ✓ Documentation is complete and formatted correctly
- ✓ Accessibility standards met
- ✓ Consistent with existing project patterns
Quick Reference Rules
Visual
- Colors: Use CSS custom properties (
var(--primary-color), not hex codes directly)
- Typography: Follow hierarchy (H1: 32px, H2: 24px, Body: 16px)
- Spacing: Multiples of 8px only
- Components: Reuse existing, don't recreate
Writing
- Voice: Clear, helpful, professional yet friendly
- Structure: Active voice, verb-first CTAs
- Terminology: Consistent (see writing-tone.md)
- Length: Concise and scannable
Code
- Naming:
- Components: PascalCase with suffix (e.g.,
UserProfileComponent)
- Services: PascalCase with suffix (e.g.,
AuthService)
- Files: kebab-case (e.g.,
user-profile.component.ts)
- Organization: Feature-based module structure
- Comments: JSDoc for public APIs, explain "why" not "what"
- Patterns: Follow Angular best practices
Documentation
- Structure: Purpose → Usage → Examples → API
- Code blocks: Syntax-highlighted with language tags
- Links: Relative paths for internal docs
- Updates: Keep in sync with code changes
Examples
See examples/before-after.md for concrete transformations across all guideline types.
Troubleshooting
Issue: Existing code doesn't match guidelines
- Solution: Refactor incrementally, prioritize user-facing areas
Issue: Guidelines conflict with technical requirements
- Solution: Document exceptions with reasoning
Issue: Unclear which guideline applies
- Solution: Check reference files or ask for clarification
Validation Checklist
Before completing any work:
1---2name: brand-guidelines3description: Apply comprehensive brand style guidelines to all project work including UI components, code, documentation, and user-facing content. Use when creating or editing Angular components, HTML/CSS, TypeScript code, writing copy, documenting features, or any customer-facing materials to ensure brand consistency.4allowed-tools: Read, Edit, Write, Grep, Glob5metadata:6 source: https://skillmd.com/skills/diegosouzapw/brand-guidelines7---89# Brand Style Guidelines1011Apply consistent brand standards across all aspects of the Angular project.1213## When to Use1415Automatically invoke this skill when:16- Creating new Angular components, modules, or services17- Writing user-facing text (labels, errors, help text, notifications)18- Editing existing components for consistency19- Creating or updating documentation20- Writing TypeScript code (to follow naming and structure conventions)21- User explicitly requests brand compliance check2223## Instructions2425### Step 1: Identify Work Type2627Determine what needs brand guidelines:28- **UI/Visual**: Angular components, templates, CSS/SCSS, styling29- **Copywriting**: Headings, body text, CTAs, messages30- **Code**: Components, services, modules, interfaces, file structure31- **Documentation**: README, API docs, guides, comments3233### Step 2: Load Relevant Guidelines3435Read the appropriate reference files from `reference/`:36- `visual-ui.md` - Colors, typography, spacing, components37- `writing-tone.md` - Voice, terminology, messaging38- `code-conventions.md` - Naming, structure, Angular patterns39- `documentation.md` - Format, style, organization4041### Step 3: Apply Guidelines4243#### For UI/Visual Work44- Use only approved brand colors from palette45- Apply correct typography hierarchy and font families46- Follow spacing system (8px grid)47- Use established component patterns48- Ensure WCAG AA accessibility compliance4950#### For Copywriting51- Match brand tone of voice (professional yet approachable)52- Use approved terminology consistently53- Write clear, action-oriented copy54- Address users directly ("you")55- Keep language concise and specific5657#### For Code58- Follow Angular style guide and naming conventions59- Use consistent file and folder structure60- Apply established architectural patterns (services, guards, interceptors)61- Write self-documenting code with clear intent62- Add JSDoc comments for public APIs6364#### For Documentation65- Follow standard document structure66- Use consistent formatting and headers67- Include required sections (Purpose, Usage, Examples)68- Write for the intended audience69- Keep examples current and tested7071### Step 4: Use Templates7273Start from templates when creating new artifacts:74- `templates/component-template.component.ts` for Angular components75- `templates/service-template.service.ts` for services76- `templates/documentation-template.md` for docs7778### Step 5: Validate Compliance7980Run through the checklist:81- ✓ Visual elements match brand system82- ✓ Copy matches tone and terminology83- ✓ Code follows Angular conventions84- ✓ Documentation is complete and formatted correctly85- ✓ Accessibility standards met86- ✓ Consistent with existing project patterns8788## Quick Reference Rules8990### Visual91- **Colors**: Use CSS custom properties (`var(--primary-color)`, not hex codes directly)92- **Typography**: Follow hierarchy (H1: 32px, H2: 24px, Body: 16px)93- **Spacing**: Multiples of 8px only94- **Components**: Reuse existing, don't recreate9596### Writing97- **Voice**: Clear, helpful, professional yet friendly98- **Structure**: Active voice, verb-first CTAs99- **Terminology**: Consistent (see writing-tone.md)100- **Length**: Concise and scannable101102### Code103- **Naming**:104 - Components: PascalCase with suffix (e.g., `UserProfileComponent`)105 - Services: PascalCase with suffix (e.g., `AuthService`)106 - Files: kebab-case (e.g., `user-profile.component.ts`)107- **Organization**: Feature-based module structure108- **Comments**: JSDoc for public APIs, explain "why" not "what"109- **Patterns**: Follow Angular best practices110111### Documentation112- **Structure**: Purpose → Usage → Examples → API113- **Code blocks**: Syntax-highlighted with language tags114- **Links**: Relative paths for internal docs115- **Updates**: Keep in sync with code changes116117## Examples118119See `examples/before-after.md` for concrete transformations across all guideline types.120121## Troubleshooting122123**Issue**: Existing code doesn't match guidelines124- **Solution**: Refactor incrementally, prioritize user-facing areas125126**Issue**: Guidelines conflict with technical requirements127- **Solution**: Document exceptions with reasoning128129**Issue**: Unclear which guideline applies130- **Solution**: Check reference files or ask for clarification131132## Validation Checklist133134Before completing any work:135- [ ] Follows visual/UI guidelines136- [ ] Copy matches brand voice137- [ ] Code adheres to Angular conventions138- [ ] Documentation is complete139- [ ] Consistent with existing patterns140- [ ] No accessibility issues141- [ ] User-facing content reviewed