agentleFS
conectlensconectlens/lenserfight/.agents/skills/mobile-ruleset/SKILL.md

mobile-ruleset

Skill18 starsChanged 6 months agoMITView on GitHub

Shared mobile workspace rules for apps/mobile and libs/* in lenserfight. Use when navigating native UI boundaries, shared tokens, verification defaults, or the canonical mobile design ruleset.

The file

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 this as the canonical baseline for every mobile skill.

    line 8

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

Mobile Ruleset

Use this as the canonical baseline for every mobile skill. Read references/RULESET.md first for workspace rules, shared vocabulary, and Soft UI guidance.

This is the source of truth for mobile UI/UX rules in .agents and .claude. The mobil-ui-ux-ruleset folder is a compatibility alias only.

Focus on:

  • apps/mobile as the app shell and composition layer
  • libs/ui/components and libs/ui/theme as the shared UI source of truth
  • libs/ui/tokens as the shared token source of truth
  • libs/features/* as reusable feature logic and feature UI
  • libs/domain/* and libs/shared/* as shared contracts and rules
  • tokens and semantic contracts before component styling
  • iOS and Android as related but distinct platform passes
  • Soft UI / Neumorphism as a token-driven visual language
  • shared components that keep libs/* and apps/* aligned
  • smallest-useful Nx verification after mobile or shared UI changes

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.