rashidee

Fix bugs reported by humans from a BUG.md file. Takes an application name (mandatory), version (optional — supports single version, comma-separated list, "all", or omit for all), and module (optional), resolves the context folder automatically from root-level application folders. When multiple versions are provided (or "all"/omitted), versions are processed SEQUENTIALLY in ascending semver order — all bugs from version N are fully resolved before version N+1 begins. Tags untagged bugs, creates a BUG_MASTER.md tracking checklist, then fixes each bug one at a time: reproduce with Playwright, write a test spec, plan the fix, apply the fix, verify, and update related artifacts (mockups, specifications, module models, user stories). Integrates with Ralph Loop to ensure all bugs are fully fixed across sessions. Use this skill when the user asks to "fix bugs", "fix bug", "start bug fixing", "resolve bugs from BUG.md", "bug fix session", or any request to systematically fix bugs from a BUG.md file. Also trigger when user says "resume bug fixing" to continue from where a previous session left off using BUG_MASTER.md progress file.

Application development orchestrator — orchestrates full-stack code implementation module-by-module (code + Playwright E2E tests), tracking progress in IMPLEMENTATION_MASTER.md and per-module IMPLEMENTATION_MODULE.md. Takes an application name (mandatory), with optional source code path, version and module filters. Version supports single version, comma-separated list, "all", or omit for all versions. When multiple versions are resolved, they are processed SEQUENTIALLY in ascending semver order — all modules for version N are fully implemented before version N+1 begins. Requires context artifacts (module models, HTML mockups, technical specifications, test specifications) to already exist — use "conductor-feature-prepare" first if they don't. Use this skill when the user asks to "implement the application", "start development", "build the app module by module", "orchestrate implementation", "develop from specs", "implement from test specs", or any request to systematically develop a full application from existing specs. Also trigger when user says "resume implementation" to continue from where a previous session left off using IMPLEMENTATION_MASTER.md and IMPLEMENTATION_MODULE.md progress files.

Context artifacts preparation orchestrator — generates all context artifacts (module models, HTML mockups, technical specifications, test specifications) by invoking the appropriate sub-skills. Takes an application name (mandatory), with optional version and module filters. Version supports single version, comma-separated list, "all", or omit for all versions. When multiple versions are resolved, they are processed SEQUENTIALLY in ascending semver order — all artifacts for version N are fully generated before version N+1 begins. Use this skill when the user asks to "prepare artifacts", "generate context", "prepare for development", "generate models and specs", "create mockups and specs", or any request to systematically generate all context artifacts from user stories before implementation begins. Also trigger when user says "resume preparation" to continue from where a previous session left off.

Version upgrade orchestrator — orchestrates both feature development (conductor-feature-develop) and bug fixing (conductor-defect) for a new version in a single session. First implements new features from user stories, then resolves all bugs from BUG.md — ensuring the upgraded version is both feature-complete and stable. Takes an application name (mandatory), version (optional — supports single version, comma-separated list, "all", or omit for all), and optional module filter. When multiple versions are resolved, they are processed SEQUENTIALLY in ascending semver order — both Phase A (features) and Phase B (bugs) for version N are fully completed before version N+1 begins. Use this skill when the user asks to "upgrade version", "version upgrade", "upgrade to new version", "new version with bugs and features", "upgrade and fix bugs", or any request to systematically implement new features and fix bugs for a version upgrade. Also trigger when user says "resume upgrade" to continue from where a previous session left off using UPGRADE_MASTER.md progress file.

Generate a Dockerfile and Kubernetes manifests for an application targeting a single environment. Supports Spring Boot (Java), Laravel (PHP), and Node.js application stacks. Auto-detects the stack from project files (pom.xml, composer.json, package.json), reads CLAUDE.md dependencies, SPECIFICATION.md tech stack, and the application's externalized environment variables. Generates a Dockerfile in the application root folder and Kubernetes manifest YAML files directly in `<app_folder>/k8s/` (no per-environment subfolders — the k8s/ folder is gitignored, each machine maintains its own copy). Standardized input: application name (mandatory), environment (optional). Use this skill whenever the user asks to create deployment artifacts, Dockerfiles, Kubernetes manifests, or containerize an application. Also trigger when the user says things like "deploy this app", "containerize this", "create a Dockerfile", "generate k8s manifests", or any request for deployment-related artifacts.

Generate React + shadcn/ui mockup screens from PRD.md files for UI/UX human designer review. Creates a Vite + React 19 + TypeScript + shadcn/ui mockup application with admin dashboard layout (collapsible sidebar navigation, header with logo/notifications/locale/user menu, footer with copyright/version) using React Router v7 for client-side navigation, organized by user role in a mockup/ folder. Input: application name (mandatory), version (mandatory), module (optional). Output: mockup/ folder in the application's context folder containing MOCKUP.html index page, Vite + React project files, layout components, shadcn/ui components, and role-specific page components. Trigger on keywords: "generate mockup shadcn", "generate shadcn mockup", "create shadcn mockup screens", "shadcn UI mockup", "React mockup from user stories", "mockup from PRD.md shadcn", "generate shadcn screens", "create shadcn UI screens". Accepts application name and version as input (e.g., `/mockgen-shadcn hub_middleware v1.0.3`). Optionally accepts a module name to limit generation to screens for that module only (e.g., `/mockgen-shadcn hub_middleware v1.0.3 module:Location Information`). When module is specified, only page components for that module are generated/updated; layout components, sidebars, server files, and other module pages are left untouched. Automatically excludes strikethrough (deprecated/removed) items.

Generate HTML mockup screens from PRD.md files for UI/UX human designer review. Creates a Node.js + Alpine.js + HTMX mockup server with admin dashboard layout (left sidebar navigation, header with logo/notifications/locale/user menu, footer with copyright/version) served as partials, organized by user role in a mockup/ folder. Input: application name (mandatory), version (mandatory), module (optional). Output: mockup/ folder in the application's context folder containing MOCKUP.html index page, server.js, package.json, partials/, and role-specific content subfolders. Trigger on keywords: "generate mockup", "generate mockups", "create mockup screens", "HTML mockup", "UI mockup from user stories", "mockup from PRD.md", "generate screens", "create UI screens". Accepts application name and version as input (e.g., `/mockgen-tailwind hub_middleware v1.0.3`). Optionally accepts a module name to limit generation to screens for that module only (e.g., `/mockgen-tailwind hub_middleware v1.0.3 module:Location Information`). When module is specified, only content files for that module are generated/updated; partials, sidebars, server files, and other module screens are left untouched. Automatically excludes strikethrough (deprecated/removed) items.

Extract NoSQL document models from Agile user stories using Domain-Driven Design (DDD) principles. Produces Mermaid class diagrams showing document structure (embedded vs referenced), JSON schema examples per collection, and detailed model documentation per module. Use this skill whenever the user asks to extract a NoSQL module model, NoSQL document model, NoSQL schema, collection design, or document structure from user stories. Also trigger when the user provides user stories grouped by module and asks for NoSQL data modeling, document-oriented design, or embed-vs-reference analysis. Even if the user says "design my NoSQL collections" or "what documents do I need", this skill applies if the input contains structured Agile user stories with module groupings. Do NOT use this skill for RDBMS or relational schema extraction — use the modelgen-relational skill for that. Also trigger when the user says "update the model" or "upgrade the model" to incrementally evolve an existing NoSQL document model based on changes in PRD.md. Accepts an application name (mandatory), version (mandatory), and optional module argument (e.g., `/modelgen-nosql hub_middleware v1.0.3` or `/modelgen-nosql hub_middleware v1.0.3 module:Location Information`).

Extract module models from Agile user stories using Domain-Driven Design (DDD) principles. Produces ERD diagrams (Mermaid) and detailed model documentation per module. Use this skill whenever the user asks to extract a module model, data model, entity model, table design, schema design, or ERD from user stories. Also trigger when the user provides a set of user stories grouped by module and asks for entity/relationship analysis, database schema extraction, or DDD model generation. Even if the user says "analyze these stories" or "what entities do I need", this skill applies if the input contains structured Agile user stories with module groupings. Also trigger when the user says "update the model" or "upgrade the model" to incrementally evolve an existing module model based on changes in PRD.md. Accepts an application name (mandatory), version (mandatory), and optional module argument (e.g., `/modelgen-relational hub_middleware v1.0.3` or `/modelgen-relational hub_middleware v1.0.3 module:Location Information`).

Generate a detailed specification document for building a monolith Laravel 12 web application with server-rendered views (Blade), Tailwind CSS, Alpine.js, htmx, and nwidart/laravel-modules modular packaging. Database (MongoDB, PostgreSQL, MySQL, or none), authentication (Keycloak OAuth2 Client, Laravel Breeze form login, or none), scheduling (Laravel Task Scheduling + Queue Batching or none), and messaging (RabbitMQ pub/sub or none) are configurable based on user input. Standardized input: application name (mandatory), version (mandatory), module (optional). Use this skill whenever the user asks to create a spec, specification, blueprint, or technical design document for a new Laravel web application with server-side rendering. Also trigger when the user says things like "spec out a new Laravel project", "design a Laravel web skeleton", "write a technical spec for my new Laravel app", "scaffold spec for a monolith Laravel app", or any request for a specification document describing a Laravel + Blade + Tailwind application. Even if the user only mentions a subset of the stack (e.g., "Laravel web app" or "Laravel with Mongo" or "Laravel with Keycloak"), this skill likely applies — ask and confirm.

Generate a detailed specification document for building a React SPA (Single Page Application) using React 19, TypeScript 5, Vite 6, Material UI (MUI) v6, React Router v7, TanStack Query v5, Zustand v5, React Hook Form v7, and Zod v3. Authentication (Keycloak OAuth2/OIDC PKCE, generic OIDC, or none), API integration (REST via Axios), and optional features (WebSocket, i18n, MUI X Data Grid, MUI X Charts) are configurable based on user input. Standardized input: application name (mandatory), version (mandatory), module (optional). Use this skill whenever the user asks to create a spec, specification, blueprint, or technical design document for a new React SPA or frontend application. Also trigger when the user says things like "spec out a new React project", "design a React SPA", "write a technical spec for my new frontend app", "scaffold spec for a React MUI app", or any request for a specification document describing a React + MUI + TypeScript application. Even if the user only mentions a subset of the stack (e.g., "React SPA" or "React with Keycloak" or "React MUI dashboard"), this skill likely applies — ask and confirm.

Generate a detailed specification document for building a monolith Spring Boot 3 web application with server-rendered views (JTE), Tailwind CSS, Alpine.js, htmx, and Spring Modulith packaging. Database (MongoDB, PostgreSQL, MySQL, or none), authentication (Keycloak OAuth2 Client, Spring Security form login, or none), scheduling (Quartz + Spring Batch or none), and messaging (RabbitMQ pub/sub or none) are configurable based on user input. Standardized input: application name (mandatory), version (mandatory), module (optional). Use this skill whenever the user asks to create a spec, specification, blueprint, or technical design document for a new Spring Boot web application with server-side rendering. Also trigger when the user says things like "spec out a new web project", "design a Spring Boot web skeleton", "write a technical spec for my new web app", "scaffold spec for a monolith web app", or any request for a specification document describing a Spring Boot + JTE + Tailwind application. Even if the user only mentions a subset of the stack (e.g., "Spring Boot web app" or "Spring web with Mongo" or "Spring Boot with Keycloak"), this skill likely applies — ask and confirm.

Generate a detailed specification document for building a Spring Boot 3 REST API application with Spring Modulith packaging. Database (MongoDB, PostgreSQL, MySQL, or none), authentication (Keycloak OAuth2 Resource Server, Spring Security JWT, or none), scheduling (Quartz + Spring Batch or none), and messaging (RabbitMQ pub/sub or none) are configurable based on user input. Standardized input: application name (mandatory), version (mandatory), module (optional). Use this skill whenever the user asks to create a spec, specification, blueprint, or technical design document for a new Spring Boot REST API application. Also trigger when the user says things like "spec out a new REST API project", "design a Spring Boot API skeleton", "write a technical spec for my new API", "scaffold spec for a REST API", or any request for a specification document describing a Spring Boot REST API application. Even if the user only mentions a subset of the stack (e.g., "Spring Boot API" or "Spring REST with MySQL" or "Spring Boot API with Keycloak"), this skill likely applies — ask and confirm.

Generate a detailed specification document for building a distributable Node.js CLI application written in TypeScript. Uses Commander.js for command parsing, tsup for bundling, and @yao-pkg/pkg for cross-platform binary packaging (Windows, macOS, Linux). Interactive prompts (Inquirer.js), persistent user config (conf), project-level config (cosmiconfig), shell execution (execa), HTTP client (got), plugin system, and auto-update checking are configurable based on application needs. Standardized input: application name (mandatory), version (mandatory), command (optional). Use this skill whenever the user asks to create a spec, specification, blueprint, or technical design document for a new CLI tool, command-line application, terminal tool, or developer tool. Also trigger when the user says things like "spec out a new CLI", "design a TypeScript CLI", "write a technical spec for my CLI tool", "scaffold spec for a Node CLI", or any request describing a command-line application. Even if the user only mentions a subset (e.g., "CLI with config file support" or "distributable Node tool"), this skill likely applies — ask and confirm.

Generate Playwright E2E test plan and specification documents from project artifacts (user stories, module models, mockups, specifications). Produces a TEST_PLAN.md root summary and per-module TEST_SPEC.md files containing test scenarios, data seeding scripts, and cleanup scripts — all as detailed Markdown blueprints, not actual test code. Input: application name (mandatory), version (mandatory), module (optional). Output: TEST_PLAN.md + per-module TEST_SPEC.md files in the auto-resolved test output folder. Trigger on keywords: "generate test plan", "generate test spec", "create test specification", "E2E test plan", "Playwright test plan", "test plan from user stories", "test spec from PRD.md", "generate test scenarios", "create test blueprint". Accepts application name and version as input (e.g., `/testgen-functional hub_middleware v1.0.3`). Optionally accepts a module name to limit generation to test specs for that module only (e.g., `/testgen-functional hub_middleware v1.0.3 module:Location Information`). Automatically excludes strikethrough (deprecated/removed) items.

Prepare Kubernetes environment infrastructure by generating K8s manifests for all 3rd party supporting applications for a single target environment defined in CLAUDE.md. Creates/updates ENVIRONMENT.md with per-environment configs and credentials, then generates persistent StatefulSet-based K8s manifests for each 3rd party application (databases, message queues, caches, SSO, API gateways, etc.) directly in the `environment/` folder. Since the `environment/` folder is gitignored, each machine maintains its own independent copy. Ensures all services are remotely accessible using tools from DEVTOOL.md. Trigger on keywords: "prepare k8s environment", "prepare kubernetes", "setup k8s infra", "generate k8s manifests for 3rd party", "prepare environment", "setup infrastructure", "prepare k8s", "init k8s environment", "scaffold k8s environment". Accepts an optional environment argument to select which Kubernetes environment to generate for.

Synchronize project folder structure, PRD.md, and BUG.md files based on the canonical application and module definitions in CLAUDE.md. Validates dependencies (circular, missing, logical) and checks for orphaned services across all applications. Creates missing application folders, scaffolds new PRD.md and BUG.md files from templates, adds missing module sections to existing files. Inserts [TODO] annotations into CLAUDE.md for validation failures. Trigger on keywords: "sync project", "project sync", "sync folders", "sync modules", "sync PRD", "sync BUG", "initialize project structure", "scaffold project", "create project folders", "sync application structure", "validate dependencies". Accepts no arguments — reads all configuration from CLAUDE.md.

Analyze PRD.md files for quality issues: incomplete sentences, non-existent references, cross-module inconsistencies, contradictory requirements, duplicate roles, design system validation, architecture principle violations, and process flow coverage gaps. Validates bi-directional coverage between User Stories/NFRs and High Level Process Flows — detects modules not covered by any process flow and process flow steps not covered by any User Story or NFR. Adds inline [TODO] annotations directly into the PRD.md file for each issue found. Trigger on keywords: "analyze user story", "analyze user stories", "check user story quality", "validate user stories", "find user story issues", "audit user stories", "review user stories", "check requirements quality", "find inconsistencies", "find contradictions". Accepts an application name as input (e.g., `/util-usanalyzer mainapp`, `/util-usanalyzer "Main App"`).

Tag new items in PRD.md files with unique ID codes and validate no duplicate tags exist. Applies to PRD.md documents structured with module sections containing User Stories, Non Functional Requirements, Constraints, References, and Test instructions. Each top-level bullet item gets a unique 9-character code with category prefix, application initials, and running number (interval of 3). Trigger on keywords: "tag user story", "tag user stories", "fix user story tag", "fix user story tags", "add IDs to requirements", "tag items in PRD.md", "number the requirements", "add requirement codes", "validate tags", "check duplicate tags", "verify tagging completeness". Accepts an application name and version as input (e.g., `/util-ustagger hub_middleware v1.0.3`, `/util-ustagger "Hub Middleware" v1.0.3`).