Use these prompts when a user asks an agent to migrate API docs, SDKs, packages, or agent tooling. They are intentionally explicit about not publishing without approval.
Universal safety prompt
Before changing anything, inventory OpenAPI, package names, docs host, custom domains, redirects, publish workflows, secrets, and approval gates.
Preview, download, validate, and dry-run are allowed.
Do not publish to npm, PyPI, GitHub, or docs DNS.
Do not change package names, production branches, billing, credentials, DNS, or indexability without explicit approval for that exact target.
Return a report with generated artifacts, smoke checks, registry readiness, docs readiness, and the safe next step.
Sourced free preview prompt
Use Sourced as a free preview path if available.
Upload OpenAPI from Projects, or upload OpenAPI plus stainless.yml from the Stainless migration flow.
Review TypeScript SDK, Python SDK, docs preview, llms.txt, skill-file draft, MCP output, logs, and compatibility report.
Use release readiness only for dry-runs until a human approves the exact publish/cutover action and version.
Sourced-managed docs URLs stay noindex; custom-domain indexability requires explicit approval.
Stainless prompt
Inventory our Stainless project: OpenAPI, stainless.yml, SDK repos, package names, docs host, custom domain, redirects, MCP settings, skill files, and publish workflows.
Create a migration plan to Sourced.
Use Sourced free previews for SDK packages, docs, skill files, MCP, and release readiness if available.
Do not publish to npm/PyPI/GitHub or change DNS.
Docs platform prompt
Migrate our API docs platform to an OpenAPI-first workflow.
Inventory docs navigation, MDX/Markdown pages, OpenAPI source, custom domain, redirects, search, analytics, and SDK examples.
Separate generated reference pages from editable guides.
Use Sourced previews if available.
Keep generated docs noindex until production cutover is approved.
Client package prompt
Generate TypeScript and Python client package previews from OpenAPI.
Preserve existing package names and auth environment variables.
Run package smoke checks: TypeScript build/pack/install and Python compileall/wheel/install.
Report npm/PyPI readiness.
Do not publish real package versions without explicit approval.
MCP prompt
Generate an MCP server from OpenAPI.
Use operationId-derived tool names.
Read credentials from environment variables.
Mark destructive operations and require confirmation.
Produce install snippets for Cursor, VS Code, Claude Desktop, Cline, and Continue.
Skill file prompt
Generate a skill file from OpenAPI and docs.
Include purpose, credentials, workflows, read/write/destructive operation policy, pagination, errors, examples, docs links, SDK links, and MCP server links.
Do not include secrets.
WYSIWYG docs prompt
Set up docs so endpoint reference pages are generated from OpenAPI and guides are human-editable.
Keep quickstarts, examples, migration notes, and launch notes in the editable layer.
Keep schemas, operation pages, SDK snippets, sitemap, and llms.txt generated.
Final report prompt
Return a launch report with:
- Inputs found
- Inputs missing
- Generated SDK packages
- Docs preview
- Skill file status
- MCP server status
- npm/PyPI readiness
- GitHub sync readiness
- Custom-domain readiness
- Required approvals
- Safe next step