yolo-labs-hq
- 10 skills
- 0 followers
- 12 hours ago last updated
- ▌ Vitest Runner · yolo-labs-hqRun vitest with the project's own config. Prefer `vitest run path/to/file.test.ts` over watch mode during agent sessions to avoid leaving processes behind. Use `--reporter=basic` for compact output the agent can parse, and `--coverage` only when explicitly asked.
- ▌ MCP Server Debug · yolo-labs-hqDiagnose an MCP server that is failing to register tools or returning errors. Walks through stdio handshake validation, env-var injection, tool-schema introspection, and host-side debugging so you can localize whether the bug is in the server, the transport, or the host's tool routing.
- ▌ Next 15 App Router · yolo-labs-hqPatterns for Next.js 15 App Router projects — server vs. client components, route handlers, dynamic params (now async), revalidation primitives, and metadata. Covers gotchas introduced when upgrading from Next 14, including the params Promise change and async cookies/headers.
- ▌ Code Simplification · yolo-labs-hq bundleSimplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.
- ▌ Yolo Plan Authoring · yolo-labs-hqAuthor a YOLO Work Plan from operator intent. Load when the operator wants to create or author a multi-step Plan, parallelize work across tracks, ship a feature as a Run, structure substrate work into a DAG, build something non-trivial, scaffold a project, or design a DAG. Concrete trigger phrases: "create a plan", "author a plan", "parallelize", "ship X as a Run", "set up a Run for", "design a DAG", "build X" (multi-step), "scaffold Y", "split across tracks", "fan out", "wire up substrate steps". Prefer this skill over tile-by-tile creation whenever the operator's intent spans more than one Step.
- ▌ Code Review And Quality · yolo-labs-hq bundleConducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.
- ▌ Test Driven Development · yolo-labs-hq bundleDrives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.
- ▌ Cloudflare Worker Deploy · yolo-labs-hqDeploy a Cloudflare Worker via wrangler with env-aware secrets. Pick the right wrangler.jsonc env, run wrangler deploy, and verify the deploy with wrangler tail. Covers common errors — missing secret bindings, KV namespace mismatches, route collisions.
- ▌ Debugging And Error Recovery · yolo-labs-hq bundleGuides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing.
- ▌ Git Workflow · yolo-labs-hqCommit, branch, and PR conventions: small commits with conventional messages, branches named with a type/scope prefix, PRs that fit on one screen and pass CI before requesting review. Includes guidance on when to squash, when to rebase, and how to write a useful PR body.