Canonical documentation — sources of truth for code patterns
Canonical documentation
Use this index alongside the bundled references selected in SKILL.md. Load their contents for task-specific guidance, including any other relevant reference files they name, before using the canonical pages for API details.
Before writing any code file, read the relevant canonical docs page using an available documentation tool. These docs are the source of truth for API patterns, component usage, and configuration — do NOT reproduce code examples from memory or from this skill file.
If you cannot access the docs, tell the user you need them to provide the current patterns rather than guessing.
Reference pages
How to use this list
- Identify which topics are relevant to the app you’re building (based on discovery answers)
- Read each relevant page before writing code
- Follow the patterns shown in the docs exactly — field names, import paths, constructor signatures
- If a pattern in your training data conflicts with what the docs show, the docs win
Common lookup scenarios
| You need to… | Read this page |
|---|---|
| Initialize the Stripe client in a UI extension | Extensions SDK API |
Verify fetchStripeSignature on your backend |
Backend + signed requests |
| Choose between platform keys, OAuth, or restricted keys | Authentication types |
| Set up webhooks for a public app | Events and webhooks |
| Store secrets (OAuth tokens, API keys) | Secret Store |
| Know which UI components are available | UI components |
| Declare permissions in the manifest | Permissions reference |
| Publish to the marketplace | Marketplace submission |