القائمة
Use before any implementation to understand the codebase structure, existing patterns, dependency graph, and project conventions.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use for general product implementation work that is not primarily backend architecture, pure integration wiring, or screenshot-driven design-to-code.
Use when backend work requires contract-first thinking, schema changes, permission checks, side-effect analysis, or test planning.
Use immediately after codebase discovery to classify task scale and determine which workflow steps are required vs. optional.
Use when the user provides screenshots, mockups, or design assets and wants implementation that stays visually close to the source.
Use when the main deliverable is maintainable documentation such as repository rules, onboarding guides, runbooks, ADRs, or architecture notes.
Use when encountering compile errors, test failures, runtime exceptions, or unexpected behavior during implementation.
| name | repo-exploration |
| description | Use before any implementation to understand the codebase structure, existing patterns, dependency graph, and project conventions. |
Use this skill to build a mental model of the codebase before making changes.
ARCHITECTURE.md, CONTRIBUTING.md, or equivalent docs if they exist.Read at least one existing file in each layer you will modify and note:
Before cross-file changes:
docs/operating-rules.md → Project-specific constraints section.DECISIONS.md if it exists.After discovery, produce a brief summary:
Modules involved: [list]
Existing patterns: [key observations]
Constraints: [project-specific rules that apply]
Files to read before coding: [list]