Alvis .Claude
alvis-.claude is a Claude Code plugin collection for the Build phase that bundles six agents, commands, and integrations for full-stack development, specs, and Notion-linked workflows.
by alvis · github.com/alvis/.claude
Install a curated six-plugin Claude Code toolkit covering specs, React/Next.js work, browser flows, Notion, and general implementation support for full-stack solo builds.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install alvis-.claude@alvis/.claudeBuilt 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:alvis/.claude") and the paste-ready config with skillselion.get_install_config("plugin:alvis/.claude").
What it does
alvis/.claude packages six Claude Code plugins into a curated workflow library for builders who want agents, slash-style commands, and integrations in one place instead of hunting disparate repos. Catalog keywords point at a full-stack indie stack: React and Next.js implementation, browser-assisted checks, Notion for specs and knowledge, plus governance-flavored themes like requirements, architecture, and quality. That makes the bundle useful from early specification through frontend build and into testing-minded ship habits, even though the canonical Skillselion shelf stays in build agent-tooling because the value is extending Claude Code’s execution surface. Solo founders can lean on it when they are simultaneously writing specs, spinning UI, and wiring integrations without a platform team. Stars and install signals are small; treat it as a personal or team starter kit you selectively enable per plugin rather than an enterprise-certified distribution channel.
Highlights
- Six plugins in one curated .claude repo spanning agents, commands, and integrations
- Full-stack and Next.js/React-oriented capabilities including component and rapid prototyping flows
- Browser-related tooling for web verification and interaction during development
- Notion integration for specs, knowledge, and product documentation alongside code
- Coverage threads for architecture, requirements, testing, quality, and technical writing
Why builders use it
Solo builders stitching React, Next.js, browser checks, and Notion specs waste time installing fragmented Claude Code extensions with inconsistent commands and overlap.
After adding the six-plugin collection, Claude Code sessions can draw on a coordinated set of dev agents and integrations for specs, implementation, browser work, and documentation in one repo.
At a glance
- Type - Plugin in Development Tools.
- Adoption - 0 installs, 3 stars, 0 votes.
FAQ
Who is alvis-.claude for?
It is for Claude Code users doing full-stack product work who want a small curated library of agents, commands, and integrations including React, Next.js, browser, and Notion-related tooling.
When should I use alvis-.claude?
Use it during build when you are drafting specs, implementing UI, integrating Notion knowledge, or running browser-backed checks, and during ship when you lean on included testing and quality-oriented commands.
How do I add alvis-.claude to my agent?
Point Claude Code at the alvis/.claude repository as your plugin source, enable the individual plugins you need from the six-plugin set, and configure any Notion or browser credentials each plugin requires.
Comments
Share how you use alvis-.claude, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.