APIAPI builds foundation packages for AI-assisted development. The Common Game System for Unity ships a canonical AGENT.md specification and task-specific skills for Claude Code, Cursor, and GitHub Copilot, so your AI coding assistant produces idiomatic, correct code on the first attempt — no manual context-priming, no trial-and-error API discovery. fluFrame brings the same production-ready baseline to Flutter.
Latest releases
Common Game System (CGS)
v2.1.0
AI Edition · 23 services · 2,600+ tests passing
Pinned for Unity 6.3 LTS
6000.3.11f1 · .NET Standard 2.1 · Mono + IL2CPP
fluFrame (Flutter)
1.1.0
Live on pub.dev · 160/160 · 59 tests passing
Featured product
A headless C# foundation for Unity 6.3 LTS PC single-player projects. Twenty-three production services wired by a single Bootstrap.Run(). No DI container, no scene singletons, no setup code in your game scripts.
Service Locator, Logger, Event Bus, Save/Load, Configuration, Input, Time, Object Pool, Audio, UI Panel Stack, Scene Flow (+additive), Localization, Achievements, Scheduler, Tween, Asset Provider, Random, FSM, Pushdown Stack, Tween Sequencing, Addressable Scene, Deferred Event Queue, Command Registry — wired together by a single Bootstrap.Run().
Core holds 18 services with zero package dependencies; Input, UI, Localization, Assets, AddressableScene and Bootstrap layer on top. Remove an unused UPM package and the dependent assemblies self-exclude — Bootstrap falls back instead of breaking your build.
Only Unity Engine + first-party Input System / UGUI / Addressables — each one optional. Permissively licensed (MIT / Apache / BSD only — no GPL family).
Ships with AGENT.md spec + 5 task skills (cgs-init / cgs-panel / cgs-event / cgs-config / cgs-test) for Claude Code, Cursor, and GitHub Copilot. Drop into .claude/skills/, .cursorrules, or .github/copilot-instructions.md.
Mono and IL2CPP scripting backends both verified. Works with URP / HDRP / Built-in / Custom RP — contains zero rendering code.
EditMode + PlayMode coverage. The full suite ships inside the package (hidden by default) — import it with one click and run it against your own Unity version.
The Motion Lab demo scene is visible right after import - open it and press Play. Six more samples import with one click from the Welcome window: UI Panel Stack menu flow, Save/Load + Seeded Random determinism proof, a working in-game Command Console, and three script templates. Plus Welcome and Service Debugger editor windows.
Every service ships a no-op 'Null' implementation. ServiceLocator.Replace<T>(new NullX()) mutes a subsystem across your whole game with zero caller-side changes.
Also from APIAPI
One command scaffolds a feature-first Flutter application with state management, routing, theming, localization, networking, flavors, strict lints, and tests — already wired together and passing. The same discipline as CGS, applied to Flutter: nothing ships unless the thing it generates is green.
Most starters are a one-way door: generate once, fork forever. fluframe upgrade reconstructs the exact template version your app came from, three-way merges the new one into it, and hands you ordinary git conflict markers. Your edits survive, nothing is deleted silently, and dry-run is the default.
Riverpod 3 with manual notifiers, go_router 17 bottom tabs and nested routes, freezed 3 + json_serializable models, dio with typed error mapping, and an offline fallback cache on the REST sample — wired together and already passing.
Email/password login, a gated profile tab with return-path redirects, and a persisted session, all behind one AuthRepository seam. Pass --backend supabase or --backend firebase (which then needs flutterfire configure) to wire the real SDK, or omit it and keep the offline fake.
Six persisted color presets with light and dark modes, and English / Korean / Japanese localization already generated. Flavors come from --dart-define-from-file.
--error-reporting sentry and --analytics amplitude (with automatic screen tracking) layer on top of the backend choice. Three variants — the plain default, the Firebase build, and the fully-stacked Supabase + Sentry + Amplitude build — are each generated and put through flutter analyze and flutter test in CI before a release ships.
A perfect pub.dev score with very_good_analysis at zero issues. A release cannot ship unless the app it generates passes flutter analyze and flutter test first.
Try it
dart pub global activate fluframe
fluframe create my_app --org com.mycompany --backend supabase
cd my_app
# --backend supabase leaves placeholder keys in env/dev.json —
# swap in your SUPABASE_URL and SUPABASE_PUBLISHABLE_KEY first.
flutter run --dart-define-from-file=env/dev.json
fluframe upgrade # later: pull template improvements into your appAbout the publisher
APIAPI is a solo studio. Every line of code, every test, and every architectural decision is reviewed and accepted by a human before release. We use AI coding assistants (Claude Code, Cursor) as disciplined collaborators under a Question → Options → Decision → Draft → Approval protocol — never as autonomous code generators. The result: clean, idiomatic, test-covered packages that respect your time as much as we respect ours.
Contact
Product support
Q&A and issues
For CGS and other Unity packages, use the Asset Store publisher Q&A tab on the package page. For fluFrame, open a GitHub issue. Public responses help future customers too.