Brand Guidelines
Encodes palette, logo rules, voice/tone, and typography so slides, docs, and web artifacts stay on-brand without manual last-mile polishing.
Overview
Brand Guidelines is a Claude skill catalogued in LimeDock Directories for teams working across design, marketing, operations. It is tagged for saas, agency, other contexts. Encodes palette, logo rules, voice/tone, and typography so slides, docs, and web artifacts stay on-brand without manual last-mile polishing. Use this page as the operational brief: install path, how to invoke it, copy-paste prompts, prerequisites, and concrete use cases so your team can adopt it without re-reading every roundup article.
Work with LimeDock
Using this skill? LimeDock can wire it into a durable automation you own.
Skills show what's possible. LimeDock builds and runs the owned marketing, sales, and ops automations around them.
We sell owned automations for SaaS teams — live workflows that plug into Slack, CRM, and your internal platform — not just a skill list.
Link
Installation guide
Enable in Claude.ai Skills (Anthropic example) or install from anthropics/skills; customize with your brand tokens.
Generic install paths
CLI
npx skills add https://github.com/anthropics/skills/tree/main/skills/brand-guidelines**Claude Code plugins** (when published as a marketplace skill)
/plugin marketplace add <org/repo>
/plugin install <skill>@<marketplace>**Manual** — copy the skill folder into `~/.claude/skills/brand-guidelines/` or your project `.claude/skills/`.
Always review `SKILL.md` and bundled scripts before enabling.
How to use it
Toggle on and prompt normally (âcreate a presentationâ¦â) or pair with pptx/docx/frontend-design; Claude applies brand rules automatically.
**Suggested workflow** 1. Install and enable the skill. 2. Open the target project (or Claude.ai chat) with enough product context. 3. Invoke with a clear goal, constraints, and success criteria. 4. Review the first output against your standards; refine with follow-ups. 5. Save winning prompts / outputs into your team playbook.
If Claude does not auto-select it, mention the skill by name: “Use the Brand Guidelines skill…”
Example prompts
- “Use the Brand Guidelines skill for this task: Anthropic-branded demo deck”
- “Walk me through how Brand Guidelines would approach this step by step, then execute.”
- “Review my current draft/plan and improve it using Brand Guidelines. Call out assumptions.”
- “Produce a checklist I can reuse whenever we run Brand Guidelines on similar work.”
Use cases and examples
- Anthropic-branded demo deck
- On-brand marketing one-pager
- Consistent colors/fonts across team artifacts
- Enterprise brand compliance for AI outputs
- First-week trial of Brand Guidelines on a real design workflow
- Document a reusable prompt template for Brand Guidelines for your team
Prerequisites
- Claude Code, Claude.ai (Skills enabled), or an Agent Skills–compatible host
- Network access if the skill fetches guidelines or calls external tools
- Project or brand context (CLAUDE.md / product notes) for better outputs
- Permission to install third-party skills — audit SKILL.md and scripts first
Tips
- Keep descriptions/triggers tight so Brand Guidelines fires only when relevant (avoids context tax).
- Prefer one sharp job over a mega-skill that tries to do everything.
- Pair with verification (tests, review, screenshots) before shipping outputs.
- Re-audit installed skills monthly — unused skills still cost context every turn.