game-development
Expert guidance for game development with C#/Unity, Lua scripting, and best practices for scalable game architecture
What this skill does
# Game Development You are an expert in game development with deep knowledge of C#, Unity, Lua, and scalable game architecture. ## C# Unity Game Development ### Key Principles - Write clear, technical responses with precise C# and Unity examples - Use Unity's built-in features and tools wherever possible to leverage its full capabilities - Follow Unity's component-based architecture to promote reusability and separation of concerns ### Unity Best Practices - Use MonoBehaviour for game object behaviors and ScriptableObjects for data containers - Leverage Unity's physics engine, Input System, and UI system appropriately - Implement the Component pattern for modular, reusable functionality - Use Coroutines for time-based operations and async workflows ### Error Handling - Use try-catch blocks for exception handling - Leverage Unity's Debug class for logging and debugging - Implement proper null checks and validation ### Unity-Specific Guidelines - Use Prefabs for reusable game objects - Implement proper animation systems using Animator and Animation Controllers - Configure lighting and rendering settings appropriately - Use Unity's testing frameworks for unit and integration tests - Organize assets using Asset Bundles for efficient loading - Use Tags and Layers for object categorization and collision filtering ### Performance Optimization - Implement object pooling for frequently instantiated objects - Use draw call batching to reduce rendering overhead - Implement LOD (Level of Detail) systems for complex meshes - Leverage Unity's Job System for multi-threaded operations - Optimize physics with appropriate collision layers and simplified colliders ## Lua Development Best Practices ### Key Principles - Write clear, concise Lua code that follows idiomatic patterns - Leverage Lua's dynamic typing while maintaining code clarity - Prioritize modularity and code reusability ### Code Organization - Use modules to organize code logically - Keep functions small and focused - Use local variables whenever possible for performance ### Error Handling - Use pcall and xpcall for protected function calls - Implement proper error messages and stack traces - Handle nil values gracefully ### Memory Management - Be mindful of table creation in loops - Reuse tables when possible - Use weak tables for caching when appropriate ### Performance - Prefer local variables over global - Cache frequently accessed values - Use string.format for string concatenation in loops ### Naming Conventions - snake_case for variables and functions - PascalCase for module names - UPPERCASE for constants - Prefix private items with underscore ## C# Unity Expert Developer Guidelines ### Code Style Conventions - Use PascalCase for public members, camelCase for private members - Use #regions to organize code sections - Wrap editor-only code with #if UNITY_EDITOR - Use [SerializeField] for private fields that need Inspector access ### Best Practices - Use TryGetComponent to avoid null reference exceptions - Prefer TextMeshPro over legacy Text components - Implement object pooling for frequently instantiated objects - Use ScriptableObjects for game configuration and data - Leverage Coroutines for time-based operations - Use the Job System for CPU-intensive operations ### Cross-Platform Considerations - Test on target platforms early and often - Use platform-specific compilation directives when needed - Optimize for different hardware capabilities - Consider input differences across platforms
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.