Design Token Setup
Custom theme extensions, CSS variables, dark mode, and typography scales mapped from Figma — so utilities mean something stable.
// hire.tailwind_developer()
Available for hireTailwind done right is fast to build and slow to regret. I ship production interfaces with consistent spacing, responsive behavior, and component patterns that survive handoff — not a wall of arbitrary classes nobody wants to edit.
Utility-first frontend delivery for marketing sites, dashboards, and component libraries where speed and consistency both matter.
Custom theme extensions, CSS variables, dark mode, and typography scales mapped from Figma — so utilities mean something stable.
Buttons, forms, cards, and layout shells with variants via cva/clsx — composable without fighting the cascade.
Landing sections, hero layouts, and content pages shipped fast in Astro or Next — responsive and Core Web Vitals aware.
Gradual Tailwind adoption, @apply where it earns its keep, and removal of conflicting global styles that break new screens.
Teams call for Tailwind help when class strings sprawl or the UI drifts from design.
200-character `className` blobs. I extract patterns into components and variants with clear naming.
Random `px` values that do not match Figma. Token-aligned scales keep every screen on the same rhythm.
Desktop-first hacks that break on tablets. I plan breakpoints around real content, not arbitrary device lists.
MUI or Radix styled alongside raw utilities without a system. I unify patterns so teams pick one obvious path.
Design-aligned, component-minded delivery — from single landing pages to multi-template site systems.
Figma audit, breakpoint strategy, and theme extension plan before the first section ships.
Base components, layout primitives, and documentation snippets the team can reuse immediately.
Sections and screens in vertical slices with staged responsive and visual QA.
Hover/focus states, motion restraint, README for tokens, and a quick guide for extending the system.
// hire.now()
Send Figma links or live URLs, note framework (Astro, Next, React), and your timeline. I will confirm scope and how I would structure the UI system.
Start a ProjectPractical companions to Tailwind — chosen for shipping speed without sacrificing structure.
Portfolio pieces where utility-first UI shows up in production quality.
Astro + Sanity fashion storefront with Tailwind-driven product grids, editorial layouts, and responsive merchandising tuned for conversion.
Cyberpunk mono aesthetic built with Tailwind utilities, custom tokens, and Astro — fast, responsive, and maintainable without a CSS framework war.
Yes. I stay current with Tailwind releases and migration notes. For new projects we pick the version that matches your hosting and build pipeline.
That is a core part of my workflow. I map frames to components, extract spacing and color tokens, and stage visual QA so revisions are about edge cases.
Depends on the product. Marketing and custom brand UI often favor Tailwind; dense admin tools sometimes mix Tailwind layout with headless primitives. I advise honestly in discovery.
No. I also build React/Next product UI with Tailwind — forms, tables, dashboards, and interactive marketing experiences.
Component extraction, cva variants, consistent naming, and eslint plugins where helpful. The goal is readable JSX, not shorter files at the cost of clarity.
// contact.init()
// status.check()
Available for freelance — US/UK/EU clients preferred.
Full projects, hourly, and retainers welcome.
// message.compose()
message.sent()
I'll respond within 24 hours.
Something went wrong. Please try again.
No spam · Project details stay confidential · NDA available on request