design-taxonomy
Design taxonomy structure for categories, tags, or hierarchical classification. Supports flat, hierarchical, and faceted patterns.
What this skill does
# Design Taxonomy Command
Design a taxonomy structure with terms, hierarchy, and classification rules.
## Usage
```bash
/cms:design-taxonomy Categories --type hierarchical
/cms:design-taxonomy Tags --type flat
/cms:design-taxonomy ProductFilters --type faceted
```
## Taxonomy Types
- **flat**: Simple tags with no hierarchy
- **hierarchical**: Parent-child tree structure
- **faceted**: Multi-dimensional classification
## Workflow
### Step 1: Parse Arguments
Extract taxonomy name and type from the command.
### Step 2: Gather Requirements
Use AskUserQuestion for structured requirements gathering:
```yaml
# Question 1: Taxonomy Scope (MCP: CMS taxonomy patterns)
question: "What is the primary purpose of this taxonomy?"
header: "Purpose"
options:
- label: "Content Organization (Recommended)"
description: "Categories for articles, pages, or documents"
- label: "Product Filtering"
description: "Faceted navigation for e-commerce catalogs"
- label: "Navigation Structure"
description: "Menu hierarchy and site sections"
- label: "Tagging System"
description: "Flexible labels for cross-cutting concerns"
# Question 2: Hierarchy Depth (MCP: CLI best practices - scope selection)
question: "How deep should the taxonomy hierarchy be?"
header: "Depth"
options:
- label: "Flat (Recommended)"
description: "Single level - simple tags or labels"
- label: "Shallow (2 levels)"
description: "Parent-child structure for basic grouping"
- label: "Deep (3+ levels)"
description: "Full hierarchical tree for complex domains"
```
Use these responses to tailor taxonomy type and structure.
### Step 3: Invoke Skill
Invoke `taxonomy-architecture` skill with gathered requirements.
### Step 4: Generate Taxonomy Design
Based on type:
**Flat Taxonomy:**
```yaml
taxonomy:
name: Tags
type: flat
settings:
allow_multiple: true
allow_new_terms: true
terms:
- name: Featured
- name: Trending
- name: Popular
```
**Hierarchical Taxonomy:**
```yaml
taxonomy:
name: Categories
type: hierarchical
max_depth: 3
settings:
allow_multiple: true
required_parent: false
terms:
- name: Technology
children:
- name: Software
children:
- name: Web Development
- name: Mobile Apps
- name: Hardware
- name: Business
children:
- name: Marketing
- name: Finance
```
**Faceted Taxonomy:**
```yaml
taxonomy:
name: ProductFilters
type: faceted
facets:
- name: Color
terms: [Red, Blue, Green, Black, White]
- name: Size
terms: [Small, Medium, Large, XL]
- name: Material
terms: [Cotton, Polyester, Wool, Leather]
- name: Price Range
terms: [$0-25, $25-50, $50-100, $100+]
```
### Step 5: Generate Implementation
Provide EF Core model for the taxonomy:
```csharp
public class Taxonomy
{
public Guid Id { get; set; }
public string Name { get; set; }
public TaxonomyType Type { get; set; }
public List<Term> Terms { get; set; }
}
public class Term
{
public Guid Id { get; set; }
public string Name { get; set; }
public string Slug { get; set; }
public Guid? ParentId { get; set; }
public int SortOrder { get; set; }
}
```
## Related Skills
- `taxonomy-architecture` - Taxonomy patterns
- `content-type-modeling` - Taxonomy fields
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.