This skill orchestrates autonomous discovery of brand materials across enterprise platforms (Notion, Confluence, Google Drive, Box, SharePoint, Figma, Gong, Granola, Slack). It should be used when the user asks to "discover brand materials", "find brand documents", "search for brand guidelines", "audit brand content", "what brand materials do we have", "find our style guide", "where are our brand docs", "do we have a style guide", "discover brand voice", "brand content audit", or "find brand assets".
Searches enterprise platforms to discover brand materials and generate structured reports.
/plugin marketplace add anthropics/knowledge-work-plugins/plugin install brand-voice@knowledge-work-pluginsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
references/search-strategies.mdreferences/source-ranking.mdOrchestrate autonomous discovery of brand materials across enterprise platforms. This skill coordinates the discover-brand agent to search connected platforms (Notion, Confluence, Google Drive, Box, Microsoft 365, Figma, Gong, Granola, Slack), triage sources, and produce a structured discovery report with open questions.
Before starting, briefly explain what's about to happen so the user knows what to expect:
"Here's how brand discovery works:
.claude/brand-voice-guidelines.md in your working folder once you approve them. Nothing is written until that step.The search usually takes a few minutes depending on how many platforms are connected. Ready to get started?"
Wait for the user to confirm before proceeding. If they have questions about the process, answer them first.
Read .claude/brand-voice.local.md if it exists. Extract:
If no settings file exists, proceed with all connected platforms and standard search depth.
Before confirming scope, check which platforms are actually connected and classify them:
Document platforms (where brand guidelines, style guides, templates, and decks live):
Supplementary platforms (valuable for patterns, but not where brand docs are stored):
Apply these rules:
If zero document platforms are connected: Stop. Tell the user: "You don't have any document storage platforms connected (Google Drive, SharePoint, Notion, Confluence, or Box). Brand guidelines and style guides almost always live on one of these. Please connect at least one before running discovery. Gong/Granola/Slack transcripts are valuable supplements but unlikely to contain formal brand documents."
If no Google Drive AND no Microsoft 365 AND no Box: Warn (but proceed): "None of your primary file storage platforms (Google Drive, SharePoint, Box) are connected. Brand documents frequently live on these platforms. Discovery will proceed with [connected platforms], but results may have significant gaps. Consider connecting Google Drive or SharePoint."
If only one platform total is connected: Warn (but proceed): "Only [platform] is connected. Discovery works best with 2+ platforms for cross-source validation. Results from a single platform will have lower confidence scores."
Before launching discovery, confirm:
Keep this brief — one question, not a questionnaire.
Launch the discover-brand agent via the Task tool. Provide:
The agent executes the 4-phase discovery algorithm autonomously:
When the agent returns, present the report to the user with a summary:
After presenting the report, offer:
/brand-voice:generate-guidelines using discovery report as inputOpen questions arise when the discovery agent encounters ambiguity it cannot resolve:
Every open question includes an agent recommendation. Present questions as "confirm or override" — not dead ends.
For detailed discovery patterns and algorithms, consult:
references/search-strategies.md — Platform-specific search queries, query patterns by platform, and tips for maximizing discovery coveragereferences/source-ranking.md — Source category definitions, ranking algorithm weights, and triage decision criteriaExpert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.