labspangaea

create-elysia-app

Scaffold a production-ready ElysiaJS/Bun application (api, consumer, or publisher) wired to @labspangaea/ts-lib. Use this whenever the user says "scaffold an Elysia service", "create a new Bun API", "generate a consumer/publisher", "set up a fresh Elysia project with @labspangaea/ts-lib", "make me an order-service / payment-service / etc.", or any phrasing that implies starting a brand-new Bun/Elysia service from scratch. The skill orchestrates create-elysia-repository -> create-elysia-service -> create-elysia-handler in sequence and adds src/index.ts, config, package.json, tsconfig, drizzle config. For adding a single layer to an existing project, use the focused skills directly instead.

create-elysia-handler

Generate the HTTP controller (inbound adapter) for ONE entity in an existing Elysia/Bun project — a thin idiomatic Elysia instance with TypeBox DTOs, cursor pagination, request validation, and the humares-style response envelopes, wired to the entity's service. Has Mode A (new schema → also generates the upstream domain/port/repo/service) and Mode B (existing service → just the controller + DTO). **Use this whenever the user wants to expose an entity over HTTP in an existing project — phrasings like 'add REST endpoints for X', 'create the handler/controller for Y', 'wire up HTTP routes for entity Z', 'expose Subscription over HTTP', 'add CRUD endpoints for the Customer entity'.** Do NOT use to scaffold a fresh project (use `create-elysia-app`), data-layer only (use `create-elysia-repository`), or service-layer only (use `create-elysia-service`).

AI & Automation Listed

create-elysia-repository

Generate the domain type, repository port, Drizzle repository adapter, Drizzle table schema, and apperr error codes for ONE entity in an existing Elysia/Bun project wired to @labspangaea/ts-lib. **Use this whenever someone wants to add a new entity's data layer, create a repository for a domain model, generate a Drizzle schema + port interface, or scaffold the persistence layer without generating the whole app** — phrasings like "I need a repo for X", "create the domain and repository for Y", "add Z to the database layer", "scaffold the Drizzle model for Order". Owns the schema-parsing rules the other layered skills delegate to. Do NOT use to scaffold a fresh project (use `/elysia-scaffolder:create-elysia-app`), to add the service layer (use `create-elysia-service`), or to expose endpoints (use `create-elysia-handler`).

create-elysia-service

Generate the service (use-case) layer for ONE entity in an Elysia/Bun project wired to @labspangaea/ts-lib — the real service, the canned stub, the service-port interface, and the build-time stub factory. **Use this whenever someone wants to add a service file to an existing Bun project, implement business logic for an entity, or wire a service to an already-created repository** — phrasings like "create the service for X", "add business logic for Y", "wire up the use-case layer". Do NOT use to scaffold a fresh project (use `/elysia-scaffolder:create-elysia-app`), to generate the data layer only (use `create-elysia-repository`), or to expose endpoints (use `create-elysia-handler`).

Testing & QA Listed

integration-test-elysia-app

Run an end-to-end integration test for a elysia-scaffolder-generated service against a real postgres + redis docker stack. Renders the api+postgres+redis combo from the live templates, seeds the DB, boots the Bun service in real mode, and asserts CRUD + cursor pagination (no-overlap) + redis cache-key presence + request_id-in-logs + the 404 error envelope. **Use this whenever the user says "test the scaffolded Elysia app", "run the integration test", "verify the generated service works against real postgres/redis", "smoke-test the runtime", or any phrasing that implies running real HTTP requests against a scaffolded Elysia service and live database/redis.** Compile-only type-checking (the smoke runner) is a different thing — this skill actually boots the binary and exercises real endpoints.

AI & Automation Listed

create-go-app

Scaffold a production-ready Go application (api, consumer, or publisher) wired to go-lib. Use this whenever the user says "scaffold a Go service", "create a new Go API", "generate a consumer/publisher", "set up a fresh Go project with go-lib", "make me an order-service / payment-service / etc.", or any phrasing that implies starting a brand-new Go service from scratch. The skill orchestrates create-go-repository -> create-go-service -> create-go-handler in sequence and adds cmd/, config/, go.mod. For adding a single layer to an existing project, use the focused skills directly instead.

create-go-handler

Generate the HTTP handler (inbound adapter) for ONE entity in an existing Go service — emits framework-agnostic huma handler funcs + `RegisterRoutes` wiring across nethttp/gin/chi/mux/echo, with cursor + offset pagination, request validation, and humares envelopes. Has Mode A (new schema → also generates upstream domain/port/repo/service automatically) and Mode B (existing service → just the handler file). **Use this skill whenever the user wants to expose an entity over HTTP in an existing project — phrasings like 'add REST endpoints for X', 'create the handler for Y', 'wire up HTTP routes for entity Z', 'expose Subscription over HTTP', 'add CRUD endpoints for the new Customer entity', 'add inbound HTTP handling for X'.** Do NOT use to scaffold a fresh project (use `create-go-app`), data-layer only (use `create-go-repository`), or service-layer only (use `create-go-service`).

API & Backend Listed

create-go-repository

Generate domain struct, port interface, repository adapter (GORM or bun), and apperr error codes for one entity in an existing Go project wired to go-lib. **Use this skill whenever someone wants to add a new entity's data layer, create a repository for a domain model, generate a GORM or bun model + port interface, or scaffold the persistence layer without generating the full application** — phrasings like "I need a repo for X", "create the domain and repository for Y", "add Z to the database layer", "scaffold the GORM model for Order", "make me a bun repository for Invoice", "add a SQL-first repo without GORM". Owns the schema-parsing rules other skills delegate to. Do NOT use to scaffold a fresh Go project (use `/go-scaffolder:create-go-app`), to add the business-logic layer (use `/go-scaffolder:create-go-service`), or to expose endpoints over HTTP (use `/go-scaffolder:create-go-handler` — its Mode A generates the upstream repository automatically).

create-go-service

Generate the service (use-case) layer for one entity in a Go service, wired to its port interface. **Use this skill whenever someone wants to add a service file to an existing Go project wired to go-lib, implement business logic for an entity, or wire a service to an already-created repository** — phrasings like "create the service for X", "add business logic for Y entity", "wire up the use-case layer", "build the service layer for the Order entity". Do NOT use to scaffold a fresh Go project (use `/go-scaffolder:create-go-app`), to generate the data layer only (use `/go-scaffolder:create-go-repository`), or to expose endpoints over HTTP (use `/go-scaffolder:create-go-handler` — its Mode A generates the upstream service automatically).

API & Backend Listed

integration-test-go-app

Run end-to-end integration tests for a go-scaffolder-generated Go service against the bundled docker-compose stack (postgres + mysql + redis). Use this skill whenever the user says "test the scaffolded Go app", "run integration tests on the API combos", "verify CRUD/pagination/cache works for nethttp/gin/chi/mux/echo", "smoke-test the runtime", "test the generated handlers against real services", or any phrasing that implies running real HTTP requests against scaffolded services and live database/redis containers. Tests both cursor and offset pagination, verifies cache keys appear in redis, asserts request_id appears in the structured logs, and validates the huma OpenAPI 3.1 spec + Stoplight Elements UI at /openapi.{json,yaml} and /docs. Compile-only smoke testing (the `tools/smoke -all` runner) is a different thing — this skill actually starts each binary and exercises real endpoints.

Web & Frontend Listed

design-fundamentals

Say why a design looks wrong, and what to change. Use this whenever something visual "looks off", "looks cheap", "feels amateurish", or "doesn't look professional" and the person cannot name why — and whenever someone needs colours, fonts or a layout chosen for them. Runs a measured review over colour, type, layout, grouping and hierarchy, then reports concrete fixes ranked by impact with a severity each; or turns a brief into a buildable spec — palette with hex and 60/30/10, a type pairing with real sizes off a scale, a grid. Checks the contrast maths people skip, including borders and other non-text elements (3:1), not just text (4.5:1). Scope is **print and static graphic design**: posters, flyers, packaging, labels, menus, signage, banners, book and album covers, logos and wordmarks, slide decks, social posts and thumbnails. Reach for it on phrasings like "why does this poster look cheap", "our deck cover feels amateurish", "these two brand colours fight each other", "what pairs with Montserrat ExtraBold"

testcase-importer

Import and normalize existing test-case data — xls/xlsx, CSV/TSV, PDF tables, or a pasted/markdown table — into this project's canonical test-case CSV and render it into the offline HTML console. Fuzzy-maps foreign headers onto the schema, standardizes Type (POS/NEG/VAPT), Outcome (TN/TP/FP/FN!) and the Priority scales, keeps source IDs (or generates them), infers missing tag fields, and flags uncertain ones for review. Use whenever someone has test cases in a sheet, CSV, PDF, or table and wants them in the project format or in the console — e.g. "convert this QA spreadsheet", "map this test matrix to our format", "normalize this testcases xlsx", "turn this PDF of test cases into the CSV", or pasting a table and asking to "add these to the matrix". Do NOT use it to author brand-new cases from a feature/flow (that's the testcase-architect agent), to import non-test-case data such as a customer or sales CSV into a database or chart, to edit/restyle the console, or to query an existing canonical CSV.

Testing & QA Listed

userflow-to-testcases

Author a complete test-case suite FROM a user-flow or feature document — a PDF (preferred), markdown, doc, text, or screenshots of an app's flows — and output an importer-ready CSV. Models the flow as state machines (actor + resource), then writes cases per transition with cross-flow downstream impact, a matrix, end-to-end journeys, and a security/abuse (VAPT) pass; tags each case Type (POS/NEG/VAPT), Outcome (TN/TP/FP/FN!) and Priority with severity reasoning. Its CSV feeds testcase-importer (flow → CSV → console). Use whenever someone has a flow/spec/guide and wants QA test cases GENERATED from it — e.g. "write test cases from this user-flow PDF", "generate a test suite from this feature spec", "cover this checkout/onboarding flow end to end", "model the states in this flow and test them". Do NOT use to import/reformat EXISTING test cases (that's testcase-importer), to generate code-level unit/integration tests (pytest/jest), to create test fixtures or seed data, or to render/edit the console.