interface-details

Applies cataloged micro-interaction, motion, and accessibility rules to polish user interfaces.

609|50|Updated Jul 7, 2026
One-click install
npx skills add https://github.com/poco-ai/Agentero --skill interface-details-poco-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: interface-details
Source: https://github.com/poco-ai/Agentero/tree/main/.agents/skills/interface-details
Command: npx skills add https://github.com/poco-ai/Agentero --skill interface-details-poco-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Interfaces often work correctly but feel rough: missing focus rings, jarring transitions, truncated text, and inconsistent microcopy erode user trust. This Skill provides a curated catalog of interface details and a decision framework for applying them with restraint when building, polishing, or reviewing UI. ## Core Features & Use Cases - Three operating modes: Build (apply details while writing UI code), Polish (improve existing UI in place), and Review (audit UI and report findings with rule IDs and file:line references). - Seven detail chapters: Typography, motion, design, easter eggs, accessibility, copywriting, and interactivity, each loaded on demand via a routing table. - Decision gate: Every candidate detail is checked against user value, exposure frequency, accessibility (prefers-reduced-motion, keyboard access), and consistency before being applied. - Use Case: When reviewing a React modal component, the Skill loads the motion chapter, flags that the close animation is not interruptible (motion-11), and suggests a concrete fix in a Before/After/Why table. ## Quick Start Ask the assistant to review your UI component for polish opportunities, for example: review my Modal.tsx for motion and accessibility details.

Frequently Asked Questions about interface-details

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

FAQPage Schema
How do I make my UI feel more polished?

Audit your interface against a catalog of details covering motion, typography, accessibility, and microcopy. Apply only details that pass a decision gate: they must serve the user, respect reduced-motion preferences, and stay consistent with the rest of the product.

How to review a React component for accessibility issues?

Check for visible focus rings on all focusable elements, keyboard operability of every control, 44px touch targets, and labeled inputs. Report findings grouped by file with rule IDs and concrete before-and-after fixes rather than rewriting code silently.

When should I skip adding animations to an interface?

Skip animation on high-frequency actions invoked dozens of times daily, when the user prefers reduced motion, or when motion would delay task completion. Reserve full motion for first-run or rare moments where the spectacle still lands.

Does this approach work with any frontend framework?

Yes, the detail rules are framework-agnostic and cover CSS, HTML semantics, and interaction patterns. Examples reference React and vanilla JavaScript, but the principles apply to Vue, Svelte, or plain HTML interfaces.

What are the limitations of automated UI polish suggestions?

Rules marked Need confirm require explicit user approval before applying, and subjective judgments like optical alignment still need human verification. The catalog covers common surfaces but cannot replace usability testing with real users.