brand-guidelines

Defines brand voice, copywriting standards, and visual identity rules for mobile applications.

1|Updated Aug 7, 2025
One-click install
npx skills add https://github.com/zzafergok/arktos --skill brand-guidelines-zzafergok
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: brand-guidelines
Source: https://github.com/zzafergok/arktos/tree/main/.agent/skills/brand-guidelines
Command: npx skills add https://github.com/zzafergok/arktos --skill brand-guidelines-zzafergok

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Mobile app teams often produce inconsistent copy, colors, and visuals across screens, notifications, and App Store listings, which weakens user trust and brand recognition. This Skill provides a single reference for voice, tone, writing, and visual standards so every contributor produces aligned output. ## Core Features & Use Cases - Brand Voice and Tone Framework: Define voice adjectives with concrete examples and adjust tone for success messages, errors, onboarding, empty states, and push notifications. - Writing Standards: Apply frameworks for App Store descriptions, onboarding text, and error messages using the formula of what failed, why, and what the user can do next. - Visual Identity Rules: Standardize color tokens, WCAG AA contrast ratios, typography roles, icon style, animation personality, and App Store assets like icons, screenshots, and preview videos. - Use Case: When writing a new App Store description or reviewing a new screen, check the consistency checklist to verify voice alignment, color token usage, and a clear single call to action. ## Quick Start Review the attached onboarding screen copy and error messages against the brand voice, tone, and error message frameworks.

Frequently Asked Questions about brand-guidelines

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a good App Store description for a mobile app?▼

Start the first sentence with the app category and primary benefit, then list outcomes rather than features. Embed keywords organically throughout the text, since keyword stuffing is penalised by the App Store algorithm.

How to write error messages for mobile apps?▼

A well-formed error message answers three questions: what did not happen, the likely reason, and what the user can do next. Use non-blaming, solution-oriented, concise language such as "Payment failed. Check your card details and try again."

What contrast ratio is required for app text and brand colors?▼

Text and background combinations must meet the WCAG AA standard with a minimum contrast ratio of 4.5:1. When a brand color is used as a background, verify the ratio and adjust the shade if the requirement is not met.

Should I use custom fonts or system fonts on iOS?▼

Deviating from the iOS system font SF Pro can weaken the user experience for body text. Reserve a display font for large headings and marketing materials, and use a mono font for numerical content like prices and data tables.

What makes an effective App Store preview video?▼

The first three seconds determine whether the video is watched, so place the strongest feature at the very beginning. The video must be comprehensible without sound because the App Store defaults to muted playback.