Distinctive Design Systems

v1.0.0

Patterns for creating design systems with personality and distinctive aesthetics. Covers aesthetic documentation, color token architecture, typography systems, layered surfaces, and motion. Use when building design systems that go beyond generic templates. Triggers on design system, design tokens, aesthetic, color palette, typography, CSS variables, tailwind config.

0· 1.2k·5 current·5 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description match the SKILL.md content: patterns and examples for design tokens, Tailwind config, typography, layered surfaces and motion. No unrelated credentials, binaries, or installs are requested.
Instruction Scope
SKILL.md contains guidance and example code snippets (CSS/TSX/Tailwind) appropriate for creating design systems. It does not instruct reading system files, environment variables, or transmitting data to external endpoints.
Install Mechanism
No install spec and no code files beyond documentation/examples — nothing is written to disk or downloaded by the skill itself.
Credentials
No environment variables, credentials, or config paths are required or referenced; examples include only public font names and CSS/TS tokens which don't require secrets.
Persistence & Privilege
No special persistence flags set (always not set). Model invocation is allowed by default, which is typical for instruction-only skills and acceptable here given the non-sensitive scope.
Assessment
This skill is coherent and focused on design system patterns and example code; it does not request credentials or install code. Before adopting: (1) review and test the example code in your dev environment (it’s only snippets), (2) verify any third‑party fonts/assets (license/hosting) referenced in the examples, and (3) when you implement tokens/config in a project, store any real secrets (if you later add them) in appropriate secret stores — the skill itself does not handle secrets. If you want additional assurance, ask the author for a source/homepage or a full implementation repo before using code in production.

Like a lobster shell, security has layers — review code before you run it.

latestvk976pek44m3kcnb5w2htzaddnn80x81v

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments