القائمة
Use when executing substantial coding tasks to maintain planning discipline, quality checks, and risk-aware delivery without blocking straightforward requests.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when designing, reviewing, or modifying backend API endpoints, schemas, validation, and API documentation.
Use when reviewing architecture boundaries, dependency direction, or multi-layer design decisions across modules.
Use when shaping new features or behavior changes that need requirements clarification and option tradeoff exploration before implementation.
Use when React components are too large or complex and need extraction, simplification, or separation of concerns.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Use when modeling domain concepts, aggregates, and bounded contexts or checking DDD alignment in existing code.
| name | core-project-rules |
| description | Use when executing substantial coding tasks to maintain planning discipline, quality checks, and risk-aware delivery without blocking straightforward requests. |
These rules define the fundamental interaction patterns and quality standards for this project.
Before writing substantial code, describe your approach and ask for approval if scope or requirements are ambiguous/high-risk.
project/plans/YYYY-MM-DD-<topic>.md for non-trivial changes.Prefer manageable, reviewable changesets; split work when it becomes hard to reason about.
After writing code, list what could break and suggest tests to cover it.
When there’s a bug, start by writing a test that reproduces it, then fix it until the test passes.
Capture repeated feedback patterns as improvements to this ruleset.