Opensource Ui

Community

bidyut10

opensource-ui

Use Opensource UI patterns and copy-paste React/Next.js components from opensourceui.in. Trigger when building or refining interfaces that need its component catalog, visual language, Tailwind conventions, mockups, widgets, forms, tables, social cards, or interactive controls.

Overview

Publisher	bidyut10
Repository	`opensourceui`
Skill name	`opensource-ui`
Stars	724
Forks	21
Bundled files	4
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
4 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by bidyut10 on GitHub. Read the source before you install it.

Installation

Install the Opensource Ui AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/bidyut10/opensourceui/tree/main/skills/opensource-ui
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/bidyut10/opensourceui.git /tmp/opensourceui
mkdir -p .claude/skills
cp -r /tmp/opensourceui/skills/opensource-ui .claude/skills/opensource-ui

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Opensource Ui in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Opensource Ui on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Opensource Ui is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Opensource UI

Use this skill when the user asks for an Opensource UI component, an Opensource UI-inspired interface, or a React/Next.js component selected from the Opensource UI catalog.

Works with any coding agent (Cursor, Claude Code, Codex, Copilot, Grok, etc.). Read the reference files in this skill folder before generating UI.

Core workflow

Identify the requested UI role, such as button, input, calendar, widget, mockup, notification, table, social card, or editorial card.
Search references/catalog.md for the closest catalog entry and route.
Read references/design.md for the visual rules. Apply the neutral stage, Instrument Serif for brand display text, Geist for UI text, restrained accents, flat surfaces, and border-based focus states.
If source code is available in the attached repository or a target project, inspect the relevant component before adapting it. Preserve the component's state behavior, accessibility, and prop API unless the user requests a change.
For a new web project, use React or Next.js with TypeScript and Tailwind CSS v4. Copy the needed component files and icon dependencies. There is no package installation step for the UI library itself.
Copy lib/cn.ts when the component uses cn, then install or preserve clsx and tailwind-merge. Copy imported icons from the repository's icons/ tree. Keep use client when the component uses browser state, effects, event handlers, or browser APIs.
Use base styles plus md: responsive variants. Do not introduce sm: breakpoints. Prefer native HTML semantics, keyboard support, labels, visible error text, and WCAG AA contrast.
Verify the result in the target project. Check interaction states, reduced-motion behavior, mobile layout, focus visibility, and import paths.

Design rules

Keep site chrome neutral: white or near-white surfaces, neutral borders, dark ink, and sparse cyan, rose, amber, teal, or emerald accents inside demos and state changes. Use flat surfaces by default. Avoid purple-family colors, gradients, glow, colored blur, glassmorphism, stacked card shadows, generic AI styling, and heavy dashboard chrome.

Use rounded-md for buttons, rounded-lg for fields and small cards, and rounded-2xl for larger editorial or testimonial surfaces. Use p-4 as the common internal padding. Style input focus with a darker border and ring-0, never a colored ring. Use rose for errors and required markers. Prefer forwardRef for interactive components, native HTML prop extension, and cn() for class merging.

Catalog use

The catalog contains 200+ documented components across 30 categories as listed on the site. The source repository contains the implementation files and may include additional support or showcase files. Use the category and slug in references/catalog.md to locate a component page. Use the source path in references/source_inventory.txt when working from the cloned repository.

Component pages provide a live preview, implementation details, and copy-ready source. Treat the site's source and repository as the authority for exact props and behavior. Do not invent a prop API when source is available.

Reference files

Read references/catalog.md to select a component by category, name, slug, and summary.
Read references/design.md for the full design system, tokens, typography, spacing, elevation, component rules, and prohibited patterns.
Read references/implementation.md for repository layout, setup commands, dependency conventions, icon conventions, and copy-paste guidance.
Read references/source_inventory.txt when exact repository file names or category directories are needed.

Invocation examples

Use requests such as:

"Use the Opensource UI Booking Slot Calendar in my Next.js page."
"Build a clean dashboard with Opensource UI tables and widgets."
"Make this form follow the Opensource UI design language."
"Find the closest Opensource UI component for a travel boarding pass."

When the user specifies a target project, adapt imports, aliases, Tailwind setup, and image handling to that project. When no target project exists, provide the component code and state the required files and dependencies.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Opensource Ui AI skill do?

Why use Opensource Ui on TypingMind?

Because you install it once and use it with any model. Opensource Ui is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Opensource Ui in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/bidyut10/opensourceui/tree/main/skills/opensource-ui. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Opensource Ui?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Opensource Ui?

As many as you like. As long as a model supports skills, you can use Opensource Ui with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Opensource Ui AI skill free?

Yes. It is published on GitHub by bidyut10 under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Concept Diagrams

NousResearch

OrganizationPopular

Generate flat, minimal educational SVG visuals as HTML.

Hyperframes

Render MP4/WebM videos from HTML compositions.

Ip As Logo

Design minimal cute IP mascot marks readable at 32px.

Mono Color

Generate one- or two-ink editorial print poster images.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Opensource UI

Core workflow

Design rules

Catalog use

Reference files

Invocation examples

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now