forma-interface
/forma-interface
Build or refine operational interfaces, clean shells, forms, navigation, search, settings, appearance editors and material profiles. Use for usable components and states; not for broad research, campaigns or 3D geometry implementation.
- Author
- figueirego ↗
- Repository
- forma ↗
- Licence
- MIT
- Last repository change
- 11.11.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 11.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Build or refine operational interfaces, clean shells, forms, navigation, search, settings, appearance editors and material profiles. Use for usable components and states; not for broad research, campaigns or 3D geometry implementation.
Original author description
Build or refine operational interfaces, clean shells, forms, navigation, search, settings, appearance editors and material profiles. Use for usable components and states; not for broad research, campaigns or 3D geometry implementation.
How it works
- When to use
- Inputs
- Procedure
- Output and stopping condition
- Coordination and execution boundaries
SKILL.md preview
--- name: forma-interface description: "Build or refine operational interfaces, clean shells, forms, navigation, search, settings, appearance editors and material profiles. Use for usable components and states; not for broad research, campaigns or 3D geometry implementation." metadata: version: 1.36.0 --- # Interface and states ## When to use - Use for sidebars, backgrounds/panels/controls, forms, search, preferences, profiles and their states. - Do not use to turn a UI improvement into a complete redesign or present a mockup as a data integration. This module requires the agent to read it; it does not trigger tools or other modules automatically. Preserve the existing brand, stack, domain, components and contracts. An operational screen organizes work: objects, scope, data and the next action. A page communicating an offer follows [Brand](../forma-brand/SKILL.md). If the page contains app fragments, treat their interiors as an interface: reuse the existing system, coherent data and actual states or labeled demonstrations. The surrounding promotional composition does not justify changing the product's tables, units, precision or flows. For a relevant saved capability, use [reuse by capability](../../references/capability-reuse.md): search by the task, not the source project, and bind the mechanism to the destination's own identity and state owners. Read only the matching contract; do not expand a local fix into a redesign. Source names and exact profiles remain provenance or explicit fidelity targets. ## Inputs - Concrete task, route/component, expected action, actual data or labeled fixtures, and access to the consumer. - Current states, API/storage contracts, permission limits and an approved reference when available. ## Procedure 1. Walk through entry, action, success and recovery; identify the owners of state and persistence. Read [interaction and content](../../references/interaction-content.md) and, when data/permissions are involved, [contracts and trust](../../references/contracts-trust.md). Identify objects, units, usage frequency and the decision the screen supports. Repeated values use the same source and scope; totals and deltas follow the domain's calculation and rounding, without adjustments to improve the image. If the direction is open, use [directions and comparison](../../references/design-directions.md); do not import a hero recipe into an approved dashboard. 2. For the background/sidebar/panel/control system, read [clean shell](../../references/clean-shell.md). For a compact fixed window with content-only scrolling, use [compact workspace](../../references/compact-workspace.md). For calm glass selection with an accent icon/marker and integrated context, use [calm navigation](../../references/calm-glass-navigation.md). Adapt surfaces and accents to the destination; neither capability requires a source-project name. The [recorded experience](../../references/helloura-experience.md) and its private kit apply to explicit source fidelity, not ordinary reuse. For the approved warm colored sidebar, diagonal glass controls, dots and inset panel, use [Soft Glass](../../references/soft-glass.md) and its portable specimen. A design-only request stops at static content, visual states and responsive/theme previews; do not add product handlers, persistence or fake success messages. Apply steps about data and recovery only when behavior is requested. For a new screen or broad visual refinement, first apply the [shared visual foundation](../../references/visual-system.md#coordinate-the-foundation) to these components together. Resolve supported themes, spacing, radius roles, and icon language. For new interactive designs, include [Motion](../forma-motion/SKILL.md) with the shared context and implement its [default layer](../../references/motion.md#default-motion-for-new-interactive-designs); a local fix uses only its affected contract. Inspect the indicated assets and adapt consumers/events to the stack. For fields, navigation and tables, use [component patterns](../../references/component-patterns.md). 3. Read only the contracts for the requested capability: [search](../../references/search-discovery.md), [settings](../../references/settings-modes.md), [appearance editor](../../references/lighting-editors-icons.md) or [material profile](../../references/adaptive-visual-systems.md). Specify query semantics, preview/commit/cancel/reset, layers and export only when they are in scope. For the complete editor, carry its [initialization, composition, gesture and persistence contracts](../../references/lighting-editors-icons.md) into implementation and transfer prompts; "draggable points" alone does not specify the mechanism. That reference owns the exact profile, measurements and regression cases. Do not impose those details on unrelated controls. 4. Implement the slice that proves the capability and connect handlers, data and storage to the correct owner. The profile uses the domain's fields and the approved object in the destination; do not impose the reference's card/role on an existing passport. Check global/contextual scope, framing of the open object and consumer updates without destroying the session or focus return. Follow reuse in another project in [playbooks](../../references/playbooks.md). The [portable AppearanceEditor](../../references/reusable-components.md#appearanceeditor-integration) supplies scoped vanilla controls, draft/commit state and explicit save/cancel adapters. Reuse it when compatible, or adapt the mechanism to existing components. Connect its persistence and context to the destination owner; the [component lab](../../assets/components-lab.html) uses browser-local sample data. The clean-shell demo does not provide a backend. For faithful reproduction, freeze the approved source's criteria before editing the consumer. Use [fidelity contracts](../../references/fidelity-contracts.md) to compare measurements; the profile does not replace persistence, access or rendered inspection. 5. Exercise keyboard input, focus, errors, extremes and reopening when persistence is promised. Use [rendered validation](../../references/rendered-validation.md) and [verification](../../references/verification.md); validate each agreed search capability against expected results. Distinguish local code, served response, isolated test context and an already-open tab. Compare the individual identity of affected CSS and JS with the tested artifact; a matching `data-revision` does not resolve an old cache. If a draft exists, preserve it and leave saving/discarding to the user before reloading. For the complete editor, run the [full-contract regressions](../../references/lighting-editors-icons.md#full-contract-regressions) under the same reference conditions, including composition, gestures, focus and persistence. Existing buttons and model tests do not prove composition or access. ## Output and stopping condition Deliver a working interface or an explicitly requested specification, states and the observable task result. Identify simulated data, in-memory-only changes and integrations that are still missing. Stop when the distinguishing operation works in the consumer and affected states have no relevant regressions. A toast does not prove saving; changing colors does not prove composition reuse; focusing an input does not prove a command palette. ## Coordination and execution boundaries Use Forma Foundations for unresolved tokens, Forma Motion for gestures and transitions, and Forma Validation for task and access checks. Keep handler diagnosis and control integration in this module. The coordinator selects additional modules; do not recursively dispatch between specialists. Use the available tools according to [capabilities](../../references/integrations.md); a tool name does not prove connection or execution. Do not replace requested volume/interaction with an image or merely tilted plane. Previously approved articulated CSS 3D remains a valid mechanism; do not replace it with WebGL by association. Keep each capability's implementation boundary visible in the delivery.
Files in this package (2)
- SKILL.md 8 KB
- agents/openai.yaml 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · figueirego/forma | 90 | MIT |
| figueirego/forma | 90 | MIT |
| figueirego/forma | 85 | MIT |
Database snapshot: 13.11.2026 · package version c266d731a510 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 85compact-interface-design
Design or refine dense dashboards, editors and operational forms without inflating typography. Use for wasted desktop space, slow everyday entry flows and mobile navigation that hides primary work. - 100forma-objects-3d
Integrate or refine reusable material objects, BookObject, books, covers and 2D/3D mascots, including geometry, materials, gestures and lifecycle. Use for object mechanisms and fidelity; not to add decorative 3D to every interface. - 100forma-objects-3d
Integrate or refine reusable material objects, BookObject, books, covers and 2D/3D mascots, including geometry, materials, gestures and lifecycle. Use for object mechanisms and fidelity; not to add decorative 3D to every interface. - 100ui-design-patterns
Provides practical UI design patterns for hierarchy, spacing, typography, color, depth, imagery, UI copy, forms, navigation, tables, empty states, loading states, accessibility, and responsive behavior. Use when designing, reviewing, polishing, or refactoring web interfaces,… - 100forma
Read and edit Forma boards, the designer's research boards that live as plain folders (board.json + media/ + components/). Use whenever the user asks to add, sort, connect, find or change anything on a Forma board, to bring research in (images, videos, links, notes, meetings,… - 100design-build
Implement or refine frontend visual design, CSS, layout, typography, color tokens, and component states. Use when creating or styling an interface.