preview-design
Skill293 starsChanged 7 days agoMITView on GitHub
Render a real artifact through this branch's local MERIDIAN design code (not the published npm package) so the team can test the new Design Convention on the document / handoff / platform surfaces before it ships. Use for `/preview-design`, "preview the design convention", "render this with the new design", or Design Convention round-1 testing.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- rutaroberts/claude-skillstheir own version, first seen Jun 25, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- rutaroberts/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository50 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- activitySkill
- announceSkill
- archiveSkill
- branchSkill
- checkupSkill
- commitSkill
- contributeSkill
- create-skillSkill
- dark-modeSkill
- dashboardSkill
- deep-reflectSkill
- delete-userSkill
- emissarySkill
- envSkill
- handoffSkill
- harvestSkill
- ingest-corpusSkill
- ingest-notionSkill
- ingestSkill
- ingest-user-interviewSkill
- inviteSkill
- issueSkill
- meetingSkill
- meSkill
- noteSkill
- notion-connectSkill
- onboardingSkill
- prSkill
- pullSkill
- pushSkill
- questSkill
- recordsSkill
- reflectSkill
- review-prSkill
- saveSkill
- slack-connectSkill
- summonSkill
- sync-reposSkill
- telegram-connectSkill
- telemetrySkill
- testSkill
- the-spiralSkill
- tui-designSkill
- tutorialSkill
- updateSkill
- viewSkill
- visual-explainSkill
- wrapSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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
- Distinctive: line 24
Run the bundled script — it handles dependency install and routes to the local CLI:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.
Files
Topic: $ARGUMENTS
Preview the Design Convention
Renders a real Egregore artifact through this branch's MERIDIAN render path
(packages/egregore-artifacts local code) — deliberately not npx egregore-artifacts,
which pulls the published npm 0.10.2 (the OLD design). This is the test vector for
Design Convention Round 1: testers see the new design on real output before it merges.
Full protocol: memory/feedback/design-convention-r1/GUIDE.md.
When to invoke
User says: "/preview-design", "preview the design convention", "render <X> with the new
design", "let me test the new design on a document / handoff / board", or is running the
design-convention round-1 test.
What it does
Run the bundled script — it handles dependency install and routes to the local CLI:
bash skills/preview-design/render.sh <surface> [file]| Surface | Command | Input |
document | render.sh document [file.md] | any markdown — defaults to a bundled sample |
handoff | render.sh handoff [file.json] | a handoff-v1 JSON — defaults to a bundled sample |
platform | render.sh platform | reads memory/board/board.json (the board view) |
emissary | render.sh emissary | harness-only this round — prints the harness URL and stops |
The CLI opens the rendered HTML in the browser. After looking it over, the tester runs the
Socratic feedback protocol ("Run the Design Convention feedback protocol").
Why it's built this way
- Local, never
npx. It runsnode packages/egregore-artifacts/bin/cli.js, so you always get THIS branch's MERIDIAN design — npm'segregore-artifactsis the old look. - Lives in top-level
skills/, not.claude/skills/./updatereplaces.claude/skills/wholesale from upstream (git checkout upstream -- .claude/skills/), which would delete an org-local preview command. Top-levelskills/survives. - Emissary is excluded on purpose. Its renderer (
api/main.py) is server-side and not yet design-system-wired — wiring it is the #1 Round-2 task. For now it's reviewed via the published harness.
Lifecycle
Retire this skill once the Design Convention merges to production and a new
egregore-artifacts is published (at which point plain /view shows MERIDIAN and the
local-vs-npm distinction disappears).
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
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.