Skill UI

A comprehensive guide to building robust, maintainable, and idiomatic Perl applications using modern features (Perl 5.36+). This resource covers best practices for object-oriented programming (Moo/Moose), advanced error handling (Try::Tiny), context sensitivity, complex regex usage, and efficient module design.

This comprehensive guide covers essential security patterns for Perl development, addressing common vulnerabilities like SQL Injection, XSS, Path Traversal, and Shell Injection. It details best practices including using Perl's Taint Mode, implementing strict allow-list validation, performing safe file operations, and executing external commands securely to ensure robust and resilient applications.

This skill is intended for Perl testing functionalities. Currently, the Japanese translation and content are under development, serving as a placeholder. Users should refer to the original English skill file for the core functionality and detailed implementation.

This skill provides sophisticated project estimation by adapting to human-only, hybrid, or agent-first development modes. It uses research-backed PERT statistics and confidence bands (P50, P75, P90) to forecast development timelines for tasks, backlogs, and capacity planning. It continuously calibrates estimates based on actual completion data, ensuring accuracy in AI-assisted and hybrid development environments.

This skill orchestrates the entire coding lifecycle as a state machine, ensuring tasks proceed from issue intake through implementation, structured review, deployment, and final acceptance verification. It enforces a rigorous 'Definition of Done' (DoD) proof, moving beyond simple code changes. Ideal for complex feature development requiring structured handoffs and explicit verification evidence.

This skill manages complex coding tasks from initial implementation through testing, review incorporation, deployment, and final runtime verification. It ensures the task meets explicit Definition of Done (DoD) criteria iteratively, minimizing the need for manual prompting across multiple development stages.

This skill enforces a mandatory, structured gate for starting new implementation tasks. It mandates that all work must be tracked via a GitHub issue, requiring explicit, testable acceptance criteria before any execution can begin. It defines a strict workflow (Problem, Goal, Scope, Acceptance Criteria, Status) to manage task readiness, ensuring that development only proceeds when criteria are fully defined and verifiable.

A structured methodology for de-risking product ideas and validating market opportunities. This framework guides teams through defining measurable outcomes, building Opportunity Solution Trees (OST), mapping critical assumptions (Desirability, Viability, Feasibility), and planning rigorous experiments (prototyping, interviews, usability tests) before committing to full development resources. Ideal for discovery sprints and pre-build validation.

This skill enforces rigorous governance and discipline when AI modifies systems, debugs code, or makes root-cause claims. It mandates safety gates (e.g., backup, blast radius check), demands evidence for every diagnosis, and prevents common AI shortcuts like guessing or deflecting. Use this for critical code modifications, complex debugging, and high-stakes deployments to ensure thoroughness and safety.

A comprehensive guide for building robust, production-grade desktop applications using Electron. This skill covers advanced topics including multi-process architecture, mandatory security hardening (contextIsolation, sandbox), secure IPC communication, and best practices for packaging, code signing, and implementing auto-update features.

Coordinates Exa MCP-driven web_search_exa and get_code_context_exa calls for up-to-date web results, code snippets, and company or people intel whenever the user requests research, competitive analysis, or development context.

This command executes the entire AgentHub lifecycle in a single, chained invocation. It automates complex development tasks by sequentially handling initialization, capturing performance baselines, spawning multiple specialized agents, evaluating the results (via metrics or LLM judging), and finally presenting a winner for merging. Use this when running an end-to-end competition or complex refactoring task.