Brand Governance
Use when creating or maintaining docs/BRAND.md as the brand-facing source of truth for tone, identity, naming, copy, storytelling, and visual direction.
Install
$ agentstack add skill-yipxiyi-openarc-brand-governance ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-yipxiyi-openarc-brand-governance) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Brand Governance
Use this skill when a repository needs brand, voice, naming, or communication consistency.
Goal
Maintain docs/BRAND.md as the source of truth for product identity and communication.
Fixed Clarification Flow
If the user has not clearly specified brand direction, follow this flow before writing:
- Discover existing signals: README, landing copy, UI labels, docs, screenshots, logos, assets, package metadata, and specs.
- Extract confirmed identity, tone, naming, audience, contradictions, and risky assumptions.
- Ask focused questions for material gaps such as positioning, voice, naming, emotional tone, and logo usage.
- Draft brand rules with concrete examples.
- Cross-check with
docs/PRD.md,docs/DESIGN.md, anddocs/assets/brand/*. - Confirm unresolved brand decisions with the user.
- Create or patch
docs/BRAND.md.
BRAND.md Owns
- Tone
- Identity
- Naming
- Copywriting
- Storytelling
- Illustration direction
- Logo rules
- Communication style
Boundary
Do not merge docs/BRAND.md with docs/DESIGN.md.
BRAND.md explains what the product should feel and sound like.
DESIGN.md explains how the UI should be implemented.
Rules
- Preserve existing product language when it is coherent.
- Avoid generic startup copy.
- Keep brand rules usable by agents writing UI copy, docs, release notes, and landing pages.
- Reference
docs/assets/brand/when logo or identity assets exist. - Do not invent positioning when product intent is still unclear.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Yipxiyi
- Source: Yipxiyi/OpenArc
- License: MIT
- Homepage: https://github.com/Yipxiyi/OpenArc
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.