Plugin Claude Code
Bundles 2 skills · 151 tokens together
Let your AI assistant scaffold and extend Better Fullstack projects through the official MCP server and focused skills.
11 tagged full-stack, measured the same way as everything else here.
Browse within: mcp-server 7programming 5vibecoding 5
Plugin Claude Code
Bundles 2 skills · 151 tokens together
Let your AI assistant scaffold and extend Better Fullstack projects through the official MCP server and focused skills.
Plugin Claude Code
Bundles 2 skills · 82 tokens together
Discover project boilerplates and create new applications with scaffold-mcp.
Plugin Claude Code
Bundles 8 skills · 193 tokens together
Production-ready skills including ralph-invoke (Claude-initiated autonomous loops), code-review, dev-workflow, git-workflow, security-scan, and more.
Plugin Claude Code
Bundles 3 commands, 1 MCP server · 40 tokens together
Build, iterate on, deploy, and manage Lovable apps from Claude Code. Bundles the official Lovable MCP server (remote, OAuth 2.1) and adds focused commands for the common build/iterate/database workflows, with credit- and publish-safety prompts.
Plugin Claude Code
Bundles 4 skills · 335 tokens together
Skills for building and verifying Nifra apps: contract-first APIs, full-stack SSR on five UI libraries, and the check/assure/capabilities gates. Prefers Nifra's live MCP server over model recall.
vaquarkhan/Fullstack-development-agent-skills
Plugin Claude Code
Bundles 129 skills, 10 commands · 5,059 tokens together
Fullstack UI, backend, microservice, and cloud delivery skills for Claude Code.
Plugin Claude Code
Bundles 1 command · 19 tokens together
Build, deploy, and operate apps on the OBTO platform — one MCP connection (Google sign-in, auto-provisioned workspace), a /obto:start session command, plus skills for the build loop, large-file deploys (patch-in-place, chunked, and deploy-by-reference), media/binary upload (signed-URL and chunked), agent memory…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: