agentleFS
conectlensconectlens/lenserfight/.agents/skills/ui-contract-guard/SKILL.md

ui-contract-guard

Skill18 starsChanged 6 months agoMITView on GitHub

Guard shared UI contracts across web and mobile in lenserfight. Use when editing libs/ui, shared components, design tokens, hooks, or platform-specific entrypoints such as index.ts and index.native.ts.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill before changing shared UI.

    line 8
  2. Distinctive:

    Do not let domain logic or network code leak into shared UI components.

    line 16
  3. Distinctive:

    Prefer prop/API refinement over duplicating similar components.

    line 23
  4. Distinctive:

    Call out breaking API changes explicitly.

    line 24

≈ “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.

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

UI Contract Guard

Use this skill before changing shared UI.

What to protect

  • Shared component APIs should remain stable and predictable.
  • libs/ui/components/src/index.ts and libs/ui/theme/src/index.ts must expose platform-safe surfaces.
  • Design tokens and contracts should be centralized, not redefined in apps.
  • Do not let domain logic or network code leak into shared UI components.

Review Sequence

  1. Inspect current exports and consumers.
  2. Separate visual primitives from app-specific compositions.
  3. Confirm whether a change is web-only, native-only, or shared.
  4. Prefer prop/API refinement over duplicating similar components.
  5. Call out breaking API changes explicitly.

Heuristics

  • Shared if semantics and lifecycle match across apps/platforms.
  • App-local if wording, layout, or data dependencies are product-specific.
  • Native/web split if implementation differs but the conceptual contract is the same.

Load only when needed:

  • Shared UI notes: platform rules

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.