Tutorial

Build your first poppy — with your AI agent

This is the honest secret of the platform: you don't hand-write a poppy, you direct one into existence. The SDK, the build guide (AGENTS.md), and the example are written for AI coding agents. You describe what to build; your agent does the rest inside the guardrails. Founders here ship 3–4 polished poppies a week this way.

What this tutorial covers

Six steps take you from an empty folder to a byte-reproducible zip that a reviewer can accept — with the exact commands, the rules review actually enforces, and the mistakes that get submissions rejected.

  1. Start from the example

    Naming, your reverse-DNS id, and the one required use of the brand.

  2. Hand your agent the starter prompt

    The copy-paste prompt that points your coding agent at the build guide, the SDK, and the non-negotiable rules.

  3. Declare access like your rating depends on it

    How permissionSet becomes the green / amber / red the user sees.

  4. Validate and install

    The dev loop, and reading your own approval screen.

  5. Prove it leaves no trace

    Certification: tear-down with the safety net off.

  6. Pack it

    A reproducible zip, its hash, and a ready-to-paste catalogue entry.

// free developer account

Read the rest with a developer account

The six build steps, the exact commands, and the rules review enforces are behind a free account. It takes an email and about twenty seconds, and the same account is where you submit your poppy when it's ready.

  • The full six-step build — commands you can paste, in order
  • The starter prompt for your AI coding agent
  • What review checks, including the defects that get submissions rejected
  • Your dashboard — submit a poppy, track review, publish updates, set pricing

No card, ever — an account is free and stays free. Listing a poppy is free too; the platform only takes a cut if you sell through its checkout. Signing up means accepting the Developer Agreement.