From welld-dev
Standardized checklists for connecting a welld project to its ecosystem tools — GitHub (repo, branch protection, secrets), CI, MCP servers, environments and databases. Use during /welld-dev:new stage 5, when the user asks to "connect", "set up", or "wire up" a tool/integration for a project, or when the devops agent needs the standard procedure. Every checklist ends with a verification command: a connection is established only when that command's output says so.
How this skill is triggered — by the user, by Claude, or both
Slash command
/welld-dev:connectionsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
One way to connect each tool, the same for every project. The core rule: **"connected"
One way to connect each tool, the same for every project. The core rule: "connected" is an observed fact — each checklist ends with a verification command; run it and read the output. Never report a connection done without it.
References (read the one you need):
references/github.md — repo creation, branch protection, CI secretsreferences/mcp-servers.md — the standard MCP set for welld projectsreferences/environments.md — env vars, secrets hygiene, local DBWhen connecting a fresh project, follow this order (later steps depend on earlier ones):
.mcp.json (usually scaffolded; verify, don't recreate).gh secret set X < file / --body from env, not inline literals).npx claudepluginhub matteocodogno/wellforge --plugin welld-devCreates bite-sized, testable implementation plans from specs or requirements, with file structure and task decomposition. Activates before coding multi-step tasks.