القائمة
Write clear, atomic commits using Conventional Commits. Use when committing changes, writing or rewriting a commit message, or splitting work into reviewable commits.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Optimize React/Next.js runtime performance — eliminate waterfalls, shrink bundles, cut unnecessary re-renders, and speed up rendering. Use when writing, reviewing, or refactoring components for speed, or chasing slow renders, large bundles, janky interactions, or high TTFB/LCP/INP.
Build agent-friendly web apps with the W3C Web Model Context API (WebMCP). Use when exposing frontend features as structured tools for in-browser AI agents, adding document.modelContext tools to React/Next.js apps, designing tool schemas for dashboards or admin UIs, or making existing UI automatable without DOM scraping.
Write clear, fast, deterministic Go tests including mandatory repo integration tests (x/testkit) and app unit tests. Use when adding or fixing Go tests, implementing internal/repo or internal/app, designing table-driven tests, writing benchmarks, using testify, or improving coverage in this workspace.
Design distinctive, production-grade frontend interfaces that don't read as templated AI defaults. Use when bootstrapping a frontend app, building or restyling a landing page, marketing site, hero, brand-forward product surface, or any UI where visual identity matters — choosing palette, typography, layout, motion, and copy. Required before running create-next-app or writing UI.
Review code (your own or others') for correctness, design, and risk before it merges. Use when reviewing a diff or pull request, doing a self-review before opening a PR, or giving structured, prioritized feedback.
Architect a scalable, themeable design-token system — primitive → semantic → component layers, CSS variables, a 4px spacing/type scale, and dark mode. Use when setting up or refactoring a project's tokens, naming color/spacing/radius values, wiring tokens into Tailwind/shadcn, enabling theme switching, or killing hard-coded hex/px scattered through components.
| name | conventional-commits |
| description | Write clear, atomic commits using Conventional Commits. Use when committing changes, writing or rewriting a commit message, or splitting work into reviewable commits. |
Commits are a changelog and a debugging tool. Keep them atomic and describe the why, using the Conventional Commits format.
<type>(<optional scope>): <subject>
<optional body — the why, not the what>
<optional footer — BREAKING CHANGE:, refs #123>
! after type/scope (feat!:) or a BREAKING CHANGE: footer.| Type | Use |
|---|---|
feat | New user-facing feature |
fix | Bug fix |
refactor | Code change with no behavior change |
perf | Performance improvement |
docs | Documentation only |
test | Adding or fixing tests |
build | Build system or dependencies |
ci | CI configuration |
chore | Maintenance, tooling, housekeeping |
style | Formatting only (no logic change) |
feat(auth): add refresh-token rotation
Rotate refresh tokens on every use so a leaked token is valid for at
most one request. Old tokens are revoked atomically.
refs #482
fix(parser): handle empty input without panicking