agentleFS
ProfSynapseProfSynapse/nexus/.claude/skills/nexus-ui-mockups/SKILL.md

nexus-ui-mockups

Skill158 starsChanged 11 days agoMITView on GitHub

Design a Nexus UI change as a standalone mockup under docs/mockups/ before any production code, then hand it off as the visual contract a plan implements against. Use when asked for a new view, panel, modal, settings tab, chat surface, or layout refactor, when revising or superseding an existing mockup, or when a plan needs something visual to be blessed against.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Before showing anyone: run python3 .claude/skills/nexus-ui-mockups/scripts/check_mockup.py from the repo root and fix every error it prints.

    line 21

≈ “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

Nexus UI Mockups

Context: a mockup is a standalone HTML/CSS/JS page in docs/mockups/ that shows a proposed Nexus surface before the plugin code exists. It is worth building only if it looks like the real product and promises only what the plugin can actually render; otherwise it is a drawing that costs a rewrite later. This router points at the procedures — the detail loads when you take the path.

Workflow

  1. Decide the artifact. A new or substantially reshaped surface gets a mockup first. A tweak inside an existing layout does not — say so and implement.
  2. New mockup: follow protocols/build-mockup.md step by step.
  3. Existing mockup to change, supersede, or retire: follow protocols/revise-mockup.md first — you MUST NOT overwrite a mockup a plan already cites as its visual contract.
  4. Before showing anyone: run python3 .claude/skills/nexus-ui-mockups/scripts/check_mockup.py from the repo root and fix every error it prints. Nothing else in the repo checks mockups — eslint and the build both ignore docs/.
  5. Implementation is a separate job under src/, governed by CLAUDE.md's hard rules and the sibling skills (nexus-mobile-compat for phone and plugin-store constraints, nexus-agents for tools behind the UI, nexus-testing for proving it in the running plugin). Mockup-only liberties never travel there.

Map

  • references/fidelity.md — how to make it look like Obsidian and like Nexus: the token block, both themes, production class naming, icons, phone widths.
  • references/honest-mockups.md — keeping the mockup buildable: Obsidian form primitives, labelling simulation, flagging what will not ship as drawn.
  • references/handoff.md — serving it, review, blessing it as a plan's visual contract, and what happens to it after the UI ships.
  • protocols/ — build-mockup.md, revise-mockup.md, self-refine.md.
  • scripts/ — check_mockup.py (validate a mockup), theme_tokens.py (extract the token set production actually relies on). Run them, do not reimplement.

Refine

At the end of a session that used this skill, run protocols/self-refine.md.

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.