Propose a focused improvement

Open an issue in the public repository describing the problem, expected behavior, and a reproducible example. Link a component preview or source file when useful. Never include service secrets, session tokens, private account data, or licensed vendor source.

For a code contribution, keep the change focused and explain its user-facing result. Maintainers can bring reviewed contributions into the canonical source and publish a verified release.

Follow the existing boundaries

Read the root AGENTS.md and the relevant repository skill. Reuse the actual component source, preserve hosted authentication/payment surfaces, and enforce data access on the server.

For reusable UI, update its implementation and real preview together. Keep gallery data local to the gallery. Update affected docs and skills when a public component interface or workflow changes.

Show how you verified it

Run the checks available in your checkout and include the results:

bun run check
bun run build:cloudflare

Describe browser verification for changed interfaces, including keyboard access, narrow screens, and both themes. Service-backed behavior needs a real service test when applicable; a fixture preview cannot establish that another project's authentication or billing is configured.

Changes to shared runtime behavior require a maintained runtime release. Public source contributions do not directly publish packages or deploy downstream products.

Documentation / Ship & maintain

Contributing

Creator Core is MIT licensed. The public repository contains the clean released template and editable registry source. The maintained canonical source and its publishing credentials remain separate.