Brand identity, voice, messaging, asset management, and consistency frameworks.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionckm:brandExecute the skills CLI command in your project's root directory to begin installation:
Fetches ckm:brand from nextlevelbuilder/ui-ux-pro-max-skill and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate ckm:brand. Access via /ckm:brand in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
1
total installs
1
this week
59.9K
GitHub stars
0
upvotes
Run in your terminal
1
installs
1
this week
59.9K
stars
Brand identity, voice, messaging, asset management, and consistency frameworks.
Inject brand context into prompts:
node scripts/inject-brand-context.cjs
node scripts/inject-brand-context.cjs --json
Validate an asset:
node scripts/validate-asset.cjs <asset-path>
Extract/compare colors:
node scripts/extract-colors.cjs --palette
node scripts/extract-colors.cjs <image-path>
# 1. Edit docs/brand-guidelines.md (or use /brand update)
# 2. Sync to design tokens
node scripts/sync-brand-to-tokens.cjs
# 3. Verify
node scripts/inject-brand-context.cjs --json | head -20
Files synced:
docs/brand-guidelines.md → Source of truthassets/design-tokens.json → Token definitionsassets/design-tokens.css → CSS variables| Subcommand | Description | Reference |
|---|---|---|
update |
Update brand identity and sync to all design systems | references/update.md |
| Topic | File |
|---|---|
| Voice Framework | references/voice-framework.md |
| Visual Identity | references/visual-identity.md |
| Messaging | references/messaging-framework.md |
| Consistency | references/consistency-checklist.md |
| Guidelines Template | references/brand-guideline-template.md |
| Asset Organization | references/asset-organization.md |
| Color Management | references/color-palette-management.md |
| Typography | references/typography-specifications.md |
| Logo Usage | references/logo-usage-rules.md |
| Approval Checklist | references/approval-checklist.md |
| Script | Purpose |
|---|---|
scripts/inject-brand-context.cjs |
Extract brand context for prompt injection |
scripts/sync-brand-to-tokens.cjs |
Sync brand-guidelines.md → design-tokens.json/css |
scripts/validate-asset.cjs |
Validate asset naming, size, format |
scripts/extract-colors.cjs |
Extract and compare colors against palette |
| Template | Purpose |
|---|---|
templates/brand-guidelines-starter.md |
Complete starter template for new brands |
$ARGUMENTS (first word)references/{subcommand}.mdMake data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
Useful defaults in ckm:brand — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Useful defaults in ckm:brand — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
We added ckm:brand from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
ckm:brand reduced setup friction for our internal harness; good balance of opinion and flexibility.
ckm:brand is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Registry listing for ckm:brand matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: ckm:brand is the kind of skill you can hand to a new teammate without a long onboarding doc.
ckm:brand has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in ckm:brand — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend ckm:brand for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 26