Answers from the documentation; checking which model is on duty
Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
Imported from ssrjkk/claude-skills (.claude/skills/frontend/material-ui-components/SKILL.md). Install upstream with npx skills add ssrjkk/claude-skills --skill material-ui-components. Copyright stays with the author.
MUI Components
Components with MUI. UI components.
Quick Start
# MUI Components# See MUI docs
When to Use
Building applications with MUI
UI components
widgets
elements
Step-by-Step
Install: npm install material-ui
Set up MUI
Configure Components
Implement features
Test and verify
Dependencies
MUI >= latest stable
Runtime environment
Dependencies as needed
Examples
# MUI Components# See MUI documentation
Resources
Official MUI documentation
Community tutorials
GitHub repositories
Validation
Run: material-ui --version
Test with sample data
Verify output correctness
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
# after Install: the listing is in your workspace's routing pool - a plan picks it for its slotcurl-s-X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'
Installed into a catalogue, chosen by a router
Install material-ui-components and it becomes one more candidate the router can pick - when it fits.
A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.
