Results for “design-implementation”

UI Designer IA — Expert en design visuel, composants UI, design systems, et pixel-perfect implementation. shadcn/ui, Tailwind, Figma → Code.

Design technical architecture, select technology stack, and define implementation strategy from specifications and constitution constraints.

Plans interface structure, component layout, and interaction details for product flows before implementation.

Use when UI expertise is needed to unblock implementation decisions.

Learn and apply CQL concepts, implementation strategies, best practices, and real-world applications in professional environments. Covers foundational concepts, Python implementation patterns, and production-grade system design.

Guides collaborative dialogue to turn ideas into approved designs and specs before any implementation begins.

Guides collaborative dialogue to turn ideas into approved designs and specs before any implementation begins.

Technical architecture and UX specialist who provides developers with solid foundations, CSS systems, and clear implementation guidance

Guides collaborative dialogue to turn ideas into fully formed designs and specs, exploring intent, requirements, and design before implementation.

Documents Renault's brand design system including color palette, typography hierarchy, and layout principles for web implementation.

Review UI implementations against design quality standards and design system compliance, or create distinctive, production-grade frontend interfaces from scratch.

Review C#/.NET code for design pattern implementation and suggest improvements without making changes.

Design, implement, audit, and plan interface animation and motion systems. Use for animation reviews, motion audits, easing and duration decisions, gesture physics, transform origins, reduced-motion behavior, animation performance, SvelteKit or Motion integration, perceptual feel checks, or self-contained animation improvement plans.

Create a detailed, step-by-step implementation plan for a feature or project. Load when the user asks to plan a feature, create a technical roadmap, break down a PRD into tasks, design an implementation strategy, or sequence engineering work. Also triggers on "how should we build this", "implementation plan for", "technical breakdown", "task list for", or any request to turn a high-level requirement into a concrete execution plan. Supports phased rollouts, architecture-first, and MVP-focused planning.

Convierte especificaciones aprobadas en un plan técnico detallado, documentando decisiones de arquitectura, flujo de datos y cambios de archivos.

Design and implement clear, modular, resilient software and create executor-grade implementation plans with explicit scope, drift checks, verification gates, tests, STOP conditions, dependencies, and delegated-work review. Use for development, refactoring, architecture, implementation planning, safe migrations, handoffs to another engineer or agent, or verifying delegated code changes.

Builds a feature implementation plan from an existing feature specification (or equivalent context) through a facilitated team conversation. Use when the user wants to plan how to implement, build, deliver, or ship a feature that has already been specified. Does not specify what the feature should do — use plan-a-feature first. Does not design the contract for an interface — use design-an-api. Does not refine or stress-test an already-written plan — use iterative-plan-review. Runs its resolution rounds to completion and holds its questions until after they finish; to review each round as it lands, use pairing.

Design UI/UX in a Sage project — Figma to Blade, design tokens to Tailwind v4, Paper/Figma MCP integration, component design, layout design, responsive design, design-to-code workflow, visual design review, design system alignment, design approval before implementation

Generate structured, machine-readable implementation plans for features, refactoring, upgrades, or infrastructure changes.

Translates Figma designs into production-ready application code with pixel-perfect accuracy, using the Figma MCP server to fetch design context, screenshots, and assets.

Implement a piece of work based on a spec or set of tickets.

Enforces system design, project structure, dependency management, error handling, testing, and documentation standards at principal-engineer level.

Implement a piece of work based on a spec or set of tickets.

Writes mechanism-first technical implementation deep-dive articles that explain design intent, data flow, trade-offs, and operations, with code locations as supporting evidence.

Design high-level system architecture, create Architecture Decision Records (ADRs), evaluate technology trade-offs, and plan for scalability.

Implements a piece of work from a spec or ticket set. Use when the user says "implement this spec", "work the tickets", or wants code written from an existing plan.

Write an implementation plan from an approved architecture and MVP scope. Use when the team needs milestones, workstreams, dependency ordering, acceptance criteria, and execution sequencing that connect product intent to shippable engineering work.

Provides design patterns and architectural approaches for implementing compilers, including optimization, debugging, and best practices.

6-phase iterative specification execution workflow covering implementation, testing, review, improvement, commit, and progress tracking with quality-gated convergence.

Design reliable, scalable, and maintainable data systems by applying principles from storage engines, replication, partitioning, transactions, and consistency models.