Samuel

Hello

Samuel in a black cap and white T-shirt, hand over his mouth, in a gold picture frame. Caption: “this is me, losing it thinking about what to put on this website.”

My name is Samuel

I started coding in high school, when I was super interested in limited edition sneakers, which basically sold out within a few seconds of being released.

I started learning JavaScript to build my own sneaker bots that would automatically purchase the sneakers I wanted, and it kinda changed my life.

Me and my buddy made Ganesh, an automated sneaker bot that was used by over 1,500 other users at its peak. We charged $400 per license, and users purchased more than $30 million worth of sneakers in 1.5 years.

About me, now

These days I reverse-engineer complex apps and APIs, taking them apart until I know exactly how they work.

Funny enough, the kid who built Ganesh, a sneaker bot, now builds bot protection: browser and TLS fingerprinting.

I built Juicer, an IoT kiosk that talks to a live dashboard on Cloudflare Workers.

On the backend I balance heavy load and concurrency, so things stay fast when traffic spikes.

My latest project is Ketagen (ketagen.com).

I work AI-first: I write the spec, agents like Claude Code and Codex build in parallel, and I review on the running app.

I live in Paris, I’m from Prague, and I spend a lot of time in St Barths and LA.

When I’m not shipping, I run with Founders Running Club.

Delivered

A mirror selfie on an iPhone camera screen: Samuel in a steel elevator wearing a cap, headphones, a black hoodie and grey sweatpants, phone raised, a silver suitcase beside him.

How I use AI

I work AI-first: I write the problem down, Claude Code plans it against a spec, and agents build it in parallel. My time goes into the spec and into reviewing the running app, and nothing ships until it feels right.

  • Agents I run

    • Claude Code
    • Codex
    • Grok bot

  • Skills I install

    • stageshow (Benji Taylor)
    • jakubkrehel/skills
    • interfaces skills

  • How I review

    • Agentation annotations
    • /better-interface
    • /break

This page was built this way. Flip Blueprint mode to see the seams.

Projects

I run a small two-person software studio with a close friend, we work on our own projects whenever we have time or think of an idea for something that we or other people could use.

  • An unlimited AI video generator: take a clip’s motion and recast it with your own characters, products or clothes.

  • Private solvers for DataDome, Akamai and Kasada, sold per request, only to scraping services.

    We used to offer these APIs and services on our Discord server.

    • DataDome
    • Akamai
    • Kasada

  • I worked on internal anti-bot protection for Footshop, freelance.

    • Browser fingerprinting
    • TLS fingerprinting
    • Identity checks
    • Rate & velocity checks

  • Where it started: in high school I wrote Ganesh, a bot to buy limited sneaker drops, and it became a product people paid for.

Agents, skills, work

  • Agentation
  • Claude Code
  • ChatGPT
  • Notion
  • Raycast
  • Supabase
  • interfaces.dev
  • X
  • Figma
  • Grok bot

Claude Code, Codex and Grok bot are linked peer-to-peer on the Reason Network, so they can ask each other directly.

npx skills add benjitaylor/skills --skill stageshownpx skills add jakubkrehel/skillsnpx skills add jakubkrehel/make-interfaces-feel-betternpx skills add vercel-labs/next-skills
2,130 contributions in the last yeargithub.com/itemscenter

About me & life

Paris

the weather’s real

the dot’s hardcoded. no GPS, promise

Samuel · Paris, FR · Now

Where I live now.

© OpenStreetMap contributorsWeather: Open-Meteo

From Prague, living in Paris, often in St Barths and Los Angeles. Czech, Slovak, English — and off the keyboard, running and travel.

Member of Founders Running Club. Strava keeps the log.

Inspiration

How I used Fredrin

I wrote one brief (spec, content, checklist), and Fredrin turned it into a foundation ticket that scaffolded the site, the design system and the snap-scroll shell. Then it ran the section tickets in parallel, one Worker per ticket on its own branch, and every Worker interviewed me first, so none of the copy is invented.

When I reviewed the running site, I dropped screenshots of what to change into a Fredrin chat, and each one became a scoped ticket. Fredrin’s Workers used skills I built myself to make it look exactly how I wanted.

  • 37 tickets
  • 35 merged PRs
  • ~19 hours

Built with

It’s built with Next.js 16 (App Router, Turbopack, React Compiler), React 19 and TypeScript 7. The styling is plain CSS Modules with OKLCH tokens: I prefer this to libraries like Tailwind for better performance, and it’s a great match for this project. Motion is hand-built, the icons come from an SVG sprite pipeline, and the handwriting is my own font, Inkhand. The contact form sends to Discord behind Cloudflare Turnstile, the map is Apple MapKit JS, Playwright and Lighthouse CI check it, and it’s deployed on Vercel.

What I’d add to Fredrin

  1. I’d love to remotely interact with my Claude Code running locally on my machine (like /rc in the official Claude app).
  2. Running too many instances of Claude Code at once (15+) makes my Fredrin app freeze. CPU and memory monitoring, and load balancing by pausing tasks for a while, would help.
  3. It would be nice if Fredrin recognised tickets as issue fix or new feature and sorted them into their own sections in each project.

Contact

Thank you for coming to my TED talk.

hey — thanks for reading this far

Seen