ChocoVine

Use when converting architecture plans into implementation phases. Creates independent, bite-sized phase files that can be executed separately.

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Extract design assets and metadata from Figma using the Figma REST API. Supports exporting frames/components as images, extracting node metadata, design tokens, and file structure. Use with ai-multimodal skill for comprehensive UI research.

Comprehensive codebase documentation generator following a layered methodology. This skill should be used when scanning and documenting a codebase for the first time, when creating onboarding documentation for new developers, when generating architecture overviews, walkthroughs, and API references. Supports README generation, architecture diagrams, entry point documentation, pattern guides, and edge case documentation.

Generate structured handoff summaries between workflow phases. Use when transitioning between RQPIV phases.

Process and generate multimedia content using Google Gemini API. Capabilities include analyze audio files (transcription with timestamps, summarization, speech understanding, music/sound analysis up to 9.5 hours), understand images (captioning, object detection, OCR, visual Q&A, segmentation), process videos (scene detection, Q&A, temporal analysis, YouTube URLs, up to 6 hours), extract from documents (PDF tables, forms, charts, diagrams, multi-page), generate images (text-to-image, editing, composition, refinement). Use when working with audio/video files, analyzing images or screenshots, processing PDF documents, extracting structured data from media, creating images from text prompts, or implementing multimodal AI features. Supports multiple models (Gemini 2.5/2.0) with context windows up to 2M tokens.

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.

Guide for implementing Google Gemini API image understanding - analyze images with captioning, classification, visual QA, object detection, segmentation, and multi-image comparison. Use when analyzing images, answering visual questions, detecting objects, or processing documents with vision.

Design RESTful APIs following conventions with proper error handling, versioning, and documentation. Use when creating or modifying API endpoints.

Enforce SOLID, DRY, KISS principles during implementation. Auto-activated when writing or modifying code.

Design React/Vue components following atomic design and composition patterns. Use when creating UI components.

Implement consistent error handling across the application. Use when adding try-catch blocks, error boundaries, or custom error classes.

Create reversible database migrations with rollback scripts. Use when modifying database schemas.

Create detailed architecture plans with decision records and risk assessments. Use when planning significant features or system changes.

Generate clarifying questions from research findings. MUST be used before planning phase. Validates requirements are complete and unambiguous before technical work begins.

Parse user requirements into structured format with explicit assumptions, constraints, and acceptance criteria. Use when initial requirements are ambiguous or informal.

Generate structured codebase maps with dependency graphs, file relationships, and architectural patterns. Use when exploring unfamiliar codebases or documenting project structure.

Analyze project dependencies for security vulnerabilities, outdated packages, and upgrade paths. Use when auditing dependencies or planning upgrades.

Detect and document existing code patterns in a codebase. Use to maintain consistency with established conventions when writing new code.

Follow git conventions for commits, branches, and PRs. Auto-activated during git operations.

Review code for quality, security, performance, and maintainability. Auto-activate after code modifications.

Generate and update documentation from code. Use after successful implementation.

Scan code for OWASP vulnerabilities and security issues. Use for security-sensitive implementations.

Generate comprehensive tests following project testing patterns. Use after implementing features.