mcpField
M
mayar-v2

mayar-v2

github.com/mayaridDevelopment14105 installsUpdated 8w ago
Repository

About mayar-v2

mayar-v2 is an agent skill for building Mayar integrations, managing accounts from the terminal, and answering Mayar questions. It routes each request through separate BUILD, OPS, and LEARN procedures.

Key features

  1. 01BUILD, OPS, and LEARN request routing
  2. 02Phased integration planning and implementation
  3. 03Terminal-based account management
  4. 04Documentation-based answers without changes

Use cases

  1. 01Add Mayar payment integration to an application
  2. 02Manage or test a Mayar account from a terminal
  3. 03Answer questions about Mayar using its documentation

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/mayarid/skills --skill mayar-v2

After installing, type/mayar-v2in Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

playbook/
discover.md
implement.md
plan.md
verify.md
references/
api-sources.md
checkout-embedded.md
checkout-native.md
checkout-types.md
cli-commands.md
product-knowledge.md
stack-nextjs.md
stack-pattern.md
stack-tanstack-start.md
stack-vite-react.md
webhook-safety.md
scripts/
validate.mjs

Details

From the project README

Mayar

Select one branch from the user request:

  • BUILD — Add a Mayar integration to an application. This branch includes the UI, server, persistent data, and fulfillment.
  • OPS — Manage or test a Mayar account from the terminal.
  • LEARN — Answer a question about Mayar itself. This branch reads documentation and changes nothing.

A live call is an agent command against the Mayar account. Use npx -y mayar@latest for every live call. Application code uses the HTTP API. Read references/cli-commands.md for CLI syntax. If a BUILD documentation fetch or HTTP probe fails, take that CLI path and continue the phase.

LEARN

Read references/product-knowledge.md. Follow only that file. Do not load the BUILD playbook. Do not run CLI commands. Do not change any file.

OPS

Read references/cli-commands.md. Follow the OPS procedure in that file. Do not load the BUILD playbook.

BUILD: strict phase gates

Complete one phase at a time. Do not read the next phase file until you meet the completion criteria for the current phase. Load references/cli-commands.md before a live call.

Phase 1 — Discover

Read playbook/discover.md. Stay in this phase until RECON is complete and all user decisions are recorded.

Phase 2 — Plan

After Discover is complete, read playbook/plan.md. Stay in this phase until you record the schema or a CLI path. The user must also approve the plan and the exact fulfillment operation.

Phase 3 — Implement

After explicit approval, read playbook/implement.md. Stay in this phase until all planned changes are complete and all project checks pass.

Phase 4 — Verify

After Implement is complete, read playbook/verify.md. Complete the sandbox evidence, regression checks, and handoff before you close the task.

Comments

Markdown supported