Arnie016 Brand Kit
Use this skill when a project needs a compact visual and messaging layer that makes it easier to publish and share.
Quick Start
- Read the project name, audience, and current visual tone before generating branding.
- Keep the identity system small: logo direction, colors, headline, and launch metadata.
- Make assets and copy consistent with the product instead of inventing a disconnected brand.
- Default to one strong direction, not a pile of weak options.
Workflow
Brand Direction
- Start from what the project does and who it is for.
- Prefer one strong direction over multiple weak options.
- Keep names, taglines, and color choices easy to reuse across README banners, social previews, and repo cards.
- Anchor the brand in a clear mood: technical, playful, premium, minimal, or utility-first.
Deliverables
- Favor practical outputs: icon concepts, logo prompts, banner text, meta description, and one-sentence positioning.
- If the user already has branding, extend it instead of replacing it.
- If visual assets are needed, keep the prompt or spec clear enough to hand to an image workflow.
- When useful, provide a mini brand system:
- color pair
- typography direction
- one-line positioning
- hero/banner text
- social preview text
Required Deliverables
- A one-sentence positioning line.
- A visual direction with 2 to 4 colors max.
- A logo or icon concept that can be rendered later.
- A repo or launch-page ready headline and description.
Editing Guidance
- Avoid generic “AI startup” branding language.
- Keep copy short enough to fit GitHub, app listings, and social previews.
- Make the result feel shareable, not corporate.
- Do not invent a luxury or futuristic voice unless the product truly supports it.
Resources
agents/openai.yaml: UI metadata and default invocation prompt.assets/: branded icons for repo listings and skill chips.references/brand-system.md: lightweight output format for brand direction, prompts, and launch metadata.