Documentation / Start building

Build with an agent

Creator Core is organized so a coding agent can understand and extend one connected system. Its instructions, focused skills, source catalog, startup commands, and checks travel with the product.

Your agent is the coding tool you bring. Creator Core does not include an AI chat service or automatically provision your service accounts.

Give the agent the project context

Open the initialized repository in your coding agent. Make sure it reads the root AGENTS.md, then the focused skill for the work. The instructions point to maintained docs and actual source, including the installed Next.js version's local guidance.

Use the relevant guidance for a task; reading every skill is unnecessary. The source and maintained documentation remain authoritative when they disagree with an older example or an agent's remembered framework API.

Describe the product behavior

Give the agent the user outcome, ownership rules, and acceptance criteria. A useful task describes what a person can do and how you will know it works:

Add a personal reading list. Signed-in users can save and remove links, and only the owner can read them. Reuse the existing controls and action feedback. Add a preview of the actual reusable view, test ownership enforcement, and verify the signed-in flow.

This is an example brief, not a feature already included in the kit. The included personal notes provide the existing pattern to inspect.

Follow the connected workflow

1. Inspect the existing route, component catalog, service boundary, and relevant skill.
2. Extend the actual implementation. Keep service hooks and callbacks in the connected component, and use a resolved-data view for previews.
3. Add application data and enforce authorization on the server. A hidden button or selected team is not an access check.
4. Reuse the design tokens, registered controls, and shared loading/motion behavior.
5. Update the real catalog preview and run the required checks.
6. Verify the user's complete flow against the intended services.

Use the existing reference flow

The notes feature connects the whole path:

Hosted sign-in → authenticated Convex connection → validated personal mutation → real action feedback → reactive animated list.

The Notes component supplies hooks and operations to NotesView. Convex notes functions derive the owner from verified identity and enforce that ownership on reads and deletes. useAsyncAction, PendingButton, and MotionList handle interaction behavior. The catalog imports the same view with local preview data.

Use this as a pattern for your product's own records. Team-owned data requires an explicit membership and permission policy; switching teams must not broaden personal-note access.

Make changes verifiable

bun run check:components
bun run check
bun run build:cloudflare

The component check catches missing registration, previews that copy their implementation, production imports of fixtures, and unsupported motion patterns. The complete check also runs lint, TypeScript, and behavioral tests. These checks support review; they do not guarantee that a new feature or another project's credentials are correct.

For service-backed changes, verify the actual signed-in page and data operations. Ask the agent to report what changed, what it verified, and any remaining failure. Keep service secrets in ignored files or secure environment settings.

Keep the system understandable

Update affected docs and skills when changing a shared workflow or public component interface. Keep runtime behavior in the shared package, visual source in the product, and services/schema local. Follow updating when bringing improvements into another product.