القائمة
Load when claiming completion requires the repository's actual deterministic build, type, lint, test, diff, smoke, and artifact gates; use diagnose while a failure's root cause is unknown.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Load when a task needs a throwaway prototype, state-model sanity check, UI variant, image-assisted visual mockup, mock interaction, or playable design; do not use for production feature work.
Load when a user describes a Web animation or motion effect without knowing its name and needs the precise term or close alternatives; use only for naming, not design, implementation, or review.
Load when a frontend task needs Apple-platform design guidance or physical, gesture-driven, velocity-aware, interruptible interaction; skip generic visual styling and use review-animations for report-only motion review.
Load when a task needs polished product UI, web pages, landing pages, dashboards, React components, HTML/CSS layouts, or styling; skip routine frontend logic and reports.
Load when a task needs React or Next.js frontend logic, component patterns, state, forms, routing, accessibility, or responsive behavior; use frontend-design for visual direction.
Load when an existing Web product, especially a dashboard, dense-data view, or multi-step app, needs a deep evidence-backed experience review; report findings only, and use design-taste-frontend for marketing-page direction, code-review for source diffs, web-design-guidelines for checklist compliance, or frontend-design for implementation.
| name | verification |
| description | Load when claiming completion requires the repository's actual deterministic build, type, lint, test, diff, smoke, and artifact gates; use diagnose while a failure's root cause is unknown. |
| license | MIT |
Verification is evidence collection, not a generic command recipe or a verdict generator.
Discover the project's actual gates from repository instructions, package/task manifests, CI configuration, existing scripts, and nearby tests. Do not invent commands, coverage thresholds, or required tools. Prefer the same entry points maintainers and CI already use.
Classify checks by the accepted task boundary:
Run independent read-only checks in parallel only when they do not compete for mutable artifacts.
For every applicable gate, record:
Report a required gate that cannot run as unavailable or unknown, with the missing dependency or access. Do not translate absence of evidence into a pass.
Deterministic failures cannot be waived by Agent judgment. If the root cause is unclear, use diagnose; if a confirmed code behavior needs a test-led fix, use tdd. Re-run affected gates after any mutation.
Inspect produced artifacts when correctness depends on rendering, packaging, generated files, migrations, or browser behavior. A successful command is not evidence that the artifact itself is usable.
Before completion, review current Git status and diff for:
Return the smallest truthful verification table:
| Gate | Evidence | Result |
|---|---|---|
| Project-defined check | Exact command/procedure and scope | pass / fail / unavailable or unknown |
State residual risk and the highest-signal next action. Do not commit, push, publish, merge, or modify remote state merely because verification passed.
