Agent skill · design visual · jeremylongshore
form-style
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
Why this skill is useful
Adds a structured workflow for selecting UI styles based on product type and industry, which the AI wouldn't reliably generate on its own.
What it needs
Requires python3 installed locally. About 1k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
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 1. Identify product type from user request or project context 2. Search product reasoning: 3. Get recommended style details: 4. Cross-reference anti-patterns from the product search results — check the AntiPatterns field 5. Output the recommendation using the format below Output format 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.
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/form-style