UI NINJA

Open to contract roles

hello@uininja.co.ukLinkedIn (opens in a new tab)YouTube (opens in a new tab)X (opens in a new tab)Get in touch

Miltiadis Bouchalakis · Senior frontend consultant, London

Frontend consulting for complex React and Next.js products.

The UI Ninja figure, a graphite card model, stands in guard on the rounded corner of a white terrace card against open sky. The corner carries the silver shuriken mark in a graphite well and the words UI Ninja · London · Frontend consulting.

UI Ninja is the frontend practice of Miltiadis Bouchalakis. I work with product teams on complex React and Next.js applications: the architecture, the standards the team works to, and the UI that ships. 10+ years building product frontends across government, betting and education. London or remote.

Discuss a roleServicesLinkedIn (opens in a new tab)
Experience
10+ years · government, betting, education
Focus
React, Next.js, design systems
Based
London · remote-friendly
Status
Open to contract roles

UI NINJA · LONDON · FRONTEND CONSULTING

01 · Services

When frontend delivery stalls.

I step into messy products, stabilise the frontend, and get delivery moving again.

  1. Delivery slows downCode
  2. The UI stops feeling coherentDesign
  3. Quality becomes unpredictableEngineering
  4. AI arrives before the guardrailsWorkflow
The Services tower: four trays carried by two exposed cores, signed 01 to 04 with the take titles below. A vermilion ring marks tray 01.

01 · Code

Delivery slows down

10+ years · government, betting, education

  1. The problemFeatures take longer: too many patterns, too much duplication.
  2. What I doI audit the codebase, agree one approach per problem and set clear boundaries.
  3. What you getOne agreed way to build each feature, and delivery that picks up again.

Features take longer because the frontend has become harder to reason about. Too many patterns, too much duplication, not enough structure. I simplify the system so teams can move faster without sacrificing quality.

What you get

  • One agreed way to build each kind of feature, written down.
  • A frontend the team can reason about and change with confidence.
  • Feature delivery that picks up again, without trading away quality.

How it runs

  1. Audit A map of the codebase
  2. Simplify Small PRs, no rewrite
  3. Handover Patterns written down
Get in touch

02 · Design

The UI stops feeling coherent

10+ years · government, betting, education

  1. The problemEvery screen solves the same problem differently, so the product drifts.
  2. What I doI audit the screens, agree one pattern per problem, build it into the system.
  3. What you getScreens that work the same way, and a design system the team actually uses.

Products drift when each screen solves the same problem differently. I make the frontend coherent again through reusable patterns, clearer boundaries, and a design system that actively supports delivery.

What you get

  • Screens that solve the same problem the same way.
  • A design system the team uses because it makes delivery easier.
  • What ships matches what the designers drew, down to empty and error states.

How it runs

  1. Audit Screens against Figma
  2. Build the system Alongside feature work
  3. Handover Every state documented
Get in touch

03 · Engineering

Quality becomes unpredictable

10+ years · government, betting, education

  1. The problemBrittle code, noisy reviews and regressions that should have been caught.
  2. What I doI set up CI and pre-commit checks, and track bundle and render cost on every PR.
  3. What you getFast feedback, quieter reviews and predictable releases from small changes.

Weak standards show up as brittle code, noisy reviews, and regressions that should have been caught earlier. I raise the quality of the frontend so day-to-day delivery gets easier over time.

What you get

  • Fast feedback for developers, from pre-commit hooks to CI.
  • Quieter reviews that focus on what the change does.
  • Predictable releases for the business, built from small changes.

How it runs

  1. Trace Where bugs slip through
  2. Tighten One check at a time
  3. Handover Every gate explained
Get in touch

04 · Workflow

AI arrives before the guardrails

10+ years · government, betting, education

  1. The problemAI tools bring more code, not better code, and nobody owns the output.
  2. What I doI run agent workflows with a written scope and review on every change.
  3. What you getOne engineer who owns every change that ships, whoever drafted it.

Teams adopt AI tooling and get more code, not better code. Review falls behind and nobody owns the output. I bring the guardrails with me: a written brief for every agent, review on every change, one engineer who owns what ships.

What you get

  • One engineer who owns every change that ships, whoever drafted it.
  • Generated code held to the same standard as code written by hand.
  • Architecture and trade-offs settled before the agents start, not by them.

How it runs

  1. Brief Architecture first
  2. Draft Agents in parallel
  3. Decide I decide what ships
Get in touch

02 · Contact

Discuss a role.

Get in touch about a role, contract, or project. I reply within 24 hours.

Based
London, UK. Remote-friendly.
Availability
Open to new contract roles.
Engagement
3-12 months typical. Short delivery sprints possible.
Focus
React, Next.js, design systems, frontend architecture.
Workflow
AI agents draft to a written brief. I review every change that ships.
Day rate
Discussed based on scope and seniority.
Response
Within 24 hours.
Day rate
Or email hello@uininja.co.uk

UI Ninja Ltd uses these details to reply to your enquiry. Privacy notice

The reply tower across the bay, its open bay dimly lit, with a thin vermilion route leading to it.