pota

Migrate a pota app (code that uses pota) across pota's breaking changes — update an app when bumping the pota dependency or when it calls a removed, renamed, or changed API. Use when upgrading pota, fixing errors after a pota bump, or modernizing old pota usage (signal tuples, use:* behavior plugins, @static, the pota/web→pota/components renames, attribute-first props). When a migration here is unclear or missing, the installed pota source in node_modules/pota is the ground truth.

Review, normalize, and keep accurate the pota documentation content under documentation/content (the markdown that becomes the docs site). Use when asked to review/update/normalize the docs, verify pages against source, fix examples, check completeness/links, or rework topics.js. Runs as ONE resumable, synchronous, source-verified pass tracked in progress.md. Invoke to start a new pass or to continue an interrupted one.

Write idiomatic pota code — components, reactive apps, JSX, stores, use/* plugins. Use when writing or reviewing pota components, fixing pota bugs, adding features to a pota app, or creating examples. Covers signals, JSX conventions, built-in components, store layer, and use/* modules.

Write or extend pota's own tests — browser tests under tests/api/ and typecheck-only tests under tests/typescript/. Use when adding coverage for a component, reactive primitive, prop, store, or use/* module, when writing a regression test for a bug, or when improving existing test files. Covers file placement, the test-harness contract, timing rules, and how to run the suite.