brand-context
Use before writing or updating the team's shared brand context document: what belongs in it, how it's structured, how to merge new information without losing what's there, and what to keep out.
- License 许可
- Apache-2.0
- 所属仓库
- vercel/eve
- 最近更新
- 2026-11-15
- Stars
- ★ 5.9k
- Forks
- 656
01 前言 Front Matter
- description
- Use before writing or updating the team's shared brand context document: what belongs in it, how it's structured, how to merge new information without losing what's there, and what to keep out.
02 资源文件 1
- 参考文档references/template.md3.7 KB
03 SKILL.md 正文
The brand context document
This is the document every specialist loads at the start of every task. That makes it the highest-leverage thing you write and the easiest to ruin, in two directions: too thin and everyone guesses, too long and everyone pays for it on every delegation.
Write it as a briefing for a competent colleague who has never seen the product. Not a manifesto, not an archive.
What goes in
Six sections, in this order, because that's roughly the order a reader needs them.
- What the product is. Two or three sentences, plain, no category jargon. What it does and what it replaces.
- Who it's for. The primary segment, specifically enough to predict a problem and a buyer. Secondary segments named as secondary.
- Positioning. The alternative you beat, the differentiators worth claiming, and the proof for each.
- Messaging. The core message and the three or four pillars, each with its proof and its grade.
- Voice. How the team writes, with two or three real examples, and the phrases that are off-limits.
- Open questions. What isn't settled, and what would settle it.
Section 6 is the one people delete and the one that earns its place. It's how a specialist knows to hedge a claim rather than assert it.
What stays out
- Campaign and task detail. A launch brief, this quarter's theme, a specific piece's angle. Those belong in the delegation that needs them. Everything in this document is read by every task, so anything task-specific is a cost paid many times for one use.
- Long-form source material. Interview transcripts, full competitor teardowns, the complete messaging framework. Store those as assets and reference them.
- Anything you can't support. An aspiration written as a fact will be published as a fact by someone downstream.
- Preferences about how a person likes to work. Those live in the per-user preferences document, not here. This document describes the product, not the reader.
Length
Keep it to a page or two. The size cap in the tool is a backstop, not a target.
The test: could a specialist read this and write a draft without asking a question, and is there anything here they wouldn't need? Cut against the second question every time you revise. A document that has only grown has stopped being maintained.
Merging rather than replacing
The write overwrites the whole document for the entire team, so a careless save destroys work that wasn't yours.
- Load the current document first, every time. Never write from memory or from the earlier part of this conversation.
- Merge into the existing structure. Fit new information into the section it belongs in rather than appending a new one.
- Preserve what you weren't asked to change, including wording you'd have written differently. Someone agreed to that sentence.
- When new information contradicts what's there, don't silently replace it. Say what changed, why, and what it was before, then let the user decide.
- Resolve an open question by moving it into the relevant section, not by deleting it.
Before saving
Show the user the full document in the conversation and get agreement. Nothing pauses to confirm the write and there is no previous version to recover, so this is the only review the document gets. Then say what changed in a line or two, so the change is legible without diffing.
references/template.md has the document skeleton and a worked example.
04 同仓库更多 Skills
writing-quality
The review rubric: writing-quality rules and reference lists for judging a content draft, covering AI-sounding phrasing, bloated wording, structure, and web-content specs. Load at the start of every review.
writing-quality
Writing-quality guardrails for any prose the agent drafts or edits: blog posts, page copy, Notion drafts, release notes, marketing text. Use this skill whenever writing or revising content meant for humans to read, to keep the prose natural, plain, and free of AI-sounding phrasing. Not needed for code, queries, or structural CMS work.
seo-aeo-best-practices
SEO and AEO best practices for metadata, Open Graph, sitemaps, robots.txt, hreflang, JSON-LD structured data, EEAT, and content optimized for search engines and AI answer surfaces. Use this skill when implementing page SEO, technical SEO, schema markup, international SEO, AI-overview readiness, or improving content for Google, ChatGPT, Perplexity, and similar assistants.
sanity-best-practices
Sanity development best practices for schema design, GROQ queries, TypeGen, Visual Editing, images, Portable Text, Studio structure, localization, migrations, Sanity Functions, Blueprints, and framework integrations such as Next.js, Nuxt, Astro, Remix, SvelteKit, Angular, Hydrogen, and the App SDK. Use this skill whenever working with Sanity schemas, defineType or defineField, GROQ or defineQuery, content modeling, Presentation or preview setups, Sanity-powered frontend integrations, Sanity Functions, documentEventHandler, defineDocumentFunction, defineMediaLibraryAssetFunction, @sanity/functions, @sanity/blueprints, sanity.blueprint.ts, event-driven content automation, or when reviewing and fixing a Sanity codebase.
portable-text-serialization
Render and serialize Portable Text to React, Svelte, Vue, Astro, HTML, Markdown, and plain text. Use when implementing Portable Text rendering in any frontend framework, building custom serializers for non-standard block types, converting Portable Text to HTML strings server-side, converting Portable Text to Markdown, extracting plain text from Portable Text, or troubleshooting rendering issues with marks, blocks, lists, or custom types.
portable-text-conversion
Convert HTML and Markdown content into Portable Text blocks for Sanity. Use when migrating content from legacy CMSs, importing HTML or Markdown into Sanity, building content pipelines that ingest external content, converting rich text between formats, or programmatically creating Portable Text documents. Covers @portabletext/markdown (markdownToPortableText), @portabletext/block-tools (htmlToBlocks), custom deserializers, and the Portable Text specification for manual block construction.