rashidee
- 24 skills
- 0 followers
- 8 hours ago last updated
- ▌ Depgen K8S · rashidee bundleGenerate 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.
- ▌ Util Updprd · rashideeApply a free-form requirement change to the PRD.md files of a CO2 project. Takes a human-written prompt describing NEW requirements or updates to existing ones, analyzes the PRD.md of every custom application to determine which applications, modules and subsections (User Story, Non Functional Requirement, Constraint, Reference, Test) are impacted, and decides for each impacted item whether to ADD, CANCEL or MODIFY it. Automatically classifies the change complexity per application as major, minor or patch, computes the next semantic version, and writes the new/updated items under a NEW version tag layered on top of the existing versions in each PRD.md — never rewriting or deleting prior versions. Cancelled items are struck through in place and recorded in the new version. New items are tagged with unique IDs (via util-ustagger) and a CHANGELOG.md entry is appended per impacted application. Presents an impact plan for human confirmation before writing (skippable with `--auto-approve` for orchestrated runs). ALW
- ▌ Util Ustagger · rashideeTag 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`).
- ▌
- ▌
- ▌
- ▌ Tracegen Matrix · rashideeRequirement-to-code traceability generator — links every PRD requirement ID (User Stories, Non-Functional Requirements, Constraints) and bug code from a module's SPEC.md to the source code that implements it, and writes a per-application context/TRACEABILITY.md matrix. Resolves links primarily from the in-source CO2 traceability comments written by conductor-feature-develop and conductor-defect (e.g. `Implements: USHM00003`, `Bug fixes: [BUG-024]`), with a name-based source-scan fallback, and OPTIONAL precision enrichment from the codebase-memory knowledge graph when that MCP server is installed. Works fully WITHOUT codebase-memory. Takes an application name (mandatory), with optional version and module filters. Use when the user asks to "generate traceability", "update the traceability matrix", "link requirements to code", "regenerate TRACEABILITY.md", or when invoked as a sub-step by the feature/defect conductors after code or bug-fix changes.
- ▌ Util Usanalyzer · rashideeAnalyze 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"`).
- ▌
- ▌
- ▌
- ▌ Util Projectinit · rashidee bundleInitialize a new CO2 project by validating a hand-authored brainstorm session document and setting up the file-based, turn-based BRAINSTORMING session kit around it. The ONLY valid input is the path to an EXISTING `<topic>.brainstorm.md` file the user authored from the CO2 application-development template (`brainstorm-template-appdev.md`) — free-form prompts, idea text or topic slugs are NOT accepted. The skill strictly validates the session document against the template, rejecting with a report on any deviation — it never creates or edits the session document. On a clean pass it scaffolds the rest of the brainstorm kit in the project folder: the shared `brainstorm-protocol.md`, the `co2-context-generation-guide.md` artifact rules, and the `/brainstorm-loop` slash command. The user then manually runs `/brainstorm-loop` — an iterative, token-efficient loop that converges the root `CLAUDE.md` (Phase A) and every application's `PRD.md` (Phase B) round by round. This skill seeds the project — it is the first skil
- ▌ Util Projectsync · rashideeSynchronize 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.
- ▌
- ▌
- ▌
- ▌ Specgen Node CLI Web · rashidee bundleGenerate a detailed specification document for building a self-hosted Node.js web application distributed as a global npm CLI — installed via `npm install -g <app-name>`, started via `<app-name> start`, and accessed at `http://IP:PORT`. Single-process, local-first architecture: one Node 22 process serves both the REST API (Hono 4) and an embedded pre-built React 19 + Vite 6 SPA styled with Tailwind CSS v4 and vendored shadcn/ui. Data lives in per-user SQLite (better-sqlite3 + Drizzle ORM with shipped migrations, auto-migrated on start). Authentication is hand-rolled scrypt sessions with a first-run auto-generated admin, forced password change, and admin-managed users — no OAuth, no JWT, no email flows. CLI parsing via commander 12, bundling via tsup 8, monorepo via pnpm workspaces, Biome lint/format, Vitest + Playwright tests, mandatory built-binary smoke test. Standardized input: application name (mandatory), version (mandatory), module (optional). Use this skill whenever the user asks to create a spec, spec
- ▌ Specgen React Tailwind · rashidee bundleGenerate a detailed specification document for building a React SPA (Single Page Application) using React 19, TypeScript 5, Vite 6, Tailwind CSS v3, Headless UI v2, Heroicons, React Router v7, TanStack Query v5, Zustand v5, React Hook Form v7, and Zod v3. Components are built utility-first with Tailwind and made accessible with Headless UI primitives (no component framework like MUI). Authentication (Keycloak OAuth2/OIDC PKCE, generic OIDC, or none), API integration (REST via Axios), and optional features (WebSocket, i18n, TanStack Table data grids, Recharts charts, react-day-picker date pickers, Tiptap rich text) 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 styled with Tailwind CSS. Also trigger when the user says things like "spec out a new React Tailwind project", "design
- ▌
- ▌ Conductor Feature Develop · rashidee bundleApplication 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 exis
- ▌ Conductor Feature Prepare · rashideeContext artifacts preparation orchestrator — generates all context artifacts (module models, HTML mockups, technical specifications, test specifications) by invoking the appropriate sub-skills, tracking progress in a PREPARE_MASTER.md file for cross-session resumption. 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.
- ▌
- ▌
- ▌