Defines and applies visual brand — logo usage, palette, typography, imagery direction, and the guidelines that keep expression consistent across product and marketing surfaces. Use this to establish a brand from scratch, audit whether an existing brand is being applied consistently, build brand guidelines, or decide how a brand should express itself in an unfamiliar format.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Brand is the accumulated impression of every surface someone encounters. Consistency is most of it; the rest is having a point of view.
Before any visual decision, settle three things in writing:
Palette. One primary, one accent, a full neutral ramp, and semantic states. The neutral ramp does most of the visible work and gets the least attention — spend time on it. Every color needs a verified contrast ratio against the surfaces it will actually sit on, not against white.
Typography. One display family, one text family, and a rule for when each is used. Both must work at the smallest size they will appear at, on a real device, before selection.
Logo. Define clear space, minimum size, and permitted variants. Then define misuse explicitly: no stretching, no recoloring outside the permitted set, no effects, no re-typesetting the wordmark. Guidelines fail by omission — what is not forbidden gets done.
Imagery. A stated direction, with examples of both what fits and what does not. "Authentic photography" means nothing without a counter-example.
The test of a brand system is an unfamiliar format: an error email, a conference badge, a slide nobody planned for. If the system does not say what to do, it is a mood board, not a system.
Collect real surfaces — product, marketing site, email, social, sales collateral — side by side. Look for: palette drift, more type families than the system defines, logo variants nobody sanctioned, and tone that changes between surfaces. Report by severity, and separate what breaks the system from what merely was not specified.
references/sources.md in this skill lists the outside authorities that settle the questions
here — what each one is authoritative for, and what you may do with it. Check them before
answering on anything they cover, and cite what you used. Most are free to read and not free
to reproduce; the use note on each is binding.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process. Use this to design a permissions model, run an access review, reduce standing privilege, handle offboarding, set up SSO or MFA, manage service and machine credentials, or diagnose why permissions have sprawled.
The English summary is being prepared. Showing the original description.
Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group inside each, tiering effort against account value, coordinating so the account experiences one campaign rather than several, and measuring account progression instead of leads. Use this to decide whether to run an account-based program, build one, or work out why an existing one produces activity and no pipeline.
The English summary is being prepared. Showing the original description.
Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account. Use this to design or fix signup and onboarding, diagnose why signups do not convert to active use, reduce time-to-value, or decide what a new user must accomplish first.
The English summary is being prepared. Showing the original description.
Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a script that runs in CI. Use this whenever the user wants to set up, expand, audit, or fix a multi-agent or subagent structure for a codebase; asks how to divide work between agents; wants agent charters, roles, or a surface map written; or is hitting agents that collide on the same files, review their own work, or drift from their remit. Also use when sizing a roster or deciding whether a new agent is justified.
The English summary is being prepared. Showing the original description.
Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory exposure, or when deciding whether an AI system is fit for a consequential decision.
The English summary is being prepared. Showing the original description.
Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit. Use this to analyze a market or industry, map competitors, evaluate a market-entry or build-versus-buy decision, produce a research brief, or assemble evidence for a decision. Also use when comparing options that need a structured, evidence-based verdict rather than an opinion.
The English summary is being prepared. Showing the original description.