DESIGN + CODE

Interactive Prototypes:
Design-to-Code Pipeline

To bridge the gap between design intent and engineering implementation, I prototype key interactions in code before Figma handoff. This practice validates technical feasibility early, provides engineers with reference implementations, and reduces ambiguity in animation timing, easing curves, and responsive behavior.

Why I Prototype in Code

Static Figma mockups can't convey timing, easing curves, or interaction nuance. By prototyping in CodePen/HTML/CSS/JS, I:

  • Validate feasibility before engineering handoff (no "impossible to implement" surprises)
  • Communicate intent through working code, not just specs
  • Accelerate development by providing reference implementations engineers can fork
  • Catch edge cases early (responsive breakpoints, animation performance, browser compatibility)

Live Interactive Demos

Beyond CodePen components — full working prototypes that run in your browser. Built using the same libraries used in production fintech platforms (TradingView, D3.js, React) to prove the design decisions are technically sound, not just visually compelling.

Open Source Study — Staying Sharp on Fintech Stack

These are open source projects I've studied, forked, and prototype against to stay current on the technical capabilities that matter for institutional fintech design. Understanding what the engineering stack can do changes how I design — knowing a chart library has an order book plugin means I can design with it, not around it.

📄
Portfolio Documentation
DESIGN.md
Read DESIGN.md →

A DESIGN.md is the artifact I produce for projects I take seriously — it lives alongside the code, explains the decisions, and makes the system legible to anyone who works with it. This one documents the visual language, token architecture, component decisions, motion principles, and accessibility standards of this portfolio itself.

Covers
Token system · Typography · Spacing grid · Colour rationale
Architecture
Single stylesheet · ES modules · i18n lazy-loading · Zero build chain
Components
Terminal NLP · Prediction cone · Multi-agent consensus · Hero WebGL
Standards
WCAG 2.1 AA · Motion principles · Performance budget · Zero !important

Impact on ACY Securities Design System

These CodePen prototypes served as the reference implementation for ACY's component library, which scaled across:

  • acy.com (Awwwards-nominated homepage)
  • finlogix.com (trading analytics platform)
  • tradingcup.com (social trading)
  • acyconnect.com (institutional B2B)
  • ACY Mobile App (iOS/Android, 100K+ downloads)

Outcome: Code prototypes served as reference implementations across all 5 platforms during ACY's design system buildout. Engineering used them directly during the ACY.com rebuild, reducing back-and-forth during handoff. The component pattern library supported multiple concurrent campaign launches across product lines.

Note on Prototype Access

Many of my CodePen prototypes contain proprietary animation patterns and brand-specific implementations for ACY Securities that I cannot publicly share due to NDA. However, I'm happy to walk through the code logic during interviews or create genericized versions for review. Screenshots shown here preserve the technical approach while protecting proprietary design patterns.