← all publishers

kelly-griffith

@kelly-griffith source repo

5 published skills

  1. Bugbot Loop · kelly-griffith
    Run Bugbot in a loop — assess each finding for legitimacy, search the codebase for similar bugs, fix them, and re-run until Bugbot reports no bugs or an iteration cap (default 5) is reached. Use when the user runs /bugbot-loop or asks to repeatedly run Bugbot and fix everything it finds.
    0 installs
  2. Openapi To Web UI · kelly-griffith bundle
    Ingests an OpenAPI specification (3.0/3.1/3.2 or Swagger 2.0, YAML or JSON, from a file, URL, or pasted text) and builds a polished web app over that API using a prescribed stack: Next.js App Router, TypeScript, Tailwind CSS, shadcn/ui, TanStack Query, and a typed client, query options, and Zod schemas generated from the spec. Bakes in evidence-based UI/UX: task-oriented page architecture, research-backed form design with spec-derived validation, loading/empty/error states, WCAG 2.2 AA accessibility, Core Web Vitals targets, SEO metadata on anonymously reachable routes, and a server-side proxy so API credentials never reach the browser. Use when the user provides an OpenAPI or Swagger spec and asks for a website, web app, frontend, UI, portal, storefront, dashboard, account area, or personal tool over it.
    0 installs
  3. Openapi To Full Stack · kelly-griffith
    Orchestrates openapi-to-spring-api, spring-api-to-service, and openapi-to-web-ui into one sequential pipeline that turns an OpenAPI spec into a complete, tested backend service and frontend web app in a single run. Expects three inputs — an OpenAPI spec (file, URL, or pasted), a backend directory, and a frontend directory — and runs each phase as its own subagent so the orchestrating context stays small. Verifies the running service's generated OpenAPI document against the source spec before handing that document to the frontend, and finishes with e2e tests against the live backend. Use when the user provides an OpenAPI spec and asks for a full stack, a backend plus frontend, or an end-to-end app built from the spec in one shot.
    0 installs
  4. Openapi To Spring API · kelly-griffith bundle
    Ingests an OpenAPI specification (3.0/3.1/3.2, YAML or JSON, from a file, URL, or pasted text) and produces an idiomatic Spring Boot REST API contract — Java interfaces carrying all mapping and OpenAPI annotations, record DTOs, an RFC 9457 problem+json error model — plus test-first MockMvc contract tests against the interface. Targets the latest Java LTS and the current stable Spring Boot. Use when the user provides an OpenAPI or Swagger spec and asks to scaffold, generate, or implement a Spring Boot API from it, or asks for contract-first Spring Boot development.
    0 installs
  5. Spring API To Service · kelly-griffith bundle
    Completes a contract-first Spring Boot scaffold — api/ contract interfaces, api/dto/ record DTOs, shared problem+json components, and red MockMvc contract tests, however they were produced — by implementing the web, service, and repository layers plus Flyway migrations under fixed cross-cutting decisions (hand SQL via JdbcClient vs JPA by criteria, server-assigned UUIDs, Clock-driven timestamps, database-enforced uniqueness translated through a constraint-name registry, Testcontainers on the deployed engine, migrations as a discrete deploy step) until the contract tests pass unchanged, then wires configuration and packaging. Use when a project contains that scaffold (api/ contract interfaces, api/dto/ records, red contract tests) and the user asks to implement or complete the service, make the contract tests pass or go green, add persistence, controllers, or migrations behind the contract, or take the scaffold to production.
    0 installs