Skip to content

Scaffolded tile folder structure ​

poe-tiles tiles init creates this layout. Vite builds tile/ into dist/, and dist/ is the bundle that players download.

<name>/
├── tile/                      # Vite root: entry point + backend wiring
│   ├── index.html
│   ├── public/                # copied to the bundle root as is
│   │   ├── assets/            # /assets/hero.png; load with Poe.bundle.loadAsset
│   │   └── deferred/          # optional; large lazy files, uploaded outside the bundle
│   └── src/
│       ├── entry.tsx          # Poe.setupStore(clientConfig); await store.waitForBootstrap(); render UI
│       └── backend.ts         # re-exports tileBackendConfig as default
├── assets/                    # icon.png from init, plus generated images and audio; copy what ships into tile/public/
├── dist/                      # build output: the tile bundle (gitignored)
├── synced-store/              # store contract
│   ├── data/
│   │   └── items.ts           # shared read helpers + table/read ctx types
│   ├── schema.ts
│   ├── mutators/
│   │   ├── index.ts           # compose exported mutator map
│   │   ├── remove-todo.ts
│   │   ├── set-todo.ts
│   │   └── types.ts
│   ├── mutators.test.ts       # colocated unit tests
│   ├── hooks.ts               # deterministic membership hooks, shared by client + backend
│   ├── client-config.ts
│   └── backend-config.ts
├── ui/                        # store-agnostic components
│   ├── App.{tsx,ts}
│   └── App.test.happydom.tsx  # colocated UI tests
├── tests/                     # Happy DOM setup/matchers + optional skipped browser examples
├── scripts/doctor.sh          # toolchain health check
├── client.ts                  # client-safe re-exports
├── package.json
├── tsconfig.json
├── vite.config.ts
└── playwright.config.ts

init creates assets/ with icon.png, an optional starter profile picture; .poe-tile.json has no profilePicture until the creator sets one. Image and audio generation add files to assets/. The creator makes tile/public/ when copying in the first file the tile loads at runtime. See assets.md for where each kind of asset goes and how to load it, and scaffolding-a-new-app.md for creating a tile.