Development

Use when implementing or refactoring an agreed application change within existing architecture and contracts.

Review project documentation for drift against completed Taskman work and update affected documents.

Review a requested code scope for concrete defects and maintainability problems; report evidence without modifying implementation.

This skill should be used when the user asks to "commit", "commit changes", "create a commit", "stage and commit", "git commit", or wants to save their work to version control. Guides Claude through staging files and writing a well-formed git commit message.

Add explanatory comments to code to improve readability and maintainability. Use when the user asks to "comment code", "add comments", "document this code", "explain this code with comments", or wants inline documentation added to source files.

Analyze a repository to generate recommended Claude Code settings.json permissions. Use when setting up a new project, auditing existing settings, or determining which read-only bash commands to allow. Detects tech stack, build tools, and monorepo structure.

Create custom external web service APIs for Moodle LMS. Use when implementing web services for course management, user tracking, quiz operations, or custom plugin functionality. Covers parameter validation, database operations, error handling, service registration, and Moodle coding standards.

Create custom external web service APIs for Moodle LMS. Use when implementing web services for course management, user tracking, quiz operations, or custom plugin functionality. Covers parameter validation, database operations, error handling, service registration, and Moodle coding standards.

Create custom external web service APIs for Moodle LMS. Use when implementing web services for course management, user tracking, quiz operations, or custom plugin functionality. Covers parameter validation, database operations, error handling, service registration, and Moodle coding standards.

Deep research and market validation for app ideas. Use when starting a new project, validating an idea, or when the user says "research my idea", "validate my app", or "help me start a new project".

Structured retrospective after completing a delivery increment or diamond. Captures learning for continuous improvement.

Authoritative guidance for modern React 19+ (Actions, use, Compiler, View Transitions, Fragment refs, Activity, browser, useEffectEvent). Use when writing, reviewing, refactoring, or migrating React components, forms, data fetching, concurrent UI, or upgrading to React 19+. Triggers on React, React 19, useActionState, useOptimistic, forwardRef, useEffect data fetch, React Compiler, ViewTransition, Suspense patterns, or codemods. Always prefer latest official patterns over training data.

Design, implement, review and refactor backend REST APIs using Hexagonal Architecture (Ports and Adapters), language-agnostic, with idiomatic best practices for Python, Go, TypeScript/Node, Java and C#/.NET. Covers use cases, domain modeling, ports, inbound/outbound adapters, composition root, error handling, REST conventions, SOLID, design patterns, clean code and testing per boundary. Use this skill whenever the user works on server-side code and mentions hexagonal, ports and adapters, clea...

Use whenever the user asks to build a feature, fix a bug, or wants strict test-driven development (red-green-refactor). Also trigger on "/foreman:tdd", "/tdd", "write the test first", or "TDD this".

Use before pushing, opening a PR, or when the user asks to review code, review a diff, or review a pull request. Also trigger on "/foreman:review" or "/review".

Use when the user asks to improve performance, find bottlenecks, optimize the backend, or speed something up. Also trigger on "/foreman:perf" or "/perf".

Use when the user asks to write, update, or improve documentation, READMEs, API docs, docstrings, ADRs, or runbooks. Also trigger on "/foreman:docs" or "/docs".

Proves a change actually works and root-causes failures — the suite runs first, output actually read. Answers "does it work", where inspect answers "is it good".

Ships a reviewed change safely, with a rollback plan and an explicit GO/NO-GO decision, and closes out the task.

Builds and tracks a personalized learning roadmap, or onboards you onto an existing codebase. A user-invoked entry point; the lifecycle never routes here.

Senior code review across correctness, complexity, architecture, security, performance, and cross-service impact. Read-only — it reports and routes fixes to construct.

The full lifecycle in one call — spec, plan, build, verify, review, ship — with approval gates and resume. The default entry point for building or delivering something, and for picking up interrupted work. Routes to every phase skill itself.

Proposes what to build next: ranked, cited feature candidates from market research and real usage. Also evaluates tools, platforms, and libraries you are considering switching to.

Crafts or reviews UI/UX for web and mobile — visual and interaction quality, design systems, screens, and flows. For schema and API design, use define.