agentleFS
ainurdevainurdev/mystical-assistant/.claude/skills/mystical-assistant-design/SKILL.md

mystical-assistant-design

Skill7 starsChanged 8 days agoMITView on GitHub

Use this skill to generate well-branded interfaces and assets for Mystical Assistant — a remote-dev bridge that runs Claude Code on your machine, driven from a Telegram bot, a Telegram Mini App, and a localhost desktop dashboard. Its look is a phosphor CRT terminal HUD (teal-on-black, monospace, scanlines, corner-bracketed panels, an occult-oracle voice). Use for production work or throwaway prototypes/mocks/decks. Contains design guidelines, color/type/spacing tokens, fonts, the brand emblem, reusable React components, and full UI-kit recreations of both surfaces.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the readme.md file within this skill, and explore the other available files.

    line 7
  2. Distinctive:

    If creating visual artifacts (slides, mocks, throwaway prototypes, etc), copy assets out and create static HTML files for the user to view.

    line 9
  3. Distinctive:

    If the user invokes this skill without any other guidance, ask them what they want to build or design, ask some questions, and act as an …

    line 14

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Read the readme.md file within this skill, and explore the other available files.

If creating visual artifacts (slides, mocks, throwaway prototypes, etc), copy assets out and create static HTML files for the user to view. If working on production code, you can copy assets and read the rules here to become an expert in designing with this brand.

If the user invokes this skill without any other guidance, ask them what they want to build or design, ask some questions, and act as an expert designer who outputs HTML artifacts or production code, depending on the need.

What's here

  • styles.css — the one stylesheet to link. @imports every token + font file in tokens/.
  • tokens/ — colors.css (the phosphor palette + moods), typography.css, spacing.css, effects.css (radius/glow/CRT primitives + the full keyframe library), fonts.css (Share Tech Mono + JetBrains Mono via Google Fonts), base.css.
  • assets/ — the brand emblem SVGs (emblem.svg, emblem-boot.svg).
  • components/ — reusable React primitives in four groups: core/ (Button, Chip, Card, Banner, StatusDot, Spinner), hud/ (Panel, Meter, Stat, Sparkline, SurfaceBadge, Emblem), terminal/ (ToolTag, ResultBlock, PromptLine), forms/ (Field, Dropdown). Each has a .d.ts (props) and .prompt.md (what/when + usage).
  • ui_kits/dashboard/ — the desktop HUD recreation (index.html + app.jsx).
  • ui_kits/miniapp/ — the Telegram Mini App recreation (index.html + app.jsx).
  • templates/ — copyable starting points (dashboard-hud/, mini-app/) that consuming projects can seed a new design from.
  • guidelines/ — foundation specimen cards (Colors / Type / Spacing / Brand).

Using the components

In an HTML file, link styles.css, load the compiled bundle _ds_bundle.js, then read components off the window namespace (run the design-system check to get the exact name — it looks like MysticalAssistantDesignSystem_<hash>):

<link rel="stylesheet" href="styles.css" />
<script src="_ds_bundle.js"></script>
<script type="text/babel">
  const { Panel, Button, Chip, Sparkline, PromptLine } = window.MysticalAssistantDesignSystem_24409d;
</script>

For static artifacts (no build), you can also just use the tokens + utility classes (.panel, .glow, .crt, .drawline) directly with the CSS custom properties.

The brand in one line

Teal phosphor (#7fe9d8) on a near-black void (#060a0a); everything monospace (Share Tech Mono for labels, JetBrains Mono for terminal/code); zero radius; corner-bracketed panels; scanlines + glow; UPPERCASE tracked instrument labels paired with a lowercase, italic oracle voice ("name the bug; i will unmake it."). See readme.md for the full content + visual + iconography guidance.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.