Skip to content

fix: correct style and stack counts in plugin.json description#282

Open
xiaolai wants to merge 1 commit intonextlevelbuilder:mainfrom
xiaolai:fix/nlpm-plugin-json-count-mismatch
Open

fix: correct style and stack counts in plugin.json description#282
xiaolai wants to merge 1 commit intonextlevelbuilder:mainfrom
xiaolai:fix/nlpm-plugin-json-count-mismatch

Conversation

@xiaolai
Copy link
Copy Markdown

@xiaolai xiaolai commented Apr 26, 2026

Automated audit: This PR was generated by NLPM, a natural language programming linter, running via claude-code-action. Please evaluate the diff on its merits.

Bug

The marketplace description in `.claude-plugin/plugin.json` contains two count mismatches:

  1. Styles: Claims "67 styles" — the actual `src/ui-ux-pro-max/data/styles.csv` contains 84 entries (84 rows, excluding header).
  2. Stacks: Claims "15 stacks" — the description itself enumerates exactly 12 stacks: React, Next.js, Vue, Svelte, Astro, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui, Nuxt, Jetpack Compose.

Why it matters: The plugin description is what users see on the Claude marketplace. Overstating the database size sets incorrect expectations — users expect 67 styles and 15 stacks but the documented and installed database is different.

Fix: Update the description to `84 styles, 12 stacks` to match the authoritative data. The stacks listed in the description itself count to 12, so no stack list changes are required.

The marketplace description claimed "67 styles, 15 stacks" but:
- styles.csv contains 84 style entries (actual count)
- The description itself lists exactly 12 stacks, not 15

Update to "84 styles, 12 stacks" to match the actual data.

Co-Authored-By: Claude Code <[email protected]>
@xiaolai xiaolai force-pushed the fix/nlpm-plugin-json-count-mismatch branch from d967fb6 to 8572ba7 Compare April 26, 2026 06:53
@xiaolai xiaolai changed the title fix: correct stack count in plugin.json from 15 to 12 fix: correct style and stack counts in plugin.json description Apr 26, 2026
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