specorator-design
Skill0 starsChanged 6 months agoMITView on GitHub
Use this skill to generate well-branded interfaces and assets for Specorator (the open-source agentic-workflow template), for production or prototypes. Contains canonical brand tokens, voice rules, iconography rules, assets, and UI kit components.
In this repository45 other files it gives its agents.
- AGENTS.mdAGENTS.md
- plugin-v2/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- plugin-v2/CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/agents.mdcCursor rule
- agentic-security-reviewSkill
- arc42-baselineSkill
- caveman-commitSkill
- caveman-helpSkill
- caveman-reviewSkill
- cavemanSkill
- create-goalSkill
- design-twiceSkill
- discovery-sprintSkill
- domain-contextSkill
- github-project-setupSkill
- grillSkill
- improve-codebase-architectureSkill
- issue-breakdownSkill
- issue-draftSkill
- issue-pr-syncSkill
- new-adrSkill
- new-glossary-entrySkill
- orchestrateSkill
- portfolio-trackSkill
- product-pageSkill
- project-reviewSkill
- project-runSkill
- project-scaffoldingSkill
- quality-assuranceSkill
- quality-metricsSkill
- record-decisionSkill
- review-fixSkill
- roadmap-managementSkill
- sales-cycleSkill
- specorator-improvementSkill
- specorator-onboardSkill
- stock-takingSkill
- tackle-issueSkill
- tdd-cycleSkill
- token-budget-reviewSkill
- tracer-bulletSkill
- ubiquitous-languageSkill
- verifySkill
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
- Distinctive: line 6
Read the README.md file within this skill, and explore the other available files.
- Distinctive: line 8
If creating visual artifacts (slides, mocks, throwaway prototypes, etc), copy assets out and create static HTML files for the user to view.
- Distinctive: line 10
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 …
≈ “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
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 map
README.md— voice, content fundamentals, visual foundations, iconography rules.colors_and_type.css— every token: color, type, spacing, radius, shadow, motion. Drop this into any new HTML.assets/—specorator-mark.svg(logo),specorator-workflow.svg(workflow diagram).ui_kits/product-page/— pixel-faithful React recreation of the live product page. Read its components to learn idiomatic Specorator section/card/terminal patterns.preview/— small specimen cards (colors, type, components) you can crib from.
Non-negotiables
- No emoji. No icons. The brand uses zero iconography. Use monospace code chips, arrows in copy (
→), middle-dots (·), and status pills instead. - Cream paper, not white. Page backgrounds use
--paper(#fbfcf8). White is for cards. - Chartreuse is a pop, not a wash.
--highlighter(#e6ff70) is reserved for the brand mark, the primary CTA, step-number circles, and inline code chips on dark backgrounds. Never as a body fill. - Sentence-case headlines that end with a period. "A specialist for every stage."
- Em-dashes glue thoughts; never en-dashes.
- Lane coding is intentional. Define = green, Build = blue, Ship = gold. Reuse the right one.
Default fonts
- Sans: Inter (weights 400–850, including the unusual 760).
- Mono: JetBrains Mono (substitute for the original system mono — flagged in README).
Load both from Google Fonts unless the project provides licensed files.
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.