Brand Guidelines
Apply, document, and enforce brand guidelines for any product.
$skillfish add ~skills/brand-guidelines Real Conversations
See how the Brand Guidelines skill responds to actual requests. These are representative examples of what your AI agent will produce.
We're a 30-person B2B SaaS (Nucleus PM) and we've never written down our brand voice. Different team members write copy and it sounds inconsistent — some emails are super formal, some are casual. The product is for engineering managers. We want to feel like a smart peer, not a vendor. Can you help us define our voice?
Nucleus PM Brand Voice Guidelines
Voice in one sentence: We're the engineering manager who's been in the room — direct, specific, and without the enterprise sales speak.
Four voice dimensions:
1. Direct, not formal
- Write like you're talking to a smart peer, not presenting to a board
- Do: "Sprint planning shouldn't take all afternoon."
- Don't: "Nucleus PM facilitates efficient sprint planning processes."
2. Specific, not vague
- Numbers and examples beat adjectives every time
- Do: "Teams average 60% less time in planning meetings."
- Don't: "Significantly improves team productivity."
3. Honest, not salesy
- Acknowledge trade-offs; recommend competitors when they're genuinely the better fit
- Do: "Nucleus PM isn't for teams that need 3,000 integrations. We're for teams that need 10 great ones."
- Don't: "The #1 choice for engineering teams worldwide."
4. Human, not corporate
- Contractions are fine. Passive voice is not.
- Do: "We built this because sprint planning was broken."
- Don't: "This feature was developed in response to customer feedback indicating..."
Words we never use: leverage, synergy, streamline, comprehensive, cutting-edge, solution, empower
Tone by channel:
- Blog: 70% informational, 30% opinionated
- Email: Conversational, short paragraphs, one CTA
- Product UI: Ultra-concise, action-oriented
- Social: Direct takes, not promotional
Want this formatted as a shareable Notion doc with do/don't examples for each writer on your team?
Get Started
How to install and use this skill in your preferred environment.
Skills are designed for AI coding agents (Claude Code, Cursor, Windsurf) and IDE-based workflows where the agent can read files, run scripts, and act on your codebase. Web-based AI can use the knowledge and frameworks, but won't have tool access.
Models & Context
Which AI models and context windows work best with this skill.
Recommended Models
Larger models produce more detailed, production-ready outputs.
Context Window
This skill's SKILL.md is typically 3–10 KB — fits in any modern context window.
All current frontier models (Claude, GPT, Gemini) support 100K+ context. Use the full window for complex multi-service work.
Pro tips for best results
Be specific
Include numbers — users, budget, RPS — so the skill can size the architecture.
Share constraints
Compliance needs, team size, and existing stack all improve the output.
Iterate
Start with a high-level design, then ask follow-ups for IaC, cost analysis, or security review.
Combine skills
Pair with companion skills below for end-to-end coverage.
Ready to try Brand Guidelines?
Install the skill and start getting expert-level guidance in your workflow — any agent, any IDE.
$skillfish add ~skills/brand-guidelines