// Run all code quality skills in sequence — effects, memo, callbacks, state, React Query, and emcn design review
| name | cleanup |
| description | Run all code quality skills in sequence — effects, memo, callbacks, state, React Query, and emcn design review |
Arguments:
User arguments: $ARGUMENTS
Run each of these skills in order on the specified scope, passing through the scope and fix arguments. After each skill completes, move to the next. Do not skip any.
/you-might-not-need-an-effect $ARGUMENTS/you-might-not-need-a-memo $ARGUMENTS/you-might-not-need-a-callback $ARGUMENTS/you-might-not-need-state $ARGUMENTS/react-query-best-practices $ARGUMENTS/emcn-design-review $ARGUMENTSAfter all skills have run, output a summary of what was found and fixed (or proposed) across all six passes.
fetch( calls in hooks, or removing as unknown as X casts, do not introduce // boundary-raw-fetch: <reason> or // double-cast-allowed: <reason> annotations to silence the audit. Fix the underlying call instead — adopt a contract from @/lib/api/contracts/** and use requestJson(contract, ...) from @/lib/api/client/request, or refine the type so the double cast is unnecessary.bun run check:api-validation:strict.Review PRs and diffs for unbounded memory loading, concurrency explosions, oversized payload materialization, and missing pagination or byte caps. Use when reviewing cleanup jobs, background jobs, data imports/exports, file parsing, API fan-out, workflow execution payloads, large arrays/files, or any change that reads many rows, files, responses, logs, or external API pages into process memory.
Audit an existing Sim integration against the service API docs and repository conventions, then report and fix issues across tools, blocks, outputs, OAuth scopes, triggers, and registry entries. Use when validating or repairing a service integration under `apps/sim/tools`, `apps/sim/blocks`, or `apps/sim/triggers`.
Install, upgrade, and operate the Sim Helm chart on Kubernetes. Covers install path selection (inline / existingSecret / External Secrets Operator), required secret generation, the values.yaml mental model (env vs envDefaults vs Secret), and common failure triage. Invoke when a user asks about deploying Sim to a cluster, authoring a Sim values.yaml, debugging a Sim pod that won't start, upgrading a Sim release, or wiring Sim into a secret manager.
Review UI code for alignment with the emcn design system — components, tokens, patterns, and conventions
Commit, push, and open a PR to staging in one shot
Add a complete Sim integration from API docs, covering tools, block, icon, optional triggers, registrations, and integration conventions. Use when introducing a new service under `apps/sim/tools`, `apps/sim/blocks`, and `apps/sim/triggers`.