spec-lookup
Skill31 starsChanged 2 months agoApache-2.0View on GitHub
Answer "what does the spec/prototype say about X" by reading the Styx handoff HTML with tags stripped. Use before implementing any screen, component, copy, shortcut, or state rule.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- HeyPuter/browser.jstheir own version, first seen Oct 8, 2026
- kyto64/aidd-template-scaletheir own version, first seen Sep 16, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- HeyPuter/browser.js★ 256same name
- kyto64/aidd-template-scale★ 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 repository10 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- db-migrationSkill
- ipc-commandSkill
- port-screenSkill
- provider-adapterSkill
- releaseSkill
- run-appSkill
- state-machine-changeSkill
- ui-componentSkill
- visual-diffSkill
The file
Files
Spec lookup
Handoff lives in design/handoff/. Files: Styx Spec.dc.html (spec §1–§11), Styx.dc.html (prototype, pixel-final), styx-tokens.css/json, UX Research Memo.dc.html.
Strip tags
python3 - "$CLAUDE_PROJECT_DIR/design/handoff/Styx Spec.dc.html" <<'PY'
import re,html,sys
t=open(sys.argv[1]).read()
t=re.sub(r'<script.*?</script>','',t,flags=re.S); t=re.sub(r'<style.*?</style>','',t,flags=re.S)
t=re.sub(r'<[^>]+>','\n',t); print(html.unescape(re.sub(r'\n\s*\n+','\n',t)))
PYSection index: pipe through grep -nE '^[0-9]+\. '. Slice a section: awk '/^8\. /{f=1} /^9\. /{f=0} f'.
Prototype markup
- Screens:
grep -n 'data-screen-label="Home"' design/handoff/Styx.dc.html, thensed -n '<start>,<next-label>p'. Artboards are sequential; markup lines 23–508, state script 509–736. - The prototype has zero CSS classes: every recipe is an inline
style="…";style-hover="…"is the hover state;data-inv/data-onare the selection attributes. - Flow/state strips (onboarding, diff, connect, spawn, new project, empty, error, toast, popout, audit) are prototype chrome, not app UI.
Report
Quote exact text, cite file and line, note if prototype and spec disagree (prototype wins for visuals, spec for behaviour; log to docs/handoff-discrepancies.md). Never paraphrase copy.
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.

