| name | form-style |
| description | Use when asked to select a UI style, choose a design direction, pick a visual
approach for a product, or match a style to an industry. Examples: "what style
fits a fintech app", "choose between neumorphism and glassmorphism", "design
direction for healthcare SaaS"
|
| allowed-tools | Read, Bash, Glob, Grep |
| version | 0.6.6 |
| author | tonone-ai <hello@tonone.ai> |
| license | MIT |
form-style ā UI Style Selection
Follow the output format defined in docs/output-kit.md ā 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
When to use
Product needs a visual direction. Industry or product type is known or discoverable from context.
Workflow
- Identify product type from user request or project context
- Search product reasoning:
python3 -m form_agent.uiux search --domain product --query "{product_type}" --limit 3
- Get recommended style details:
python3 -m form_agent.uiux search --domain style --query "{recommended_style}" --limit 3
- Cross-reference anti-patterns from the product search results ā check the Anti_Patterns field
- Output the recommendation using the format below
Output format
āā Style Recommendation āāāāāāāāāāāāāāāāāāāāāā
ā Product: {product_type} ā
ā Style: {primary_style} ā
ā Fallback: {secondary_style} ā
āā Effects āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā¤
ā {key_effects from style search} ā
āā Anti-patterns āāāāāāāāāāāāāāāāāāāāāāāāāāāāāā¤
ā ā {anti_pattern_1} ā
ā ā {anti_pattern_2} ā
āā Implementation Checklist āāāāāāāāāāāāāāāāāāā¤
ā ā” {checklist_item_1} ā
ā ā” {checklist_item_2} ā
āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā
Anti-patterns
- Never pick style based on aesthetics alone ā match to product type + audience
- Never ignore anti-pattern list from reasoning rules
- Never recommend more than 2 combined styles (primary + fallback)
- Never recommend a style marked as incompatible with the target framework
Delivery
If output exceeds the 40-line CLI budget, invoke /atlas-report with the full findings. The HTML report is the output. CLI is the receipt ā box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.