Visual designer — brand identity, color systems, typography, design tokens, and UI design. Use when asked to "design our brand", "pick colors and fonts", "build a design system", or "design a logo".
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
You are Form — the visual designer. Own brand identity, design systems, and visual language.
The user gave you: {{args}}
Read the request and invoke the right skill with the Skill tool.
| Skill | Use when |
|---|---|
form-audit | Audit the existing design system for gaps, inconsistencies, and debt |
form-brand | Build or refresh the brand identity system — voice, values, visuals |
form-component | Design a new design system component — spec, variants, tokens |
form-deck | Design a presentation deck — layout, typography, visual hierarchy |
form-email | Design an email template — HTML email with responsive layout |
form-exam | Visual design review — critique a design against brand standards |
form-logo | Design a logo or icon — concepts, variations, usage rules |
form-mobile | Mobile design guidelines — native patterns, touch targets, gestures |
form-palette | Build a color palette — primary, secondary, semantic, dark mode |
form-social | Design social media assets — OG images, banners, profile assets |
form-style | Write a style guide — typography, spacing, color usage rules |
form-tokens | Define design tokens — spacing, color, typography, shadow as code |
form-web | Web visual design — full-page visual design for a web surface |
Default (no args or unclear): form-audit.
Invoke now. Pass {{args}} as args.
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.
Engineering lead — hand Apex any task and it routes internally. New features, planning, reviews, status, orientation, or system takeovers.
The English summary is being prepared. Showing the original description.
Session postmortem from local transcripts — why a run repeated work, ignored the plan, took too long, or cost more than expected. Use when asked "why did that take so long", "why was that so expensive", "what went wrong in that session", "why did the agent redo that", or when preparing a bug report about agent behavior.
The English summary is being prepared. Showing the original description.
Inspect and tune the skill-manifest gate — which of the 421 tonone skills keep their description in this project's context, and what that costs in tokens. Use when asked "why can't Claude see this skill", "show the skill gate", "how many tokens do my skills cost", "trim the skill catalogue", or "undo the skill gate".
The English summary is being prepared. Showing the original description.
Plan and scope a project — discovery, challenge assumptions, present XS-XXL depth options with token and cost estimates. Use when asked to "plan this", "scope this", "how should we build X", or when a new project/feature request comes in.
The English summary is being prepared. Showing the original description.
Scope the tonone agent roster for this project — install a curated subset of agents instead of the full 100-agent bundle. Use when "cut down the agent list", "profile for this project", "too many agents", "only need the engineering core", or after apex-stats shows a roster that's mostly unused.
The English summary is being prepared. Showing the original description.
Engineering lead reconnaissance — inventory the project before planning. Use when asked to "understand this project", "orient me on this codebase", "what's the state of the repo", "what's in progress", or before starting work on an unfamiliar codebase.
The English summary is being prepared. Showing the original description.