clawker-plugin

Use when the user asks about clawker setup, configuration, troubleshooting, or onboarding. Acts as a clawker internals expert — understands how config maps to generated Dockerfiles, where to add packages vs scripts vs injection points, firewall architecture, MCP setup, credential forwarding, and container lifecycle. Use when the user mentions clawker config, .clawker.yaml, blocked domains, build errors, Docker image build failures, post_init, pre_run, build.packages, container networking, or container issues — even without saying "clawker" explicitly.

Methodically walks the user through creating or modifying clawker extension components — harnesses, stacks, and monitoring extensions — either as loose local components or packaged into a distributable bundle. Use whenever the user wants to author, scaffold, edit, validate, or publish a clawker bundle or component: "create a bundle", "add a stack", "write a harness for <agent>", "make a monitoring extension", "package this for sharing", questions about bundle.yaml / harness.yaml / stack.yaml / monitoring.yaml, or work inside a .clawker/{harnesses,stacks,monitoring} directory — even if the user never says the word "bundle".