marketplace.rkito.com

Put your design intent where the work happens.

A2D plugins and set-ups for Claude Code, VS Code, GitHub Copilot, Cursor and the command line. Steering packs for the standards you follow and the integration patterns your vendors recommend. Product packs that put those vendors' APIs, UI components and data models into your Architecture Ledger. Everything installs through your normal design review.

Try

claude code · A2D plugin~/acme/payments

> /plugin install rkito
✓ rkito plugin 0.9.2 installed
✓ MCP server connected · org acme
✓ Steering Ledger · 212 lenses available
✓ Architecture Ledger · 41 systems

> /rkito scope payments-api
  in scope     payments-api  (PCI)
  downstream   ledger-service, notifications,
               finance-reporting
  lenses       14 loaded for this session

Illustrative mock of the Claude Code A2D plugin (early access). Command names, version and counts are sample data, not real output.

IDEHints and scope while you edit

AgentLenses loaded into every session

LedgerStandards and systems, pre-mapped

PR gateDesign audit on every pull request

WorkflowReviews and alerts in your tools

Built by rkito

Official plugins and extensions.

One connection to your org's ledgers, available in every tool your engineers and agents use. Each extension reads the same Steering and Architecture record, so a session in Cursor and a pull request audit agree.

CCEarly accessFree

A2D plugin for Claude Code

plugin · catalog · terminal and VS Code extension

Iterate on designs against your approved ADRs, policies and current architecture, then implement within the approved scope as Claude writes. Built and running on rkito's engineering environment.

AgentView →

VSComing soonFree

A2D extension for VS Code

extension

Planned: bring the A2D session into the VS Code sidebar, with scope and downstream dependencies in view.

IDEView →

CpComing soonFree

A2D set-up for GitHub Copilot

VS Code and CLI

Planned: connect GitHub Copilot, in VS Code and on the command line, to your ledgers through A2D.

IDE · AgentView →

CuComing soonFree

A2D set-up for Cursor

desktop · CLI · cloud agents

Planned: connect Cursor's desktop app, CLI and cloud agents to your ledgers through A2D.

IDE · AgentView →

CLComing soonFree

@rkito/cli helper

command line

Planned: a command line helper for setting up A2D and working with your ledgers from the terminal.

WorkflowView →

GHAvailableFree

rkito GitHub App

app · PR checks

Runs a Continuous Design Audit on every pull request and posts findings inline. No YAML.

PR gateView →

GAAvailableFree

rkito CDA Action

GitHub Actions step

The same audit as a single workflow step, for teams that keep every gate in their pipeline file.

PR gateView →

Only the Claude Code plugin is built (early access, on rkito's engineering environment). VS Code, GitHub Copilot, Cursor and the command line are placeholders, coming soon. Other statuses are illustrative and may change before launch. rkito's own listings are shown as Free (included with your rkito plan).

What the IDE extensions do

Change your systems without breaking your norms.

The Claude Code plugin, IDE extensions and MCP server bring your approved ADRs, policies, patterns and best practices from the Steering Ledger into design sessions, along with the current reality of your Architecture Ledger. Iterate on options with Claude. Each one is checked against what's already decided, so design thinking stays fast and lands inside your guardrails.

Claude Code · rkito plugin · design explorationscope payments-api

YouWe need partial refunds in checkout. What's the cleanest design?

Option A

checkout-web calls Ledgerly directlyconflicts

Fewest moving parts. Breaks an approved decision and the vendor's guidance.

✕ADR-022Only payments-api talks to payment providers.
✕LP-IDEMLedgerly writes need an idempotency key the browser can't hold safely.

Option B

New /v3/refunds on payments-api1 open question

Respects ownership, but changes a response shape three systems depend on.

✓ADR-022Provider calls stay in payments-api.
?BP-API-07Breaking change. checkout-web, support-console and finance-reporting would migrate.

Option C

Additive /v2 field plus refund.partial eventfits

payments-api calls Ledgerly with an idempotency key, adds partial_amount to /v2 and publishes refund.partial through the outbox.

✓LP-IDEMFollows the Ledgerly integration pattern.
✓BP-API-07Additive change. No new version needed.
✓PAT-004Cross-service event goes through the outbox.

17 of 17 lenses satisfied · 3 downstream systems notedDraft CHI-0142 →

Illustrative mock with sample decisions. Ledgerly is a fictional vendor.

Think wide, land inside the lines

Explore bold options. rkito shows which decisions each one respects or breaks, so you weigh trade-offs with facts, not memory.

Every trade-off cites its source

Findings name the ADR, policy, pattern or vendor guidance and the systems affected, so the discussion starts from what's already agreed.

Ends in a Change Intention

The chosen design goes to human review. Once approved, it is the scope the agent implements and the PR gate checks.

Browse by ledger

Start where your org is today.

Most teams begin with a Steering pack and an Architecture connector, then add the PR gate. The marketplace follows the same path.

Steering Ledger

Steering packs

Best practices, policies and integration patterns, already resolved into Lenses. From standards bodies and from the vendors you integrate with.

Architecture Ledger

Product packs and connectors

Your vendors' products as external systems, plus connectors that map your own systems from where they already live.

Code Ledger

PR gate

Run the Continuous Design Audit where your pull requests and pipelines already run.

Sessions

Agent and IDE

Bring ledger context into Claude Code, VS Code, GitHub Copilot, Cursor and the command line.

Illustrative. Statuses on the Agent and IDE list are real; the other lists, and every Verified publisher named, are sample data.

Product packs

Install the products you integrate with.

A partner's product arrives in two parts. The product pack describes what the product is: its UI components, APIs, data models, events and integration scenarios. It lands in your Architecture Ledger as an external system. Its companion Steering pack describes how to integrate with it well, as code patterns and Lenses in your Steering Ledger.

Architecture Ledger · what it is

Ledgerly PaymentsProduct pack · v2026.09 · Verified partner

UICheckout element · web, iOS, Android

APIPOST /v3/charges · POST /v3/refunds · 38 more · OpenAPI 3.1

DataCharge, Refund, Customer · 14 models

Eventscharge.succeeded · refund.updated · 22 events

ScenariosAccept a card payment · Issue a partial refund · Save a card · 9 more

Steering Ledger · how to use it

Ledgerly integration patternsSteering pack · v2026.09 · Verified partner

PatternSend an idempotency key on every write request

PatternVerify webhook signatures before parsing the body

PracticeStore amounts in minor units with an explicit currency

PolicyCard data never reaches your servers. Use the Checkout element.

Lenses17 yes-or-no checks · run in the IDE and at the PR gate

In the ledgerLedgerly is an external system

payments-api and checkout-web show it as a dependency, with the exact interfaces they use.

In the IDEAgents follow the scenario

When Claude builds partial refunds, it loads the vendor's scenario and patterns before it writes code.

At the PR gateMisuse is caught before merge

A webhook handler that skips signature verification is blocked, with the vendor's pattern cited.

Illustrative mock. Ledgerly is a fictional vendor used as sample data.

All listings

Catalog

Filter by what it adds and who publishes it. Official and Verified listings pass rkito's certification before they appear here.

Put your design intent where the work happens.

Official plugins and extensions.

A2D plugin for Claude Code

A2D extension for VS Code

A2D set-up for GitHub Copilot

A2D set-up for Cursor

@rkito/cli helper

rkito GitHub App

rkito CDA Action

Change your systems without breaking your norms.

checkout-web calls Ledgerly directlyconflicts

New /v3/refunds on payments-api1 open question

Additive /v2 field plus refund.partial eventfits

Think wide, land inside the lines

Every trade-off cites its source

Ends in a Change Intention

Start where your org is today.

Steering packs

Product packs and connectors

PR gate

Agent and IDE

Install the products you integrate with.

Catalog

A2D plugin for Claude Code

A2D extension for VS Code

A2D set-up for GitHub Copilot

A2D set-up for Cursor

@rkito/cli helper

OWASP Top 10

AWS Well-Architected

ISO 27001 Annex A

PCI DSS 4.0

Secure API design

Event-driven patterns

Payments patterns

Ledgerly integration patterns

Beacon Identity integration patterns

Ledgerly Payments

Beacon Identity

Parcelpoint Shipping

Quarry Search

Northwind Design System

OpenAPI importer

Terraform and Helm

AsyncAPI importer

Service catalog sync

Data model importer

rkito GitHub App

rkito CDA Action

Slack findings

Confluence import

Jira change intentions

Nothing enters your ledger without a human approving it.

Three kinds of publisher, clearly marked.

Built by rkito

Certified by rkito

Shared by the community

Kits for a specific goal.

Agent-ready starter

Integrate a payments provider

Turn on the gate

Build for teams getting ready for agentic engineering.