frontend-skill

Generates art-directed landing pages and app interfaces with restrained composition and motion.

111|73|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/autopus-ai/autopus-adk --skill frontend-skill-autopus-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: frontend-skill
Source: https://github.com/autopus-ai/autopus-adk/tree/main/.omp/skills/frontend-skill
Command: npx skills add https://github.com/autopus-ai/autopus-adk --skill frontend-skill-autopus-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Building visually strong web interfaces often results in generic card grids, weak branding, cluttered heroes, and inconsistent design decisions. This Skill guides the AI to produce deliberate, premium-feeling landing pages, apps, dashboards, and game UIs by enforcing composition-first thinking, image-led hierarchy, and tasteful motion. ## Core Features & Use Cases - Design Discovery Matrix: Synthesizes surface type, product category, density, trust level, and platform into a working design system before any code is written. - Design System Preflight: Inspects project-local design docs via auto design docs and Astryx component/template queries so generated UI matches existing tokens and component APIs instead of inventing props or colors. - Composition and Motion Rules: Enforces full-bleed heroes, cardless layouts, one accent color, two typefaces max, and 2-3 intentional motions with reduced-motion fallbacks. - Use Case: Ask the agent to build a landing page for a new SaaS product; it will produce a full-bleed hero with strong brand presence, sparse copy, scroll-linked motion, and a pre-delivery accessibility checklist covering contrast, touch targets, and responsive widths. ## Quick Start Use the frontend skill to design and build a landing page for my product with a full-bleed hero and restrained motion.

Frequently Asked Questions about frontend-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a landing page that doesn't look like a generic SaaS template?▼

Start with composition instead of components: use a full-bleed hero with one dominant visual, make the brand the loudest text, keep copy scannable, and avoid card grids, stat strips, and logo clouds. Limit the system to two typefaces and one accent color.

How to choose colors, typography, and components for a new web UI?▼

Run a design discovery pass first: define surface type, product category, density, and trust level, then synthesize palette roles, type scale, and required components. If the project has a DESIGN.md or token file, treat it as the source of truth.

Does this work with shadcn, Tailwind, or Astryx component libraries?▼

Yes. The preflight step runs auto design docs to detect Astryx, shadcn/Radix/Tailwind, or local design sources, then reads component docs and skeletons before coding. It never invents props, import paths, or raw color values when a doc source exists.

What accessibility checks should a landing page pass before delivery?▼

Verify visible hover/focus/disabled states, 44px touch targets, WCAG AA text contrast, layout at 375/768/1024/1440px widths, prefers-reduced-motion support, and stable image dimensions. Icons should come from the project icon library, not emoji.

When should I avoid using cards in app UI design?▼

Avoid cards by default in app interfaces; use sections, columns, dividers, and lists instead. Cards are only appropriate when the card itself is the interaction. If a panel works as plain layout without losing meaning, remove the card treatment.