القائمة
Run all code quality skills in sequence — effects, memo, callbacks, state, React Query, and emcn design review
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Add a new Sim settings page, or audit existing settings pages for design-system compliance with the shared SettingsPanel layout. Use when creating a settings tab, or when asked to check/clean up settings pages so they match the design system (consistent title, header, search, spacing).
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.
Add or update a Sim knowledge base connector for syncing documents from an external source, including auth mode, config fields, pagination, document mapping, tags, and registry wiring. Use when working in `apps/sim/connectors/{service}/` or adding a new external document source.
Audit an existing Sim knowledge base connector against the service API docs and repository conventions, then report and fix issues in auth, config fields, pagination, document mapping, tags, and registry entries. Use when validating or repairing code in `apps/sim/connectors/{service}/`.
Author or review a Drizzle DB migration for zero-downtime safety — expand/contract phasing, backward-compatibility with the deployed app version, and writing the `-- migration-safe` acknowledgment the check:migrations lint requires. Use when adding/editing files under `packages/db/migrations/` or changing `packages/db/schema.ts`.
Commit, push, and open a PR to staging in one shot — runs the cleanup pass and, when migrations changed, the db-migrate safety review first
| 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.