agentleFS
xenitV1xenitV1/Antigravity-Workflows/skills/game-development/pc-games/SKILL.md

pc-games

Skill130 starsChanged 10 months agoMITView on GitHub

PC and console game development principles. Engine selection, platform features, optimization strategies.

Files
SKILL.md

PC/Console Game Development

Engine selection and platform-specific principles.


1. Engine Selection

Decision Tree

What are you building?
│
├── 2D Game
│   ├── Open source important? → Godot
│   └── Large team/assets? → Unity
│
├── 3D Game
│   ├── AAA visual quality? → Unreal
│   ├── Cross-platform priority? → Unity
│   └── Indie/open source? → Godot 4
│
└── Specific Needs
    ├── DOTS performance? → Unity
    ├── Nanite/Lumen? → Unreal
    └── Lightweight? → Godot

Comparison

FactorUnity 6Godot 4Unreal 5
2DGoodExcellentLimited
3DGoodGoodExcellent
LearningMediumEasyHard
CostRevenue shareFree5% after $1M
TeamAnySolo-MediumMedium-Large

2. Platform Features

Steam Integration

FeaturePurpose
AchievementsPlayer goals
Cloud SavesCross-device progress
LeaderboardsCompetition
WorkshopUser mods
Rich PresenceShow in-game status

Console Requirements

PlatformCertification
PlayStationTRC compliance
XboxXR compliance
NintendoLotcheck

3. Controller Support

Input Abstraction

Map ACTIONS, not buttons:
- "confirm" → A (Xbox), Cross (PS), B (Nintendo)
- "cancel" → B (Xbox), Circle (PS), A (Nintendo)

Haptic Feedback

IntensityUse
LightUI feedback
MediumImpacts
HeavyMajor events

4. Performance Optimization

Profiling First

EngineTool
UnityProfiler Window
GodotDebugger → Profiler
UnrealUnreal Insights

Common Bottlenecks

BottleneckSolution
Draw callsBatching, atlases
GC spikesObject pooling
PhysicsSimpler colliders
ShadersLOD shaders

5. Engine-Specific Principles

Unity 6

  • DOTS for performance-critical systems
  • Burst compiler for hot paths
  • Addressables for asset streaming

Godot 4

  • GDScript for rapid iteration
  • C# for complex logic
  • Signals for decoupling

Unreal 5

  • Blueprint for designers
  • C++ for performance
  • Nanite for high-poly environments
  • Lumen for dynamic lighting

6. Anti-Patterns

❌ Don't✅ Do
Choose engine by hypeChoose by project needs
Ignore platform guidelinesStudy certification requirements
Hardcode input buttonsAbstract to actions
Skip profilingProfile early and often

Remember: Engine is a tool. Master the principles, then adapt to any engine.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.