agentleFS
Sign inStart free
botirkhaltaevbotirkhaltaev/botir-skills/skills/cross-platform-design/SKILL.md

cross-platform-design

Skill4 starsChanged 3 months agoApache-2.0View on GitHub

Design for multiple platforms while respecting native conventions. Covers iOS HIG vs Material Design 3 differences, platform-specific patterns, when to diverge for branding, and hybrid approaches. Use when designing for mobile, tablet, or cross-platform products. Triggers on: "iOS design", "Android design", "Material Design", "cross-platform", "native patterns", "platform conventions", "HIG", "mobile platform differences".

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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
  1. Very specific:

    Use native system components for pickers/alerts/share

    line 34

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Cross-Platform Design

Respect platform conventions while keeping brand and IA consistent. Depth in references/.

Sources: Apple HIG, Material Design 3.

Snapshot

iOSAndroid
BackEdge swipe / leading backSystem back
Primary navBottom tabsBottom nav / drawer
Primary actionTrailing button / tabOften FAB
Targets≥44 pt≥48 dp

Follow always: navigation model, system gestures, permission timing, keyboards, safe areas.
Brand freely: color (accessible), illustration, voice, motion personality.

Hybrid rules

  1. Share IA and feature parity
  2. Adapt navigation chrome per platform
  3. Use native system components for pickers/alerts/share
  4. Responsive web: mobile-first; hover is enhancement only

Reference Map

  • references/ios-vs-material.md — philosophy, chrome, decision matrix
  • references/responsive-strategy.md — breakpoints, reflow/reveal/transform

Related Skills

  • For touch targets / thumbs / gestures → use mobile-touch-design
  • For navigation patterns → use interaction-design-patterns
  • For typography / space → use ui-visual-design
  • For accessibility → use a11y-accessibility-design

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free