Dev Kit

Build from the user's requirements and leave outputs under normal repository ownership. Use the transient CLI for catalog and migration mechanics. Preserve repository conventions and existing authorization; generated repositories keep no Dev Kit runtime dependency or lifecycle manager.

For repository setup, TypeScript tooling, or a Cloudflare Worker API, read .agents/skills/project-setup/SKILL.md. dev-kit setup installs it alongside this entrypoint. For an older installation, add it with bunx @danieljvdm/dev-kit@latest skills add project-setup. Its canonical source is danieljvdm/skills.

Install only the skills relevant to the repository and the linked support needed by those workflows. Keep repository copies self-contained and name their exact paths in required repository workflows, even when a same-named global skill is available. Follow the skill installation guidance to check relative links and preserve local deviations when refreshing copies.

• Remove legacy Dev Kit manifests or managed configuration: legacy ejection.
• Discover, add, update, fork, or detach skills: skills.

Follow installed API documentation and the repository's command, Effect, and testing policies. Verify changed entrypoints with the resulting project's normal commands.