What problem does it solve? Writing code for an Innovation Platform app without knowing the platform's contract leads to CI failures: rejected files, failed security scans, broken deploys, and auth or storage implementations the gateway already handles. This Skill loads the full set of platform conventions before any app code is written, so every rule maps to the CI gate that enforces it. ## Core Features & Use Cases - Version gate and live contract: Verifies the plugin version against the platform via get_platform_status and fetches the authoritative app contract with get_app_contract before any code is written. - Deployment type guidance: Covers container, function, mcp-function, and mcp-container app types, including entry points, health checks, storage bindings, and MCP Streamable HTTP transport requirements. - Security and CI compliance rules: Defines identity handling via X-Forwarded-User headers, storage through the http://storage.internal client instead of local disk, XSS-safe rendering, Variables and Connections for secrets, and the protected files (src/, root package.json, wrangler.jsonc, .npmrc) that the config-integrity gate rejects. - Use Case: Before scaffolding a new Starlette app in an inno-{app} repo, load this Skill to learn that persistence must use the Storage client, identity comes from gateway-injected headers, and a root-level lockfile will fail the deploy. ## Quick Start Load the inno-platform-conventions skill before writing any application code inside an Innovation Platform app's app/ directory.
