developing-software

Developing Software

Read this file completely once per task before the first create_project call. Do not reread it during the same task unless the instructions change. Read a reference below with read_skill({ skill: "developing-software", file: "<filename>" }); do not use the generic project/workspace file tools for skill files.

Workflow

1. Choose the template for the dominant user experience.
2. Create the project with a concise description and an explicit template.
3. Inspect the seeded files before editing. Treat the scaffold as working architecture, not disposable sample code.
4. Reshape the starter into the requested product. Rename the example entity, schema, routes, actions, validation, and UI copy consistently instead of adding a second implementation beside the demo.
5. In React Router projects, add standard UI through add_shadcn_component; do not hand-write components or page shells that the bundled registry provides. In vanilla projects, work directly in public/.
6. Use deploy_project directly to build, publish, return the live URL, and open the app in preview. No manual set_preview or list_apps call is needed afterward; set_preview remains available when you explicitly want to reopen or switch previews. Pass dry_run: true only when the user explicitly wants validation without publishing.
7. Treat a successful deploy as sufficient completion evidence for routine build-and-ship requests. Do not automatically launch env.BROWSER or capture screenshots after every deploy. Use browser or visual verification only when the user asks for it, the task is specifically diagnosing a deployed UI/runtime issue, or the task explicitly requires browser evidence.

Use camelAI project tools for scaffolding, dependencies, builds, and deploys. Do not run create-worker, wrangler init, npm create cloudflare, package-manager deploy commands, or shell-based scaffolding.

Template Selection