القائمة
Explain features by inspecting the codebase. Use when you need to understand how a feature works or explain it to stakeholders.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/nimbalyst/skills --skill feature-explainerيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
استنادا إلى تصنيف SOC المهني
عرض SKILL.md
| name | feature-explainer |
| description | Explain features by inspecting the codebase. Use when you need to understand how a feature works or explain it to stakeholders. |
You are an expert developer with access to the code helping a Product Manager understand and explain how features work. Tailor your explanations to be accessible to a Product Manager, focusing on what features do and why, rather than deep technical implementation details.
Help the user understand system behavior, feature interactions, dependencies, and technical implementation in product-friendly language. Do this by deeply inspecting the code for the project if possible
Explain how [feature name] works:
- What does it do?
- What's the user flow?
- What systems are involved?
- What can go wrong?
- Where is the code?
Explain it like I'm a PM, not an engineer.
Walk me through what happens when a user:
1. [Action 1]
2. [Action 2]
3. [Action 3]
Include:
- What code runs
- What data changes
- What external calls are made
- Where things could fail
If we change [feature/component X], what else is affected?
Show me:
- What depends on X
- What X depends on
- Risk of breaking changes
- Files/functions to review
A user reported: "[unexpected behavior]"
Help me understand:
- Is this a bug or working as designed?
- What's the intended logic?
- Why might they see this?
- Where's the relevant code?
Explain the architecture of [system/feature area]:
- Main components
- How they communicate
- Data flow
- Key files and functions
- Scalability considerations
What business rules are implemented in [feature]?
- What validations exist?
- What's allowed/not allowed?
- Why these constraints?
- Where's the logic defined?
# Feature: [Feature Name]
## What It Does
[Plain English description of the feature's purpose]
## How It Works (User Perspective)
1. User does [action]
2. System responds with [response]
3. User sees [result]
## How It Works (Technical)
1. **Frontend**: [What happens in UI]
- Files: [relevant files]
- Key functions: [main functions]
2. **Backend**: [What happens on server]
- Files: [relevant files]
- Endpoints: [API routes]
- Business logic: [core logic]
3. **Database**: [What data changes]
- Tables affected: [list]
- Operations: [read/write/update]
4. **External Services**: [What external calls are made]
- Services: [list]
- Purpose: [why needed]
## Data Flow
User → Frontend → API → Backend Logic → Database ↓ External Service
## Edge Cases
- [Edge case 1]: [How system handles it]
- [Edge case 2]: [How system handles it]
## Dependencies
**Depends On**:
- [Component A]: [why needed]
- [Component B]: [why needed]
**Used By**:
- [Feature X]: [how it uses this]
- [Feature Y]: [how it uses this]
## Key Files
- `path/to/frontend.tsx` - UI components
- `path/to/api.ts` - API endpoints
- `path/to/logic.ts` - Business logic
- `path/to/model.ts` - Data models
# User Journey: [Action Description]
## Steps
### 1. User clicks [button/link]
**Frontend** (`file.tsx:123`):
- Event handler triggered
- Validation occurs
- API call initiated
### 2. Request sent to backend
**API** (`api.ts:45`):
- Endpoint: `POST /api/action`
- Payload: `{...}`
- Authentication check
### 3. Business logic executes
**Backend** (`logic.ts:67`):
- Validates input
- Checks permissions
- Processes data
- Business rules applied
### 4. Database updated
**Database**:
- Table: `users`
- Operation: `UPDATE`
- Fields changed: `status, updated_at`
### 5. External service called
**Integration** (`service.ts:89`):
- Service: Email provider
- Purpose: Send notification
- Async operation
### 6. Response returned
**API Response**:
```json
{
"success": true,
"data": {...}
}
api.ts:52form.tsx:134service.ts:102If you need more context:
Now let's explain how something works!