Whinc My Claude Plugins
whinc-my-claude-plugins is a Claude Code plugin for the Build phase that bundles four personal development plugins for frontend, diagram, generator, git, and Taro-oriented work.
by whinc · github.com/whinc/my-claude-plugins
Load a personal four-plugin Claude Code toolkit spanning React hooks (ahooks), diagrams (drawio), generators, git helpers, and Taro mini-program work.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install whinc-my-claude-plugins@whinc/my-claude-pluginsBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:whinc/my-claude-plugins") and the paste-ready config with skillselion.get_install_config("plugin:whinc/my-claude-plugins").
What it does
whinc-my-claude-plugins is a personal Claude Code plugin collection described as “Personal claude plugins” and packaged as four plugins in the whinc/my-claude-plugins repository. Catalog keywords—ahooks, drawio, generator, git, and taro—suggest a builder who ships React-style frontends, documents flows in diagrams, scaffolds code, manages git operations, and sometimes targets Taro cross-end mini programs. For Skillselion’s solo-builder audience, this entry is best understood as a small, opinionated toolchain you adopt when your stack overlaps that author’s: you get multiple agent affordances in one install path rather than a single hyper-focused skill. It does not replace official Claude or framework docs; it accelerates repetitive build-phase chores inside the agent. Expect intermediate familiarity with those ecosystems. Validate each plugin’s behavior against your repo conventions before trusting generators or git automation on main.
Highlights
- Personal plugin pack: 4 plugins in one repository (pluginCount: 4)
- Coverage hints: ahooks, drawio, generator, git, and taro mini-program tooling
- Community bundle for whinc’s own Claude Code workflows—not a vendor marketplace
- Useful when you mirror a solo full-stack stack: web UI, diagrams, and mobile-ish targets
- Install as a curated set instead of hunting one-off skills per task
Why builders use it
You waste session time reinstalling or re-explaining the same personal Claude helpers for React hooks, diagrams, git, and mini-program tasks.
After registering the bundle, you have four named plugins available in Claude Code aligned with a full-stack indie frontend and tooling workflow.
At a glance
- Type - Plugin in Development Tools.
- Adoption - 0 installs, 10 stars, 0 votes.
FAQ
Who is whinc-my-claude-plugins for?
It is for developers who want whinc’s personal Claude Code plugins—especially around frontend, diagrams, generators, git, and Taro—in one repository.
When should I use whinc-my-claude-plugins?
Use it during build and docs work when you already use similar tools and want agent shortcuts bundled instead of configuring each helper separately.
How do I add whinc-my-claude-plugins to my agent?
Follow the install steps in github.com/whinc/my-claude-plugins to register all four plugins in Claude Code, then enable only the pieces that match your project.
Comments
Share how you use whinc-my-claude-plugins, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.