Lttr Claude Marketplace
lttr-claude-marketplace is a Claude Code plugin marketplace for the Build phase that packages six workflow plugins for Nuxt/Vue development, Azure DevOps, browser automation, media tooling, and structured reviews.
by lttr · github.com/lttr/claude-marketplace
Install lttr’s six-plugin marketplace to reuse battle-tested Claude Code flows for Nuxt/Vue work, Azure DevOps, browser automation, media, and spec-driven reviews.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install lttr-claude-marketplace@lttr/claude-marketplaceBuilt 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:lttr/claude-marketplace") and the paste-ready config with skillselion.get_install_config("plugin:lttr/claude-marketplace").
What it does
lttr-claude-marketplace is a personal-but-shareable Claude Code plugin collection: six plugins distilled from workflows its author actually runs while building Nuxt/Vue products, talking to Azure DevOps, drafting Confluence specs, driving headless or Chrome browsers, and processing video with ffmpeg or ElevenLabs transcription. Solo builders who mirror that stack—modern Vue frontend, structured commits, agent-assisted reviews, and occasional content artifacts—get named skills and commands instead of rebuilding prompts. The marketplace spans more than one journey moment: frontend build patterns, integration calls, and ship-time review or testing hooks all appear in the keyword surface. It is a plugin bundle, not an hosted agent platform; you register it in Claude Code and enable only the plugins you need. Complexity is intermediate because several plugins assume framework literacy (Nuxt ecosystem) and optional cloud credentials for Azure or media APIs. Tags lean Build/integrations with secondary frontend and ship/testing placement for review and automated check flows.
Highlights
- Six plugins extracted from real lttr development workflows—not generic templates
- Nuxt, Nuxt UI, Vue, Pinia, and VueUse-oriented patterns and auto-import awareness
- Azure DevOps and Confluence integration flows for specs, triage, and devops rituals
- Browser and Puppeteer/Chrome automation plus ffmpeg and video transcription pipelines
- Commitlint conventions, code-review commands, and artifact authoring for lectures and articles
Why builders use it
Rebuilding the same Claude prompts for Nuxt commits, Azure tickets, browser checks, and video pipelines wastes time on every new repo.
After adding the marketplace, you enable targeted plugins that encode lttr’s conventions for framework work, integrations, and review in one installable set.
At a glance
- Type - Plugin in Development Tools.
- Adoption - 0 installs, 2 stars, 0 votes.
FAQ
Who is lttr-claude-marketplace for?
Claude Code users shipping Nuxt/Vue software who also touch Azure DevOps, structured commits, browser automation, or media transcription in their routine.
When should I use lttr-claude-marketplace?
Use it when starting or standardizing a project that matches lttr’s toolchain—enable individual plugins for frontend patterns, DevOps integration, review, or video workflows as needed.
How do I add lttr-claude-marketplace to my agent?
Add lttr/claude-marketplace as a Claude Code plugin source, install the marketplace, then turn on whichever of the six plugins fit your repo and credentials.
Comments
Share how you use lttr-claude-marketplace, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.