Create a Solution Design with AI

Use Cobre’s Skill to produce a Solution Design Document for your integration — Local Payments, Cross Border, FX, Stablecoins, balances, and operational features — from your own technical team.

The skill reads Cobre’s live API documentation and OpenAPI specification, then writes a Markdown design you can share with engineering.

The file you install is a wrapper. On every run it fetches the current workflow, product rules, templates, and validation ontology from Cobre’s hosted skill content. You do not need a new zip when Cobre updates those rules — only when your KAM sends a new wrapper.

The same .skill file works in Claude Code, Cursor, Codex, Copilot, Gemini CLI, and other Agent Skills-compatible coding agents. It does not run in a chat UI that cannot execute scripts or fetch documentation.

Use a current wrapper and let it refresh itself. The zip your KAM sent is not the full rule set. Each run pulls the latest skill content over HTTPS, then reads the live OpenAPI spec through the Cobre Docs MCP.

Before start working in a Solution Design:

Ask your Key Account Manager (KAM) for cobre-create-solution-design.skill.

Connect the Cobre Docs MCP and refresh it in the same chat. The skill will not generate a design from published pages alone.

Do not keep a private fork of the skill. If the output disagrees with docs.cobre.com, trust the published documentation and ask your KAM whether you need a new wrapper.

What the skill produces

A Markdown Solution Design covering the products you describe: architecture, balances, counterparties, API mapping by rail, webhooks, reconciliation, and open decisions.

Request, response, and webhook examples taken from the live OpenAPI spec — not paraphrased from memory.

The document is written for your engineering kickoff. Commercial terms, pricing, FX spreads, KYC requirements, and per-account limits are not sourced from public docs; the design will say so instead of inventing numbers.

Conversation, intake, and the document can be English, Spanish, or Simplified Chinese. The skill asks which language to use first.

See Example

Prerequisites

Requirement	Why
A coding agent with shell access (Claude Code, Cursor, Codex, Copilot, Gemini CLI, or similar)	The skill must fetch hosted content, refresh the OpenAPI spec, and run `validate_spec.py`.
Cobre Docs MCP	Required. Endpoints, schemas, examples, and enums come from a refreshed OpenAPI spec. See Build with AI.
`cobre-create-solution-design.skill` from your KAM	Local scripts and validator.
Python 3, curl, HTTPS	Fetch hosted pages and validate the design.

1. Request the skill from your KAM

Ask your Key Account Manager for cobre-create-solution-design.skill.

Cobre does not publish the zip for self-serve download. If you still have create-solution-design-self-service.skill, delete it and install the current wrapper instead.

2. Install it in your agent

The folder inside the zip must be named cobre-create-solution-design/ and must contain exactly one SKILL.md at its root. Delete any older copy first.

Agent	Install
Claude Code	Import the `.skill` in Settings → Skills, or unzip to `~/.claude/skills/`
Cursor	Import the `.skill` in Skills settings, or unzip to `~/.cursor/skills/` or `.cursor/skills/`
Codex	Unzip to `~/.agents/skills/` or `.agents/skills/`
Copilot / VS Code / Gemini CLI	Unzip into that product’s skills folder so `SKILL.md` sits at the skill root

Replace any older copy

Description: Remove cobre-create-solution-design and create-solution-design-self-service from the skills folder you will use, then import or unzip the file your KAM sent.

What to expect after the action: Only one copy of the skill is on disk.

Confirm the skill loads

Description: Start a new agent conversation and ask for a Cobre Solution Design (see How to use it).

What to expect after the action: The assistant fetches hosted skill content, then follows intake instead of inventing an integration from memory.

If you previously installed this skill, delete the old copy before installing the new one.

3. Connect live Cobre documentation

The skill will not write a Solution Design from memory or from llms.txt alone.

Follow Build with AI and add Cobre’s public documentation MCP (site-id=760877). No token is required. Then, in the same chat, ask:

Refresh MCP and reload the latest API specification.

MCP caches the OpenAPI spec locally. A refresh in this run is mandatory. If refresh fails or MCP is not connected, the skill stops.

Hosted skill content (workflow and product rules) is separate from the product OpenAPI spec. The wrapper fetches the first; MCP supplies the second.

How to use it

Work in agent mode so the assistant can run scripts and call MCP.

Start a new conversation

Description: Ask for a Solution Design. You do not need Cobre’s product names — describe how your business moves money.

Example prompts:

Create a Solution Design for our Cobre integration.

We are a PSP in Mexico and Colombia. We need SPEI payouts, collections, FX, and USDC on-ramp. Generate a Solution Design.

What to expect after the action: The assistant asks for language (English, Spanish, or Simplified Chinese).

Let the skill refresh itself

Description: Approve the fetch of hosted skill content and the MCP OpenAPI refresh when the agent asks.

What to expect after the action: Intake and validation use the current ruleset and the current spec — not whatever was inside last month’s zip.

Answer intake

Description: The skill asks a short scope screen, then a maximum of two rounds of intake. Answer in your own words. “I don’t know” is a valid answer — the design will list the options, what each one costs, and which choice it assumes in the meantime.

What to expect after the action: The assistant has enough to write the Markdown. You do not need sandbox credentials; account enablement appears as decisions in the design.

Review the Markdown

Description: The skill writes one Markdown file. That file is the deliverable. Ask for edits until it is right.

What to expect after the action: A client-facing document. A run report may appear in the chat (sources used, gaps). Keep that report internal — do not paste MCP or cache warnings into the file you share.

Typical Markdown contents:

Objective and scope

Architecture and design principles

Operating model (balances, counterparties, flow of funds)

API mapping by process — payouts first, then payins, then Cross Border / Stablecoins when in scope

Events, webhooks, and state synchronisation

Reconciliation and reports

Codes and catalogs needed for your geographies

Decisions and trade-offs (including irreversible choices such as the balance model)

Keep the skill current

Two layers stay current in different ways:

Layer	How it updates
Hosted skill content (intake, product rules, templates, ontology)	Fetched on every run. You do not need a new zip.
OpenAPI spec	MCP refresh in this run. See Managing API and Product Changes.
Wrapper (fetch script, validator)	Ask your KAM for a new `cobre-create-solution-design.skill` only when they send one, or when fetch fails after a Cobre notice.

If the skill output and docs.cobre.com disagree, treat the published documentation as correct.

How to integrate with Cobre — client journey from pre-sales to go-live

Explore API Workflow Examples — interactive walkthroughs of Cobre API sequences

Generate Code with MCP — prompts for PMs and developers to scaffold code from the live spec

Build with AI — connect the Cobre Docs MCP in your IDE

Connect Cobre's Documentation to AI — use llms.txt for documentation-grounded answers

Managing API and Product Changes — how Cobre notifies you when APIs change

Example

Solution Design — NorteLedger MX integration with Cobre

Create a Solution Design with AI

What the skill produces#

Prerequisites#

1. Request the skill from your KAM#

2. Install it in your agent#

3. Connect live Cobre documentation#

How to use it#

Keep the skill current#

Related guides#

Example#

What the skill produces

Prerequisites

1. Request the skill from your KAM

2. Install it in your agent

3. Connect live Cobre documentation

How to use it

Keep the skill current

Related guides

Example