Driving your AI assistant

The general pattern is the same everywhere: give the assistant the docs corpus, then describe what you want it to build. The details differ a little per tool.

Claude Code / claude.ai

Claude can fetch URLs directly — just include the URL in your message:

Read https://docs.sudomimus.com/llms-full.txt then implement a complete
Sudomimus integration for my Next.js app. The application anchor is
your-application. Support passkeys and email OTP. Add routes for
/api/auth/establish, /api/auth/callback, and /api/auth/refresh.

Cursor / Continue / similar editor tools

Use your editor’s URL-attach feature (e.g. Cursor’s @web, Continue’s @docs) to attach https://docs.sudomimus.com/llms-full.txt to the conversation, then ask the same question.

ChatGPT with web browsing

Fetch https://docs.sudomimus.com/llms-full.txt and write a Python Flask
backend that integrates Sudomimus. Use application anchor your-app and
store pending sessions in PostgreSQL.

Let the assistant use the CLI

When the task involves your Sudomimus account or developer resources, the assistant should use the CLI instead of trying to drive the With portal through a browser. Give it a narrow instruction like:

Use the Sudomimus CLI for Sudomimus account operations. Prefer JSON output,
for example `sudomimus whoami --json`. If the CLI is not logged in, stop and
ask me to run `sudomimus login --no-open`; do not read or print the local
credentials file.

See Sudomimus CLI for AI agents for the command surface, endpoint overrides, and security boundaries.

Tips for better output

• Be specific about your stack. “Node.js + Express” produces different code than “Bun + Hono”. The docs cover the protocol; you tell the assistant the surrounding context.
• Name the authentication methods you need. Sudomimus supports passkeys, email OTP, Steam, AccessKey, and OIDC — the assistant has no way to guess which apply to your product.
• Give it your application anchor, callback URL, and any env vars you have. The assistant cannot make these up.
• Point it at the OpenAPI reference for exact contracts. When you want strongly-typed client code, the generated API pages beat prose-derived guesses.
• Keep the conversation open for follow-ups. The docs are already in context, so debugging or asking for variants is one more message away.