Frontend
Integrations
Plans and implements reliable third-party integrations: APIs, forms, payments, CRM, email, analytics, maps, booking.
What it does
Plans and implements reliable third-party integrations: APIs, forms, payments, CRM, email, analytics, maps, booking.
When to use it
Use whenever a site exchanges data with a vendor: authentication, failure handling, security and maintenance included.
Problems it prevents
Prevents integrations that work in the demo and fail silently the first time a vendor call actually errors.
Typical workflow
- Map the data exchange
- Plan authentication and failure handling
- Implement with security in view
- Document for future maintenance
Example output
A vendor integration with a defined failure path (what the user sees, what gets retried, what gets logged) not just a happy-path call.
What's included
- 01The complete prompt
The full manual as a ready-to-save SKILL.md file, matched exactly to what ships in the T7 library.
- 02Install walkthrough
Personal (~/.claude/skills/) and project (.claude/skills/) folder instructions, whichever fits how you work.
- 03Use notes
How Claude invokes it, what a good result looks like, and what to check before you trust the output.
Installation
Save the manual as SKILL.md in ~/.claude/skills/integrations/ to use it on every project, or in .claude/skills/integrations/ to scope it to one repository. Then invoke it directly:
/integrations