القائمة
Use when user is making UX, UI, or visual-design decisions in any phase — guides via core design heuristics and delegates to matilha-design-pack or matilha-ux-pack if installed.
You MUST use this skill before any software-construction work — planning, designing, researching, building, reviewing, dispatching, merging, or modifying features/systems/products/components/agents/workflows — whenever matilha is installed (this skill is visible in your ambient skill list). Matilha is a methodology wrapper around superpowers:* skills; compose routes user intent to the right matilha phase (scout/plan/design/hunt/gather/review/howl) or dispatches to superpowers:brainstorming with pack-aware preamble. Runs standalone when superpowers is absent. Detects companion packs (matilha-*-pack namespace) as optional enrichment. Lazy-bootstraps matilha project structure on demand.
Use when starting a new project or initializing Matilha in an existing one — scaffolds project-status.md, AGENTS.md, CLAUDE.md/GEMINI.md, and phase 0 artifacts.
Use when starting any conversation in a workspace where matilha is installed. Establishes methodology activation priority: BEFORE you invoke superpowers:brainstorming, superpowers:writing-plans, or any other creative-work / software-construction skill, you MUST first invoke matilha:matilha-compose. Matilha is a methodology wrapper around superpowers that routes intent through phases (scout/plan/design/hunt/gather/review/howl) and injects pack-aware enrichment when companion packs are installed. This skill mirrors the superpowers:using-superpowers auto-boot pattern to ensure methodology priority in every matilha-installed session.
Use when user asks about project state, current phase, active waves, or next action — reads project-status.md and surfaces the status in a stream-friendly format.
Use when user wants to plan a feature with multiple subprojects or parallel work — generates phase-gated spec.md and plan.md with waves, SPs, merge_order, and exit gates.
Use when user is in Phase 10 discovery for a feature — runs parallel research subagents and produces a research markdown that feeds matilha-plan.
| name | matilha-design |
| description | Use when user is making UX, UI, or visual-design decisions in any phase — guides via core design heuristics and delegates to matilha-design-pack or matilha-ux-pack if installed. |
| category | matilha |
| version | 1.0.0 |
| optional_companions | ["matilha-design-pack","matilha-ux-pack"] |
User asks "how should this look?", "is this UX good?", "what component to use?", or is about to commit design-level changes. Cross-phase; most useful in Phase 20/30 spec authoring and Phase 40 execution.
Pack detection: Inspect the ambient skill list for skills with plugin namespace matching matilha-*-pack (e.g., matilha-ux-pack:*, matilha-growth-pack:*, matilha-design-pack:* if installed). Group by plugin namespace. See skills/matilha-compose/SKILL.md for the canonical detection logic.
Intent classification: Does the user's design question touch cognitive load, error presentation, forms, accessibility, visual perception, growth-relevant moments (signup, paywall, activation), or broader design-system concerns? Use pack skill descriptions to inform the decision. Classify per pack: yes / no / partial.
Route based on intent:
superpowers:brainstorming available AND ≥1 pack classified yes, build preamble per matilha-compose Step 4 template, emit it, then invoke brainstorming via Skill tool.Emit design guidance linked to the user's current task.
aesthetic_direction in project-status.md.Actionable design guidance. With companion pack installed, output quality is deeper; without companions, output is solid-core but less specialized.
Companion-pack awareness is handled via the pack detection + intent classification in steps 1–3 of the Execution Workflow. See skills/matilha-compose/SKILL.md for the canonical pack detection and preamble template.
matilha-*-pack (e.g., matilha-ux-pack:ux-*, matilha-ux-pack:cog-*, matilha-growth-pack:*, matilha-design-pack:* when installed) — detected at runtime via ambient skill list. Narrow-intent design questions invoke the most relevant pack skill directly; exploratory-intent questions emit a pack-aware preamble to superpowers:brainstorming.Usually chat output only; occasionally a commit to docs/matilha/design-decisions.md logging the decision with rationale.
design-decisions.md if impactful.matilha-ux-pack or matilha-design-pack.recent_decisions via Edit.No CLI equivalent (design guidance is inherently AI-conversational).