Apply Anthropic's official brand colors, typography, and visual identity to artifacts.
Automate repetitive workflows and reduce manual effort
Example: Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example: Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example: Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Time estimate: 15-45 minutes depending on use case complexity
Prerequisites
Submit your Claude Code skill and start earning
epx add composiohq/awesome-claude-skills --skill brand-guidelinesCompatible with
Supported agents
Includes six brand colors (dark, light, mid/light gray, orange, blue, green) with RGB values for precise matching across platforms
Automatically applies Poppins font to headings (24pt+) and Lora font to body text, with fallback to Arial and Georgia if custom fonts unavailable
Smart color selection adapts text and accent colors based on background for readability and visual hierarchy
Works with s
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionbrand-guidelinesExecute the skills CLI command in your project's root directory to begin installation:
epx add composiohq/awesome-claude-skills --skill brand-guidelinesFetches brand-guidelines from composiohq/awesome-claude-skills 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:
.cursor/skills/brand-guidelines
Restart Cursor to activate brand-guidelines. Access via /brand-guidelinesin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
karpathy-guidelines
forrestchang/andrej-karpathy-skills · Frontend · tag: guidelines
premium-frontend-ui
github/awesome-copilot · Frontend · same category
senior-frontend
alirezarezvani/claude-skills · Frontend · same category
aceternity-ui
secondsky/claude-skills · Frontend · same category
tailwind
pproenca/dot-skills · Frontend · same category
game-design-core
omer-metin/skills-for-antigravity · Frontend · same category
brand-guidelines has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in brand-guidelines — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
brand-guidelines fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for brand-guidelines matched our evaluation — installs cleanly and behaves as described in the markdown.
brand-guidelines reduced setup friction for our internal harness; good balance of opinion and flexibility.
We added brand-guidelines from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in brand-guidelines — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend brand-guidelines for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
brand-guidelines fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for brand-guidelines matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 25