brand-book-concept-page
Use when a founder, product team, or agent needs multiple brand directions, a compact brand book, logo/tagline/palette/type/voice exploration, or a single interactive concept page for an app, product, venue, or campaign.
- License 许可
- MIT
- 最近更新
- 2026-11-10
- Stars
- ★ 13
- Forks
- 4
01 前言 Front Matter
- name
- brand-book-concept-page
- description
- Use when a founder, product team, or agent needs multiple brand directions, a compact brand book, logo/tagline/palette/type/voice exploration, or a single interactive concept page for an app, product, venue, or campaign.
02 资源文件 1
- 参考文档.hivemind-skill-source.json1.0 KB
03 SKILL.md 正文
Brand Book Concept Page
Generate a small set of distinct brand directions and package them into a usable concept artifact.
Contract
The output is exploratory brand work, not a trademark clearance, final legal identity, or guaranteed original mark. Use original language and generated or licensed assets. Do not imitate a living brand or copy protected logos.
Inputs
- Product or company name, audience, category, desired feeling, and dealbreakers.
- Existing logo, screenshots, product photos, or style references if any.
- Output target: written brand book, static HTML page, dashboard-ready artifact, slide, or asset prompts.
Workflow
- Clarify the brand job: who needs to believe what, and what should they do next.
- Create three meaningfully different directions. Each needs a positioning sentence, visual principle, palette, typography direction, voice rules, tagline options, and product/application examples.
- For each direction, generate or specify assets:
- logo concept and usage notes
- app/product screen treatment
- social or out-of-home application
- merch or physical touchpoint
- do/don't examples
- If building a page, make the experience functional first: switchable directions, responsive layout, accessible contrast, and no hidden text truncation.
- Verify that every direction uses different strategy, not just different colors.
Capability Map
- Visual generation: use a discovered image generator or local media capability. Verify generated assets are nonblank and legible.
- Frontend artifact: use existing HivemindOS frontend/design guidance and run a local visual check if code is created.
- Delivery: save artifacts locally or to the requested channel only after approval.
Safety
- Do not claim trademark availability.
- Do not use private product screenshots in external generators without approval.
- If the user wants a real launch identity, add a legal/trademark review note and source-file handoff checklist.
Provenance
This is a HivemindOS-authored clean-room skill prompted by a public skill catalog. No unlicensed upstream text, JSON, or scripts are copied.
04 同仓库更多 Skills
tailscale-generation-skill-authoring
This skill should be used when the user asks to "create a Tailscale generation skill", "add a local generation skill", "document a generation endpoint", "add an image generation provider", "add a TTS provider", "add video generation", "add 3D generation", or needs guidance on where HivemindOS Tailscale or local generation providers belong in the shared skills shelf.
localtts
This skill should be used when the user asks to "generate local TTS", "use local text to speech", "use remote TTS over Tailscale", "make speech audio", "add a TTS provider", "use Qwen3-TTS", or needs TTS endpoint setup through local or HivemindOS Tailscale routes.
karpathy-guidelines
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
comfyui-image-generation
This skill should be used when the user asks to "generate images", "generate images with ComfyUI", "use local ComfyUI", "use remote ComfyUI", "use Z-Image", "add an image generation provider", or needs image-generation endpoint setup through local or HivemindOS Tailscale routes.
wrangler
Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.
workers-best-practices
Reviews and authors Cloudflare Workers code against production best practices. Load when writing new Workers, reviewing Worker code, configuring wrangler.jsonc, or checking for common Workers anti-patterns (streaming, floating promises, global state, secrets, bindings, observability). Biases towards retrieval from Cloudflare docs over pre-trained knowledge.