skills.rest
MithrilMan
MithrilManCOMMUNITY
Explore all skills by this author →
𝕏@MithrilManGitHub

compose-neomithril-ui

Compose Neomithril UI components from packaged recipes and manifests.

Updated Mar 12, 2026
Search Tags:#documentation#compose#neomithril-ui#packaged-recipes#surface-model#ui-assembly
One-click install
npx skills add https://github.com/MithrilMan/neomithril-ui --skill compose-neomithril-ui
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: compose-neomithril-ui
Source: https://github.com/MithrilMan/neomithril-ui/tree/main/codex-skills/compose-neomithril-ui
Command: npx skills add https://github.com/MithrilMan/neomithril-ui --skill compose-neomithril-ui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Compose 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.

Core Features & Use Cases

  • Leverage packaged recipes and surface-model guidance to assemble consumer-facing UI sections (cards, hero regions, dialogs, forms, toolbars).
  • Follow a clear composition workflow: classify the need, pick the nearest packaged recipe, adapt structure while preserving the surface semantics.
  • Guardrails ensure surfaces stay neutral and avoid over-saturation, while referencing the library manifest for consumer docs and notes.

Quick Start

Start by selecting a packaged recipe that matches your UI surface and adapt its structure to your consumer app.

Frequently Asked Questions about compose-neomithril-ui

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

FAQPage Schema
How do I assemble UI components for consumer app workflows like cards and dialogs?▼

Neomithril UI composition works by selecting a packaged recipe that matches your target surface and adapting its structure. You classify the UI need, pick the nearest recipe, and modify it while preserving surface model semantics.

What is the surface model approach for building multi-component UI sections?▼

Use packaged recipes and surface-model guidance when building consumer-facing UI sections such as cards, heroes, dialogs, forms, and toolbars. This ensures structure and semantics are preserved while keeping surfaces neutral.

Can I adapt a packaged recipe structure for forms and toolbars without breaking semantics?▼

No external dependencies are required to compose Neomithril UI surfaces. The Skill operates independently using packaged recipes, library manifests, and surface models to assemble multi-component UI sections for consumer apps.

What's the best way to keep consumer-facing UI surfaces neutral and avoid over-saturation?▼

Yes, you can adapt packaged recipe structures for forms and toolbars without breaking semantics. The composition workflow allows structural modifications while guardrails ensure the surface model semantics remain intact and neutral.

Do I need external dependencies to compose Neomithril UI sections?▼

The best way to keep consumer-facing UI surfaces neutral and avoid over-saturation is to follow the composition guardrails. These leverage packaged recipes and library manifest references to constrain visual and structural density.

Related Skills

Explore More Software Engineering Skills→
MithrilManMithrilMan

use-neomithril-ui

Navigate the installed @mithrilman/neomithril-ui package manifest, docs, and type declarations.

Community
Basic
monobaselabsmonobaselabs

shadcn

Automate adding shadcn/ui components to a frontend app via the CLI.

Official
Intermediate
overviewlabsoverviewlabs

qmd

Search local Markdown collections with hybrid keyword and vector retrieval.

Community
Advanced
zoomzoom
7

choose-zoom-approach

Maps use cases to optimal Zoom surfaces and integration paths.

Official
Intermediate