use-neomithril-ui

name	use-neomithril-ui
description	Navigate the installed @mithrilman/neomithril-ui package like a consumer agent. Use when you need imports, setup rules, prop-discovery guidance, theming expectations, or high-level usage help without browsing the library repository.

Use Neomithril UI

This skill is intentionally thin. It should point you to the packaged docs and manifest that ship with @mithrilman/neomithril-ui, not duplicate them.

Start Here

When the package is installed in a consumer app, prefer these surfaces in order:

1. @mithrilman/neomithril-ui/manifest
   • Start with libraryManifest.docs, libraryManifest.componentDocs, libraryManifest.components, libraryManifest.distributedCodexSkills, and libraryManifest.agentNotes.
2. Installed Markdown docs under the package root:
   • node_modules/@mithrilman/neomithril-ui/docs/agent-reference.md
   • node_modules/@mithrilman/neomithril-ui/docs/components/INDEX.md
   • node_modules/@mithrilman/neomithril-ui/docs/consumer-setup.md
   • node_modules/@mithrilman/neomithril-ui/docs/composition-recipes.md
   • node_modules/@mithrilman/neomithril-ui/docs/theme-customization.md
3. Published type declarations for prop-level detail:
   • node_modules/@mithrilman/neomithril-ui/dist/index.d.ts
   • relevant node_modules/@mithrilman/neomithril-ui/dist/**/**/*.d.ts

If the package is not installed yet, answer from the explicit docs surface in the package repository only as a fallback.

Working Rules

• Prefer root imports from @mithrilman/neomithril-ui.
• Import @mithrilman/neomithril-ui/styles.css once.
• Inject generated theme CSS with createThemePreferenceCss('system') unless the consumer needs lower-level control.
• Render one feedback host near the app root.
• Treat Card, Dialog, Hero, Toolbar, and MarkdownEditor as structural surfaces first.
• Put semantic urgency in Notice / InlineNotice, badges, icons, progress, or CTA tone.
• Treat variant as structure, neoDepth as material feel, and affordance props such as clickable / interactive as interaction.

Prop Discovery

• Use libraryManifest.componentDocs when you need the packaged Markdown file for one exact component export.
• Use libraryManifest.components[*].propTypes to find the exported type names.
• Use libraryManifest.components[*].consumerDocs to choose the packaged docs to open first.
• Validate exact prop names against the published .d.ts files, not against assumptions.

Guardrails

• Do not depend on repository-only src/... or Storybook paths unless you are explicitly working inside the library repository.
• Do not hand-maintain derived --surface-neo-* or --shadow-neo-* variables unless the user explicitly wants a custom override strategy.
• If the request is about a likely library defect or docs gap, hand off to $report-neomithril-ui-issue.