Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By lennetech
Skills & Commands for analyzing software projects and creating showcases on showroom.lenne.tech — MCP tools for showcases, screenshots, analytics, and content management
npx claudepluginhub lennetech/claude-code --plugin lt-showroomAnalyze a software project and create a versioned SHOWCASE.md with features, architecture, and screenshot paths. If screenshots exist in docs/showcase/screenshots/, reference them. Otherwise, use placeholder paths that match the naming convention.
Read SHOWCASE.md, fetch customer feedback and web research, then create and publish a detailed showcase on showroom.lenne.tech with modern interactive content blocks
Start the project (Docker or dev server), create demo data, and capture feature screenshots saved to docs/showcase/screenshots/
Update content block schemas and showcase model reference docs from the showroom API and project source code
Detect source code changes via tree hash comparison, re-analyze only affected areas, update SHOWCASE.md and refresh the showcase on showroom.lenne.tech
Autonomous agent for deep source code analysis of software projects. Analyzes all 8 dimensions (tech stack, architecture, features, API, testing, UI/UX, security, performance), detects how the application starts (Docker/npm/pnpm), inventories all pages and views for screenshot planning, and extracts a feature list with file:line evidence. Can create SHOWCASE.md in the project repository. Spawned by showroom:analyze and showroom:create commands.
Autonomous agent for capturing feature screenshots of running projects. Reads SHOWCASE.md to determine which features and pages to capture. Starts the project via Docker Compose (preferred) or npm/pnpm dev server. Creates realistic demo data via seed script or Chrome DevTools MCP. Captures desktop (1440x900) and mobile (390x844) screenshots per feature and saves them to docs/showcase/screenshots/. Spawned by showroom:screenshot command.
Analyzes software projects to extract technology stack, architecture, features, API surface, testing strategy, UI/UX patterns, security measures, and performance optimizations. Produces structured, evidence-based reports where every claim is backed by a source code reference. Also detects how the application is started (scripts, Docker, database requirements) and enumerates all pages and views for screenshot planning. Outputs a structured report that feeds directly into SHOWCASE.md creation and screenshot automation. Activates when analyzing a project for showroom showcases, portfolio entries, project documentation, or when a user asks what a project does or how it is built. NOT for creating or publishing showcases (use creating-showcases). NOT for platform development (use generating-nest-servers).
Creates, updates, and manages showcases on the lenne.tech Showroom platform (showroom.lenne.tech). Implements a 5-phase workflow: (1) project analysis, (2) screenshot capture with Docker/app startup and demo data, (3) SHOWCASE.md creation as single source of truth in the project repository, (4) showcase creation via API using SHOWCASE.md + customer feedback + web research, (5) interactive presentation with modern content blocks. Fetches customer feedback from https://lenne.tech/kundenerfolge. Uses MCP tools (showroom-api) or REST API for CRUD operations. Activates when creating, editing, managing showcases, portfolio entries, or the Showroom platform. NOT for platform development on the showroom codebase itself (use generating-nest-servers or developing-lt-frontend).
External network access
Connects to servers outside your machine
Uses power tools
Uses Bash, Write, or Edit tools
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Project health and permission management, dev sessions, team updates with feedback triage, GitHub releases, multi-model brains trust, git workflows, UX audits, responsive layout testing, and browser automation.
A curated collection of AI coding agent skills for browser automation, frontend design, performance auditing, task tracking, and structured problem-solving workflows.
Give soul to your workflow. 58 AI-powered skills across 17 roles — PM, Dev, Backend, Frontend, QA, UX, Data, Detect, WordPress, Release, Security, DevOps, and Core. Spec-to-ship pipeline: scaffold, implement, test, secure, deploy. Features two-phase workflow with human approval, quality-reviewer agent, token optimization, and continuous improvement via LEARN.md system.
Production-ready Claude Code configuration with role-based workflows (PM→Lead→Designer→Dev→QA), safety hooks, 44 commands, 19 skills, 8 agents, 43 rules, 30 hook scripts across 19 events, auto-learning pipeline, hook profiles, and multi-language coding standards
Use this agent when evaluating new development tools, frameworks, or services for the studio. This agent specializes in rapid tool assessment, comparative analysis, and making recommendations that align with the 6-day development cycle philosophy. Examples:\n\n<example>\nContext: Considering a new framework or library
Development agents, skills, hooks, and commands for Claude Code workflows
Skills & Commands for creating and managing business offers on angebote.lenne.tech — MCP tools for offers, knowledge base, analytics, and content management
lenne.tech Development Skills, Commands and Hooks for Claude Code - Frontend (Nuxt 4), Backend (NestJS), TDD and CLI Tools
No model invocation
Executes directly as bash, bypassing the AI model
No model invocation
Executes directly as bash, bypassing the AI model
Share bugs, ideas, or general feedback.
Claude Code Plugins by lenne.tech.
# Install CLI if not already installed
npm i -g @lenne.tech/cli
# Install or update ALL available plugins
lt claude plugins
# Install or update specific plugin(s)
lt claude plugins lt-dev
lt claude plugins lt-dev another-plugin
# List available plugins (shown on error if plugin not found)
lt claude plugins non-existent
The CLI automatically:
~/.claude/settings.json# Add marketplace
/plugin marketplace add lenneTech/claude-code
# Install plugin
/plugin install lt-dev@lenne-tech
Note: Manual installation requires you to configure permissions yourself. Copy the permission patterns from plugins/lt-dev/permissions.json into ~/.claude/settings.json:
{
"permissions": {
"allow": [
// Copy patterns from permissions.json
]
}
}
If the file already exists, merge the allow entries with your existing permissions. See plugins/lt-dev/permissions.json for the current list of required permissions.
Skills, Commands, Hooks and Agents for Frontend (Nuxt 4), Backend (NestJS/nest-server), TDD and CLI Tools.
| Skill | Description |
|---|---|
developing-lt-frontend | Nuxt 4, Nuxt UI 4, TypeScript, Valibot Forms |
generating-nest-servers | NestJS with @lenne.tech/nest-server |
building-stories-with-tdd | Test-Driven Development Workflow |
nest-server-updating | Migration guides and strategies for @lenne.tech/nest-server updates |
rebasing-branches | Rebase workflows for feature branches onto dev/develop |
general-frontend-security | OWASP-based frontend security (XSS, CSRF, CSP) |
coordinating-agent-teams | Agent Teams coordination and parallel workflows |
using-lt-cli | lenne.tech CLI for Git and Fullstack Init |
maintaining-npm-packages | Discovery skill for npm package maintenance commands |
developing-claude-plugins | Plugin development best practices and validation |
| Agent | Description |
|---|---|
npm-package-maintainer | Maintaining, updating, and auditing npm packages |
nest-server-updater | Automated @lenne.tech/nest-server version updates with migration |
fullstack-updater | Synchronize fullstack project with latest starter templates |
branch-rebaser | Autonomous rebase execution for feature branches |
code-reviewer | Single-pass code review across 6 quality dimensions |
Root:
/create-ticket - Create Linear Ticket (Story, Task, or Bug)/create-story - Create User Story for TDD (German)/create-task - Create Technical Task/create-bug - Create Bug Report/resolve-ticket - Resolve ticket end-to-end with TDD/review - Comprehensive code review across 9 review domains/debug - Adversarial debugging with competing hypotheses using Agent Teams/comment - Generate and post testing comment on Linear issue/skill-optimize - Validate and optimize Claude SkillsPlugin (/plugin/):
/plugin:element - Create new plugin elements (skills, commands, agents, hooks)/plugin:check - Verify elements against best practices (use after /clear)Backend (/backend/):
/backend:update-nest-server - Update @lenne.tech/nest-server with automated migration/backend:sec-audit - OWASP security audit for dependencies, config, and code/backend:sec-review - Perform security review/backend:code-cleanup - Clean up and optimize code/backend:test-generate - Generate testsFrontend (/frontend/):
/frontend:env-migrate - Migrate environment configurationFullstack (/fullstack/):
/fullstack:update - Sync fullstack project with latest starter templatesDocker (/docker/):
/docker:gen-setup - Generate Docker development & production setupGit (/git/):
/git:commit-message - Generate commit message/git:mr-description - Create Merge Request description/git:mr-description-clipboard - Copy MR description to clipboard/git:rebase - Rebase current branch onto dev/develop/git:rebase-mrs - Batch rebase for open MRs/PRsVibe (/vibe/):
/vibe:plan - Create implementation plan from SPEC.md/vibe:build - Execute IMPLEMENTATION_PLAN.md/vibe:build-plan - Plan + Build in one step