Design System

v1.0.0

Build design systems with tokens, components, and documentation that scale across teams and products.

0· 750·11 current·11 all-time
byIván@ivangdavila
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
Name/description (design system tokens, components, docs) align with the instructions and included templates. No unrelated binaries, env vars, or services are requested.
Instruction Scope
SKILL.md and setup.md limit behavior to asking the user questions, advising on patterns, and reading/writing files in ~/design-system/. The skill explicitly states it will not access files outside that directory or make network requests.
Install Mechanism
No install spec and no code files — instruction-only means nothing is downloaded or written by an installer. Lowest-risk install posture.
Credentials
No environment variables, credentials, or config paths are requested. All required state is local and file-based (~/design-system/). Proportional to the claimed functionality.
Persistence & Privilege
The skill persists a memory file under the user's home (~ /design-system/memory.md). This is reasonable for a design-system assistant, but it is persistent data stored on disk — users should be aware of what is written and avoid saving secrets there.
Assessment
This skill appears coherent and low-risk: it only uses local files and includes templates for storing design-system memory at ~/design-system/memory.md. Before installing or using it, consider: 1) inspect the contents of ~/design-system/ if you want to confirm what the agent wrote; 2) do not paste secrets or credentials into the memory files (they are persistent); 3) the skill claims it won’t make network requests, but the platform hosting the agent may allow network access — if you need to enforce no-network behavior, verify platform/network policies; 4) if you don’t want any persistent files, avoid enabling the skill or delete ~/design-system/ after use. If the skill later requests environment variables, executables, or external URLs, treat that as a red flag and re-evaluate.

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

latestvk97cvs81s0d648n9myy2687ehs81mdgg

License

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

Runtime requirements

🎨 Clawdis
OSLinux · macOS · Windows

Comments