cubetiq/design-screen
workflows/workflows/agent-environment-setup/platforms/codex/generated-skills/design-screen/SKILL.md
Turn a product goal into a concrete screen direction, then implement or hand off the resulting UI specification.
$ install --global
skillsauthnpx skillsauth add cubetiq/cubis-foundry design-screenInstall 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, 10:00 AM4.5s1 file scanned
SKILL.md
- name:
- design-screen
- description:
- Turn a product goal into a concrete screen direction, then implement or hand off the resulting UI specification.
- license:
- MIT
- author:
- cubis-foundry
- route-kind:
- workflow
- route-id:
- design-screen
- platform:
- Codex
- command:
- /design-screen
- compatibility:
- Codex
Design Screen Workflow
What this workflow does
Creates a screen-level brief, locks the style contract and thesis set, chooses the correct owning surface, and converts that direction into implementation-ready work.
When to use
Use this for one screen, page, or view where the main problem is composition, hierarchy, interaction cost, or presentation.
Agent chain
planner -> implementer
Step details
- Route through
frontend-designfirst to lock the style contract, visual thesis, content or system thesis, and interaction thesis. - Use
designto decide whether the work is browser-first, phone-first, or desktop-first, and whetherdesign-systemmust refresh canonical state before screen execution. - Build a concrete screen brief with user goal, hierarchy, states, accessibility, motion, and anti-generic constraints.
- Implement or hand off the design through the owning surface with platform-specific verification notes.
Skill routing
frontend-designfor the public UI-design front door, style contract, and thesis capturedesignfor routing, critique language, and execution-boundary decisionsweb-ui-designfor browser-first screen workmobile-ui-designfor app-first or phone-first screen workdesktop-ui-designfor workspace-first, multi-pane, or expert-oriented desktop workdesign-systemwhen the screen depends on shared tokens, component vocabulary, or canonical system guidance
Context notes
Provide screen purpose, content requirements, target surfaces, state expectations, and any brand or interaction constraints.
Verification
The output should describe hierarchy, layout, states, styling decisions, and rejected anti-patterns clearly enough to build from.
Output contract
DESIGN_SCREEN_WORKFLOW_RESULT:
direction_name: <2-5 word direction>
style_contract:
surface_type: <value>
style_family: <value>
anti_patterns:
- <value>
theses:
visual: <summary>
content_or_system: <summary>
interaction: <summary>
owning_surface: web-ui-design | mobile-ui-design | desktop-ui-design
implementation_notes:
- <note>
Follow-up items
Typical next step: /implement
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