kentcdodds
- 18 skills
- 0 followers
- last month last updated
- ▌ Orchestrate 3 · kentcdoddsOrchestrate sub-agents for large tasks: plan, delegate coding to cheap/fast models, parallelize the critical path, layer reviews, and close every loop without a human relay. Use when acting as an orchestrator or writing a kickoff prompt for one.
- ▌ Ship Pr 4 · kentcdoddsBabysit a PR. Iterate with AI reviewers and CI. Get it ready and maybe merge. Send summary message.
- ▌ Remix 2 · kentcdodds bundleBuild and review Remix 3 applications using the `remix` npm package and subpath imports. Use when working on Remix app structure, routes, controllers, middleware, validation, data access, auth, sessions, file uploads, server setup, UI components, hydration, navigation, or tests.
- ▌ Conduct 2 · kentcdoddsCoordinate a fleet of cloud agents across separate environments for large multi-track programs (migrations, purges, upgrades). The conductor audits, partitions, spawns one agent per track, monitors, and QAs — but implements nothing. Use only when work needs multiple environments; otherwise load orchestrate or implement directly.
- ▌ Ship Pr 3 · kentcdoddsBabysit a PR: iterate with AI reviewers and CI until green, get it ready, optionally squash-merge as Kent and watch the deploy, then send a Discord summary. Medium risk waits for AI reviewer(s) and addresses valid feedback. Use when a pull request needs to be shepherded to done.
- ▌ Orchestrate 2 · kentcdoddsOrchestrate sub-agents for large tasks inside a single environment: plan, delegate coding to cheap/fast models, parallelize the critical path, keep reviews lean, and close every loop. Use when acting as an orchestrator or writing a kickoff for one. Prefer implement when fan-out does not clearly pay. For multi-environment fleets, use conduct instead.
- ▌ Visual Recap 2 · kentcdodds bundleGenerate and maintain the system recap block in a PR description - a GitHub-rendered visual summary of which system primitives a change touches, how risky it is, and what changed. Use when planning a non-trivial change (plan mode), when creating or updating a pull request (recap mode), or when the user asks for a visual recap, visual plan, system review, or PR recap.
- ▌ Ship Pr 2 · kentcdoddsBabysit a PR. Iterate with AI reviewers and CI. Get it ready and maybe merge. Send summary message.
- ▌ Ask Kent · kentcdoddsAsk which kcd-skills flow fits your situation. A router over the skills in this repo. Use when you don't know which Kent skill to run, or which order.
- ▌ Remix · kentcdodds bundleBuild and review Remix 3 applications using the `remix` npm package and subpath imports. Use when working on Remix app structure, routes, controllers, middleware, validation, data access, auth, sessions, file uploads, server setup, UI components, hydration, navigation, or tests.
- ▌ Conduct · kentcdoddsCoordinate a fleet of cloud agents across separate environments for large multi-track programs (migrations, purges, upgrades). The conductor audits, partitions, spawns one agent per track, monitors, and QAs — but implements nothing. Use only when work needs multiple environments; otherwise load orchestrate or implement directly.
- ▌ Ship Pr · kentcdoddsBabysit a PR: iterate with AI reviewers and CI until green, get it ready, optionally squash-merge as Kody and watch the deploy, then send a Discord summary. Medium risk waits for AI reviewer(s) and addresses valid feedback. Use when a pull request needs to be shepherded to done.
- ▌ Orchestrate · kentcdoddsOrchestrate sub-agents for large tasks inside a single environment: plan, delegate coding to cheap/fast models, parallelize the critical path, keep reviews lean, and close every loop. Use when acting as an orchestrator or writing a kickoff for one. Prefer implement when fan-out does not clearly pay. For multi-environment fleets, use conduct instead.
- ▌ Control Kody · kentcdodds bundleDrive and verify the Kody app with a Feature Map and one CLI. Use when changing UI, account routes, preview deploys, or proving a Cloud Agent change with a real origin, session, and /health SHA.
- ▌ Visual Recap · kentcdodds bundleGenerate and maintain the system recap block in a PR description - a GitHub-rendered visual summary of which system primitives a change touches, how risky it is, and what changed. Prefer mermaid sequence diagrams for the change; pick another graph type when it explains the diff better. Use when planning a non-trivial change (plan mode), when creating or updating a pull request (recap mode), or when the user asks for a visual recap, visual plan, system review, or PR recap.
- ▌ Preview Manual Test · kentcdoddsDiscover, wait for, sign in, create specific user data, and assert a PR preview deploy. Use on medium or high risk PRs, after pushing a ready-for-review PR, or when the user asks to test the preview URL.
- ▌ Cleanup After Migrations · kentcdoddsClean up leftover code, schema, shims, dual-writes, compatibility aliases, feature flags, and docs after a migration or similar change. Use when you introduce transitional leftovers, leave a deprecated path, need a soak or follow-up migration before dropping something, or are finishing a migration runbook. Remove the leftover in the same change when it is safe; otherwise open a GitHub issue so it is not forgotten.
- ▌ Testing Multi Worker Dev · kentcdoddsHow to run and test kody's multi-worker local dev (origin kody worker + kody-platform + kody-runtime + kody-jobs secondary configs), including known wrangler multi-config pitfalls (secondary worker env-name suffix, remote AI binding, .env secrets not propagated) and how to verify runtime-worker forwarding.