Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →zzafergok/brand-guidelines
Mobile application brand identity creation and application guide. Brand voice and tone, colour palette standards, typography system, icon and visual language, App Store assets, and consistency across all touchpoints.
Passed 20 of 22 test cases with the skill, and 18 of 22 without it.
and 1 more in the full report
2 fixed18 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
Our design team is assembling an icon set for our mobile app navigation bar. Is it acceptable to combine outlined icons for inactive tabs with filled icons for primary actions?
| Checked | Without skill | With skill |
|---|---|---|
| Requires adhering to a single icon style throughout, using either outline or filled icons consistently. | Missed | Passed |
The instructions your model reads when the skill loads.
A consistent brand experience builds user trust and recognition. This guide ensures that everyone — from developers to content writers — produces the same voice and visual presentation.
Voice is fixed and reflects the same personality across all platforms and content types. Tone adjusts based on context.
A brand's voice is defined by three to five adjectives. For each adjective, "what it means" and "what it does not mean" are established with concrete examples.
Example: Productivity application
Trustworthy — but not arrogant. A trustworthy statement reads "Your data is encrypted and stored on your device." An arrogant one reads "We are the most secure app on the market."
Clear — but not dry. A clear statement reads "Get started in three steps." A dry one reads "The onboarding process offers an optimised experience."
Human — but not informal. A human statement reads "Great — you've completed the first item on your list." An informal one reads "Yo! First task done 🔥🔥"
While voice remains constant, tone is flexible. Five distinct situations call for different tone adjustments.
For success messages, use short, measured energy. Avoid over-celebration. "Done." or "Saved — you're ready." are appropriate.
For error messages, use non-blaming, solution-oriented, concise language. "Connection lost. Try again." is preferable to "An error has occurred."
For onboarding, use a welcoming and guiding tone, presenting steps one at a time. Avoid overwhelming the user with choices.
For empty states, use hopeful and action-oriented language. "No tasks yet. Add your first one to get started."
For push notifications, lead with value. Do not manufacture urgency unless a genuine deadline exists. "Your weekly report is ready."
test cases passed, vs 18 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.