Neo Glow Control Board logo

Neo Glow Control Board

Community
Dezoff-max
neo-glow-control-board

Apply or adapt a dual-theme neo-glow control board for UI kits, design-system previews, settings surfaces, admin panels, control rooms, and dense operational interfaces. Use when Codex should build or restyle interface work with bright white or dark control surfaces, compact neumorphic cards, vertical icon rails, blue/cyan halo accents, glowing active states, luminous toggles, and a board focused on control states, inputs, and specification details.

Overview

PublisherDezoff-max
Repositorycodex-ui-board-skills
Skill nameneo-glow-control-board
Stars
15
Forks
0
Bundled files
9
LicenseMIT
Links
  • 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.

  • 9 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by Dezoff-max on GitHub. Read the source before you install it.

Installation

Install the Neo Glow Control Board AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

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.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/Dezoff-max/codex-ui-board-skills/tree/main/NeoGlowControlBoard/codex-skill
  4. 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.
2

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/Dezoff-max/codex-ui-board-skills.git /tmp/codex-ui-board-skills
mkdir -p .claude/skills
cp -r /tmp/codex-ui-board-skills/NeoGlowControlBoard/codex-skill .claude/skills/neo-glow-control-board
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Neo Glow Control Board 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 Neo Glow Control Board 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 Neo Glow Control Board 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.

Neo Glow Control Board

Use this skill to build or restyle interfaces in a luminous control-board style derived from soft-neumorphic surfaces plus bright blue glow states. Keep the system dense, technical, tactile, and state-driven.

Workflow

  1. Read references/usage.md first.
  2. Load only the files needed for the task:
    • references/NeoGlowControlBoard.tokens.json for semantic token values
    • references/NeoGlowControlBoard.css for component and glow behavior
    • references/tailwind.preset.cjs when the host project uses Tailwind
    • references/preview.html when you need the full board or screenshot-safe capture behavior
  3. Decide whether the task needs:
    • token remapping
    • component restyling
    • a full control-board or design-system preview
  4. Keep active states luminous and neutral states quiet.
  5. Verify that glow is concentrated on meaningful controls instead of flooding the whole screen.

Non-Negotiables

  • Keep the base interface calm and pale or dark-neutral; reserve blue/cyan glow for active and highlighted states.
  • Use glow as an intentional signal, not background decoration.
  • Maintain compact, control-heavy layout with clear component groupings.
  • Keep rails, cards, inputs, toggles, and chips within the same material family.
  • Do not mix this style with colorful dashboard mosaics, glassmorphism, or heavy gradient backgrounds.

Component Rules

Foundations

  • Surfaces should feel soft, compact, and slightly technical.
  • Border radius should stay generous but not overly playful.

Controls

  • Buttons, toggles, sliders, selects, and focused inputs should carry the strongest glow behavior.
  • Focus rings should remain visible and deliberate.

Rails and Navigation

  • Side icon rails should feel like control strips, not consumer app sidebars.
  • Active rail items may glow more strongly than secondary items.

Specs and States

  • The board should document behavior as much as appearance.
  • Include checklists, state chips, and grouped control samples when useful.

Deliverables

  • Provide both light and dark themes unless the user explicitly asks for one theme only.
  • Prefer shareable preview pages with screenshot-safe capture mode.
  • Keep the resulting kit suitable for handoff to frontend developers or designers.

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 Neo Glow Control Board AI skill do?

Apply or adapt a dual-theme neo-glow control board for UI kits, design-system previews, settings surfaces, admin panels, control rooms, and dense operational interfaces. Use when Codex should build or restyle interface work with bright white or dark control surfaces, compact neumorphic cards, vertical icon rails, blue/cyan halo accents, glowing active states, luminous toggles, and a board focused on control states, inputs, and specification details.

Why use Neo Glow Control Board on TypingMind?

Because you install it once and use it with any model. Neo Glow Control Board 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 Neo Glow Control Board in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Dezoff-max/codex-ui-board-skills/tree/main/NeoGlowControlBoard/codex-skill. 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 Neo Glow Control Board?

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 Neo Glow Control Board?

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

Is the Neo Glow Control Board AI skill free?

Yes. It is published on GitHub by Dezoff-max 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

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇