dreamboard 0.1.21 → 0.1.22

package/skills/dreamboard/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: dreamboard
-description: Guides development of multiplayer, rule-enforced, turn-based games on the Dreamboard.games platform. Use this skill when building a new Dreamboard game, implementing game logic with the reducer pattern, writing game rules or manifest, using the Dreamboard CLI, or iterating on game UI and tests.
+description: Create multiplayer, rule-enforced, turn-based game on Dreamboard.games platform.
 metadata:
   short-description: Dreamboard Game Development Workflow
   tags: [dreamboard, cli, game-dev, board-game, turn-based, multiplayer]
@@ -17,91 +17,51 @@ compile, run, and test against the current reducer-native scaffold.
 
 - Dreamboard CLI installed and available as `dreamboard`
   Install with `npm install -g dreamboard`
-- Authenticated via `dreamboard auth status` or log in via `dreamboard login`
+- Authenticated via `dreamboard login`
 
-## New game workflow
-
-Copy this checklist and track your progress:
-
-```
-New Game Development Progress:
-- [ ] Step 1: Author rule.md
-- [ ] Step 2: Author manifest.ts to define game topology
-- [ ] Step 3: Run `dreamboard sync` to update generated type-safe contracts
-- [ ] Step 4: Implement reducer contract, phases, interactions, and views in `app/`
-- [ ] Step 5: Keep reducer files organized by ownership: `game-contract.ts` for schemas, `game.ts` for assembly, phase `index.ts` files for `definePhase` registration, and concept files for reducer bodies
-- [ ] Step 6: Run `dreamboard compile` and fix any type errors
-- [ ] Step 7: Write bases and scenarios in `test/`, then run `dreamboard test generate` and `dreamboard test run`
-- [ ] Step 8: Implement the playable UI in `ui/App.tsx` — start from generated `PromptInbox`, `Interaction`, and `Zone` primitives before writing custom runtime plumbing (see [references/ui-architecture.md](references/ui-architecture.md))
-- [ ] Step 9: Verify end-to-end with `dreamboard dev`
-```
-
-For the end-to-end authoring loop, start with [references/quickstart.md](references/quickstart.md) and [references/authoring-lifecycle.md](references/authoring-lifecycle.md).
+## Buliding Your First Game
+See [tutorials/building-your-first-game.md](references/building-your-first-game.md)
 
 ## References
 
 - Quickstart:
   [references/quickstart.md](references/quickstart.md)
-- Workspace layout:
-  [references/workspace-layout.md](references/workspace-layout.md)
-- Core concepts:
-  [references/core-concepts.md](references/core-concepts.md)
+- Tutorial:
+  [references/building-your-first-game.md](references/building-your-first-game.md)
 - CLI:
   [references/cli.md](references/cli.md)
 - Rules:
   [references/rule-authoring.md](references/rule-authoring.md)
 - Manifest:
-  [references/manifest.md](references/manifest.md),
-  [references/manifest-fields.md](references/manifest-fields.md)
-- Reducer authoring:
-  [references/game-contract.md](references/game-contract.md),
-  [references/game-definition.md](references/game-definition.md),
-  [references/phases.md](references/phases.md),
-  [references/interactions.md](references/interactions.md),
-  [references/card-actions.md](references/card-actions.md),
-  [references/effects.md](references/effects.md),
-  [references/views.md](references/views.md)
-- Tiled Boards:
-  [references/board-topology.md](references/board-topology.md)
-- UI:
-  [references/ui-architecture.md](references/ui-architecture.md),
-  [references/game-shell.md](references/game-shell.md),
-  [references/board-surfaces.md](references/board-surfaces.md),
-  [references/hand-surfaces.md](references/hand-surfaces.md),
-  [references/prompts-and-choices.md](references/prompts-and-choices.md),
-  [references/custom-renderers.md](references/custom-renderers.md),
-  [references/ui-components.md](references/ui-components.md)
+  [references/manifest-authoring.md](references/manifest-authoring.md)
+- Reducer:
+  [references/reducer.md](references/reducer.md)
+- Game interface:
+  [references/game-interface.md](references/game-interface.md)
 - Testing:
-  [references/testing.md](references/testing.md),
-  [references/testing-bases.md](references/testing-bases.md),
-  [references/testing-scenarios.md](references/testing-scenarios.md),
-  [references/testing-runtime-assertions.md](references/testing-runtime-assertions.md),
-  [references/testing-ui-tests.md](references/testing-ui-tests.md),
-  [references/testing-generated-contracts.md](references/testing-generated-contracts.md)
+  [references/testing.md](references/testing.md)
 
 ## Current Scaffold
 
-A fresh `dreamboard new` workspace contains:
+The current scaffold centers on these files:
 
 - authored source:
-  `rule.md`, `manifest.ts`
+  `rule.md`, `manifest.json`
 - reducer:
-  `app/game-contract.ts`, `app/game.ts`, `app/phases/setup.ts`,
-  `app/setup-profiles.ts`, `app/reducer-support.ts`, `app/README.md`
+  `app/game-contract.ts`, `app/game.ts`, `app/phases/*.ts`,
+  `app/setup-profiles.ts`
 - UI:
-  `ui/App.tsx`, usually built from generated `@dreamboard/ui-contract` primitives plus generic components from `@dreamboard/ui-sdk`
+  `ui/App.tsx`
 - tests:
-  `test/bases/initial-turn.base.ts`, `test/testing-types.ts`
-  _(scenarios are not scaffolded — create them in `test/scenarios/`)_
-- generated (do not edit):
-  `shared/manifest-contract.ts`, `shared/generated/ui-contract.ts`
+  `test/bases/*.base.ts`, `test/scenarios/*.scenario.ts`,
+  `test/testing-types.ts`
 
 ## Command Flow
 
 Use the commands for different kinds of state:
 
 - `dreamboard sync`
-  Upload local authored changes and advance the remote authored head. Run this after editing `rule.md`, `manifest.ts`, or authored source files that should be part of the next remote build. Re-running `sync` against the same authored content is safe; Dreamboard reuses already-uploaded source blobs and still refreshes framework-owned generated files. When `package.json` changes, `sync` also prepares workspace dependencies automatically.
+  Upload local authored changes and advance the remote authored head. Run this after editing `rule.md`, `manifest.json`, or authored source files that should be part of the next remote build.
 - `dreamboard compile`
   Compile the current remote authored head. Run this after `sync`, or re-run it after a failed compile when you have not made new authored edits.
 - `dreamboard pull`
@@ -113,36 +73,43 @@ Quick rule:
 - compile failed but you have not edited files since: `dreamboard compile` again
 - remote authored head moved: `dreamboard pull` first
 
+## Workflow
+
+Use this order by default:
+
+1. Write or revise `rule.md`.
+2. Align `manifest.json` to the rules.
+3. Run `dreamboard sync`.
+4. Implement reducer state, phases, actions, and views in `app/`.
+5. Implement the playable UI in `ui/App.tsx`.
+6. Run `dreamboard compile`.
+7. Generate test artifacts with `dreamboard test generate`.
+8. Run scenarios with `dreamboard test run`.
+9. Validate the local runtime with `dreamboard run`.
+10. For agent-built games, run `dreamboard dev` and verify the browser UI before handoff. Use Playwright to open the dev host, check that the plugin iframe renders without console errors, and click a primary interaction such as selecting a playable hand card. Reducer scenarios alone are not enough when the game has an interactive UI.
+
 ## Guardrails
 
-- `manifest.ts` and `rule.md` are the source of truth for scaffolding.
-- Choose files by ownership before editing: schemas in `app/game-contract.ts`, `defineGame` wiring in `app/game.ts`, player projections in view files, and phase reducers in `app/phases/*`.
-- A single `app/phases/<phase>.ts` is fine while small. Once a phase has multiple action families, shared input helpers, card actions, or is roughly 250-300 lines, move to `app/phases/<phase>/index.ts` plus neighboring concept files such as `build.ts`, `trade.ts`, or `dev-cards.ts`.
-- Keep phase `index.ts` files as assembly: import interactions, register them with `definePhase`, and export the phase plus stable test-facing schemas.
-- Use `kind: "simultaneousPlayer"` for hidden concurrent choices. Declare `actors`, a single `submit` descriptor, and a phase-level `resolve` callback; do not hand-roll sealed choices in `hiddenState` unless the mechanic needs custom behavior outside the SDK barrier.
-- Keep `app/reducer-support.ts` small. Split real game rules into `app/rules/*` modules by domain instead of adding unrelated helpers to one catch-all file.
+- `manifest.json` and `rule.md` are the source of truth for scaffolding.
 - Run `dreamboard sync` after authored changes to keep generated files and the remote authored head in sync.
-- Fresh `app/setup-profiles.ts` placeholders are framework-owned until you customize them. `dreamboard sync` refreshes empty placeholder entries to match manifest profile IDs, then preserves the file once you add real setup logic.
 - `dreamboard pull` reconciles authored divergence into the current workspace.
 - `dreamboard compile` is separate from authored sync; failed compiles do not mean the workspace needs a pull or another sync unless you changed authored files again.
 - Use `dreamboard status` to distinguish authored sync from compile health before deciding whether the next command should be `sync`, `compile`, or `pull`.
-- Re-run `dreamboard test generate` after runtime-shape changes in `manifest.ts` or `app/`.
+- Re-run `dreamboard test generate` after runtime-shape changes in `manifest.json` or `app/`.
 - Keep reducer-owned UI data in views; do not reintroduce the old `shared/ui-args.ts` pattern in new scaffolds.
+- When a game exposes clickable hands, markets, boards, or prompts, prove the same interaction works through `dreamboard dev` in a browser. A direct scenario submission can pass even when the rendered surface does not collect the input.
+- For interactive card hands, render generated surfaces such as `handSurface.Hand` and `handSurface.Card` consistently. Do not swap a surface card for a raw `Card` or custom tile based on `me.canAct`; the surface primitive is responsible for disabling unavailable interactions.
 
 ## Editable Surface
 
 Edit:
 
 - `rule.md`
-- `manifest.ts`
+- `manifest.json`
 - `app/game-contract.ts`
 - `app/game.ts`
 - `app/phases/*.ts`
-- `app/phases/*/*.ts`
-- `app/rules/*.ts` (when you split game-domain helpers)
 - `app/setup-profiles.ts`
-- `app/reducer-support.ts`
-- `app/*-view.ts` (view files you create, e.g. `app/player-view.ts`)
 - `ui/App.tsx`
 - `test/bases/*.base.ts`
 - `test/scenarios/*.scenario.ts`
@@ -155,8 +122,7 @@ Do not edit generated or framework-owned files such as:
 - `ui/index.tsx`
 - `test/generated/*`
 
-## Official Documentation
-
+## Offical Documentation
 Visit https://dreamboard.games/docs
 
 ## Framework Feedback

package/LICENSE

@@ -1,89 +0,0 @@
-# PolyForm Shield License 1.0.0
-
-<https://polyformproject.org/licenses/shield/1.0.0>
-
-## Acceptance
-
-In order to get any license under these terms, you must agree to them as both strict obligations and conditions to all your licenses.
-
-## Copyright License
-
-The licensor grants you a copyright license for the software to do everything you might do with the software that would otherwise infringe the licensor's copyright in it for any permitted purpose.  However, you may only distribute the software according to [Distribution License](#distribution-license) and make changes or new works based on the software according to [Changes and New Works License](#changes-and-new-works-license).
-
-## Distribution License
-
-The licensor grants you an additional copyright license to distribute copies of the software.  Your license to distribute covers distributing the software with changes and new works permitted by [Changes and New Works License](#changes-and-new-works-license).
-
-## Notices
-
-You must ensure that anyone who gets a copy of any part of the software from you also gets a copy of these terms or the URL for them above, as well as copies of any plain-text lines beginning with `Required Notice:` that the licensor provided with the software.  For example:
-
-> Required Notice: Copyright Yoyodyne, Inc. (http://example.com)
-
-## Changes and New Works License
-
-The licensor grants you an additional copyright license to make changes and new works based on the software for any permitted purpose.
-
-## Patent License
-
-The licensor grants you a patent license for the software that covers patent claims the licensor can license, or becomes able to license, that you would infringe by using the software.
-
-## Noncompete
-
-Any purpose is a permitted purpose, except for providing any product that competes with the software or any product the licensor or any of its affiliates provides using the software.
-
-## Competition
-
-Goods and services compete even when they provide functionality through different kinds of interfaces or for different technical platforms.  Applications can compete with services, libraries with plugins, frameworks with development tools, and so on, even if they're written in different programming languages or for different computer architectures.  Goods and services compete even when provided free of charge.  If you market a product as a practical substitute for the software or another product, it definitely competes.
-
-## New Products
-
-If you are using the software to provide a product that does not compete, but the licensor or any of its affiliates brings your product into competition by providing a new version of the software or another product using the software, you may continue using versions of the software available under these terms beforehand to provide your competing product, but not any later versions.
-
-## Discontinued Products
-
-You may begin using the software to compete with a product or service that the licensor or any of its affiliates has stopped providing, unless the licensor includes a plain-text line beginning with `Licensor Line of Business:` with the software that mentions that line of business.  For example:
-
-> Licensor Line of Business: YoyodyneCMS Content Management System (http://example.com/cms)
-
-## Sales of Business
-
-If the licensor or any of its affiliates sells a line of business developing the software or using the software to provide a product, the buyer can also enforce [Noncompete](#noncompete) for that product.
-
-## Fair Use
-
-You may have "fair use" rights for the software under the law. These terms do not limit them.
-
-## No Other Rights
-
-These terms do not allow you to sublicense or transfer any of your licenses to anyone else, or prevent the licensor from granting licenses to anyone else.  These terms do not imply any other licenses.
-
-## Patent Defense
-
-If you make any written claim that the software infringes or contributes to infringement of any patent, your patent license for the software granted under these terms ends immediately. If your company makes such a claim, your patent license ends immediately for work on behalf of your company.
-
-## Violations
-
-The first time you are notified in writing that you have violated any of these terms, or done anything with the software not covered by your licenses, your licenses can nonetheless continue if you come into full compliance with these terms, and take practical steps to correct past violations, within 32 days of receiving notice.  Otherwise, all your licenses end immediately.
-
-## No Liability
-
-***As far as the law allows, the software comes as is, without any warranty or condition, and the licensor will not be liable to you for any damages arising out of these terms or the use or nature of the software, under any kind of legal claim.***
-
-## Definitions
-
-The **licensor** is the individual or entity offering these terms, and the **software** is the software the licensor makes available under these terms.
-
-A **product** can be a good or service, or a combination of them.
-
-**You** refers to the individual or entity agreeing to these terms.
-
-**Your company** is any legal entity, sole proprietorship, or other kind of organization that you work for, plus all its affiliates.
-
-**Affiliates** means the other organizations than an organization has control over, is under the control of, or is under common control with.
-
-**Control** means ownership of substantially all the assets of an entity, or the power to direct its management and policies by vote, contract, or otherwise.  Control can be direct or indirect.
-
-**Your licenses** are all the licenses granted to you for the software under these terms.
-
-**Use** means anything you do with the software requiring one of your licenses.

package/NOTICE

@@ -1 +0,0 @@
-Required Notice: Copyright Dreamboard Games.