Kimliss Claude Code Inhand
kimliss-claude-code-inhand is a Claude Code plugin marketplace bundle for the Build phase that ships 11 stack-focused plugins so full-stack solo builders get scaffolding, patterns, and devops helpers without assembling s
Install a single Claude Code plugin bundle that adds stack-specific skills and workflows across React, Vue, Flutter, Python, Java, Go, Docker, and Kubernetes so you do not hunt repos one language at a
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install kimliss-claude-code-inhand@kimliss/claude-code-inhandBuilt 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:kimliss/claude-code-inhand") and the paste-ready config with skillselion.get_install_config("plugin:kimliss/claude-code-inhand").
What it does
kimliss-claude-code-inhand is a curated Claude Code plugin collection marketed as everything at your fingertips for day-to-day development. The catalog lists 11 plugins spanning web (React, Next, Vue), mobile (Flutter, iOS/Swift, Kotlin/Jetpack Compose), backend (Python with Django/FastAPI, Java/Spring), Go-specific tooling, databases, and devops (Docker, Kubernetes, IaC). Solo builders who jump between a SaaS API, a mobile client, and deployment scripts can register one marketplace entry instead of assembling separate skill packs per stack. Plugins emphasize scaffolding, schema and query work, migration, language-server alignment, hooks, and workflow automation so sessions stay consistent across projects. It is strongest when you already know what you are building and want agent-native guardrails per ecosystem, not when you still need market validation or distribution playbooks. Complexity is intermediate because you must pick the right sub-plugin for each repo and keep Claude Code updated.
Highlights
- 11-plugin bundle covering React/Next, Vue, Flutter, iOS/Swift, Android/Compose, Python/Django-FastAPI, Java/Spring, Go,
- Language-server oriented keywords (pyright, gopls, jdtls, sourcekit-lsp) signal IDE-quality assistance inside Claude Cod
- Cross-cutting topics: database schema/migration/query, Docker/Kubernetes, infrastructure-as-code, and component/state pa
- Hooks, contexts, and workflow plugins for repeatable agent routines beyond one-off prompts.
- Broad keyword surface (scaffolding, optimization, patterns, toolkit) for full-stack solo builders shipping multiple prod
Why builders use it
Jumping between React, mobile, Python, Java, Go, and Kubernetes repos means constantly reinstalling or rediscovering Claude Code skills that match each stack.
After you add the bundle, Claude Code gains a wide multi-language toolkit—components, servers, queries, containers, and workflows—aligned to the stack you name in the session.
At a glance
- Type - Plugin in Development Tools.
- Adoption - 0 installs, 0 stars, 0 votes.
FAQ
Who is kimliss-claude-code-inhand for?
It is for solo and small-team developers using Claude Code who ship across several stacks and want bundled skills for frontend, backend, mobile, database, and devops in one place.
When should I use kimliss-claude-code-inhand?
Use it when you start or maintain real product code—scaffolding UI, APIs, migrations, or deployment files—and want stack-specific agent behavior instead of generic coding advice.
How do I add kimliss-claude-code-inhand to my agent?
In Claude Code, add or register the kimliss/claude-code-inhand marketplace or plugin source from the repo, install the bundle, then enable the individual plugins that match your current project stack.
Comments
Share how you use kimliss-claude-code-inhand, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.