cubetiq/frontend-design-mobile-patterns
foundry/modules/frontend-design-mobile-patterns/SKILL.md
Adapt the design engine to mobile and Flutter surfaces using Foundry's normalized mobile-pattern dataset and implementation-first constraints.
$ install --global
skillsauthnpx skillsauth add cubetiq/cubis-foundry frontend-design-mobile-patternsInstall 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, 9:48 AM334.1s3 files scanned
SKILL.md
- name:
- frontend-design-mobile-patterns
- description:
- Adapt the design engine to mobile and Flutter surfaces using Foundry's normalized mobile-pattern dataset and implementation-first constraints.
- license:
- MIT
- author:
- cubis-foundry
- version:
- 1.0
- compatibility:
- Claude Code, Codex, GitHub Copilot, Gemini CLI, Antigravity
Frontend Design Mobile Patterns
Purpose
Translate the design engine into mobile-specific decisions that survive real Flutter implementation instead of staying as web-first UI ideas.
When to Use
- Designing Flutter screens, flows, or navigation
- Adapting a Stitch-inspired concept into a mobile-native screen brief
- Reviewing whether a design will survive small screens and thumb-driven interaction
Instructions
- Load
workflows/design-datasets/mobile-patterns.jsonfirst — Use it to shape navigation placement, card rhythm, CTA placement, and progress visibility. - Design for thumb reach and scroll rhythm — Primary actions should stay reachable and section breaks should remain scannable on smaller screens.
- Prefer Flutter-feasible patterns — Avoid browser-specific assumptions like hover-led navigation or overly dense freeform layouts that do not translate well to Flutter widgets.
- Write implementation cues, not Figma prose — Specify scaffold usage, navigation model, card rhythm, token usage, and expected widget states.
- Feed the result into
frontend-design-implementation-handoffandflutter-mobile-qa— Mobile design is not complete until implementation and QA can consume the same brief.
Output Format
Deliver:
- Mobile-specific layout notes
- Navigation and CTA placement rules
- Widget/state expectations
- Flutter feasibility notes
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