welld-dev

Adopt WellForge in an existing (brownfield) project — AI-readiness, spec workflow, calibrated quality gates

Scaffold a new welld project — interview, stack recommendation, generation, connections

Orchestrate the full agent team on a goal (spec → plan → tasks → implementation → QE verdict)

Create the technical plan for a spec, following the **spec-driven** skill conventions

Write a feature specification (spec-driven workflow, step 1 of 3)

Architecture Decision Record (ADR) specialist. Fires automatically when a significant design decision is made during a cc-sdd session — technology choices, pattern adoptions, trade-off resolutions, API design decisions, or any choice that will constrain future work. Also invoke manually with: "write an ADR for [decision]". Outputs a versioned ADR file and optionally updates CLAUDE.md with a summary reference.

Software Architect for the welld spec-driven workflow. Use to turn an APPROVED spec into a technical plan (specs/NNN-slug/plan.md): architecture, data model, API contracts, test strategy, risks. Also use for stack-fit evaluations and to flag decisions that need an ADR. Trigger phrases: "plan the implementation of", "act as architect", "design the solution for".

Backend Developer for the welld spec-driven workflow. Use to implement backend tasks from a specs/NNN-slug/tasks.md — Spring Boot + Kotlin + jOOQ + Liquibase per the kotlin-springboot-welld skill, or Hono + TypeScript per the hono-ts-backend skill. Invoke with one or more task IDs. Trigger phrases: "implement T2", "act as backend dev", "build the API for task".

UX/UI Designer for the welld spec-driven workflow. Use for features with a user interface: UX flows, screen/state inventory, component reuse mapping (Mantine), and accessibility requirements. Runs between spec approval and task derivation. Can drive the running app with Playwright to audit current UI. Trigger phrases: "design the UX for", "act as designer", "map the screens for".

DevOps Engineer for the welld spec-driven workflow. Use for CI/CD pipelines, Docker and infrastructure files, environment configuration, release wiring, and connecting projects to ecosystem tools (GitHub settings, MCP servers, registries, observability). Trigger phrases: "set up CI", "act as devops", "wire up the pipeline", "connect this project to".

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.

Hono + TypeScript best practices for modern backend services. Use this skill whenever building or reviewing Hono TypeScript APIs, setting up a new service, defining routes, implementing middleware, handling validation, or managing database operations. Covers project setup with modern tooling (pnpm, tsx, Biome), Hono routing patterns, Zod validation, functional error handling with Effect TS, Drizzle ORM with PostgreSQL, OpenAPI documentation, and Docker deployment. Always trigger this skill for any Hono TypeScript task — even partial ones like "add a route", "create middleware", or "set up validation".

Kotlin and Spring Boot development. Trigger this skill for ANY task involving Kotlin, Spring Boot, JVM, Maven, jOOQ, Liquibase, database migrations, REST APIs, or backend services. Covers welld-style best practices including functional error handling with Result/DomainError, Spring Modulith module boundaries, repository patterns, and Spring configuration. Use for writing code, reviewing code, setting up new services, defining migrations, configuring dependencies, scaffolding modules, or debugging Spring applications. Always trigger for partial tasks like "add a repository", "create a migration", "set up a new module", "add an endpoint", or "fix a Spring Boot issue".

mise (dev tools version manager) expert for welld monorepos. Use this skill whenever the user asks to set up mise, add tools to mise, create or edit a mise.toml, define mise tasks, manage Java/Node/pnpm/Maven versions, or replace npm scripts / Makefile with mise tasks. Also trigger for phrases like "pin the node version", "add a task for", "run with mise", "how do I manage tool versions", "set up dev environment", or any question about .mise.toml configuration. Always use this skill proactively when scaffolding new projects or services — every welld project should have a mise.toml.

Expert React + TypeScript + Vite frontend development skill. Use this skill whenever the user asks to build, scaffold, extend, or refactor a React application using TypeScript. Triggers include: "create a React component", "build a page with React", "add a feature to my React app", "scaffold a new Vite project", "write a custom hook", "set up React Context", "add TanStack Query/Router", "style with Tailwind", "refactor this component", "use Effect TS in React", or any time the user describes frontend work in a React/TypeScript codebase. Always use this skill proactively whenever frontend React/TypeScript code is being produced — even if the user just says "create a form" or "add a new page". Prefer this skill over generic coding responses for any React work.

6 hooks across 6 events