| name | external-api-knowledge |
| description | Look up current third-party API docs and reference material instead of guessing from memory. Use this when external frameworks, SDKs, or platform APIs are part of the task. |
| owner | any |
| trigger | null |
| version | 2 |
External API Knowledge
Use this when external libraries or platform APIs are involved and accuracy matters more than recall.
Workflow
- Identify the exact external dependency involved.
- Check the skill
references/ directory first for bundled docs that already match the dependency.
- If the bundled references are insufficient or the API may have changed, fetch current docs from the authoritative source.
- Base code changes on verified signatures, option names, and documented usage patterns.
- When the answer is inferred from docs rather than stated directly, say that.
In This Repo
- Check
references/phaserjs.md when the task touches PhaserJS.
- For other dependencies, use the current official docs rather than guessing from training data.
Good Uses
- type errors against external SDKs
- browser automation APIs
- framework configuration and lifecycle hooks
- auth or cloud SDK integration work
This skill is about verified external knowledge, not generic TypeScript advice.
