/ Products

What we ship today,
and what we're building next.

Alongside client work, Rojiura Studio quietly builds its own products. This page lists what is live, what is in development, and what is still on the workbench.

01 Live

Rojiura Studio

A lantern in every alleyway.

The studio's brand LP and portfolio rolled into one site — built almost end-to-end with multiple AI coding agents (Claude Code, Codex, Gemini). A live showcase of how we work.

How it's built

  • ● Generate multiple copy and structure drafts with LLMs, then pick the angle.
  • ● Lock visual direction by moodboarding with image models before color & type.
  • ● Hand Astro + Tailwind implementation to coding agents; humans focus on review.
  • ● Ship to Cloudflare Pages, then keep extending forms, i18n, and sections incrementally.

Stack

  • Astro
  • Tailwind CSS
  • Cloudflare Pages
  • Claude Code / Codex
See services →
02 In development

STOQ

A family PWA that connects home stock, shopping, and packing.

After validating an MVP on a no-code platform (Base44), the product is being rebuilt with Supabase and a custom front end, led by Claude Code. The spec doc acts as the source of truth that AI agents port and cross-check against.

How it's built

  • ● Validate the MVP on Base44 with real family usage, surface must-have features.
  • ● Treat the spec doc as the single source of truth — the map AI agents work from.
  • ● Hand per-screen porting to Claude Code; humans own API boundaries and data design.
  • ● Roll Supabase RLS and migrations in stages so the family never loses access.

Stack

  • PWA
  • Supabase
  • Stripe
  • Claude Code
03 In development

Hatake

Never lose track of the next task — a calendar-driven home-garden app.

PRD, architecture, and sprint plans live in docs; each sprint ships as a PR mostly written by AI agents. Humans hold the line at PRD-level intent and PR review, while AI does the bulk of the implementation — a doc-driven, AI-native build loop.

How it's built

  • ● Centralize PRD, roadmap, and sprint plans in docs that AI agents can read.
  • ● Open one issue + PR per sprint; Claude Code drives generation and self-review.
  • ● Humans review for spec drift, naming, and dependencies — not for keystrokes.
  • ● Compose Flutter, Supabase, and Cloudflare Workers for the lowest-cost stack.

Stack

  • Flutter (iOS / Android)
  • Supabase
  • Cloudflare Workers
  • Claude Code
04 In development

Wadachi

Every trace you leave with your car.

A two-surface product: a Flutter app and a Next.js web app sharing the same Supabase backend. Repos are separated, but the PRD and data model live in a shared docs space so AI agents can move between both surfaces without losing coherence.

How it's built

  • ● Separate repos for app and web, but a shared PRD + data model in docs.
  • ● Supabase schema is canon; AI generates and aligns types across both clients.
  • ● Spike features as small parallel PRs from AI; humans integrate the direction.
  • ● Outsource the heavy lifting to AI so a solo builder can keep polishing UX.

Stack

  • Flutter (iOS / Android)
  • Next.js 15
  • Supabase
  • Claude Code

/ Collaborate

Maybe there's a product
we should build together.

Beta testers, co-builders, and ideas in their early stages — all welcome.

Get in touch →