cubetiq/design-system
workflows/workflows/agent-environment-setup/platforms/codex/generated-skills/design-system/SKILL.md
Define or refine reusable design tokens, components, and rules so the interface system becomes more coherent and scalable.
$ install --global
skillsauthnpx skillsauth add cubetiq/cubis-foundry design-systemInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 24, 2026, 7:46 AM3.7s1 file scanned
SKILL.md
- name:
- design-system
- description:
- Define or refine reusable design tokens, components, and rules so the interface system becomes more coherent and scalable.
- license:
- MIT
- author:
- cubis-foundry
- route-kind:
- workflow
- route-id:
- design-system
- platform:
- Codex
- command:
- /design-system
- compatibility:
- Codex
Design System Workflow
What this workflow does
Guides systematic UI work around canonical design state, tokens, components, states, interaction patterns, and cross-surface visual direction rather than isolated screen polish.
When to use
Use this when a request affects multiple screens, needs consistent system-level decisions, or requires docs/foundation/DESIGN.md to become the durable design source of truth.
Agent chain
planner -> implementer
Step details
- Use
frontend-designto lock the style contract and thesis set that the system must preserve. - Audit the current design-system surface and canonical direction.
- Define the reusable token, primitive, component, responsive, and do or do not rules needed for the main target surfaces.
- Apply and verify the system-level update in documentation or code, with
docs/foundation/DESIGN.mdtreated as canonical and Stitch treated as a downstream consumer only.
Skill routing
frontend-designfor public UI-design intake and system-before-screen framingdesign-systemfor the canonicalDESIGN.mdcontract and cross-surface systemizationdesignfor route and critique support when the system work starts from drift or audit findingsweb-ui-designfor browser-first system structure and component vocabularymobile-ui-designwhen the system change must survive app-first surfaces toodesktop-ui-designwhen the system change must support multi-pane, keyboard-first, or desktop-grade productivity surfaces
Context notes
Provide screenshots, existing component constraints, target platforms, and any brand direction or anti-patterns to reject.
Verification
The result should improve consistency across components and surfaces, not just one example view.
Output contract
DESIGN_SYSTEM_WORKFLOW_RESULT:
direction_name: <2-5 word direction>
design_doc_sections:
- style contract
- theses
- token roles
- component vocabulary
- responsive rules
system_changes:
- <token or component update>
verification:
- <evidence>
follow_on_surfaces:
- <remaining screen or component>
Follow-up items
Typical next step: /implement or /design-screen
Related Skills
cubetiq/deep-research
tools
VerifiedTrustedCommunity
Use when investigating latest vendor behavior, comparing tools or platforms, verifying claims beyond the repo, or gathering external evidence before implementation.
1SKILL.mdUpdated Apr 4, 2026
cubetiq/database-design
documentation
VerifiedTrustedCommunity
Use when designing database schemas, normalization strategies, indexing plans, query optimization, and migration workflows for relational, document, or hybrid data stores.
1SKILL.mdUpdated Apr 4, 2026
cubetiq/csharp-best-practices
development
VerifiedTrustedCommunity
Use when writing, reviewing, or refactoring modern C#/.NET code, including minimal APIs, records, async streams, pattern matching, DI lifetimes, and memory-efficient performance tuning.
1SKILL.mdUpdated Apr 4, 2026
cubetiq/code-review
development
VerifiedTrustedCommunity
Use when conducting code reviews, building review checklists, calibrating review depth, providing structured feedback, or establishing team review practices. Covers review methodology, feedback patterns, automated checks, and batch review strategies.
1SKILL.mdUpdated Apr 4, 2026