maxforge-lab

Plugin maxforge-lab from marketplace maxforge-lab in mancaf779-boop/-Max-Geld-Generation. Commands read from the repo's manifest — 1 month ago.

Skills (24)

• run-maxforge-lab

  Build, load, and drive the Maxforge Lab Claude Code plugin (maxforge-lab) — run its SessionStart hook, launch a headless Claude Code session with the plugin loaded, and verify that skills (researching-topics, analyzing-data, designing-workflows, orchestrating-tasks, using-maxforge) actually auto-tri

• run-biz-automation

  Build, start, and drive the biz-automation app — a dependency-free Node HTTP API for invoice triage, lead routing, and scheduled report generation. Use when asked to run, start, test, or smoke-test biz-automation, hit its API, generate a report, or verify the report scheduler.

• run-youtube-dashboard

  Build, run, and screenshot the Maxforge Lab YouTube dashboard — a Vite + React mobile YouTube-analytics dashboard served by a self-contained Node server. Use when asked to run, start, launch, serve, drive, or screenshot the app, or to verify a change renders (dashboard, live data, AI Coach, keywords

• analyzing-data

  Use when you have data of any kind - CSV/JSON/logs/spreadsheets/query results/survey text/metrics/time series - and need to extract insight, whether descriptive (what happened), diagnostic (why), predictive (what next), or qualitative (themes). Triggers on "analyze this data", "what does this show",

• brainstorming

  You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

• designing-workflows

  Use when turning a goal or a pile of findings into an ordered, step-by-step workflow or plan that someone (human or agent) can execute without further questions - "make a plan", "lay out the steps", "design the workflow/pipeline/process", "how do we get from here to done". For code implementation pl

• dispatching-parallel-agents

  Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

• executing-plans

  Use when you have a written implementation plan to execute in a separate session with review checkpoints

• finishing-a-development-branch

  Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

• orchestrating-tasks

  Use when you have a plan or workflow and must turn every step into concrete tasks and actually execute them - creating the task list, doing the work, taking real actions, verifying each one, and driving to done. Triggers on "execute this", "do all of it", "run the whole thing", "take action on the p

• receiving-code-review

  Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

• requesting-code-review

  Use when completing tasks, implementing major features, or before merging to verify work meets requirements

• researching-topics

  Use when you need to gather, evaluate, and synthesize information on a question or topic before acting - literature reviews, competitive/market scans, technical spikes, fact-finding, "look into X", "find out how Y works", or any decision that depends on evidence you don't yet have. Also when pressur

• subagent-driven-development

  Use when executing implementation plans with independent tasks in the current session

• systematic-debugging

  Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

• test-driven-development

  Use when implementing any feature or bugfix, before writing implementation code

• using-git-worktrees

  Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

• using-maxforge

  Use when starting any conversation - establishes how to find and use Maxforge Lab skills, requiring skill invocation before any response or action including clarifying questions, answering, or executing a plan

• using-superpowers

  Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

• verification-before-completion

  Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

• writing-plans

  Use when you have a spec or requirements for a multi-step task, before touching code

• writing-skills

  Use when creating new skills, editing existing skills, or verifying skills work before deployment

• install-n8n-mcp-full-access

  Installiert und konfiguriert den vollständigen n8n-mcp Server (czlonkowski/n8n-mcp) für Claude Code, der Zugriff auf alle 2000+ n8n Nodes (Core + Community + AI-Nodes) gibt, um n8n-Workflows programmatisch zu bauen, validieren, aktualisieren und auszuführen. Nutze diesen Skill, wenn der User sagt "i

• skill-creator-on-demand

  Erstellt auf Zuruf komplette, funktionierende Claude Code Skills (SKILL.md + Scripts + Referenzdateien) fuer beliebige Aufgaben — analog zu install-superpowers und install-n8n-mcp-full-access. Nutze diesen Skill, wenn der User sagt "erstelle mir einen Skill fuer X", "baue einen Skill der Y kann", "i

Hooks (1)

• SessionStart

  "${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.cmd" session-start

Similar plugins