Build with AI agents

If you are writing app code:
  read with useBitfieldData(...)
  request work with sendRequestToBitfieldTarget(...)

If you are declaring package material:
  edit things-to-store-and-run.json
  keep files inside the package
  expose stable data names and action names

Use only the public Runtime Kit surface.

App code may import:
- sendRequestToBitfieldTarget from @bitfield/runtime-kit
- useBitfieldData from @bitfield/runtime-kit/react

App code must not import unpublished Runtime Kit code, parse things-to-store-and-run.json,
construct storage addresses, choose low-level readers, or call the implementation for
an action directly.

Package work belongs in things-to-store-and-run.json.
React work reads named data or sends action requests.
If a feature needs new data, add it to things-to-store-and-run.json first.
If a feature needs work to run, declare a stable action name and call that action.

Add a welcome panel that reads the data name "welcome-copy"
with useBitfieldData(...). Render loading, error, empty, and success states.
Do not import unpublished Runtime Kit code.

Add a record for welcome copy in things-to-store-and-run.json. Keep the address stable,
use one payload action, and do not put secrets in the package.

Add a button that calls the action "welcome.suggest" with a JSON payload.
Decode the reply bytes as JSON only because this action's reply shape says it
returns JSON.

Build the first Runtime Kit feature for a launch screen.

Create or update one package file:
- package set: launch-starter
- package: launch-product
- package file: things-to-store-and-run.json
- record: package::launch-product::welcome-copy
- action: launch.next-step

Create one React screen:
- read data name "welcome-copy" with useBitfieldData(...)
- render loading, error, empty, and success states
- add one button that calls sendRequestToBitfieldTarget(...)
- decode reply bytes only according to the reply shape below

Public action shape:
- action: launch.next-step
- request payload: { topic: string }
- reply payload: { suggestion: string }

Before editing, list the files you will touch and the product job each file owns.
After editing, report package set, package, package file, data names, action names, payloads, replies, screens, and verification.

Add a React screen that reads the data name "launch-checklist".

Use only:
- useBitfieldData from @bitfield/runtime-kit/react

The component must render:
- loading
- error
- empty
- success

Do not parse things-to-store-and-run.json.
Do not construct storage addresses.
Do not import package files.

Add a user action that calls "help.search".

Use only:
- sendRequestToBitfieldTarget from @bitfield/runtime-kit

Request payload:
- { query: string }

Reply payload:
- { results: { title: string; url: string }[] }

Support cancellation if the query changes before the previous request finishes.
Do not import the implementation for "help.search".
Do not assume every action returns JSON unless this reply shape says it does.

Create things-to-store-and-run.json for package "help-package".

Package file:
- things-to-store-and-run.json

Things:
- one stored_bytes file named "help/getting-started.txt"
- one slot action named "help.search"

Rules:
- keep every package file path inside the package folder
- use exactly one payload action for each record
- do not include secrets
- keep action names stable and product-facing

Add a screen placement named "launch.help".

Descriptor:
- id: launch.help
- label: Help
- region: panel
- componentKey: surface.launch.help
- preparedInputs: []
- targets: [help.search]

Shell rule:
- the shell renders descriptor labels, order, active id, region, and componentKey
- the shell must not branch on "help" or import HelpSearch directly

Screen body rule:
- the body may call help.search through sendRequestToBitfieldTarget(...)
- the body must not import the implementation for help.search

Debug this Runtime Kit feature by walking the public chain.

Return this table:
- package set
- package
- package file exists?
- data names
- action names
- request payload shape
- reply payload shape
- screen states rendered
- exact failed link: package file, data read, action request, reply decoding, local state, or activation
- fix
- verification

Do not fix by importing unpublished Runtime Kit code.
Do not fix by editing local state by hand.

const packageFile = await fetch('/packages/help-package/things-to-store-and-run.json');
const data = await packageFile.json();

const help = useBitfieldData<HelpCopy>('help-copy');

import { createBitfieldReadScope } from '@bitfield/runtime-kit/internal';

import { useBitfieldData } from '@bitfield/runtime-kit/react';

const welcome = useBitfieldData<WelcomeCopy>('welcome-copy');
return <h2>{welcome.data.headline}</h2>;

const welcome = useBitfieldData<WelcomeCopy>('welcome-copy');

if (welcome.loading) return <p>Loading...</p>;
if (welcome.error) return <p>Could not load welcome copy.</p>;
if (!welcome.data) return <p>No welcome copy yet.</p>;

return <h2>{welcome.data.headline}</h2>;

const data = JSON.parse(new TextDecoder().decode(reply.payload));

type SearchReply = { results: { title: string; url: string }[] };
const data = JSON.parse(new TextDecoder().decode(reply.payload)) as SearchReply;

Open ~/.bitfield and edit the package record until the screen works.

Inspect local state for evidence, then repair `things-to-store-and-run.json`, account activation, or the Runtime Kit feature path that produced the bad state.

Tell me:
1. Which things-to-store-and-run.json file changed.
2. Which data names the UI reads.
3. Which action names the UI calls.
4. Which payload and reply shapes are public.
5. Which unpublished Runtime Kit code you did not import.

App read       -> useBitfieldData(...)
App action     -> sendRequestToBitfieldTarget(...)
Package data   -> things-to-store-and-run.json
Public names    -> data names, action names, payloads, replies
Review failure -> reject unpublished imports and storage wiring in app code

Build a Runtime Kit feature named launch-assistant.

Create one package file with:
- one record named launch-checklist
- one stored file named launch-help
- one action named launch.next-step

Create one React screen with:
- useBitfieldData('launch-checklist')
- a button that calls sendRequestToBitfieldTarget(...)
- loading, error, empty, and success states

Before writing code, list:
- package name
- data names
- action names
- request payload shape
- reply payload shape

Use only @bitfield/runtime-kit and @bitfield/runtime-kit/react.
Do not import unpublished Runtime Kit code.