القائمة
Verify claims against real command output before reporting status. Use before saying a task is done, a build passes, tests are green, or a bug is fixed.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Design, build, verify, and publish a curated Claude Code pack — a reusable collection of rules, skills, hooks, loops, and review agents — to GitHub. Trigger this skill whenever the user wants to "create a Claude Code pack", "build a rules/hooks/skills collection", "make a guardrail pack", "package my hooks/skills/agents", "publish a Claude Code config to GitHub", or assemble enforced standards for a stack (e.g. Next.js + Supabase, Django, etc.). This skill is the methodology that produced github.com/m-binimran/dev-pack; reuse it instead of re-deriving the process. Run it BEFORE writing any pack files — it sequences research, clarification, building, verification, and safe publishing.
Audit a web page/component against WCAG 2.2 AA — semantics, keyboard, contrast, labels, focus, alt text. Use when reviewing UI for accessibility or before shipping a page.
Implement web animations with the right engine (Motion, GSAP, Anime.js, React Spring, tailwindcss-motion) and a mandatory prefers-reduced-motion fallback at 60fps. Use when adding any motion to a site.
Design Next.js route handlers and server actions with input validation, correct status codes, error handling, and rate limiting. Use when building an API endpoint, server action, or webhook receiver.
Get Next.js App Router caching right — static vs dynamic rendering, fetch cache, revalidatePath/revalidateTag, and ISR. Use when data is stale, a page won't update, or you're tuning performance vs freshness.
Build a production React component on shadcn/ui + Tailwind — variants, compound pattern, accessible states, and a clean prop API. Use when creating a new UI component or refactoring a messy one.
| name | truthful-reporter |
| description | Verify claims against real command output before reporting status. Use before saying a task is done, a build passes, tests are green, or a bug is fixed. |
Turn "it should work" into "here's proof it works" — or an honest "unverified."
| Claim | Proof required |
|---|---|
| "Tests pass" | Run the test command. Paste pass/fail counts. |
| "It builds" | Run the build. Paste success or the error. |
| "Type-safe" | Run tsc --noEmit / the typecheck. |
| "Bug fixed" | Reproduce the bug, apply fix, show it no longer reproduces. |
| "Query is faster" | EXPLAIN ANALYZE before and after. |
| "Page works" | Load it (browser/preview) and observe, or say it's unverified. |
next build exited 0." or
"2 of 14 tests fail — output below."(The truth-gate and verify-tracker hooks back this up automatically, but this skill is the
discipline you apply yourself.)