ideate-component

Brainstorm plugin component concepts and produce structured concept cards for skills, agents, commands, and hooks.

1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/JaviMontano/mao-plugin-qa --skill ideate-component-javimontano
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ideate-component
Source: https://github.com/JaviMontano/mao-plugin-qa/tree/main/skills/ideate-component
Command: npx skills add https://github.com/JaviMontano/mao-plugin-qa --skill ideate-component-javimontano

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When extending a Claude Code plugin, it is hard to decide whether a new idea should be a skill, agent, command, or hook, and whether it overlaps with existing components. This Skill analyzes the existing plugin structure and produces a reviewed concept card before any code is written. ## Core Features & Use Cases - Component Type Decision: Uses a decision matrix to determine whether an idea should be a skill, agent, command, or hook. - Conflict and Dependency Analysis: Reads the existing plugin structure to detect responsibility overlap and missing dependencies. - Concept Card Output: Produces a structured card with name candidates, responsibility statement, movement placement, MOAT depth recommendation, tools, and line estimates. - Use Case: You want to add CSV validation to a data-pipeline plugin. The Skill inspects the plugin, proposes the name validate-csv, maps its dependencies, and recommends a STANDARD MOAT depth before you design it. ## Quick Start Ask the assistant to ideate a new skill component for your plugin that validates CSV files before import.

Frequently Asked Questions about ideate-component

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decide between a skill, agent, command, or hook for a plugin?▼

Use the decision matrix: skills handle multi-step procedures, agents coordinate multiple skills, commands provide user entry points, and hooks trigger on lifecycle events. The Skill walks through a flowchart based on whether the behavior is user-invoked or event-driven.

How do I brainstorm a new component for an existing Claude Code plugin?▼

Provide the component type and plugin path. The Skill reads the plugin's existing components, proposes kebab-case name candidates, maps relationships and conflicts, and outputs a concept card with a MOAT depth recommendation.

Does the ideate-component skill create files in my plugin?▼

No, it is strictly read-only. It reads the existing plugin structure and proposes a concept card, but never creates files or directories. Implementation happens later through a separate design step.

What is MOAT depth and how is it recommended?▼

MOAT depth defines how much supporting material a component needs: MINIMAL (SKILL.md only), STANDARD (plus references), FULL (plus examples), or DEEP (plus prompts). The recommendation is based on the component's assessed complexity.

What are the limitations of component ideation before a plugin is scaffolded?▼

Without an existing plugin structure, relationship mapping is inferred from an architecture plan or brief rather than verified against real files. The Skill also cannot judge whether a component is useful to end users, only that it is structurally sound.