Turns REST API documentation into a runnable curl, fetch, or code example with required headers, request body, and placeholders for secrets. Use when the user wants to generate a request from API docs, an endpoint, or a Swagger/OpenAPI spec — "give me a curl for this", "show a fetch example", "how do I call this API".
Turn the documented API endpoint into the smallest runnable example the user can paste and run — curl, fetch, or a language-specific snippet — complete with the required headers, request body shape, and placeholders for every secret. Work only from what the docs show; don't invent undocumented fields or claim a parameter is required when the docs don't say so.
$API_KEY or <account-id> for secrets and private values.Return concise headings and include these sections when they fit: Runnable example, Required inputs, Expected response, Common mistakes. Preserve exact endpoint paths, header names, and field names. Be specific but don't overclaim; never include real secrets, and if the docs are incomplete, say what's missing and give the best supported example. Respond in the same language as the user's request.
Docs (an endpoint that creates a charge):
POST /v1/charges— requiresAuthorization: Bearer <key>. Body:amount(integer, required),currency(string, required),description(string, optional).
Example:
Runnable example (curl):
bashcurl https://api.example.com/v1/charges \ -H "Authorization: Bearer $API_KEY" \ -H "Content-Type: application/json" \ -d '{"amount": 2000, "currency": "usd", "description": "Test charge"}'Required inputs:
$API_KEY(secret bearer token);amountin the smallest currency unit; a supportedcurrencycode.Expected response:
200with the created charge object, including itsidandstatus.Common mistakes: Omitting
Content-Type: application/json(the body is ignored); sendingamountas a decimal instead of an integer; a stale key returns401.
Repo Onboarder
surfmindExplains a repository's purpose, structure, setup and run commands, key scripts, and the first files worth opening. Use when the user wants to understand a new repo or codebase — "what does this project do", "how do I get started", "give me a codebase overview", "onboard me to this repo".
Code Translator
surfmindConverts a code snippet from one programming language to another while preserving behavior and flagging library, runtime, and type-system differences. Use when the user asks to translate, port, rewrite, or convert code between languages — "port this to Python", "rewrite in Rust", "convert Java to Go".
Regex Decoder
surfmindBreaks a regular expression down into plain-language parts with examples of what it matches and what it rejects. Use when the user asks to explain, decode, or understand a regex, regexp, or pattern — "what does this regex match", "explain this pattern", a .match/.test call.