lennetech-claude-code

Plugin lennetech-claude-code from marketplace cascade-code-languages-misc-2 in joshuarweaver/cascade-code-languages-misc-2. Commands read from the repo's manifest — 1 month ago.

Skills (34)

• marketplace-optimizer

  Optimizes this Claude Code marketplace against the current Claude Code documentation and the current default model. Refreshes the docs cache, derives the documentation and changelog delta, fans out one analysis agent per element type (skills, commands, agents, hooks, mcp) plus a marketplace agent fo

• building-stories-with-tdd

  Orchestrates the Test-Driven Development cycle for user stories and features: writes the story test in tests/stories/ first, agrees the seams, then implements until every test passes. Activates on "TDD", "test first", "tests zuerst", "story test", "Story umsetzen", or any feature implementation that

• checking-upstream-first

  Before writing a custom fix for a framework- or library-level problem, verifies that the current version does not already solve it. Covers the version actually resolved vs. the current one, reading the dependency''s own code in node_modules, release notes and issue tracker, and whether an lt base re

• contributing-to-lt-framework

  Guides local development on the lenne.tech framework libraries themselves (@lenne.tech/nest-server, @lenne.tech/nuxt-extensions) and validating those changes from a consuming starter via `pnpm link`, including the build/watch loop and rollback. Activates on "Grund-Repo", "pnpm link", "test framework

• coordinating-agent-teams

  Coordination patterns and worktree isolation for parallel operations this session starts: Agent Teams (independent sessions with messaging) and parallel subagent spawning (Agent tool with isolation worktree). Covers when teams beat single agents and what they cost in tokens. Activates on "agent team

• coordinating-peer-sessions

  Rules for working alongside other Claude Code sessions the user started in parallel. Defines the four coordination channels (Linear and Git, the ledger, `ListAgents`, `SendMessage`), the seven message occasions (LANDED, CLAIM, CONFLICT, SOLVED, READY, ASK, ORIGIN), and the permission boundary a peer

• deploying-to-turboops

  Takes a lenne.tech fullstack monorepo live on TurboOps (turbo-ops.de) via GitLab CI/CD. Covers the deploy contract (.turboops.json, .gitlab-ci.yml, docker-compose.yml, image drift), `lt deployment create`, CI/CD variables, multi-service stages via `turbo deploy --compose`, DNS-before-Let''s-Encrypt,

• developing-claude-plugins

  Develops, optimizes, and validates Claude Code plugins: skills (SKILL.md), commands, agents, hooks (hooks.json), and scripts. Covers YAML frontmatter, element structure, cross-references, naming conventions, the skill listing budget, and manifest validation via `claude plugin validate`. Activates wh

• developing-lt-frontend

  Handles ALL Nuxt 4 and Vue frontend work: components, composables, forms (Valibot), API integration (types.gen.ts, sdk.gen.ts), authentication (Better Auth), SSR, and Playwright E2E. Supports monorepos (projects/app/, packages/app/). Activates on .vue files, nuxt.config.ts, Nuxt UI, TailwindCSS, fil

• filing-ai-proposed-tickets

  Governs every Linear ticket Claude opens for work nobody asked for: an improvement idea, an out-of-scope finding, a refactor, a follow-up. Requires a duplicate search before filing, routes the ticket into the team Triage state, marks it with an AI label so a human sees at a glance that a machine pro

• general-frontend-security

  Framework-agnostic frontend security guide based on OWASP Secure Coding Practices: XSS prevention, CSRF protection, Content Security Policy, secure cookie configuration, client-side auth patterns, input validation, secure storage, and security headers. Applies to any web frontend, not only Nuxt. Act

• generating-nest-servers

  Handles ALL NestJS and @lenne.tech/nest-server work: modules, services, controllers/resolvers, models, DTOs, and debugging. Covers `lt server` generators, @Roles/@Restricted security, CrudService patterns, and API tests via TestHelper. Supports monorepos (projects/api/, packages/api/). Activates on

• grilling-decisions

  Relentless round-based interview that settles every open decision before implementation starts. Maps the decisions as a tree, asks the whole frontier (every question whose prerequisites are settled) per round with a recommended answer on each, looks facts up in the codebase instead of asking for the

• maintaining-lt-stack

  Single source of truth for stack-wide maintenance and releases of the lt base repos ("Grund-Repos"): the dependency graph (nuxt-extensions to nuxt-base-starter, nest-server to nest-server-starter), the release recipe per repo including both marketplaces, npm propagation waits, the push-channel check

• maintaining-npm-packages

  Analyzes and optimizes npm package dependencies across five maintenance modes: FULL (update all), DRY-RUN (analysis only), SECURITY-ONLY (urgent CVE fixes), PRE-RELEASE (conservative patch-only), POST-FEATURE (cleanup). Activates on updating packages, `npm audit` findings, deprecated or unused depen

• managing-agent-memory

  Decides per project whether `.claude/agent-memory/**` is committed, records that decision next to the memory it governs, and curates the notes before every commit that carries them. Activates before committing whenever agent-memory files are dirty: git:ship, ticket-cycle, review runs, or any standal

• managing-dev-servers

  Rules for starting, monitoring, and stopping local dev servers (nuxt dev, nest start, pnpm run dev, build --watch, Playwright, Mailpit) and for closing Chrome DevTools MCP tabs afterward. Prefers `lt dev up/down/status/tunnel` for lt projects: stable HTTPS URLs, project-scoped env, parallel projects

• modernizing-toolchain

  Migrates lenne.tech projects from the legacy jest+eslint+prettier toolchain to the current vitest+oxlint+oxfmt baseline used by nest-server-starter and nuxt-base-starter. Covers swc decoratorMetadata config, the @Prop union-type fix, supertest default-import correction, the Nitro PORT-vs-NITRO_PORT

• nest-server-core-vendoring

  Knowledge base for projects that vendored the @lenne.tech/nest-server core into their source tree (projects/api/src/core/, no npm dependency). Covers detecting a vendored project, the one-way vendor model, when `src/core/` may be touched, the flatten-fix pattern, upstream sync and upstream-PR workfl

• nest-server-updating

  Migration guides, release notes, and error solutions for updating @lenne.tech/nest-server in npm mode. Covers version-specific breaking changes, stepwise major upgrades, and starter comparisons; delegates execution to the lt-dev:nest-server-updater agent. Activates on nest-server version upgrades ("

• nuxt-extensions-core-vendoring

  Knowledge base for projects that vendored the @lenne.tech/nuxt-extensions module into their source tree (app/core/, no npm dependency). Covers detecting a vendored frontend, the one-way vendor model, when `app/core/` may be touched, upstream sync and upstream-PR workflows, and cosmetic-vs-substantia

• rebasing-branches

  Rebases feature branches onto the current development branch (dev/develop). Handles conflict resolution with priority ordering, extracts Linear ticket context from the branch name for smarter conflict decisions, optimizes after the rebase, and force-pushes with lease. Activates on "rebase", "branch

• running-check-script

  Single source of truth for running the package.json `check` script. Defines discovery (multi-package monorepo aware), the iterate-until-green auto-fix loop, the mandatory audit-finding escalation ladder, residual classification (Accepted vs Critical), and report formatting. Activates on "check laufe

• running-load-tests-with-k6

  Runs and interprets k6 load tests against lenne.tech fullstack APIs. Covers installation, Better-Auth authentication for a realistic path, the three canonical scenarios (smoke / load / soak), threshold defaults for ~10 concurrent users (p95 under 500ms, error rate under 1%), and the optimisation lad

• unslop

  Cuts AI tells from any text that reaches a human reader: Linear tickets and comments, commit messages, MR/PR descriptions, READMEs and migration guides, QA instructions, offer and showcase copy, and the body of skills, commands, and agents. Carries the English pattern catalogue, a German one (Nomina

• using-lt-cli

  Reference for the lenne.tech CLI (`lt`). Covers lt fullstack init/update/convert-mode, lt git get/reset, lt server create/object/addProp, lt deployment, and lt dev (parallel project orchestration via Caddy: install/up/down/status/doctor/tunnel). Activates on any `lt` subcommand, "lenne.tech CLI", "-

• validating-changes-in-browser

  Final browser validation after implementation AND review have succeeded. Boots the app via `lt dev up`, seeds realistic `@test.com` data, derives a step-by-step test list from the diff (every affected page, role, flow, empty/error state, mobile pass, console + network sweep), then walks it autonomou

• validating-ci-pipelines-locally

  Executes GitLab CI/CD pipelines locally with the same image, env vars, and service containers as the real runner, so pipeline failures surface before the push. Covers pipeline discovery, per-job execution via gitlab-runner exec, service-container orchestration, env injection without secrets, and a j

• validating-production-readiness

  The lenne.tech fullstack production-readiness checklist. Defines the eight pillars (configuration and secrets, observability, health and lifecycle, security hardening, data durability, resilience under load, deployment hygiene, runbook and rollback) with file/line evidence, severity classification,

• writing-linear-comments

  Shapes every Linear comment an lt-dev command posts so a product owner grasps it without scrolling: what changed in plain language, the full test steps with links and example data, and nothing else. Owns the split between the short comment and the attached Linear document that carries the technical

• writing-qa-test-instructions

  Decides whether a ticket is manually testable by non-developers and writes the German QA test instructions for the Linear comment. Makes frontend verifiability — directly or through a named reproducible symptom — the hard gate: no browser path means QA Testing is never offered as an option. Defines

• creating-offers

  Creates and edits business offers on the Offers platform (angebote.lenne.tech) and its demo instance (demo-angebote.lenne.tech), using the account''s own knowledge base for company profile, services and references. Knows all 18 content block types, offer lifecycle (draft/sent/viewed/template), custo

• analyzing-projects

  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 ap

• creating-showcases

  Creates, updates, and manages showcases on the 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 creati

Similar plugins