frontend-ui-ux

Translate design briefs into production-ready frontend UI components.

Updated Feb 23, 2026
One-click install
npx skills add https://github.com/dev-mirzabicer/crucible --skill frontend-ui-ux-dev-mirzabicer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: frontend-ui-ux
Source: https://github.com/dev-mirzabicer/crucible/tree/main/.opencode/skills/frontend-ui-ux
Command: npx skills add https://github.com/dev-mirzabicer/crucible --skill frontend-ui-ux-dev-mirzabicer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designer-turned-developer who translates design intent into robust code, ensuring spacing, color harmony, micro-interactions, and a cohesive interface even without formal mockups. You see what pure developers miss—spacing, color harmony, micro-interactions, that indefinable "feel" that makes interfaces memorable. You envision and create beautiful, cohesive interfaces that align with a strong visual language.

Core Features & Use Cases

  • Pixel-perfect translation of visual design into production-ready UI across web and mobile.
  • Design-to-code workflow that preserves typography, color tokens, spacing scales, and motion cues within a shared design system.
  • Accessible, responsive components with clear documentation that scales as features grow.

Quick Start

Convert the designer's brief into ready-to-run UI components with accessible interactions.

Frequently Asked Questions about frontend-ui-ux

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

FAQPage Schema
How do I translate a design brief into pixel-perfect frontend UI?

Translating a design brief into pixel-perfect frontend UI involves converting visual design intent into production-ready code while preserving typography, spacing scales, and color tokens. This ensures a cohesive interface with accessible, responsive components across web and mobile layouts.

What is design-to-code workflow for component libraries?

Design-to-code workflow for component libraries is the process of mapping visual design systems into scalable, component-driven architecture. It maintains color harmony, spacing scales, and motion cues within shared design tokens to ensure cohesive interfaces as features grow.

How do I build accessible, responsive components without formal mockups?

Building accessible, responsive components without formal mockups requires applying established design system principles to generate functional frontend code. You define typography, spacing, and color tokens to create cohesive interfaces with micro-interactions that maintain accessibility standards.

Can I use this approach for mobile-responsive layouts and web interfaces?

Yes, this approach works for both mobile-responsive layouts and web interfaces by applying a shared design system. It handles typography, spacing, color tokens, and motion cues to ensure pixel-perfect translation of visual design across different viewport sizes.

What's the best way to maintain design tokens when converting visual design to code?

The best way to maintain design tokens when converting visual design to code is using a component-driven architecture within an established design system. This preserves typography, spacing scales, color tokens, and motion cues while generating scalable, documented frontend implementations.

Why does my frontend UI lack the visual feel that pure developers miss?

Frontend UI often lacks visual feel because pure developers may miss spacing, color harmony, and micro-interactions. Translating design intent into robust code ensures these aesthetic details are preserved, creating memorable interfaces that align with a strong visual language.