Agent-Skills/Dev-Skills/brand-identity/SKILL.md
Provides the single source of truth for brand guidelines, design tokens, technology choices, and voice/tone. Use this skill whenever generating UI components, styling applications, writing copy, or creating user-facing assets to ensure brand consistency.
npx skillsauth add MaVoid-Team/Capital-Consultancy-Final brand-identityInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Brand Name: [INSERT BRAND NAME HERE]
This skill defines the core constraints for visual design and technical implementation for the brand. You must adhere to these guidelines strictly to maintain consistency.
Depending on the task you are performing, consult the specific resource files below. Do not guess brand elements; always read the corresponding file.
If you need exact colors, fonts, border radii, or spacing values, read:
👉 resources/design-tokens.json
If you are generating code, choosing libraries, or structuring UI components, read the technical constraints here:
👉 resources/tech-stack.md
If you are writing marketing copy, error messages, documentation, or user-facing text, read the persona guidelines here:
👉 resources/voice-tone.md
development
Create product backlog items in Why-What-Acceptance format — independent, valuable, testable items with strategic context. Use when writing structured backlog items, breaking features into work items, or using the WWA format.
content-media
Create user stories following the 3 C's (Card, Conversation, Confirmation) and INVEST criteria with descriptions, design links, and acceptance criteria. Use when writing user stories, breaking down features into backlog items, or defining acceptance criteria.
testing
Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step actions, and expected outcomes. Use when writing QA test cases, creating test plans, defining acceptance tests, or preparing for feature validation.
testing
Summarize a meeting transcript into structured notes with date, participants, topic, key decisions, summary points, and action items. Use when processing meeting recordings, creating meeting notes, writing meeting minutes, or recapping discussions.