mobile-app-designer
Skill18 starsChanged 6 months agoMITView on GitHub
Use when designing or refining Expo Go React Native screens in apps/mobile, with separate iOS and Android considerations, to keep the UI minimalist, performant, and aligned with the shared native design system.
In this repository55 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- ai-cost-manager-reducerSkill
- api-contract-reviewerSkill
- apps-language-rulesSkill
- cli-developerSkill
- contract-dto-consistency-reviewerSkill
- database-schema-reviewerSkill
- deep-code-reviewerSkill
- docs-managerSkill
- docs-publication-managerSkill
- feature-slice-designerSkill
- github-issue-solverSkill
- grasp-ooad-reviewSkill
- language-integratorSkill
- link-workspace-packagesSkill
- mcp-managerSkill
- migration-risk-reviewerSkill
- mobile-app-integratorSkill
- mobile-app-product-ownerSkill
- mobile-app-reviewerSkill
- mobile-language-checkerSkill
- mobile-rulesetSkill
- mobil-ui-ux-rulesetSkill
- monitor-ciSkill
- nx-generateSkill
- nx-importSkill
- nx-pluginsSkill
- nx-run-tasksSkill
- nx-workspaceSkill
- product-owner-deciderSkill
- react-native-performance-reviewerSkill
- react-vite-performance-reviewerSkill
- release-readiness-reviewerSkill
- repo-architecture-auditorSkill
- repo-performance-guardSkill
- repository-pattern-reviewerSkill
- security-reviewerSkill
- smart-commitSkill
- supabase-api-rpc-reviewerSkill
- supabase-index-trigger-reviewerSkill
- supabase-rls-security-reviewerSkill
- supabase-schema-reviewerSkill
- tailwind-ui-ux-reviewerSkill
- ui-contract-guardSkill
- test-managerSkill
- unit-test-plannerSkill
- vite-performance-engineerSkill
- link-workspace-packagesSkill
- monitor-ciSkill
- nx-generateSkill
- nx-importSkill
- nx-pluginsSkill
- nx-run-tasksSkill
- nx-workspaceSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 26
keep all mobile screens feeling like one product
- Distinctive: line 27
prefer shared primitives and mature native libraries over custom one-off components when they improve security or performance
- Distinctive: line 29
use the existing palette before introducing new colors
- Distinctive: line 32
avoid decorative complexity unless it improves clarity
- Distinctive: line 33
keep mobile work centered on mobile-first flows, not desktop parity
- Very specific: line 35
After design work, verify with the smallest useful mobile test set.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Mobile App Designer
Load ../mobile-ruleset/references/RULESET.md first, then follow
references/DESIGN_GUIDELINES.md.
Design for apps/mobile only. Treat iOS and Android as related but distinct
platforms, and evaluate both before deciding on interaction, spacing,
navigation, or component choices.
Focus on:
- sector-standard mobile patterns for iOS and Android separately
- the app's default palette and theme tokens
- shared secure, sector-standard native primitives from
libs/ui/components - theme and token wiring from
libs/ui/themeandlibs/ui/tokens - the real mobile product tree, especially Chao Chat, Chao features, project management, notifications, CRON jobs, and settings
- consistent spacing, typography, and surface hierarchy
- simple, predictable interactions over novelty
Rules:
- keep all mobile screens feeling like one product
- prefer shared primitives and mature native libraries over custom one-off components when they improve security or performance
- use the existing palette before introducing new colors
- preserve the app-specific feature tree; do not mirror forum pages into mobile one-for-one
- avoid decorative complexity unless it improves clarity
- keep mobile work centered on mobile-first flows, not desktop parity
After design work, verify with the smallest useful mobile test set. Prefer
pnpm nx run mobile:test, pnpm nx run mobile:build, and pnpm nx run ui:lint
when shared UI is touched.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

