cubetiq/stitch-design-system
workflows/workflows/agent-environment-setup/platforms/copilot/skills/stitch-design-system/SKILL.md
Create or refresh a Stitch-compatible design-system context by maintaining docs/foundation/DESIGN.md as the canonical source and mirroring it to a Stitch-facing design file when Stitch flows need persistent visual consistency.
$ install --global
skillsauthnpx skillsauth add cubetiq/cubis-foundry stitch-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 4, 2026, 11:02 AM10.0s5 files scanned
SKILL.md
- name:
- stitch-design-system
- description:
- Create or refresh a Stitch-compatible design-system context by maintaining docs/foundation/DESIGN.md as the canonical source and mirroring it to a Stitch-facing design file when Stitch flows need persistent visual consistency.
- license:
- MIT
- author:
- cubis-foundry
- version:
- 1.0
- compatibility:
- Claude Code, Codex, GitHub Copilot, Gemini CLI, Antigravity
Stitch Design System
Purpose
Maintain the design context that lets Stitch generate consistent screens across a project. This skill keeps docs/foundation/DESIGN.md as the canonical design document and mirrors it to a Stitch-facing design file for Stitch-oriented generation flows.
When to Use
- A Stitch project needs consistent visual language across multiple screens
docs/foundation/DESIGN.mdis missing or stale- A repo already has tokens and component patterns that should be reflected in Stitch prompts
- A team wants to refresh Stitch design context from an existing screen or artifact
Instructions
-
Keep
docs/foundation/DESIGN.mdcanonical — The project-owned design context lives underdocs/foundation/DESIGN.md. The Stitch-facing design mirror is generated compatibility state for Stitch workflows. -
Derive from repo evidence first — Prefer existing tokens, CSS variables, typography scales, component primitives, and brand docs from the repo before extracting from Stitch output.
-
Use Stitch artifacts only when they add real missing context — When the repo design system is incomplete, inspect Stitch screens with
get_screenand extract the visual language from the real artifact. -
Describe the system semantically — Write colors by role, typography by hierarchy, spacing by rhythm, shape by character, and motion by purpose. Include exact values only when they help generation consistency.
-
Capture component vocabulary — Document how buttons, cards, forms, navigation, tables, and empty states should look and feel so future prompts stay consistent.
-
Keep the scope proportional — Do not build or refresh the design-system document for every one-off component task. Use this skill when the work spans multiple screens, iterative Stitch work, or a real design refresh.
-
Mirror the canonical file into the Stitch-facing design file — When this skill updates the canonical file, it must also update the Stitch compatibility mirror so Stitch-oriented flows read the same design language.
-
Mark unknowns clearly — If a color role, typography rule, or motion style is inferred rather than directly evidenced, call that out instead of presenting it as a verified fact.
Output Format
Deliver:
- Canonical design path —
docs/foundation/DESIGN.md - Mirror path — Stitch-facing design mirror
- Design-system summary — palette roles, typography, spacing, shape, components, and motion
- Evidence notes — what came from repo truth vs Stitch artifact inference
References
| File | Load when |
| --- | --- |
| references/design-template.md | Need the canonical structure for docs/foundation/DESIGN.md and the Stitch mirror. |
| ../design-system/SKILL.md | Need the canonical section order and system rules before mirroring to Stitch. |
| ../design/references/design-tokens.md | Need token structure and semantic value naming. |
Examples
| File | Use when |
| --- | --- |
| examples/01-design-context.md | Need a minimal template for the canonical design doc and Stitch mirror. |
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