Skip to content

feat(maxio-sdk-clone): experimental map-in-clone plugin variant#2

Open
mohammadali2549 wants to merge 2 commits into
dev-rawfrom
feat/maxio-sdk-clone
Open

feat(maxio-sdk-clone): experimental map-in-clone plugin variant#2
mohammadali2549 wants to merge 2 commits into
dev-rawfrom
feat/maxio-sdk-clone

Conversation

@mohammadali2549

Copy link
Copy Markdown
Collaborator

Add an experimental maxio-sdk-clone plugin (map-in-clone variant)

Adds a new experimental plugin, maxio-sdk-clone, forked from maxio-sdk (v0.2.0). It tests a
different way of delivering the SDK map: instead of bundling the generated map inside the plugin,
the map ships inside the SDK's own source, and the agents clone the SDK to read it.

What changes vs maxio-sdk

  • The bundled map is removed from the plugin (sdk-map.md + map/, ~4,180 lines). It is read
    from <clone>/sdk-map.md + <clone>/map/ instead.
  • maxio-plan clones the SDK first (gains Bash) and grounds against the map that ships with the
    source, opening the exact source file the map names only when the map genuinely can't settle a fact.
    maxio-debug reuses that clone via the shared temp .maxio-session.md.
  • A hard anti-spelunk guard in both agents + maxio-getting-started: map first, always; open only
    the exact file the map's row names, scoped; grepping/globbing/find-ing the tree to locate
    something is a defect
    — the map is the locator.
  • Main-agent fallback for a missing fact is now ask the warm maxio-plan agent (the map no longer
    lives in the plugin for the main agent to read).
  • The clone stays hidden from the main agent (temp-only, path never enters maxio-plan.md); the
    version pin is dropped (the map co-versions with the source by construction).

Why

Probes the middle ground between the bundled-map maxio-sdk and the map-less upstream plugin: does
co-locating a fresh, always-in-sync map with the source (source always at hand) beat bundling? It also
realizes the generator's stated end-state — the map generated and shipped alongside the SDK.

Notes for review

  • Additive: the baseline maxio-sdk plugin is untouched, so the experiment's baseline
    comparability is intact. Targets dev-raw (the experimental line); main stays frozen.
  • claude plugin validate --strict passes for both the plugin and the marketplace manifest.
  • During the experiment the agents clone the fork/branch that carries the map
    (mohammadali2549/advanced-billing-sample-sdk @ docs/sdk-map, PR pending); once that map is
    merged upstream this points to the canonical asadali214/advanced-billing-sample-sdk at a tag.
  • Caveat: maxio-sdk-clone shares skill/agent names with maxio-sdk — don't install both at once
    (noted in its marketplace description). Fine for the experiment (arms install one plugin at a time).

🤖 Generated with Claude Code

mohammadali2549 and others added 2 commits July 17, 2026 07:29
Forks maxio-sdk (v0.2.0) into a new experimental plugin, maxio-sdk-clone, that reads the SDK map from the SDK source clone instead of bundling it. maxio-plan clones the SDK first (gains Bash) and grounds against the shipped-with-source map, with a source fallback under a hard anti-spelunk guard; maxio-debug reuses the clone. Additive — baseline maxio-sdk untouched; targets the experimental dev-raw line. claude plugin validate --strict passes for plugin + marketplace.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Remove prior-version comparative framing ("not bundled", "unlike the bundled-map plugin", "in this variant", "variant of maxio-sdk") from the consumer-facing skills, agents, README, and manifests — from a fresh consumer's perspective it is bloat. Behavior is now stated positively: the SDK map ships with the SDK source; the agents clone and read it from there.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant