frontend-design-direction

Define an explicit design direction first: purpose, audience, tone, one memorable detail, and constraints. Then match typography, color, and layout to the product domain instead of defaulting to common generated patterns like purple gradients or oversized hero text.

A SaaS operations tool should usually be dense, quiet, and scannable, with stable grids, toolbars, and controls. Expressive editorial or maximal styles fit portfolios and launch pages, not repeated daily workflows.

No. ECC intentionally does not rebundle the canonical Anthropic frontend-design skill. This is an ECC-specific salvage of design-direction guidance, and the official skill can be installed separately from anthropics/skills.

Avoid purple gradients, decorative blobs, cards nested inside cards, vague hero copy, single-hue palettes, and hiding the actual product behind marketing sections. Also avoid adding dependencies for purely decorative flourishes.

Do not force landing-page composition onto tools used repeatedly every day. The first viewport should show the actual usable product or workflow, with visual hierarchy optimized for scanning rather than marketing impact.