Claude Code connector playbook
Open Claude Code in the repository of the application you want to connect and paste the prompt from Connect a platform prompt. This page explains how to run it well.
Before you start
- Have a sandbox application and sandbox business ready (Developer console). Put the credentials in the host's local
.envyourself — do not paste secrets into the chat. - Work on a branch:
git checkout -b feat/techtur-pos-connector. - If the host repository has a
CLAUDE.md, Claude Code reads it; add a line pointing to this playbook.
How Claude Code should work
- Use plan mode for steps 1–10 of the AI agent guide and present findings (auth, tenant, catalogue, inventory, orders) before writing code.
- Fetch the OpenAPI document with WebFetch from
https://pos.techtursolutions.com/developers/openapi.json(or readdocs/api/openapi.jsonif thetechtur-posrepo is available) and only call operations listed there. - Keep the mapping in one module with unit tests; keep network calls in another.
- Run the host's own test suite and lint after every significant change; fix failures rather than weakening tests.
- Commit in small, meaningful steps; do not push or deploy without the owner's go-ahead.
- Finish with the completion report from the guide.
Useful references in the techtur-pos repository
examples/techtur-pos-connector-template/— runnable connector with tests.examples/rekadijo-connector/— a mapping from a real TechTur app's models.apps/api/test/integrations.test.ts— the behaviours the API guarantees.