By name: project-structure description: "Analyze and explain project architecture"
Project Structure
Purpose
Analyze and explain project architecture
Routing
- Use when: Use when the user asks to analyze and explain project architecture.
- Do not use when: Do not use when the request is asking for planning documents, high-level strategy, or non-executable discussion; use the relevant planning or design workflow instead.
- Outputs: Outcome from Project Structure: task-specific result plus concrete action notes.
- Success criteria: Returns concrete actions and decisions matching the requested task, with no fabricated tool-side behavior.
Trigger Examples
Positive
- Use the project-structure skill for this request.
- Help me with project structure.
- Use when the user asks to analyze and explain project architecture.
- Project Structure: provide an actionable result.
Negative
- Do not use when the request is asking for planning documents, high-level strategy, or non-executable discussion; use the relevant planning or design workflow instead.
- Do not use project-structure for unrelated requests.
- This request is outside project structure scope.
- This is conceptual discussion only; no tool workflow is needed.
Runtime Prompt
- Current runtime prompt length: 563 characters.
- Runtime prompt is defined directly in
../project-structure.json.