agentleFS
jamesbrinkjamesbrink/nxv/.agents/skills/nxv-design/SKILL.md

nxv-design

Skill136 starsChanged 3 months agoMITView on GitHub

Use this skill to generate well-branded interfaces and assets for nxv (Nix Version Index) — either for production or throwaway prototypes/mocks. Contains essential design guidelines, colors, type, fonts, assets, and UI kit components for prototyping the "Blueprint" dark developer-tool look.

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 11

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.

Quick orientation

  • Look: "Blueprint" — dark-only, deep cool-navy canvas with a faint 48px engineering grid (masked to fade behind content), the colourful Nix snowflake as the hero mark, JetBrains Mono as the signature voice, one Nix-blue accent.
  • Tokens: link styles.css (it @imports everything in tokens/). Reference semantic aliases — --surface-page, --surface-glass, --text, --accent, --border, --ring-focus, --grid-image — not raw hexes. All colour is oklch.
  • Fonts: fonts/inter-var.woff2 (UI/body) + fonts/jetbrains-mono-var.woff2 (data/code/headings). Real binaries, no substitutes.
  • Assets: assets/nix-snowflake.svg (hero mark + favicon), assets/nxv-logo-dark.svg / nxv-logo-light.svg (bracket monogram).
  • Icons: Lucide-style 2px-stroke line icons (stroke="currentColor", no fill). No emoji, no icon font.
  • Voice: lowercase terminal-native labels, second-person imperative prose, dry wit, concrete numbers and real package names. Mono for anything machine-shaped. Eyebrows read like // code comments.

Components

Compiled to _ds_bundle.js under window.NxvDesignSystem_0fa7ce. Core: Button, Chip, Kbd, StatusPill, Panel, Metric, SegmentedToggle, Callout, Toast. Product: SearchPrompt, Terminal, VersionBadge, PackageRow, PackageCard, VersionTimeline, ActivityBars. Each component has a .prompt.md with a usage example. ui_kits/search-app/ is a full interactive reference; Landing.html is the marketing page.

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.