[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DXKXEQYHTA0BPMFC1YBVZC":3,"skill-same:01M6DXKXEQYHTA0BPMFC1YBVZC":61},{"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":33,"linkOnly":34,"markdownContent":35,"markdownBody":36,"frontMatter":37,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":14,"repositoryHtmlUrl":42,"repositoryHomepageUrl":6,"ownerHtmlUrl":43,"ownerBlogUrl":44,"ownerDescription":45,"updatedAt":46,"install":47,"resources":60},"01M6DXKXEQYHTA0BPMFC1YBVZC","pc-games",null,"PC and console game development principles. Engine selection, platform features, optimization strategies.","EthanSheehan\u002FGrid-Sentinel","EthanSheehan","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F174215275?v=4","01M6DX9589ENESB2AYW9YK4Y50","Ethan Sheehan","01M6DX95P06JXASASFQZRFQ1NM",0,"MIT","https:\u002F\u002Fgithub.com\u002FEthanSheehan\u002FGrid-Sentinel\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fgame-development\u002Fpc-games\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32],"pc games","development","console","Optimization","game development","game","engine","grep","read","write","edit","selection","strategies","platform","2026-11-10 10:12:30",false,"---\nname: pc-games\ndescription: PC and console game development principles. Engine selection, platform features, optimization strategies.\nallowed-tools: Read, Write, Edit, Glob, Grep\n---\n\n# PC\u002FConsole Game Development\n\n> Engine selection and platform-specific principles.\n\n---\n\n## 1. Engine Selection\n\n### Decision Tree\n\n```\nWhat are you building?\n│\n├── 2D Game\n│   ├── Open source important? → Godot\n│   └── Large team\u002Fassets? → Unity\n│\n├── 3D Game\n│   ├── AAA visual quality? → Unreal\n│   ├── Cross-platform priority? → Unity\n│   └── Indie\u002Fopen source? → Godot 4\n│\n└── Specific Needs\n    ├── DOTS performance? → Unity\n    ├── Nanite\u002FLumen? → Unreal\n    └── Lightweight? → Godot\n```\n\n### Comparison\n\n| Factor | Unity 6 | Godot 4 | Unreal 5 |\n|--------|---------|---------|----------|\n| 2D | Good | Excellent | Limited |\n| 3D | Good | Good | Excellent |\n| Learning | Medium | Easy | Hard |\n| Cost | Revenue share | Free | 5% after $1M |\n| Team | Any | Solo-Medium | Medium-Large |\n\n---\n\n## 2. Platform Features\n\n### Steam Integration\n\n| Feature | Purpose |\n|---------|---------|\n| Achievements | Player goals |\n| Cloud Saves | Cross-device progress |\n| Leaderboards | Competition |\n| Workshop | User mods |\n| Rich Presence | Show in-game status |\n\n### Console Requirements\n\n| Platform | Certification |\n|----------|--------------|\n| PlayStation | TRC compliance |\n| Xbox | XR compliance |\n| Nintendo | Lotcheck |\n\n---\n\n## 3. Controller Support\n\n### Input Abstraction\n\n```\nMap ACTIONS, not buttons:\n- \"confirm\" → A (Xbox), Cross (PS), B (Nintendo)\n- \"cancel\" → B (Xbox), Circle (PS), A (Nintendo)\n```\n\n### Haptic Feedback\n\n| Intensity | Use |\n|-----------|-----|\n| Light | UI feedback |\n| Medium | Impacts |\n| Heavy | Major events |\n\n---\n\n## 4. Performance Optimization\n\n### Profiling First\n\n| Engine | Tool |\n|--------|------|\n| Unity | Profiler Window |\n| Godot | Debugger → Profiler |\n| Unreal | Unreal Insights |\n\n### Common Bottlenecks\n\n| Bottleneck | Solution |\n|------------|----------|\n| Draw calls | Batching, atlases |\n| GC spikes | Object pooling |\n| Physics | Simpler colliders |\n| Shaders | LOD shaders |\n\n---\n\n## 5. Engine-Specific Principles\n\n### Unity 6\n\n- DOTS for performance-critical systems\n- Burst compiler for hot paths\n- Addressables for asset streaming\n\n### Godot 4\n\n- GDScript for rapid iteration\n- C# for complex logic\n- Signals for decoupling\n\n### Unreal 5\n\n- Blueprint for designers\n- C++ for performance\n- Nanite for high-poly environments\n- Lumen for dynamic lighting\n\n---\n\n## 6. Anti-Patterns\n\n| ❌ Don't | ✅ Do |\n|----------|-------|\n| Choose engine by hype | Choose by project needs |\n| Ignore platform guidelines | Study certification requirements |\n| Hardcode input buttons | Abstract to actions |\n| Skip profiling | Profile early and often |\n\n---\n\n> **Remember:** Engine is a tool. Master the principles, then adapt to any engine.\n","# PC\u002FConsole Game Development\n\n> Engine selection and platform-specific principles.\n\n---\n\n## 1. Engine Selection\n\n### Decision Tree\n\n```\nWhat are you building?\n│\n├── 2D Game\n│   ├── Open source important? → Godot\n│   └── Large team\u002Fassets? → Unity\n│\n├── 3D Game\n│   ├── AAA visual quality? → Unreal\n│   ├── Cross-platform priority? → Unity\n│   └── Indie\u002Fopen source? → Godot 4\n│\n└── Specific Needs\n    ├── DOTS performance? → Unity\n    ├── Nanite\u002FLumen? → Unreal\n    └── Lightweight? → Godot\n```\n\n### Comparison\n\n| Factor | Unity 6 | Godot 4 | Unreal 5 |\n|--------|---------|---------|----------|\n| 2D | Good | Excellent | Limited |\n| 3D | Good | Good | Excellent |\n| Learning | Medium | Easy | Hard |\n| Cost | Revenue share | Free | 5% after $1M |\n| Team | Any | Solo-Medium | Medium-Large |\n\n---\n\n## 2. Platform Features\n\n### Steam Integration\n\n| Feature | Purpose |\n|---------|---------|\n| Achievements | Player goals |\n| Cloud Saves | Cross-device progress |\n| Leaderboards | Competition |\n| Workshop | User mods |\n| Rich Presence | Show in-game status |\n\n### Console Requirements\n\n| Platform | Certification |\n|----------|--------------|\n| PlayStation | TRC compliance |\n| Xbox | XR compliance |\n| Nintendo | Lotcheck |\n\n---\n\n## 3. Controller Support\n\n### Input Abstraction\n\n```\nMap ACTIONS, not buttons:\n- \"confirm\" → A (Xbox), Cross (PS), B (Nintendo)\n- \"cancel\" → B (Xbox), Circle (PS), A (Nintendo)\n```\n\n### Haptic Feedback\n\n| Intensity | Use |\n|-----------|-----|\n| Light | UI feedback |\n| Medium | Impacts |\n| Heavy | Major events |\n\n---\n\n## 4. Performance Optimization\n\n### Profiling First\n\n| Engine | Tool |\n|--------|------|\n| Unity | Profiler Window |\n| Godot | Debugger → Profiler |\n| Unreal | Unreal Insights |\n\n### Common Bottlenecks\n\n| Bottleneck | Solution |\n|------------|----------|\n| Draw calls | Batching, atlases |\n| GC spikes | Object pooling |\n| Physics | Simpler colliders |\n| Shaders | LOD shaders |\n\n---\n\n## 5. Engine-Specific Principles\n\n### Unity 6\n\n- DOTS for performance-critical systems\n- Burst compiler for hot paths\n- Addressables for asset streaming\n\n### Godot 4\n\n- GDScript for rapid iteration\n- C# for complex logic\n- Signals for decoupling\n\n### Unreal 5\n\n- Blueprint for designers\n- C++ for performance\n- Nanite for high-poly environments\n- Lumen for dynamic lighting\n\n---\n\n## 6. Anti-Patterns\n\n| ❌ Don't | ✅ Do |\n|----------|-------|\n| Choose engine by hype | Choose by project needs |\n| Ignore platform guidelines | Study certification requirements |\n| Hardcode input buttons | Abstract to actions |\n| Skip profiling | Profile early and often |\n\n---\n\n> **Remember:** Engine is a tool. Master the principles, then adapt to any engine.\n",{"name":5,"description":7,"allowed-tools":38},"Read, Write, Edit, Glob, Grep","main","33d99efaac9ea5758fc27120b467eca96ad020d9",".agent\u002Fskills\u002Fgame-development\u002Fpc-games","https:\u002F\u002Fgithub.com\u002FEthanSheehan\u002FGrid-Sentinel","https:\u002F\u002Fgithub.com\u002FEthanSheehan","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fethan-sheehan\u002F","Aerospace Engineering Student at the University of Bristol \u002F\u002F Propulsion Lead at HyPower Bristol","2026-05-22 21:19:23",{"source":8,"skillName":5,"commands":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add EthanSheehan\u002FGrid-Sentinel --skill pc-games",{"tool":53,"command":54},"bunx","bunx skills add EthanSheehan\u002FGrid-Sentinel --skill pc-games",{"tool":56,"command":57},"pnpm","pnpm dlx skills add EthanSheehan\u002FGrid-Sentinel --skill pc-games","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FEthanSheehan\u002FGrid-Sentinel\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fgame-development\u002Fpc-games\u002FSKILL.md",true,[],[62,93,126,146,160,185],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":73,"publishedAt":33},"01M6DY3X97YDSKHCCZG9KMASHA","zapier-make-patterns","No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points.  This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power","https:\u002F\u002Fgithub.com\u002FEthanSheehan\u002FGrid-Sentinel\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fzapier-make-patterns\u002FSKILL.md",[68],{"categoryNo":69,"categoryName":70,"taxonomyType":71,"taxonomyTypeDesc":72},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[74,75,76,77,78,79,32,80,81,82,83,84,85,86,87,88,89,90,91,92],"zapier make patterns","patterns","workflow","integrations","how to","apps","but","build","complexity","power","simplicity","use","business","automate","how","apache","code","automation","writing",{"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":105,"publishedAt":33},"01M6DY3SVP128ZZPF2478H9JYZ","Cross-Site Scripting and HTML Injection Testing","This skill should be used when the user asks to \"test for XSS vulnerabilities\", \"perform cross-site scripting attacks\", \"identify HTML injection flaws\", \"exploit client-side injection vulnerabilities\", \"steal cookies via XSS\", or \"bypass content security policies\". It provides comprehensive techniques for detecting, exploiting, and understanding XSS and HTML injection attack vectors in web applications.","https:\u002F\u002Fgithub.com\u002FEthanSheehan\u002FGrid-Sentinel\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fxss-html-injection\u002FSKILL.md",[99,102],{"categoryNo":100,"categoryName":101,"taxonomyType":71,"taxonomyTypeDesc":72},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":103,"categoryName":104,"taxonomyType":71,"taxonomyTypeDesc":72},"01JBSEEDCAT000000000000009","前端开发",[106,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,123,124,125],"html injection testing","Cross Site Scripting and HTML Injection Testing","injection","scripting","site","html","testing","exploit","user","applications","xss","cookies","content","web","test","vectors","via","steal","security","vulnerabilities",{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":141,"publishedAt":33},"01M6DY3D694G80Y5N79CD1J575","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002FEthanSheehan\u002FGrid-Sentinel\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[132,133,136],{"categoryNo":100,"categoryName":101,"taxonomyType":71,"taxonomyTypeDesc":72},{"categoryNo":134,"categoryName":135,"taxonomyType":71,"taxonomyTypeDesc":72},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":137,"categoryName":138,"taxonomyType":139,"taxonomyTypeDesc":140},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[92,142,143,85,144,145],"writing skills","deployment","editing","work",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":154,"publishedAt":33},"01M6DY3A7BM31W5Q2QARW00JHS","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002FEthanSheehan\u002FGrid-Sentinel\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[152,153],{"categoryNo":134,"categoryName":135,"taxonomyType":71,"taxonomyTypeDesc":72},{"categoryNo":137,"categoryName":138,"taxonomyType":139,"taxonomyTypeDesc":140},[155,92,156,157,158,85,90,159],"writing plans","plans","requirements","task","spec",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":167,"publishedAt":33},"01M6DY36NSATM95HR7HMVZJYB3","workflow-automation","Workflow automation is the infrastructure that makes AI agents reliable. Without durable execution, a network hiccup during a 10-step payment flow means lost money and angry customers. With it, workflows resume exactly where they left off.  This skill covers the platforms (n8n, Temporal, Inngest) and patterns (sequential, parallel, orchestrator-worker) that turn brittle scripts into production-grade automation.  Key insight: The platforms make different tradeoffs. n8n optimizes for accessibility","https:\u002F\u002Fgithub.com\u002FEthanSheehan\u002FGrid-Sentinel\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fworkflow-automation\u002FSKILL.md",[166],{"categoryNo":69,"categoryName":70,"taxonomyType":71,"taxonomyTypeDesc":72},[168,91,76,169,170,171,89,172,173,174,175,176,177,178,179,180,181,182,183,184],"Workflow Automation","Production","flow","network","workflows","accessibility","ai agents","execution","scripts","worker","payment","n8n","money","resume","orchestrator","parallel","inngest",{"skillNo":186,"name":187,"nameZh":6,"description":188,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":189,"categories":190,"keywords":192,"publishedAt":33},"01M6DY32QTGD80MQHJ8TPDH53H","WordPress Penetration Testing","This skill should be used when the user asks to \"pentest WordPress sites\", \"scan WordPress for vulnerabilities\", \"enumerate WordPress users, themes, or plugins\", \"exploit WordPress vulnerabilities\", or \"use WPScan\". It provides comprehensive WordPress security assessment methodologies.","https:\u002F\u002Fgithub.com\u002FEthanSheehan\u002FGrid-Sentinel\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fwordpress-penetration-testing\u002FSKILL.md",[191],{"categoryNo":100,"categoryName":101,"taxonomyType":71,"taxonomyTypeDesc":72},[112,187,193,194,195,196,197,198,113,85,114,199,200,125,124],"penetration testing","wordpress","security assessment","sites","scan","pentest","plugins","assessment"]