Loading...
Loading...
Found 285 Skills
Create HTML UI mockups stored in ideas/[project]/docs/ui-designs/
Visualizes datasets in 2D using embeddings with UMAP or t-SNE dimensionality reduction. Use when exploring dataset structure, finding clusters, identifying outliers, or understanding data distribution.
Navigates C3 architecture docs and explores corresponding code to answer architecture questions. Use when the user asks: - "where is X", "how does X work", "explain X", "show me the architecture" - "find component", "what handles X", "diagram of X", "visualize X" - "describe X", "list components", "trace X", "flow of X" - References C3 IDs (c3-0, c3-1, adr-*) <example> Context: Project with .c3/ directory user: "explain what c3-101 does and how it connects to other components" assistant: "Using c3-query to navigate the architecture docs." </example> <example> Context: Project with .c3/ directory user: "show me a diagram of the C3 architecture" assistant: "Using c3-query to generate an architecture overview." </example> DO NOT use for changes (route to c3-change). DO NOT use for pattern artifact management — listing, creating, updating refs (route to c3-ref). Requires .c3/ to exist.
Strategic discovery of a project's capabilities from a solutions architect perspective. Deploys parallel discovery agents to map architecture, inventory features, and assess infrastructure, then synthesizes findings into a capabilities report with strategic improvement recommendations. Use when user says "explore", "what does this do", "project overview", "capabilities", "feature inventory", or asks about strategic direction.
Use this skill when the user doesn't yet know what to test. This is the "learn the site first" step — for unfamiliar websites, new projects, or any situation where Feature/Persona artifacts don't exist yet. Use when the user: gives a URL with no specific test in mind, asks what features or flows a site has, wants to explore or walk through a site, is new to a project, or says "explore before we test". Also use for bare "test [URL]" commands with no further context. Do not use when Feature artifacts already exist or the user references specific known tests or bugs.
Analyze and explore codebases using Repomix CLI. Use when: analyzing repositories, exploring code structure, finding patterns. Triggers on: 'analyze this repo', 'explore codebase', 'what's the structure'.
Use this when you are exploring the codebase. It lets you ask the AI who wrote code questions about how things work and why they chose to build things the way they did. Think of it as asking the engineer who wrote the code for help understanding it.
Conducts a guided conversational interview with the user about the image or scene they want to create, asking pertinent questions to fully understand their vision, then synthesizes a perfect model-appropriate prompt with recommended settings. Use when the user says "I want to create...", "help me make an image of...", "I have an idea for...", or asks for help crafting a prompt.
Use when researching technical approaches before building. Triggers on: "explore options", "what are my options for", "research approaches", "compare solutions", "dev explore", "generate proposals", "help me decide between". Runs parallel proposal generation via subagents and outputs to .codevoyant/explore/.