feature-implementation
Step-by-step guide for implementing new game features and domain logic
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Menu
Step-by-step guide for implementing new game features and domain logic
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Sync new/changed game image assets from Android device to S3 CDN. Use after a game version update when new images may have been added.
Update game data when a new Legends of Idleon version is released. Extracts game code from Steam, processes it through WikiBot, and syncs updated data back.
Guide for live game extraction testing, writing domain tests, and validating calculations
Understanding data flow, domain patterns, cross-domain dependencies, and architectural constraints
Based on SOC occupation classification
| name | feature-implementation |
| description | Step-by-step guide for implementing new game features and domain logic |
| triggers | [{"path":"data/domain/*.tsx","exclude":["data/domain/data/**","data/domain/enum/**","data/domain/model/**"]}] |
For comprehensive implementation documentation, read docs/NEW_FEATURE_IMPLEMENTATION_GUIDE.md.
Prerequisites to gather before starting:
../IdleonWikiBot/exported/ts/)reference-repos/IdleonToolbox/ for reference implementationsCritical constraints:
data/domain/data/, data/domain/enum/, data/domain/model//testing skillCommon patterns to follow:
stamps.tsx (simple), alchemy.tsx (medium), sailing.tsx (complex)