unity-build-platforms
Unity builds — IL2CPP vs Mono, build profiles, addressables-aware builds, Android (Gradle, AAB, Play Asset Delivery), iOS (Xcode post-processing, capabilities), WebGL, console NDA paths (high-level only). USE WHEN: configuring build settings, fixing platform-specific issues, signing, store submission, build size optimization, multi-platform CI. DO NOT USE FOR: editor-side build code (use `unity-editor-tooling`); runtime perf (use `unity-performance`).
What this skill does
# Unity Builds & Platforms
## Scripting backend
| Backend | Where | Trade-off |
|---|---|---|
| **IL2CPP** | All shipping builds | AOT-compiled, smaller perf surprises, slow build, larger binary |
| **Mono** | Editor + dev iteration | Fast build, dynamic features, larger memory, JIT not allowed on iOS |
Ship IL2CPP for production on every platform that supports it.
## Build profiles (Unity 6)
`Window > Build Profiles` — distinct configs per target (development PC, release PC, mobile dev, mobile release). Each profile has its own scripting backend, scenes list, scripting defines, and build path.
## Android
### Gradle + libraries
`Assets/Plugins/Android/` for AAR/JAR drops. Use **Custom Main Manifest / Custom Gradle Properties** when third-party SDKs need them — avoid editing `Library/` generated files.
### AAB (App Bundle)
Mandatory on Play Store since 2021. Configure:
- Minimum API level (typically 26+)
- Target API level (latest stable)
- Architectures: **ARM64 only** for shipping (x86 is dev-only)
- IL2CPP Code Generation: Faster runtime
- **Strip Engine Code = ON**
### Play Asset Delivery (PAD)
Splits content into install-time / fast-follow / on-demand asset packs. Pair with Addressables: configure remote group → builds into `.aab` asset packs. Use for big games (>150 MB base APK limit).
### Permissions
Declare only what you use; runtime-request location/camera/mic. Recent Android requires `Manifest.permission.POST_NOTIFICATIONS` for push.
## iOS
### Build flow
Unity → Xcode project → archive → notarize/upload via Xcode or `altool`. Most issues come from **Build Phases** missing entitlements; fix via `OnPostprocessBuild`:
```csharp
[PostProcessBuild]
public static void Modify(BuildTarget t, string path) {
if (t != BuildTarget.iOS) return;
var pbx = new PBXProject();
var pbxPath = PBXProject.GetPBXProjectPath(path);
pbx.ReadFromFile(pbxPath);
string targetGuid = pbx.GetUnityMainTargetGuid();
pbx.AddFrameworkToProject(targetGuid, "UserNotifications.framework", false);
pbx.WriteToFile(pbxPath);
}
```
### Capabilities & Info.plist
Push (`UserNotifications`), Sign in with Apple, Game Center, IAP — via Capabilities. Privacy strings (`NSCameraUsageDescription`) — must explain user-visible reason.
## WebGL
Constraints:
- No real threads (until SharedArrayBuffer is fully unlocked)
- Memory cap (usually 256–512 MB; configure in Player Settings)
- Compression: **Brotli** when server supports it; **Gzip** otherwise; **Disabled** only for itch.io-style hosts that decompress for you
Disable: bloom (heavy), realtime shadows (gather), reflection probes if static.
## Console (PS5/XSX/Switch)
Behind NDA. High-level: separate Unity install per platform; console-specific Build Pipeline calls; first-party libs (PSN/Xbox Live/Nintendo Account) wrap their own SDK on top of Unity. Get developer account + Unity console license before scoping.
## CI for multi-platform
```yaml
# pseudo-yaml: matrix over platforms
strategy:
matrix:
target: [StandaloneWindows64, Android, iOS]
steps:
- uses: game-ci/unity-builder@v4
with:
targetPlatform: ${{ matrix.target }}
buildMethod: CIBuild.Build
```
## Anti-patterns
| Anti-pattern | Fix |
|---|---|
| Mono on shipping mobile | IL2CPP + ARM64 |
| Engine code stripping disabled | Enable High; add `link.xml` for reflection types |
| Forgotten dev provisioning profile | Use distribution profile in Release builds |
| Big base APK exceeding 150 MB | PAD asset packs + Addressables |
| WebGL gzip on a host that doesn't decompress | Brotli or Disabled compression |
| Same scripting defines across all platforms | Per-platform defines in Build Profiles |
## Production checklist
- [ ] Build Profiles configured per target
- [ ] Signing keys stored securely (GitHub secrets, not committed)
- [ ] Minimum/target SDK / iOS deployment target documented
- [ ] Addressables built before player on every platform
- [ ] Platform-specific permissions strings + capabilities reviewed
- [ ] Build size budget tracked over time (alert on regressions)
- [ ] Day-1 patch / fast-follow path tested
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.