compose-neomithril-ui

name	compose-neomithril-ui
description	Compose @mithrilman/neomithril-ui components using the packaged recipes and surface model. Use when building cards, heroes, dialogs, forms, toolbars, or other multi-component UI sections in a consumer app.

Compose Neomithril UI

This skill helps you assemble components from the consumer side. Keep it thin: reach for the packaged recipes and manifest first, then adapt.

Recipe Sources

Start from these packaged surfaces:

1. node_modules/@mithrilman/neomithril-ui/docs/composition-recipes.md
2. node_modules/@mithrilman/neomithril-ui/docs/agent-reference.md
3. node_modules/@mithrilman/neomithril-ui/docs/components/INDEX.md
4. node_modules/@mithrilman/neomithril-ui/docs/consumer-setup.md
5. @mithrilman/neomithril-ui/manifest
   • use libraryManifest.componentDocs
   • use libraryManifest.components[*].consumerDocs
   • use libraryManifest.agentNotes

Composition Workflow

1. Classify the user need:
   • structural surface
   • semantic feedback
   • overlay / modal flow
   • page hero / summary region
   • form section
2. Choose the nearest packaged recipe.
3. Adapt the structure while keeping the surface model intact.
4. Explain why the chosen configuration fits better than the nearest alternative.

Default Composition Rules

• Keep large shells neutral or muted unless the component is explicitly a feedback primitive.
• Put semantic urgency in Notice / InlineNotice, badges, icons, progress, or CTA tone.
• Separate structure (variant), material depth (neoDepth), and affordance (clickable, interactive, pressed/selected state).
• Prefer root imports.
• Check consumer prerequisites when examples rely on theming, feedback hosts, or Material Symbols.

Recipe Shortcuts

• Settings, dashboard, or summary panel: start from the card recipe.
• Page intro with metrics or quick actions: start from the hero recipe.
• Confirmation or destructive flow: start from the dialog recipe.
• Form area with guidance plus validation: start from the form-panel recipe.

Guardrails

• Do not turn Card, Dialog, Hero, or Toolbar into fully saturated warning/success/danger shells.
• Do not invent repo-only guidance when the installed package already exports a docs surface.
• If the consumer asks for a pattern that is not covered, compose from the nearest recipe and say which rule you preserved.