claude-skills

Expert in TypeScript codebase patterns for backend and frontend. Helps with creating services, repositories, DALs, entities, controllers, handlers, use cases, React components, and UI screens. Make sure to use this skill whenever the user mentions TypeScript, Node.js, Express, TypeORM, React, React Router, React Native, Expo, creating an API endpoint, building a feature, implementing CRUD operations, or asks about codebase architecture - even if they don't explicitly say "clean architecture" or mention specific layers. For testing, use the test-typescript skill.

Expert in migrating CI/CD pipelines to Woodpecker CI from GitHub Actions, Semaphore CI, GitLab CI, Jenkins, Drone CI, and other platforms. Helps write and debug .woodpecker.yml configurations, translate pipeline steps, find Woodpecker plugins, set up services, workflows, matrix builds, secrets, volumes, and when-conditions. Use this skill whenever the user mentions Woodpecker CI, .woodpecker.yml, migrating CI pipelines, converting GitHub Actions to Woodpecker, Woodpecker plugins, Woodpecker syntax, or asks for help with any CI/CD configuration that involves Woodpecker — even if they don't explicitly name "Woodpecker" but mention migrating away from GitHub Actions or Semaphore CI.

Generate lightweight technical specification documents with PlantUML diagrams. Use this skill whenever the user asks to design a feature, plan an implementation, document architecture changes, specify database schema changes, describe API endpoints, or needs to capture WHAT changes across services - even if they don't explicitly say "tech spec" or "specification".

Break down a user story into multiple testable tasks. Use when user mentions: story, ticket, task breakdown, implement feature, plan implementation, create tasks, split into tasks, story breakdown, task decomposition, acceptance criteria, definition of done, sprint planning, backlog, user story, feature breakdown, ralph, ralph loop, autonomous implementation, .TASK.md, progress.txt, run through ralph. Each task must be independently verifiable. NOTE: Ralph-loop task files (.TASK.md) are generated ONLY when explicitly requested — never automatically during normal story creation.

Expert in PlantUML diagramming language. Automatically invoke when users need to visualize processes, systems, architectures, workflows, data structures, or relationships between components. This includes when users describe how things connect, request flow documentation, explain system interactions, show lifecycle states, or need to communicate design visually - even if they don't explicitly say "diagram", "PlantUML", or "UML". Covers sequence, class, activity, use case, state, component, object, and flowchart diagrams.

Walks the user through validating a product idea using The Mom Test method (from the book by Rob Fitzpatrick) - clarifying the idea and customer segment, finding the riskiest assumptions, crafting interview questions that pass the Mom Test, finding people to talk to, debriefing raw interview notes, and reaching a proceed/pivot/kill verdict. Includes a mock-interview practice mode. Use this skill whenever the user wants to validate a product, startup, SaaS, or app idea, prepare for or review customer discovery interviews, mentions The Mom Test, customer conversations, user interviews, talking to users or customers, or asks whether their business or product idea is any good - even if they never mention the book.

Expert in TypeScript monorepo architecture using pnpm workspaces. Helps with structuring packages (microservices, web apps, mobile apps, shared libs), configuring ES modules with path aliases, centralized config, Docker Compose orchestration, and inter-package dependencies. Use when user mentions monorepo, pnpm workspace, packages folder, shared libraries, common libs, multi-package project, microservices architecture, Docker Compose development environment, workspace setup, monorepo structure, package organization, shared config. Also use when starting a new TypeScript project that might grow to multiple services/apps, when splitting a service into smaller pieces, when asking about code sharing between frontend and backend, or when setting up any project with more than one deployable unit.