fix: correct client support claims across package metadata - #19
Merged
Conversation
The plugin and npm manifests described stitch-kit as a Claude Code tool. The installer has handled seven clients for months — Claude Code, Codex CLI, OpenCode, Crush, Cursor, VS Code, Gemini CLI — at three different tiers depending on what each host accepts. Anyone reading the plugin browser or the npm page was told less than they were getting. - Align descriptions across npm, both plugin manifests, and the marketplace - Add a "Works with" table tiered by real capability, verified against `stitch-kit status` output rather than the client table in the source - Lead the README with four real generated screens above the install command; it previously shipped only SVG diagrams, which is a poor look for a tool that argues about aesthetic quality - Move the Google Stitch account requirement above the install command instead of 170 lines below it, and state the access reality - Log the screenshot resolution quirk: get_screen returns a 512px thumbnail while reporting 2560x2048, unless you append =s0 to the download URL - Add opencode, cursor, crush, gemini-cli to npm keywords - Ignore .omc/, which is local agent state
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The plugin and npm manifests described stitch-kit as a Claude Code tool. The installer has handled seven clients for months, at three different tiers depending on what each host accepts. Anyone reading the plugin browser or the npm page was told less than they were getting.
What changed
Client support, stated honestly. New "Works with" table, tiered by real capability and verified against
stitch-kit statusoutput rather than the client table in the source:Descriptions aligned across npm, both plugin manifests, and the marketplace. Added
opencode,cursor,crush,gemini-clito npm keywords.Real output above the fold. The README previously shipped three hand-authored SVGs — a banner, a pipeline diagram, an architecture diagram — and zero screenshots of anything stitch-kit produced. For a tool that argues about aesthetic quality, that's a bad look. Four real generated screens now sit above the install command, chosen for range: 2 desktop / 2 mobile, 2 light / 2 dark.
Dependency disclosed up front. The Google account and API key requirement moved from Prerequisites (170 lines down) to above the install command, with the actual access situation stated — no waitlist, free as of mid-2026, monthly generation limits, paid tiers signalled.
Troubleshooting entry for a Stitch API quirk that cost real time:
get_screenreports a screen as 2560x2048 and then serves a 512px thumbnail unless you append=s0to the download URL. No error, no warning.Note on the commit type
fix:rather thandocs:deliberately. Evidence from this repo's history:docs:andchore:commits appear in changelogs but never trigger a release on their own — twochore:commits sat on main for two months without cutting 1.10.1. The corrected metadata only reaches npm and the plugin browser if a release ships, and shipping wrong compatibility claims is the thing being fixed.Merging this cuts 1.11.1.