[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M783SNM8T0W528YTNX71F236":3,"skill-same:01M783SNM8T0W528YTNX71F236":57},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":34,"commitSha":35,"skillDirectory":36,"forksCount":37,"repositoryHtmlUrl":38,"repositoryHomepageUrl":39,"ownerHtmlUrl":40,"ownerBlogUrl":6,"ownerDescription":41,"updatedAt":42,"install":43,"resources":56},"01M783SNM8T0W528YTNX71F236","add-feature",null,"Add a new gameplay feature to an existing browser game following its architecture patterns. Use when the user says \"add a feature\", \"add double-jump\", \"add a power-up\", \"add a leaderboard\", or describes a specific game mechanic to implement. Do NOT use for visual-only changes (use design-game) or replacing shapes with sprites (use add-assets).","Lord1Egypt\u002Fawesome-skill-forge","Lord1Egypt","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99746359?v=4","01M7592YDNT0XK9WJ0T2MQVPDN","Mohamed Mounir Ali AL Keshita","01M75GRFNHC8VZNWEB8DKDE433",3,"MIT","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fskills_sh\u002Fs\u002Fskills-sh_opusgamelabs_game-creator_add-feature\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: add-feature\ndescription: Add a new gameplay feature to an existing browser game following its architecture patterns. Use when the user says \"add a feature\", \"add double-jump\", \"add a power-up\", \"add a leaderboard\", or describes a specific game mechanic to implement. Do NOT use for visual-only changes (use design-game) or replacing shapes with sprites (use add-assets).\nargument-hint: \"[feature-description]\"\nlicense: MIT\nmetadata:\n  author: OpusGameLabs\n  version: 1.3.0\n  tags: [game, feature, gameplay, mechanic, power-up]\n---\n\n## Performance Notes\n\n- Take your time to do this thoroughly\n- Quality is more important than speed\n- Do not skip validation steps\n\n# Add Feature\n\nAdd a new feature to your game. Just describe what you want in plain English — for example, \"add a double-jump power-up\" or \"add a high score leaderboard\" — and the feature will be built following your game's existing patterns.\n\n## Instructions\n\nThe user wants to add: $ARGUMENTS\n\n### Step 1: Understand the codebase\n\n- Read `package.json` to identify the engine (Three.js or Phaser)\n- Read `src\u002Fcore\u002FConstants.js` for existing configuration\n- Read `src\u002Fcore\u002FEventBus.js` for existing events\n- Read `src\u002Fcore\u002FGameState.js` for existing state\n- Read `src\u002Fcore\u002FGame.js` (or GameConfig.js) for existing system wiring\n- Read existing scene and gameplay files to understand what's already built\n\n### Step 2: Plan the feature\n\nBefore writing code, explain the plan in plain English:\n\n1. **What it does**: Describe the feature from the player's perspective\n2. **How it works**: List the new files, events, and settings that will be created\n3. **What it touches**: List existing files that need small changes to wire in the feature\n\nThen determine what's needed technically:\n- New module file(s) and where they go in the directory structure\n- New events to add to the Events enum\n- New constants to add to Constants.js\n- New state to add to GameState.js\n- How to wire it into the Game orchestrator\n\n### Step 3: Implement\n\nFollow these rules strictly:\n1. Create the new module in the correct `src\u002F` subdirectory\n2. Add ALL new events to `EventBus.js` Events enum\n3. Add ALL configuration values to `Constants.js` (zero hardcoded values)\n4. Add any new state domains to `GameState.js`\n5. Wire the new system into `Game.js` (import, instantiate, update in loop)\n6. Use EventBus for ALL communication with other systems\n7. Follow the existing code style and patterns in the project\n\n### Step 4: Verify\n\n- Run `npm run build` to confirm no errors\n- Confirm the feature integrates without breaking existing systems\n- Check that no circular dependencies were introduced\n- Ensure event listeners are properly cleaned up if applicable\n- Summarize what was added in plain English\n\n## Troubleshooting\n\n### Game breaks after adding feature\n**Cause:** New code conflicts with existing EventBus events or GameState fields.\n**Fix:** Check for event name collisions in EventBus.js. Ensure new state fields have defaults in GameState.reset().\n\n### Feature works but breaks existing gameplay\n**Cause:** Modified shared constants or collision groups.\n**Fix:** Add new constants rather than changing existing ones. Test original gameplay after changes.\n\n## Output\n\nTell the user:\n1. What the feature does (from the player's perspective)\n2. What files were created or changed\n3. How to test it — \"Run `npm run dev` and try [specific action]\"\n\n## Example Usage\n\n### Adding a power-up\n```\n\u002Fadd-feature add a speed boost power-up that spawns randomly\n```\nResult: Creates `src\u002Fentities\u002FPowerUp.js`, adds `POWER_UP` events to EventBus, adds spawn timing and duration to Constants.js, wires into Game.js. Player collects power-up → speed doubles for 8 seconds.\n\n### Adding a scoring mechanic\n```\n\u002Fadd-feature add combo multiplier that increases when you score quickly\n```\nResult: Adds `comboMultiplier` and `comboTimer` to GameState, creates combo logic in scoring system, adds `COMBO_CHANGED` event for UI updates.\n\n## Tips\n\n> You can run this command as many times as you want to keep adding features. Each one builds on the last.\n>\n> When you're happy with the gameplay, run `\u002Fgame-creator:design-game` to polish the visuals, `\u002Fgame-creator:add-audio` for music and sound effects, or `\u002Fgame-creator:review-game` for a full quality check.\n","## Performance Notes\n\n- Take your time to do this thoroughly\n- Quality is more important than speed\n- Do not skip validation steps\n\n# Add Feature\n\nAdd a new feature to your game. Just describe what you want in plain English — for example, \"add a double-jump power-up\" or \"add a high score leaderboard\" — and the feature will be built following your game's existing patterns.\n\n## Instructions\n\nThe user wants to add: $ARGUMENTS\n\n### Step 1: Understand the codebase\n\n- Read `package.json` to identify the engine (Three.js or Phaser)\n- Read `src\u002Fcore\u002FConstants.js` for existing configuration\n- Read `src\u002Fcore\u002FEventBus.js` for existing events\n- Read `src\u002Fcore\u002FGameState.js` for existing state\n- Read `src\u002Fcore\u002FGame.js` (or GameConfig.js) for existing system wiring\n- Read existing scene and gameplay files to understand what's already built\n\n### Step 2: Plan the feature\n\nBefore writing code, explain the plan in plain English:\n\n1. **What it does**: Describe the feature from the player's perspective\n2. **How it works**: List the new files, events, and settings that will be created\n3. **What it touches**: List existing files that need small changes to wire in the feature\n\nThen determine what's needed technically:\n- New module file(s) and where they go in the directory structure\n- New events to add to the Events enum\n- New constants to add to Constants.js\n- New state to add to GameState.js\n- How to wire it into the Game orchestrator\n\n### Step 3: Implement\n\nFollow these rules strictly:\n1. Create the new module in the correct `src\u002F` subdirectory\n2. Add ALL new events to `EventBus.js` Events enum\n3. Add ALL configuration values to `Constants.js` (zero hardcoded values)\n4. Add any new state domains to `GameState.js`\n5. Wire the new system into `Game.js` (import, instantiate, update in loop)\n6. Use EventBus for ALL communication with other systems\n7. Follow the existing code style and patterns in the project\n\n### Step 4: Verify\n\n- Run `npm run build` to confirm no errors\n- Confirm the feature integrates without breaking existing systems\n- Check that no circular dependencies were introduced\n- Ensure event listeners are properly cleaned up if applicable\n- Summarize what was added in plain English\n\n## Troubleshooting\n\n### Game breaks after adding feature\n**Cause:** New code conflicts with existing EventBus events or GameState fields.\n**Fix:** Check for event name collisions in EventBus.js. Ensure new state fields have defaults in GameState.reset().\n\n### Feature works but breaks existing gameplay\n**Cause:** Modified shared constants or collision groups.\n**Fix:** Add new constants rather than changing existing ones. Test original gameplay after changes.\n\n## Output\n\nTell the user:\n1. What the feature does (from the player's perspective)\n2. What files were created or changed\n3. How to test it — \"Run `npm run dev` and try [specific action]\"\n\n## Example Usage\n\n### Adding a power-up\n```\n\u002Fadd-feature add a speed boost power-up that spawns randomly\n```\nResult: Creates `src\u002Fentities\u002FPowerUp.js`, adds `POWER_UP` events to EventBus, adds spawn timing and duration to Constants.js, wires into Game.js. Player collects power-up → speed doubles for 8 seconds.\n\n### Adding a scoring mechanic\n```\n\u002Fadd-feature add combo multiplier that increases when you score quickly\n```\nResult: Adds `comboMultiplier` and `comboTimer` to GameState, creates combo logic in scoring system, adds `COMBO_CHANGED` event for UI updates.\n\n## Tips\n\n> You can run this command as many times as you want to keep adding features. Each one builds on the last.\n>\n> When you're happy with the gameplay, run `\u002Fgame-creator:design-game` to polish the visuals, `\u002Fgame-creator:add-audio` for music and sound effects, or `\u002Fgame-creator:review-game` for a full quality check.\n",{"name":5,"license":15,"metadata":24,"description":7,"argument-hint":33},{"tags":25,"author":31,"version":32},[26,27,28,29,30],"game","feature","gameplay","mechanic","power-up","OpusGameLabs","1.3.0","[feature-description]","master","4aa004da461d820f4ea5499e58eb8d196cf99016","community\u002Fskills_sh\u002Fs\u002Fskills-sh_opusgamelabs_game-creator_add-feature",0,"https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge","https:\u002F\u002Fskill-explorer-rho.vercel.app","https:\u002F\u002Fgithub.com\u002FLord1Egypt","Unbreakable. Unstoppable. Unmatched⚡.\r\n Speaker of machine tongues 🤖  | World-builder of decentralized dreams 🌐 | Defender of the digital realm🛡️.","2026-06-10 08:21:01",{"source":8,"skillName":5,"commands":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add Lord1Egypt\u002Fawesome-skill-forge --skill add-feature",{"tool":49,"command":50},"bunx","bunx skills add Lord1Egypt\u002Fawesome-skill-forge --skill add-feature",{"tool":52,"command":53},"pnpm","pnpm dlx skills add Lord1Egypt\u002Fawesome-skill-forge --skill add-feature","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fskills_sh\u002Fs\u002Fskills-sh_opusgamelabs_game-creator_add-feature\u002FSKILL.md",true,[],[58,65,72,79,86,93],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M785WKJB99G3STR1NF9NRTJW","youtube-content","YouTube transcripts to summaries, threads, blogs.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fyoutube-content\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M785WEFHB0G2S9YA6EPR3H0E","xurl","X\u002FTwitter via xurl CLI: post, search, DM, media, v2 API.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fxurl\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M785W98EDN4EFJXJPMQEHCRC","touchdesigner-mcp","Control a running TouchDesigner instance via twozero MCP — create operators, set parameters, wire connections, execute Python, build real-time visuals. 36 native tools.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Ftouchdesigner-mcp\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M785W5S9FP3QBH2V191E025P","test-driven-development","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Ftest-driven-development\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M785W2AS08NSSH9YATCV6FJB","teams-meeting-pipeline","Operate the Teams meeting summary pipeline via Hermes CLI — summarize meetings, inspect pipeline status, replay jobs, manage Microsoft Graph subscriptions.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fteams-meeting-pipeline\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M785VXKW4T34BTP1SCHW1R7F","systematic-debugging","4-phase root cause debugging: understand bugs before fixing.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fsystematic-debugging\u002FSKILL.md",[],[]]