surface-modes

Classifies UI surfaces into four modes that define success criteria before design decisions.

Updated Aug 12, 2026
One-click install
npx skills add https://github.com/brunoolf/frontend-craft --skill surface-modes-brunoolf
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: surface-modes
Source: https://github.com/brunoolf/frontend-craft/tree/main/skills/surface-modes
Command: npx skills add https://github.com/brunoolf/frontend-craft --skill surface-modes-brunoolf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designers and AI agents often apply the wrong evaluation criteria to a screen — judging a dashboard by landing-page standards or decorating documentation — producing competent work that fails its actual purpose. This Skill establishes the correct success criteria before any layout, density, or motion decision. ## Core Features & Use Cases - Four Surface Modes: Defines Persuadir (landing pages, marketing), Operar (dashboards, apps, admin), Ler (docs, articles, changelogs), and Experimentar (portfolios, immersive showcases), each with its own rules for spacing, density, motion, and typography. - Concrete Constraints per Mode: Provides measurable guidance such as 65–75 character line measures for reading surfaces, 24–48px section spacing for operational tools, and one primary CTA per viewport for persuasive pages. - Mixed-Surface Handling: Explains how to handle products combining multiple modes, including dominant-mode rules and recording per-surface scales in DESIGN.md. - Use Case: Before redesigning a SaaS product, classify its marketing site as Persuadir, its app as Operar, and its docs as Ler, then apply the correct spacing scale and motion policy to each instead of forcing one system-wide standard. ## Quick Start Load the surface-modes skill and classify each screen of my project into Persuadir, Operar, Ler, or Experimentar before reviewing the design.

Frequently Asked Questions about surface-modes

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

FAQPage Schema
How do I choose the right design criteria for a dashboard vs a landing page?▼

Classify the surface by its job: a dashboard is Operate mode, favoring density, scannability, and keyboard navigation, while a landing page is Persuade mode, favoring generous spacing, large type scale, and one primary CTA per viewport. Applying landing-page criteria to a dashboard wastes space and hides information.

What line length should I use for documentation and articles?▼

Reading surfaces should use a line measure of 65 to 75 characters, which the skill defines as non-negotiable for comfortable reading. Pair this with consistent vertical rhythm and more space above headings than below.

When is heavy motion or 3D justified in a UI?▼

Heavy motion and 3D are justified as content only in Experience mode surfaces like portfolios and immersive showcases. In Operate mode, entrance animations on frequently opened panels are harmful, and in Read mode they should be avoided entirely.

How do I handle a product that mixes multiple surface modes?▼

Let the dominant mode control the layout and treat divergent blocks as contained exceptions, not new patterns. Record which spacing scale applies to which surface in DESIGN.md rather than forcing one scale across landing pages and dashboards.

Why does my dashboard feel wrong after a redesign?▼

A common cause is applying Persuade-mode criteria — large spacing, low density, decorative moments — to an Operate-mode surface. Operational tools need high density, visible system state, and precise details like toast timing and focus styling instead of expressive decoration.