القائمة
Generate concise specifications for development tools, editors, and utilities. Use this when planning a new tool, editor plugin, or standalone utility to assist with game development.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Read a prototype GDD and generate a phased implementation roadmap with concrete tasks, organized by implementation phases with specific deliverables and test criteria.
Generate complete, game-ready VFX scenes for Godot 4.x using NO custom art assets. Creates procedural effects using GPUParticles2D, ColorRect, Line2D, and geometric shapes. Use this when the user wants to create visual effects without sprites.
Implement tool features from roadmaps, building editor plugins, standalone tools, and CLI utilities for game development. Use this when implementing features from a tool roadmap.
Create phased implementation roadmaps for development tools, breaking them into MVP, enhancements, and polish phases with feature-level deliverables compatible with tool-feature-implementer.
Build and maintain a living architecture document tracking scene trees, data structures, system hierarchies, and game architecture. Use this when visualizing game structure, documenting scene hierarchies, or tracking data schemas.
Add animations to existing PixelLab characters. Lists available characters, shows animation templates organized by category (movement, combat, utility), and supports custom action descriptions. Use this when the user wants to animate a character sprite.
استنادا إلى تصنيف SOC المهني
| name | tool-spec-generator |
| description | Generate concise specifications for development tools, editors, and utilities. Use this when planning a new tool, editor plugin, or standalone utility to assist with game development. |
| domain | tooling |
| type | generator |
| version | 1.0.0 |
| allowed-tools | ["Read","Write","Glob","Grep","AskUserQuestion"] |
This skill generates structured, moderate-detail specifications for development tools, editor plugins, and standalone utilities. Keeps specs concise (~1-2 pages) while capturing enough detail to guide implementation.
Invoke this skill when the user:
Ask the user:
Use the template below, filling in based on user answers and your analysis.
# Tool Spec: [Tool Name]
**Version:** 0.1
**Type:** [Editor Plugin / Standalone / CLI]
**Priority:** [High / Medium / Low]
**Created:** [Date]
---
## Problem Statement
**Pain Point:**
[One sentence describing the problem this tool solves]
**Current Workaround:**
[How is this done today without the tool?]
**Impact:**
[Why is solving this worth the effort?]
---
## Target Users
| User | Use Case |
|------|----------|
| [Role] | [What they do with this tool] |
---
## Core Functionality (MVP)
### Must Have
1. **[Feature]** - [Brief description]
2. **[Feature]** - [Brief description]
3. **[Feature]** - [Brief description]
### Nice to Have (Post-MVP)
- [Feature idea]
- [Feature idea]
---
## User Workflow
```mermaid
graph LR
A[User Action 1] --> B[Tool Response]
B --> C[User Action 2]
C --> D[Result]
Primary Flow:
[Description or simple ASCII/Mermaid mockup]
┌─────────────────────────────────┐
│ [Header/Toolbar] │
├─────────────────────────────────┤
│ [Main Content Area] │
│ │
├─────────────────────────────────┤
│ [Status Bar / Actions] │
└─────────────────────────────────┘
| Element | Purpose |
|---|---|
| [Element] | [What it does] |
[If the tool uses custom data formats]
# Example structure
{
"key": "value"
}
MVP Complete When:
Tool is Successful When:
---
## Spec Detail Guidelines
### Keep It Concise
- Problem statement: 1-3 sentences
- MVP features: 3-5 bullet points max
- Workflow: 4-6 steps max
- UI description: Simple mockup + key elements table
### Focus On
- **Why** this tool exists (problem)
- **What** it does (MVP features)
- **How** users interact (workflow)
- **When** it's done (success criteria)
### Avoid
- Implementation details (save for Systems Bible)
- Exhaustive feature lists
- Premature optimization concerns
- Over-specified UI (iterate during development)
---
## Examples by Tool Type
### Editor Plugin Example
```markdown
# Tool Spec: Balance Dashboard Dock
**Type:** Editor Plugin (Dock)
**Priority:** High
## Problem Statement
**Pain Point:** Weapon and enemy stats are scattered across multiple .tres files, making balance comparison difficult.
**Current Workaround:** Manually open each resource file, copy values to spreadsheet.
**Impact:** Balance iteration takes 30+ minutes per cycle. A dashboard could reduce this to seconds.
## Target Users
| User | Use Case |
|------|----------|
| Designer | Compare weapon DPS, spot outliers |
| Programmer | Verify balance changes after code updates |
## Core Functionality (MVP)
1. **Weapon Table** - Display all weapons with key stats (damage, fire rate, DPS)
2. **Enemy Table** - Display all enemies with key stats (HP, damage, speed)
3. **Sort/Filter** - Sort by any column, filter by type
## User Workflow
1. Open Balance Dashboard dock in editor
2. View all weapons/enemies in sortable tables
3. Click row to open resource file
4. Edit resource, dashboard auto-refreshes
## Success Criteria
- [ ] Displays all WeaponData and EnemyData resources
- [ ] Calculates derived stats (DPS, TTK)
- [ ] Sorts by any column
- [ ] Opens resource on double-click
# Tool Spec: Dialogue Tree Validator
**Type:** Standalone (CLI + optional GUI)
**Priority:** Medium
## Problem Statement
**Pain Point:** Dialogue JSON files can have broken node references, missing conditions, or orphaned branches that only surface at runtime.
**Current Workaround:** Manually trace dialogue paths, test in-game.
**Impact:** Broken dialogue discovered during playtests wastes everyone's time.
## Core Functionality (MVP)
1. **Parse Check** - Validate JSON syntax
2. **Reference Check** - Verify all node IDs exist
3. **Orphan Detection** - Find unreachable nodes
4. **Report** - Output issues with file:line references
## Success Criteria
- [ ] Catches missing node references
- [ ] Identifies orphan nodes
- [ ] Runs in <1 second for all dialogue files
- [ ] Exit code 0/1 for CI integration
Save specs to: docs/tools/[tool-name]-spec.md
Examples:
docs/tools/balance-dashboard-spec.mddocs/tools/dialogue-validator-spec.mddocs/tools/asset-importer-spec.mddocs/tools/[name]-spec.mdtool-roadmap-plannertool-roadmap-plannereditor-plugin-scaffolder (if created)This skill ensures tools are planned before built, with clear success criteria and focused scope.