Skill UI

This skill guides the creation of comprehensive Product Requirements Documents (PRDs) following industry best practices. It ensures all critical sections are included, such as problem statements, user stories, functional/non-functional requirements, technical considerations, and success metrics. Use it when formalizing a new feature or product specification for engineers and stakeholders.

A comprehensive template designed to structure complex technical specifications, ensuring a complete record of engineering decisions. It guides users to document problem statements, proposed solutions, system architecture, data models, API designs, security considerations, and rollout plans, bridging product requirements and technical implementation.

This skill guides users through Phases 2 (Pseudocode Design) and 3 (Architecture Design) of the SPARC methodology. It translates high-level specifications into detailed technical blueprints, covering algorithm pseudocode, module boundaries, API contracts (using DDD patterns), and infrastructure planning, ensuring a robust plan before writing production code.

This tool executes the foundational SPARC Specification Phase (Phase 1) for new features or projects. It guides the user through systematically gathering comprehensive requirements, including functional/non-functional needs, defining concrete acceptance criteria (Given/When/Then), identifying technical constraints, and mapping edge cases. It creates a robust, formalized specification document that serves as the blueprint for all subsequent design and development phases.

A comprehensive, final-gate audit guide for submitting papers to major robotics conferences like ICRA using the PaperPlaza system. It details mandatory technical specifications, including page limits (6 content + 2 refs), IEEE two-column compliance, double-anonymous rules, video attachment specs, and critical deadlines. Essential reading to prevent submission rejection or administrative disqualification.

This guide details how to prepare the mandatory video attachment for robotics conference submissions. It covers strict technical specifications (e.g., 180 seconds, 20 MB), the crucial self-containment rule, effective storyboarding techniques, and necessary steps for anonymization. Learn to transform your video from a mere demonstration into robust, undeniable scientific evidence.

This gate review forces a transition from vague product direction to a concrete, buildable technical specification. It mandates the creation of architectural diagrams, data flow maps, state machines, and failure mode inventories before a single line of implementation code is written. Essential for complex features with async components or external dependencies.

This robust pipeline guides development teams through a rigorous, five-phase planning process *before* writing any code. It systematically analyzes PRDs, design specifications (UX, accessibility), and existing architecture to produce a comprehensive implementation plan. Key outputs include Architecture Decision Records (ADRs), detailed task breakdowns, and verification strategies, ensuring all technical and design decisions are documented and scoped.

This comprehensive guide defines a structured, multi-stage workflow for generating, sourcing, and validating all visual game assets. It covers everything from establishing art direction and style guides to managing technical specifications (resolution, scale, compression), and integrating assets into game engines. Use this for planning sprites, UI elements, concept art, and 3D models to ensure visual consistency and production readiness.

This specialized sub-agent is responsible for transforming high-level feature proposals and technical specifications into a formal, comprehensive 'design.md' document. It systematically captures all necessary technical details, including architectural decisions, data flow diagrams, detailed file changes, API contracts, and thorough testing strategies. Use this skill during the planning phase of any complex software change to ensure technical completeness and feasibility.

This skill guides you through a comprehensive, multi-phase interview to capture every necessary detail of a new project idea. It is designed to run BEFORE any code is written, forcing detailed specification gathering across purpose, features, data models, and technical constraints. The output is a clean, self-contained prompt.md file, ensuring subsequent development is based on solid, unambiguous requirements and preventing costly mistakes.

This skill converts complex, narrative technical documents, research excerpts, or natural language problem descriptions into a highly structured Mathematical Problem Specification (MPS). It systematically extracts variables, constraints, objectives, and uncertainty parameters. By adhering to a strict Zero-Inference Protocol, it ensures all extracted elements are strictly grounded in the source text, making it invaluable for formalizing real-world optimization, data science, and engineering problems.