菜单
Create comprehensive project overview documents for major features or projects. Use when starting significant work that needs context documentation for team members or future reference. Provides strategic context, goals, and architectural decisions.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Run the GitHub issue triage tool for Redux repos. This skill should be used when triaging GitHub issues, generating triage reports, or understanding triage output for redux-toolkit, react-redux, reselect, redux, or immer repositories.
Create architecture review documents to understand and document existing codebases. Use when onboarding to an unfamiliar codebase, conducting architecture audits, or creating reference documentation for team members.
Document coding conventions, patterns, and guidelines for an existing codebase. Use when onboarding to a new project to understand its coding style, or when creating style documentation for team reference.
Design patterns for data-dense dashboard UIs with dark themes. Use when building tables, charts, status panels, and data visualization components. Focuses on readability, information density, and consistent design systems.
Create detailed development plans with task lists and progress tracking for major projects. Use for multi-phase work requiring detailed task breakdown, progress tracking, and living documentation of decisions and learnings.
Manage tasks via dex CLI. Use when breaking down complex work, tracking implementation items, or persisting context across sessions.
| name | project-overview |
| description | Create comprehensive project overview documents for major features or projects. Use when starting significant work that needs context documentation for team members or future reference. Provides strategic context, goals, and architectural decisions. |
Create comprehensive project overview documents that provide strategic context and understanding for major projects or features.
Don't use for:
# [Project Name]: Project Overview
**Project Name:** [Short identifier]
**Status:** [Planning / In Progress / Complete]
**Timeline:** [Estimated duration]
**Purpose:** [One-sentence summary]
---
Provide background for someone unfamiliar with the project. Answer:
Length: 3-5 paragraphs
Example:
## Understanding the Context
### What is [System Name]?
[Brief description of the system, its purpose, what it generates/does]
### The [Prototype/Reference Project]
[Describe any reference implementation or prototype that validated the approach]
### Recent Progress
[Key decisions or progress that led to this work]
Define the project scope clearly.
## What is This Project?
### Current State
[Describe what exists today and why it's insufficient]
### Target State
[Describe the desired end state]
### Important Scope Decisions
**In Scope:**
- [What you ARE doing]
**Out of Scope:**
- [What you are NOT doing - be explicit]
Critical: Use blockquotes or callouts for major scope constraints:
> **⚠️ SCOPE:** This focuses exclusively on [X]. We are NOT:
> - [Thing 1]
> - [Thing 2]
Explain the value. Don't assume it's obvious.
Categories:
Length: 2-4 paragraphs or bullet sections
List 3-5 major goals. Be specific and measurable when possible.
## Big Picture Goals
### 1. [Goal Name]
[1-2 sentences describing what success looks like]
### 2. [Goal Name]
[1-2 sentences]
...
High-level phase breakdown. Keep it brief - detailed tasks belong in the development plan.
## Major Phases Overview
### Phase 1: [Name]
**Goal:** [One sentence]
**Key Activities:** [3-5 bullet points of major work items]
### Phase 2: [Name]
...
Length: 1 paragraph per phase (2-3 sentences + bullets)
Document important technical decisions with rationale.
## Key Architectural Decisions
### 1. [Decision Name]
**Decision:** [What was chosen]
**Rationale:** [Why this choice over alternatives]
**Impact:** [What this means for implementation]
### 2. [Decision Name]
...
Include:
Be explicit about what to do and what to avoid.
## Key Constraints and Principles
### Do's
- [Guideline 1]
- [Guideline 2]
### Don'ts
- [Anti-pattern 1]
- [Anti-pattern 2]
### Commands
If relevant, document correct vs incorrect commands:
**Correct:**
- `pnpm typecheck`
**NEVER use:**
- `tsc --noEmit` (won't work with split config)
Define what "done" looks like.
## Success Metrics
### Functional Requirements
- [ ] [Requirement 1]
- [ ] [Requirement 2]
### Quality Indicators
- Code coverage: [target]
- Type safety: [target]
- Performance: [target]
### Validation Metrics
- [How you'll know it works]
Link to other relevant docs and code.
## Related Documentation
### This Project
- [Development Plan](./development-plan.md)
- [Architecture Doc](./architecture.md)
### Reference Implementation
- [Prototype repo/folder]
### Key Code Locations
- Backend: `path/to/code`
- Frontend: `path/to/code`
Identify risks by impact level.
## Risk Assessment
### High Impact Risks
- **[Risk Name]:** [Description] | **Mitigation:** [Strategy]
### Medium Impact Risks
- **[Risk Name]:** [Description] | **Mitigation:** [Strategy]
### Hardest Parts
- [Challenge 1]
- [Challenge 2]
One paragraph wrap-up. Restate the core goal and why it matters.