skills/pitfall-capture/SKILL.md
This skill should be used when documenting problems encountered and how to avoid them in the future. Triggers on "capture pitfall", "document mistake", "save this warning", or after encountering a significant issue during development.
npx skillsauth add sipherxyz/universal-ue-skills pitfall-captureInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Document problems encountered to prevent future occurrences.
Save to claude-agents/pitfalls/{issue}-pitfall.md:
---
date: YYYY-MM-DD
pitfall: {pitfall-slug}
domain: {GAS|Combat|AI|Animation|Memory|Platform|...}
severity: {Critical|High|Medium}
source-feature: {feature-slug}
---
# Pitfall: {Title}
## Problem
{What went wrong}
## Symptoms
- {Observable symptom 1}
- {Observable symptom 2}
- {How this manifests at runtime}
## Root Cause
{Technical explanation of why this happens}
## Wrong Approach
```cpp
// What NOT to do
{Bad code example with explanation}
// What to do instead
{Good code example}
How to catch this in the future:
## Good Pitfall Candidates
| Type | Example |
|------|---------|
| Memory | Raw `new` for GE causing leak |
| Certification | LoadSynchronous blocking |
| Runtime | Uncached component lookup |
| Subtle Bug | TPair without template params |
| Platform | Console-specific issue |
## Not Good Candidates
- Typos (too trivial)
- Personal preferences (not universal)
- Already in CODING_PITFALLS.md (duplicate)
## Process
1. **Document** - Capture while fresh
2. **Generalize** - Beyond specific instance
3. **Add Detection** - How to prevent recurrence
4. **Update Standards** - Add to CODING_PITFALLS.md if significant
## Update CODING_PITFALLS.md
For significant pitfalls, add to project standards:
```markdown
## {Domain}: {Pitfall Title}
**Problem:** {Brief description}
**Wrong:**
```cpp
{Bad code}
Correct:
{Good code}
Why: {Explanation}
## Integration
Pitfalls are referenced by:
- `/ugm:review` - Check for known pitfalls
- `/ugm:implement` - Avoid documented mistakes
- ue-code-reviewer - Add to review checklist
## Legacy Metadata
```yaml
skill: pitfall-capture
invoke: /ugm:pitfall-capture
development
This skill should be used when implementing features in isolation using git worktrees. Triggers on "create worktree", "isolated workspace", "parallel development", or when starting implementation that should not affect main workspace.
testing
Manage VFX team issues on GitHub Projects - timeline scheduling, status updates, member commit checks, bulk assign. Use when managing VFX team project board, adding issues to timeline, checking member progress, or bulk-updating issue fields.
tools
Generate C++ validation rules from JSON definitions. Use when team updates ValidationRules.json or asks to add/modify validation rules.
development
Check codebase for Microsoft Xbox XR (Xbox Requirements) compliance issues. Scans for account picker, cloud saves, achievements, Quick Resume, and Xbox certification requirements. Use before console submission or when preparing for Microsoft certification. Triggers on "XR", "Xbox certification", "Microsoft compliance", "Xbox cert", "Xbox requirements", "GDK compliance".