AGENT SKILL

pc-games

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

License 许可
MIT
最近更新
2026-11-10
Stars
★ 1
Forks
0

01 前言 Front Matter

name
pc-games
risk
safe
source
community
date_added
2026-02-27
description
PC and console game development principles. Engine selection, platform features, optimization strategies.

03 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

Factor Unity 6 Godot 4 Unreal 5
2D Good Excellent Limited
3D Good Good Excellent
Learning Medium Easy Hard
Cost Revenue share Free 5% after $1M
Team Any Solo-Medium Medium-Large

2. Platform Features

Steam Integration

Feature Purpose
Achievements Player goals
Cloud Saves Cross-device progress
Leaderboards Competition
Workshop User mods
Rich Presence Show in-game status

Console Requirements

Platform Certification
PlayStation TRC compliance
Xbox XR compliance
Nintendo Lotcheck

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

Intensity Use
Light UI feedback
Medium Impacts
Heavy Major events

4. Performance Optimization

Profiling First

Engine Tool
Unity Profiler Window
Godot Debugger → Profiler
Unreal Unreal Insights

Common Bottlenecks

Bottleneck Solution
Draw calls Batching, atlases
GC spikes Object pooling
Physics Simpler colliders
Shaders LOD 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 hype Choose by project needs
Ignore platform guidelines Study certification requirements
Hardcode input buttons Abstract to actions
Skip profiling Profile early and often

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

When to Use

This skill is applicable to execute the workflow or actions described in the overview.

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

04 同仓库更多 Skills

YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

vercel-sandbox

Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include "Vercel Sandbox browser", "microVM Chrome", "agent-browser in sandbox", "browser automation on Vercel", or any task requiring Chrome in a Vercel Sandbox.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

slack

Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include "check my Slack", "what channels have unreads", "send a message to", "search Slack for", "extract from Slack", "find who said", or any task requiring programmatic Slack interaction.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

electron

Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

dogfood

Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

shadcn

Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", "switch to --preset", and for building a design system or applying a DESIGN.md or brand spec to shadcn/ui.

★ 1