discover-brand — Claude Code command: features and setup
The discover-brand Claude Code command searches connected platforms for brand materials and creates a discovery report. Searches can target a company or selected platforms.
MIT ★ 36,654 updated 2026-10-24
/plugin marketplace add anthropics/knowledge-work-plugins
/plugin install brand-voice@knowledge-work-pluginsWhat discover-brand does
The command looks for brand guidelines, style guides, messaging frameworks, templates, and conversation transcripts across connected services. Supported sources include Notion, Confluence, Google Drive, Box, SharePoint, Figma, Gong, Granola, and Slack. A company name narrows the search; platform names restrict it to those sources.
It reads settings from .claude/brand-voice.local.md, checks platform coverage, and confirms the search scope. A subagent runs a four-phase search, then the command presents sources, brand elements, conflicts, and open questions. Nothing is saved until approval. After reviewing the report, the user can request guidelines and save them to .claude/brand-voice-guidelines.md.
At least one document platform is required: Notion, Confluence, Google Drive, Box, or Microsoft 365. The search stops if only Slack, Gong, Granola, or Figma is connected. Without Google Drive, Microsoft 365, or Box, it warns that results may have gaps.
What it helps with
- locate brand guidelines across connected document stores
- compare brand materials found on different platforms
- surface conflicting brand details and unresolved questions
- compile a sourced report on brand elements
Example prompts for the agent
- Run
/brand-voice:discover-brandto find Acme’s brand materials. - Search Notion and Google Drive only with
/brand-voice:discover-brand. - Use
/brand-voice:discover-brandto gather brand messaging and style references.
How to install discover-brand
1Plugin marketplace
/plugin marketplace add anthropics/knowledge-work-plugins/plugin install brand-voice@knowledge-work-plugins2Manually: put the files in place
.claude/commands/discover-brand.mdCall it with /discover-brand. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/discover-brand.mdCall it with /prompts:discover-brand. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/discover-brand.prompt.mdManually: put the files in place
.gemini/commands/discover-brand.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about discover-brand
How do I install discover-brand in Claude Code?
Run /plugin marketplace add anthropics/knowledge-work-plugins, then /plugin install brand-voice@knowledge-work-plugins. The command file is .claude/commands/discover-brand.md.
What does discover-brand do?
It searches connected platforms for brand materials and produces a report covering sources, brand elements, conflicts, and open questions. With explicit approval, it can generate guidelines and save them to .claude/brand-voice-guidelines.md.
What does discover-brand need to run?
At least one document platform must be connected: Notion, Confluence, Google Drive, Box, or Microsoft 365. Figma, Gong, Granola, and Slack are also supported; Google Drive and Slack are available as native Claude integrations.
Source text
discover-brand.md · MIT
--- description: Search connected platforms for brand materials and produce a discovery report argument-hint: "[company name or platforms to search]" --- Discover brand materials across the user's connected enterprise platforms. Search Notion, Confluence, Google Drive, Box, SharePoint, Figma, Gong, Granola, and Slack for brand guidelines, style guides, messaging frameworks, templates, and conversation transcripts. If $ARGUMENTS includes a company name, use it for targeted searches. If platforms are specified, limit search to those platforms. Before doing anything else, briefly orient the user on what's about to happen: the process will search their connected platforms, produce a discovery report, and then (optionally) generate and save brand guidelines to `.claude/brand-voice-guidelines.md` in the working folder. Nothing is saved until they explicitly approve. Keep the orientation to 2-3 sentences — don't recite the full workflow. Follow the discover-brand skill instructions to: 1. Check `.claude/brand-voice.local.md` for settings (company name, enabled platforms, search depth) 2. Validate platform coverage (stop if no document platforms, warn if gaps) 3. Briefly confirm scope with the user (which platforms, include transcripts?) 4. Delegate to the discover-brand agent for autonomous 4-phase search 5. Present the structured discovery report with sources, brand elements, conflicts, and open questions 6. Offer next steps: generate guidelines, resolve open questions, save report, or expand search **Platform validation:** - If **no platforms** are connected, inform the user which MCP servers the plugin supports (Notion, Atlassian Confluence, Box, Figma, Gong, Granola, Microsoft 365) and that Google Drive and Slack are available as native Claude integrations. - If **no document platforms** (Notion, Confluence, Google Drive, Box, Microsoft 365) are connected — only supplementary platforms like Slack, Gong, Granola, or Figma — stop and tell the user: "You don't have any document storage platforms connected. Brand guidelines and style guides almost always live on Google Drive, SharePoint, Notion, Confluence, or Box. Please connect at least one before running discovery." - If **no primary file storage** (Google Drive, Microsoft 365, Box) is connected, warn: "None of your primary file storage platforms are connected. Brand documents frequently live on these. Discovery will proceed but results may have significant gaps." - If **only one platform** is connected, warn: "Discovery works best with 2+ platforms for cross-source validation. Results from a single platform will have lower confidence scores."
© Tribe AI · MIT · anthropics/knowledge-work-plugins