Ship spec-first
Nothing gets built without a spec, a plan, and a tasks file. The 20 minutes of writing saves a day of re-work every single time.
About
A studio of one, running with the model.
I'm Ruslan Hrekov — a solo builder shipping production software with Claude at the keyboard and taste at the helm. I run a studio of one out of Kyiv → Ohio, and I've spent the last two years turning the AI-collaboration workflow from a novelty into a reliable operating system.
The register I care about is honesty. Every case study on this site links to commit hashes; every claim about scale points to a number I can defend; every one of the five shipped projects passed through the same spec-plan-DEVLOG loop before a single line landed in production.
My taste settles late in the process, not early. I'll rewrite a design token before I refactor a feature, and I'll kill a nice-looking abstraction the moment it starts hiding decisions. Claude does the typing. I do the pivots, the frozen-logic calls, and the parts that only matter when a user is watching.
Experience
The path so far.
- 2026 — now
Solo studio · AI-collaborative software
Shipping five production case studies with Claude as pair. Every build ships spec + plan + DEVLOG. ShipLoop discipline as the operating system.
- 2025 — 2026
First Claude-collaborative production builds
Noble booking SaaS, Angel Trucking pipeline, Fieldmark PDF-to-checklist. Learned the frozen-logic discipline the hard way — refactored what I would have shipped.
- 2024 — 2025
Prompt patterns · internal automation
Built early Opus/Sonnet/Haiku routing rigs and volume automation for small teams. First contact with the “spec before code” instinct.
- 2022 — 2024
Full-stack engineering · remote (Kyiv → Ohio)
Next.js + Supabase + Stripe stacks for boutique clients. Learned to measure everything and to trust commit hashes over screenshots.
AI stack
Right-sized model for the
decision on the table.
The interesting question isn’t which model is smartest — it’s which model matches the cost, latency, and reversibility of what you’re about to ship.
Base
Kyiv → Ohio · remote
Practice
AI collaboration · solo builds
Cadence
2–3 months per case study
OpusStrategy, architecture, review
Angel five-stage pipeline · Noble frozen-logic authoring
SonnetFeature implementation, refactors
Lexora audio pipeline · Fieldmark auth pivot
HaikuHigh-volume, low-stakes
smm-factory comment replies · analytics summaries
How I work
Four rules that keep
solo work honest.
One decision at a time
Batching architectural choices is how you end up rewriting three of them at once. I pick, ship, review, then pick again.
Numbers over screenshots
A commit hash and a benchmark beat a slick demo. If the number isn't there, the claim isn't either.
Reduce-motion first, always
Every animation ships with a static fallback. Every canvas gates on hover-capability. The site works for the reader who needs it to be still.
Fractional engagement, or a full-time seat.
Both doors are open. Say what you’re after and I’ll reply within two business days.