<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Rizvanop Pulky Izni Nadzirul Faza</title>
    <description>The latest articles on DEV Community by Rizvanop Pulky Izni Nadzirul Faza (@real0xsi).</description>
    <link>https://dev.to/real0xsi</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4250911%2F234510a9-e5c1-43b9-99f2-ab65670c7b20.jpg</url>
      <title>DEV Community: Rizvanop Pulky Izni Nadzirul Faza</title>
      <link>https://dev.to/real0xsi</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/real0xsi"/>
    <language>en</language>
    <item>
      <title>I Built a Store-in-a-Box for Phone-First Sellers with Kiro CLI</title>
      <dc:creator>Rizvanop Pulky Izni Nadzirul Faza</dc:creator>
      <pubDate>Wed, 18 Nov 2026 04:09:10 +0000</pubDate>
      <link>https://dev.to/real0xsi/i-built-a-store-in-a-box-for-phone-first-sellers-with-kiro-cli-3075</link>
      <guid>https://dev.to/real0xsi/i-built-a-store-in-a-box-for-phone-first-sellers-with-kiro-cli-3075</guid>
      <description>&lt;p&gt;&lt;em&gt;This post is part of Kiroween 2026 — I built Warung Digital with Kiro, and this is the honest story of how it went.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;I'm a solo founder in Indonesia. No laptop, no office — just a phone, and a problem I kept running into: most sellers around me don't run a "store." They run a WhatsApp number.&lt;/p&gt;

&lt;p&gt;Orders come in by chat or DM. Payment is a screenshot of a transfer. Digital goods — a Claude seat, a Canva invite, a game top-up — get delivered by hand, one message at a time. It works, until it doesn't: orders get lost, buyers ask "where's my key?" at midnight, and the seller is the entire backend.&lt;/p&gt;

&lt;p&gt;I wanted to give those sellers a real store-in-a-box. Something they could run from their phone, with a storefront, a checkout, and delivery that happens by itself. That's Warung Digital.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Live app:&lt;/strong&gt; &lt;a href="https://warung.digitalshoup.my.id/" rel="noopener noreferrer"&gt;https://warung.digitalshoup.my.id/&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Repo:&lt;/strong&gt; &lt;a href="https://github.com/real0xSI/warung-digital" rel="noopener noreferrer"&gt;https://github.com/real0xSI/warung-digital&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Demo video (2:21):&lt;/strong&gt; &lt;a href="https://youtu.be/Nkn_BXsEuqM" rel="noopener noreferrer"&gt;https://youtu.be/Nkn_BXsEuqM&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The problem, up close
&lt;/h2&gt;

&lt;p&gt;Indonesia's small sellers are phone-first, not website-first. A full e-commerce setup — hosting, payment gateway onboarding, a dashboard nobody opens — is overkill for someone selling ten seats a week. But the manual alternative has a real cost: every order is a conversation, every delivery is a copy-paste, and there's no record of anything.&lt;/p&gt;

&lt;p&gt;What they actually need is small: a page that lists products, a checkout that takes payment, a key or invite delivered automatically, and a cockpit that shows today's orders at a glance.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Warung Digital does
&lt;/h2&gt;

&lt;p&gt;Warung Digital is a single zero-dependency Cloudflare Worker — one &lt;code&gt;worker.js&lt;/code&gt; file, no framework, no build step. It gives a seller:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;A storefront&lt;/strong&gt; with products, prices in rupiah, and live stock.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Checkout on three rails&lt;/strong&gt; — QRIS, Stripe, and crypto — plus seat invites for account-based products.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;HMAC-signed license keys&lt;/strong&gt;, issued automatically on a paid order and verifiable in-app, so a key can't be faked by editing a URL.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;An admin cockpit&lt;/strong&gt;: today's orders and revenue, low-stock alerts, a license-verify box, and a "My orders" view for buyers.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;WhatsApp order confirmation&lt;/strong&gt;, because that's where the buyer already lives.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;One honest line before I go further: &lt;strong&gt;the checkout is a mock. No real money moves.&lt;/strong&gt; All three payment rails are labelled MOCK in the app. The QRIS code, the Stripe flow, the crypto payment — they simulate the full order-to-key journey so the product can be tested end to end, but nothing charges anyone. I built it this way deliberately: a hackathon demo should never pretend to take real payments it can't settle.&lt;/p&gt;

&lt;h2&gt;
  
  
  How Kiro built it
&lt;/h2&gt;

&lt;p&gt;I built Warung Digital with Kiro CLI 3.3.0, and I did it spec-first, not vibe-first. Before any feature code existed, there was a spec, and the work followed it.&lt;/p&gt;

&lt;p&gt;The &lt;code&gt;.kiro/&lt;/code&gt; directory in the repo tells the story:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;1 spec&lt;/strong&gt; — the product requirements, design, and task list, written before implementation.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;3 steering docs&lt;/strong&gt; — persistent project rules Kiro follows on every run, so the product, tech stack, and structure stay consistent.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;1 hook&lt;/strong&gt; — automation that fires on agent events.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;2 custom agents&lt;/strong&gt; — specialised agents for distinct parts of the work.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A 4-tool MCP server&lt;/strong&gt; — tools Kiro calls to work with the project.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A 3-skill pack&lt;/strong&gt; — reusable skills that encode how parts of the build are done.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That structure is the whole point. Kiro wasn't guessing what I wanted from a one-line prompt. It was working from a written spec with written rules, and I could review, correct, and re-run against the same source of truth.&lt;/p&gt;

&lt;p&gt;I also redeemed the &lt;strong&gt;4,000-credit Kiroween grant&lt;/strong&gt; for this build, which covered the Kiro usage behind it.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Kiro did not do
&lt;/h2&gt;

&lt;p&gt;Honesty cuts both ways. Kiro did not run a vibe-coding loop, and there is no property-based testing here. The test suite is &lt;strong&gt;28/28 example-based tests passing&lt;/strong&gt; — real assertions against real behaviour (checkout flows, HMAC tamper rejection, stock handling, admin stats), run and re-run until green. That's solid for a one-file Worker, but it's example-based, not property-based, and I'm not going to dress it up as something it isn't.&lt;/p&gt;

&lt;p&gt;What Kiro did do: turn a spec into a working, tested, deployed product — storefront, mock checkout, signed keys, admin cockpit — in a single file I can read end to end and redeploy with one command.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I learned
&lt;/h2&gt;

&lt;p&gt;Three things stuck with me.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;First, spec-first beats prompt-first.&lt;/strong&gt; The spec and steering docs meant Kiro's tenth change was as consistent as its first. Without them, every session would have drifted.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Second, small is a feature.&lt;/strong&gt; One Worker, one file, zero dependencies. There's nothing to install, nothing to keep in sync, and the whole product fits in my head.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Third, honesty is a feature too.&lt;/strong&gt; Labelling the checkout MOCK isn't a weakness — it's what makes the demo trustworthy. A seller who tests it knows exactly what's real (the storefront, the keys, the cockpit) and what's simulated (the money movement).&lt;/p&gt;

&lt;h2&gt;
  
  
  What's next
&lt;/h2&gt;

&lt;p&gt;Warung Digital is live, tested, and submitted for Kiroween 2026. The next steps are real payment integration, real sellers trying it on their own products, and whatever breaks first in their hands — because that's the feedback that actually matters.&lt;/p&gt;

&lt;p&gt;If you're building for phone-first sellers, or you built something for Kiroween too, I'd love to hear how you approached it.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Built with Kiro CLI 3.3.0 for Kiroween 2026. Live app: &lt;a href="https://warung.digitalshoup.my.id/" rel="noopener noreferrer"&gt;https://warung.digitalshoup.my.id/&lt;/a&gt; · Repo: &lt;a href="https://github.com/real0xSI/warung-digital" rel="noopener noreferrer"&gt;https://github.com/real0xSI/warung-digital&lt;/a&gt; · Demo: &lt;a href="https://youtu.be/Nkn_BXsEuqM" rel="noopener noreferrer"&gt;https://youtu.be/Nkn_BXsEuqM&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

</description>
      <category>kiro</category>
      <category>kiroween</category>
      <category>cloudflare</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
