use-neomithril-ui

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

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/MithrilMan/neomithril-ui --skill use-neomithril-ui
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: use-neomithril-ui
Source: https://github.com/MithrilMan/neomithril-ui/tree/main/codex-skills/use-neomithril-ui
Command: npx skills add https://github.com/MithrilMan/neomithril-ui --skill use-neomithril-ui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Navigate the consumer-facing surface of the installed package to surface its manifest, docs, and guidance without browsing the repository.

Core Features & Use Cases

  • Surface the library manifest data (docs, components, and agent notes) to inform usage decisions.
  • Point to installed Markdown docs and published type declarations for quick reference.
  • Guide consumers on preferred import surfaces and theming expectations with minimal setup.

Quick Start

Prefer the packaged surfaces in order: library manifest, installed Markdown docs, then published type declarations.

Frequently Asked Questions about use-neomithril-ui

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

FAQPage Schema
How do I find documentation and component props for the installed neomithril-ui package?

To find neomithril-ui documentation and component props, navigate the installed package's manifest data, Markdown docs, and published type declarations. This approach surfaces high-level usage guidance and prop-discovery without inspecting the library source code directly.

What is the correct way to import neomithril-ui components and apply theming in my client app?

Correct neomithril-ui imports and theming application are guided by the library manifest and installed docs. Consumers should reference these packaged surfaces to understand preferred import paths and theming expectations with minimal setup required.

Can I browse the repository source code to understand neomithril-ui setup rules?

Browsing the repository source code is not recommended for neomithril-ui setup. Surface-first guardrails direct users to the installed package manifest, Markdown docs, and type declarations to enforce usage guidance and avoid repository paths.

What is the recommended order for looking up neomithril-ui manifest data and type declarations?

The recommended order for looking up neomithril-ui data is: library manifest first, installed Markdown docs second, then published type declarations. This packaged surface hierarchy ensures accurate usage decisions and prop-discovery.

Why does my neomithril-ui documentation lookup fail when inspecting package internals?

Neomithril-ui documentation lookups fail when inspecting package internals because the Skill enforces a surface-first approach. It directs consumers to the manifest, installed docs, and type declarations, applying guardrails to prevent accessing repository paths.