القائمة
Understand the true intent behind a request before writing any code. Use at the start of every non-trivial task, especially vague ones ("make it better", "add a page", "fix the layout").
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Clean code and structure standards for this repo. Use when writing or refactoring any TypeScript/React code — covers naming, file layout, typing, and testing discipline.
Self-review a change before declaring it finished. Use after implementing any feature or fix, before committing or reporting completion.
Next.js 16 App Router best practices for this repo. Use when creating routes, layouts, data fetching, metadata, or anything touching the Next.js framework surface.
Security rules for all code in this repo. Use when handling any external input, env vars, auth, API routes, server actions, or dependencies.
UI/UX design standards for this stack (Tailwind v4 + shadcn/ui). Use whenever creating or modifying any page, component, layout, or style — the goal is professional, consistent UI with zero AI slop.
| name | impeccable-intent |
| description | Understand the true intent behind a request before writing any code. Use at the start of every non-trivial task, especially vague ones ("make it better", "add a page", "fix the layout"). |
Code written against a misunderstood requirement is worse than no code. Before implementing anything non-trivial, lock the intent.
src/components/ and src/app/ before adding files./dashboard,
without auth — say so if you meant otherwise."A task is done when: the stated goal works end-to-end, npm run lint, npm run type-check, and npm run test pass, and nothing unrelated was changed.