# Platform Guide

> Answers how-to questions about third-party platforms (e.g. 'how to change theme in Shopify', 'set up a Stripe webhook', 'connect a domain in Vercel', Meta/TikTok/Google consoles, Laravel Forge, app stores) with fresh data: always WebSearch the current official guide first and cite it — never answer from stale memory. Use whenever the user asks how to do, configure, enable, or find anything in an external platform's UI, or to set up API credentials.

- Skill: `asunalabs/platform-guide` (Agent Skill)
- Install (CLI): `npx skillmds@latest add asunalabs/platform-guide`
- Raw SKILL.md: https://api.skillmd.com/api/skills/asunalabs/platform-guide/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Integrations & APIs
- Author: asunalabs (https://skillmd.com/u/asunalabs)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/asunalabs/platform-guide

---


# platform-guide — fresh-docs discipline for third-party platforms

Third-party dashboards change constantly (a real example: Forge's Oct-2025 UI
rework renamed "aliases" to Custom Domains and made site-type choices one-shot —
pre-rework instructions were confidently wrong). Stale memory produces walkthroughs
that look right and waste an afternoon.

## Rules

1. **Search before instructing.** Before any UI walkthrough, configuration guide, or
   credential-setup explanation for an external platform: WebSearch for the current
   official documentation (qualify the query with the current year where UIs churn).
   WebFetch the top official source. Cross-check a second source when steps are
   security-sensitive (OAuth scopes, webhooks, payment config).
2. **Prefer official channels**: platform docs > changelogs/release notes > reputable
   recent tutorials. If a dedicated plugin exists for the platform (e.g. a Shopify
   plugin), use its skills as the first stop — and **never fabricate endpoints,
   GraphQL fields, or doc URLs**.
3. **Cite freshness**: note the source and fetched date
   (`platform docs <url> (fetched YYYY-MM-DD)`), consistent with the docs
   convention. If the live UI may differ from the doc, say so and offer to verify
   against the real dashboard (browser MCP) instead of guessing.
4. **API versions matter**: pin/mention the API version rather than "latest", and
   check deprecation notices for anything the instruction depends on.
5. If search is unavailable, say the answer is from memory as of the knowledge
   cutoff and mark every step that could have changed — don't present stale steps as
   current.