Skill UI

An interactive skill designed to interview users to capture project vision, core decisions, and technical preferences. It systematically converts raw discussions into structured documentation, maintaining the project's history in ADRs (Architectural Decision Records) and its overarching goal in the README.

This skill helps developers create highly focused, folder-specific documentation (`CLAUDE.md` and `AGENTS.md`). It systematically analyzes all files in a target directory to extract project purpose, operational constraints, naming conventions, and critical decisions. This deep context ensures that future AI agents (like Claude or Codex) operate with localized knowledge, preventing them from relying on global, generalized instructions and improving their accuracy in that specific domain.

The /goal command converts standard agent prompts into persistent, self-correcting loops (plan → act → test → review → iterate). It is designed for long-running, complex engineering tasks like migrations, coverage lifts, or refactoring, ensuring progress is tracked against a verifiable stop condition and mandated documentation.

WGM is a robust, agentic methodology designed to transform vague or rough requirements into working, validated software. It enforces a disciplined workflow across six stages: deep alignment (Grill), structured planning, deterministic iterative building (Loop), mandatory holdout-scenario judging, and final documentation audits. It ensures that the resulting code converges against rigorously tested acceptance criteria rather than relying on single-pass generation.

This skill automates the creation of Architecture Decision Records (ADRs) by generating sequential IDs, writing markdown files, and registering entries in AgentDB. It handles slugification, template generation, and links related decisions for better project documentation management.

Generate API documentation from TypeScript/JavaScript source code, extracting JSDoc annotations and producing OpenAPI 3.0 specs for HTTP endpoints.

Generate and maintain technical documentation automatically using MCP workers and cron scheduling. This skill detects drift between code and docs, supports scoped generation for APIs or full projects, and stores patterns for consistency. Ideal for keeping documentation up-to-date without manual effort.

This skill fetches the latest, live documentation and code examples for specific libraries and frameworks (e.g., Next.js, React, Prisma). Instead of relying on static or outdated training data, it utilizes the Context7 MCP to provide accurate, up-to-date answers for setup questions, API references, and code generation based on current best practices.

This skill manages the secure transition of private internal projects to public open-source releases. It executes a three-stage pipeline: Forking (removing secrets), Sanitizing (verifying clean code), and Packaging (generating required documentation like README, setup.sh, and CLAUDE.md). It ensures code safety and readiness before public deployment.

This skill transforms you into an expert design system guideline author, specializing in creating structured, implementation-ready documentation for the Power brand. It provides a comprehensive workflow covering style foundations (color, typography, spacing), component anatomy, accessibility standards (keyboard-first, high contrast), and quality gates. Use it to ensure all digital products maintain superior aesthetic consistency, usability, and accessibility.

This skill executes the final two phases of the SPARC methodology: Refinement and Completion. It systematically reviews the implemented feature through rigorous code reviews, expands test coverage (unit, integration, edge cases), validates performance, generates a traceability matrix, creates comprehensive documentation, and confirms deployment readiness. It ensures the feature is robust, tested, and production-ready.

This skill acts as an expert guide for creating comprehensive, implementation-ready design system documentation. It structures guidelines by defining foundational tokens (color, typography, spacing), detailing component anatomy, interaction states, and adhering to strict accessibility standards (WCAG 2.2 AA). Use it to ensure your design standards are consistent, technically sound, and actionable for engineering and design teams.