القائمة
5 expert personas debate proposed changes before implementation. Catches architectural, security, performance, and UX issues early. Use before major features or risky changes.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Asset Hunter Pro — unused asset detection, dependency graph, duplicate finder, project cleanup automation for Unity
Practical tools and validation methods for game balance — DPS calculators, EHP formulas, spreadsheet layouts, stat audits, difficulty spike detection
GDD structure, templates, and living documentation patterns for game projects — wiki pages, design docs, section layout, sync triggers
Game feel and juice — screen shake, hit stop, particles, animation curves, input responsiveness, feedback timing. Makes actions feel satisfying.
Mobile game design patterns — session design, retention mechanics, notification strategy, portrait/landscape, battery/thermal constraints, FTUE
Create or update TheOneKit agent .md files with canonical structure. Use when adding a new agent, updating maxTurns/model, or fixing frontmatter fields.
| name | t1k:predict |
| description | 5 expert personas debate proposed changes before implementation. Catches architectural, security, performance, and UX issues early. Use before major features or risky changes. |
| version | 1.0.0 |
| argument-hint | <proposed change description> |
| effort | medium |
| origin | theonekit-core |
| repository | The1Studio/theonekit-core |
| module | null |
| protected | true |
5 expert personas review a proposed change and debate its merits, risks, and alternatives.
/t1k:predict "Add caching layer to API responses"
| # | Persona | Focus | Looks For |
|---|---|---|---|
| 1 | Architect | System design, scalability, coupling | Over-engineering, tight coupling, wrong abstractions, missing extensibility |
| 2 | Security | Attack surface, data flow, trust boundaries | Auth bypass, injection, data exposure, insufficient logging |
| 3 | Performance | Bottlenecks, memory, latency | N+1 queries, unnecessary allocations, cache invalidation issues |
| 4 | UX/DX | User/developer impact, edge cases | Breaking changes, poor error messages, confusing APIs |
| 5 | Devil's Advocate | Assumptions, alternatives, hidden costs | "What if this is the wrong approach entirely?" |
## Prediction: {change description}
### Architect (Risk: 3/5)
- Concern: ...
- Mitigation: ...
### Security (Risk: 2/5)
- Concern: ...
- Mitigation: ...
### Performance (Risk: 4/5)
- Concern: ...
- Mitigation: ...
### UX/DX (Risk: 1/5)
- Concern: ...
- Mitigation: ...
### Devil's Advocate (Risk: 3/5)
- Alternative: ...
- Hidden cost: ...
### Consensus
- **Overall Risk: 2.6/5**
- **Recommendation: GO with conditions**
- **Top 3 concerns to address:**
1. ...
2. ...
3. ...
| Trap | Reality |
|---|---|
| "This change is too simple for a debate" | Simple changes with hidden complexity cause the worst incidents. |
| "We already discussed this" | Discussion ≠ structured risk assessment. |
| "The user wants to start coding" | 5 minutes of prediction saves 5 hours of debugging. |