ai-dynamo
- 27 skills
- 0 followers
- 1 week ago last updated
- ▌ Dynamo Clone Hotpath Audit · ai-dynamo-dynamo bundleAudit Dynamo Rust hot-path `.clone()` calls, explain which clones are removable and why, and only apply clone-removal patches when explicitly requested.
- ▌ Perform Adversarial Review · ai-dynamo-dynamoAdversarially reviews an evidence-backed Dynamo optimization proposal and DGD draft for comparability, duplication, attribution, correctness, feasibility, and worthwhile GPU spend. Use after hypothesis-generator writes knowledge-consult.md and deploy-draft.yaml and before recipe-deployer creates the next deployment iteration.
- ▌ Create Optimization Hypothesis · ai-dynamo-dynamoMaterializes one evidence-backed proposal from a flexible knowledge-consult.md into a challenger-ready deploy-draft.yaml by applying only its selected DGD change to the current successful manifest. Use after consult-perf-knowledge writes a proposed consultation in the current deployment iteration's next-candidate directory.
- ▌ Repo Codeowners · ai-dynamo-dynamoWorks with Dynamo's generated CODEOWNERS - finds out who reviews a change, fixes a failing codeowners CI check, changes review routing, or grants an external contributor area-scoped ownership. Use when the codeowners check fails on a PR, a new directory is unclaimed, someone asks who reviews a path or PR, review routing needs to change, or a contributor should be added as a code owner.
- ▌ Graham Code Review · ai-dynamo-dynamoReviews code changes in the style of Graham King's ai-dynamo/dynamo reviews — exacting Rust and systems-level standards covering error handling, tracing discipline, unnecessary clones, async and concurrency correctness, log levels, and minimal diff surface. Use when reviewing Rust changes, code under lib/ or components/src/dynamo, or any performance-critical or networking path that needs a strict senior-engineer review.
- ▌ Author Baseline Dgd · ai-dynamo-dynamoDrafts a candidate baseline DynamoGraphDeployment from interview requirements when no catalog recipe matches the user's model, hardware, and backend, presenting per-decision evidence for the user's confirmation. Use only from user-interviewer at interview time, at rung 3 of the baseline-source ladder, and never to deploy or to replace a baseline the user already provided.
- ▌ Troubleshoot Dynamo · ai-dynamo-dynamo bundleDiagnose failed or unhealthy Dynamo deployments. Use when pods, model-cache jobs, PVCs, workers, frontend/router health, endpoints, or benchmark jobs fail; use deploy-dynamo-recipe or dynamo-router-starter before this for normal bring-up.
- ▌ Deploy Dynamo Recipe · ai-dynamo-dynamoDeploys one assigned DynamoGraphDeployment and proves it with an OpenAI-compatible smoke test. Use when user-interviewer has captured the user-provided baseline DGD or hypothesis-challenger has approved a later DGD.
- ▌ Dynamo Agent Harness · ai-dynamo-dynamo bundleDrives persistent Claude Code, Codex, or OpenCode agent sessions through a Dynamo OpenAI/Anthropic-compatible endpoint over Agent Client Protocol (ACP). Use when an agent must delegate a bounded task to another coding-agent harness running a model served by Dynamo, continue that harness across multiple turns, exercise tool calls, or validate agent request traces.
- ▌ Run Aiperf Benchmark · ai-dynamo-dynamoLaunches, monitors, debugs, and collects one run-scoped AIPerf Kubernetes benchmark without changing its workload semantics. Use after perf.yaml and aiperf-config.yaml have been configured for a smoke-tested Dynamo deployment.
- ▌ Dynamo Router Starter · ai-dynamo-dynamo bundleStart or patch Dynamo router modes and run router endpoint smoke checks. Use for round-robin, KV-aware, least-loaded, or device-aware routing setup; use deploy-dynamo-recipe for recipe deployment and troubleshoot-dynamo for failure diagnosis.
- ▌ Analyze Aiperf Results · ai-dynamo-dynamoValidates and normalizes raw AIPerf outputs, then evaluates valid results against target SLOs and comparable prior candidates. Use after an AIPerf Job completes to produce benchmark audit, summary, and performance analysis artifacts.
- ▌ Consult Perf Knowledge · ai-dynamo-dynamoConsults the repository performance rules and applicable Dynamo and engine guides to select one evidence-backed optimization proposal, then writes the generator's knowledge-consult.md reasoning record. Use after perf-analyzer completes a valid AIPerf analysis and before create-optimization-hypothesis materializes a DGD draft.
- ▌ Dynamo Kv Replay Parity · ai-dynamo-dynamo bundleRuns deterministic byte-parity and paired performance campaigns for Dynamo offline KV-aware replay across native-G1 vLLM and SGLang configurations, including forced scheduler-pressure and disaggregated handoff lifecycles. It is used when validating replay refactors, routing changes, scheduler-event changes, or performance-sensitive offline simulation changes against a baseline revision.
- ▌ Synthesize User Workload · ai-dynamo-dynamo bundleSynthesizes a canonical user_workload.yaml and captures the user's immutable DynamoGraphDeployment from an optimization user's initial request, attachments, and minimal follow-up interview. Use as the first skill in a new Dynamo recipe optimization run, or to validate supplied workload and DGD inputs before deployment or benchmarking.
- ▌ Dynamo Frontend Benchmark · ai-dynamo-dynamo bundleBenchmark and profile the Dynamo frontend (dynamo.frontend HTTP + tokenizer + KV router) against mock workers (dynamo.mocker). Use when measuring frontend throughput/latency, A/B-testing a frontend change, or on-CPU/off-CPU profiling the frontend or mock workers to find bottlenecks. Covers topology setup, CPU isolation, aiperf load generation, perf/BPF profiling, throughput analysis, and the sharp edges of this setup.
- ▌ Dynamo Interconnect Check · ai-dynamo-dynamo bundleValidate that a Dynamo deployment's NIXL/UCX/NCCL interconnect is ready for disaggregated serving over RDMA/NVLink. Use after deploy-dynamo-recipe brings a deployment up (especially disagg/multi-node) to confirm the KV transport is correct; use troubleshoot-dynamo for diagnosing already-failed pods.
- ▌ Configure Aiperf Benchmark · ai-dynamo-dynamoSelects and freezes a question-driven AIPerf workload, objective, load policy, and Kubernetes execution manifest for a successfully deployed Dynamo candidate. Use when a candidate needs performance characterization or a comparable measurement against a reference.
- ▌ Dep Create · ai-dynamo-dynamoCreates or updates Dynamo Enhancement Proposals as GitHub issues, including lightweight DEPs, implementation plans, and retroactive DEPs for ai-dynamo/dynamo. Use when proposing a feature or architecture change, drafting an implementation plan, or filing a retroactive DEP.
- ▌ Dep Status · ai-dynamo-dynamoChecks Dynamo Enhancement Proposal issue status, lists DEPs by lifecycle state or area, and finds related DEP issues in ai-dynamo/dynamo. Use when asking where a DEP stands or which DEPs exist for an area.
- ▌ Dep Update · ai-dynamo-dynamoUpdates Dynamo Enhancement Proposal lifecycle state in GitHub, including triage, PIC assignment, review, approval, and status label changes. Use when triaging a new DEP, assigning a PIC, or moving a proposal through review and approval.
- ▌ Pr Monitor · ai-dynamo-dynamoRuns a CI health check on an ai-dynamo/dynamo pull request — report check status, explain why full CI has or has not triggered, root-cause failed job logs, cross-reference failures against main to separate PR-caused regressions from pre-existing flakes, and flag unexpected skips. Use when asked whether a PR's CI is healthy, why checks are failing or missing, or whether a failure is a flake.
- ▌ Dynamo Docs · ai-dynamo-dynamoAdds, updates, moves, or removes content on the Dynamo Fern docs site — standard docs pages, catalog-driven recipe and feature-benchmark pages, examples, recipes, and translations — keeping everything in line with the documentation style guide. Use for any change under docs/, recipes/, or examples/ (new page, edit, tab or section move, rename, removal, recipe/benchmark page, .zh-CN translation, version cut), when deciding which docs tab a page belongs in (Kubernetes Guide vs CLI Guide vs Reference vs Use Cases), and whenever content needs its frontmatter, headings, links, callouts, or terminology fixed.
- ▌ Debug Session · ai-dynamo-dynamoSets up a structured debugging session for a Dynamo bug — pull the report from a Linear ticket, GitHub issue, or pasted text, capture the environment, create a persistent worklog markdown file, and walk through rebuild, reproduction, and investigation steps. Use when starting to investigate a reported Dynamo bug or regression and the investigation should be tracked in a worklog.
- ▌ Visual Review · ai-dynamo-dynamo bundleCreate self-contained interactive HTML code-review dashboards from GitHub or GitLab pull requests, checked-out branch diffs, or supplied unified diffs, with correctness and safe-to-merge scores, smell indicators, interactive component and finding diagrams, structured finding packages, per-finding diff tabs with important references, expandable full context, API manifests, annotated red/green diffs, minimaps, validation cases, and fix prompts. Use when Codex is asked for a visual PR review or any of those visual review artifacts.
- ▌ Fern Components · ai-dynamo-dynamo bundleKnowledge of Fern's built-in MDX component library (accordions, callouts, cards, steps, tabs, code blocks, API-reference snippets, and more) for authoring docs pages. Use when writing or editing a Fern `.mdx` page and deciding whether a component would present content better than plain Markdown, when a user asks "what Fern components exist" or "how do I use `<X>`", or when reviewing a page for missed opportunities to use a component. Complements dynamo-docs (which owns page placement, nav, frontmatter, and the style guide).
- ▌ Fern Navigation · ai-dynamo-dynamo bundleKnowledge of Fern's site-level navigation and structure configuration — how a docs site is organized in `docs.yml` (and product/version `.yml` files) using sections, pages, folders, tabs, tab variants, versions, products, changelogs, and site-level settings, plus per-page frontmatter. Use when designing or changing the shape of a Fern docs site (adding a tab, splitting into products, cutting a version, restructuring the sidebar, moving the changelog, tuning the navbar/layout/theme) or when a user asks "what options does Fern give me for navigation" or "how do I configure X in docs.yml". Complements fern-components (in-page MDX components) and dynamo-docs (this repo's page placement, style guide, and .md/.mdx rules).