Results for “design-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.

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

Implements and applies algorithms concepts, designs solutions using algorithmic principles, and optimizes performance for algorithm implementations.

Chains architecture review, implementation, and pull request creation to take a story from design through to a convention-compliant PR.

Audits a codebase's animation and motion code, then produces a prioritized list of findings and self-contained implementation plans for other agents to execute.

Creates a complete change proposal with design, specs, and tasks in one step, ready for implementation.

Creates a complete change proposal with design, specs, and tasks in one step, ready for implementation.

Translates Figma designs into project code using the Figma MCP server, fetching design context, screenshots, and assets to implement pixel-perfect UI.

Analyzes and documents Vodafone's design language, including color palette, typography hierarchy, spacing system, and layout patterns for brand-consistent implementation.

Creates executable implementation plans that break down a brainstorming design into detailed, unambiguous per-batch tasks for execution.

Generates premium website design images, then deeply analyzes them to implement faithful frontend code for hero sections, landing pages, and marketing sites.

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

Design interaction flows, states, and microinteractions for usability and feedback clarity. Use when: (1) defining flows, (2) state/error handling, (3) reducing cognitive load. NOT for: final code 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.

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.

Use before any creative or ambiguous work - new features, new components, or behavior changes - to explore intent, requirements, and design before implementation starts.

Generates multiple radically different interface designs for a module, compares them, and synthesizes the best approach.

Prepare implementation handoffs with states, flows, assets, edge cases, and acceptance criteria.

Perform a post-implementation retrospective analysis measuring spec adherence, implementation deviations, and lessons learned.

Shared vocabulary for designing deep modules — a small interface hiding a lot of behavior. Use when designing or improving a module's interface, deciding where a seam belongs, deciding whether to extract or merge modules, or making code more testable.

Implements work from a PRD or set of issues using TDD, typechecking, and regular testing, then reviews and commits the changes.

Run a structured 5-day process to prototype, test, and validate product ideas with real users. Covers mapping, sketching, deciding, prototyping, and testing across Monday-Friday.

Designs chaos experiments, creates failure injection frameworks, and facilitates game day exercises for distributed systems — producing runbooks, experiment manifests, rollback procedures, and post-mortem templates.

Use this when the team needs detailed interaction behavior for user inputs, transitions, feedback, validation, confirmations, or stateful UI behavior that should be implementation-ready rather than purely visual.