design-webapp

Generates HTML/CSS for authenticated app surfaces like dashboards, settings, and data tables.

1|Updated Jul 29, 2026
One-click install
npx skills add https://github.com/fusengine/kimi-code --skill design-webapp-fusengine
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-webapp
Source: https://github.com/fusengine/kimi-code/tree/main/plugins/design-expert/skills/design-webapp
Command: npx skills add https://github.com/fusengine/kimi-code --skill design-webapp-fusengine

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Designing logged-in product interfaces (dashboards, auth flows, settings, data tables) often produces generic, marketing-flavored screens with silent blank states and undifferentiated layouts. This Skill builds dense, glanceable app surfaces in the product register with every interaction state explicitly covered. ## Core Features & Use Cases - Page and pattern libraries: Provides starting structures for dashboards, login/register, onboarding, profile, settings, and error pages, plus patterns for data tables, command palettes, modals, toasts, and empty states. - Hard rules for data surfaces: Enforces skeleton loading over spinners, right-aligned numeric columns, sticky table headers, bar/line charts over pie, and explicit empty/loading/error states on every data view. - Corpus-grounded craft: Draws UI procedures from two local application references (reve and linear token systems) and declares three reproduced elements in a Je reproduis line that design-review parses for verdicts. - Use Case: When asked to build a SaaS settings page, the Skill applies the responsive sidebar shell, auto-save patterns, the Domain-Specificity Floor test, and corpus procedures like borderless fields on neutral wells, then outputs production HTML/CSS ready for design-motion. ## Quick Start Use the design-webapp skill to build a dashboard page with KPI cards, a sortable data table, and full empty, loading, and error states.

Frequently Asked Questions about design-webapp

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

FAQPage Schema
How do I design a dashboard layout with KPI cards and data tables?▼

Use the dashboard page pattern: place the North Star metric top-left following F-pattern eye tracking, add 3-4 KPI cards with trend indicators, charts in the middle row, and a sortable data table at the bottom. Include skeleton loading states for all async content.

What is the difference between design-webapp and design-web?▼

design-webapp builds logged-in app surfaces (dashboards, settings, data tables) in the product register, optimizing for density and glance-speed. design-web handles marketing and landing pages in the brand register, where hero treatments and scroll narratives apply.

Should loading states use skeletons or spinners in data tables?▼

Use skeleton rows matching column widths, never spinner-only overlays. NNG research shows skeletons are perceived as 9-12% faster than spinners, and they preserve the table structure during loading.

How should empty states be designed for app screens?▼

Never show a blank view. Name the actual object type and the real first action, such as "No invoices yet — create one from a quote" instead of "No data yet". Include a context-specific illustration and a primary CTA.

When should I not use this skill for a page inside an app?▼

Marketing-adjacent pages inside the app shell, such as an in-app pricing page, route to design-web instead. The product register explicitly excludes hero treatments, scroll-reveal effects, and CTA-driven structures.