OpenTUI
Build terminal user interfaces with OpenTUI — Core, React or Solid APIs
- What
- Build terminal user interfaces with OpenTUI — Core, React or Solid APIs
- Cost
- Free
- Needs
- a JavaScript runtime (bun recommended) and the OpenTUI packages for the framework you target
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a consolidated skill for building terminal user interfaces with OpenTUI: decision trees pick the right framework (Core, React or Solid) and components, then five-file framework references (overview, API, configuration, patterns, gotchas) guide the implementation — with critical rules baked in (use `create-tui` for new projects, never call `process.exit()` directly, text styling via nested tags in React/Solid). By @msmps, listed here with credit to its creator. Honest caveats: it teaches the agent to write OpenTUI code — you still need the OpenTUI packages and a JS runtime to run it; the decision-tree structure means the agent must actually read the referenced files, not skim. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: a JavaScript runtime (bun recommended) and the OpenTUI packages for the framework you target Install "OpenTUI" for me. Build terminal user interfaces with OpenTUI — Core, React or Solid APIs Repository: https://github.com/msmps/opentui-skill/blob/main/skill/opentui/SKILL.md 1. Fetch the SKILL.md file for the msmps-opentui skill from the repository into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "msmps-opentui". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. any accounts, API keys, or CLI tools mentioned in the prerequisites above). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.