Mobile fonts

Skill ahtishamshahzad/agent_dev_flow/.ai/skills/mobile/mobile-fonts

Tool-neutral AI Engineering System: 174 reusable skills (installable as Claude Code plugins) for planning and building software with AI agents. Classify → plan → approve → build under quality gates. Works with Claude Code, Codex, Cursor, Windsurf, Copilot & Antigravity. Canonical in .ai/.

Install

npx -y skills add ahtishamshahzad/agent_dev_flow --skill mobile-fonts

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

21 days oldThe repository was created 21 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use to plan custom font integration — font loading, weights/variants, and typography wiring into the design system — with correct async loading and fallbacks per runtime.

SKILL.md

2.8 KB, 555 tokens by cl100k_base, as published. Nobody here has run it

Mobile Fonts

Purpose

Plan custom font usage: which families/weights, how they load per runtime (Expo font loading vs native linking), fallbacks, and integration into the typography scale.

When to Use

When the app uses custom fonts or a specific typographic identity.
Not when system fonts suffice.

Inputs

Design system typography scale.
Font files/licenses; runtime (Expo/CLI).

Discovery Questions

Which families/weights/variants are needed?
Expo font loading or CLI native font linking?
What fallback while fonts load?
Are the font licenses cleared for the platforms?

Responsibilities

Select families/weights matching the typography scale.
Plan loading per runtime (Expo async load vs CLI linking) with a fallback.
Wire fonts into the design system/theme typography.
Avoid layout shift during load.

Required Workflow

Confirm required families/weights + licenses.
Plan runtime-appropriate loading + fallback.
Integrate into typography tokens.
Handle loading state to avoid shift.
Record the font plan.

Decision Rules

Load fonts async with a fallback; don't block first render unnecessarily.
Only include weights/variants actually used.
Integrate via typography tokens, not per-component font names.

Rules

Verify font licenses for iOS/Android.
Wire through the design system, not ad hoc.
Handle the loading state (avoid flash/shift).

Anti-Patterns

Bundling many unused weights.
Hard-coding font names per component.
Ignoring loading state (layout shift/flash).
Using unlicensed fonts.

Validation Checklist

Families/weights selected + licensed.
Runtime-appropriate loading + fallback.
Integrated into typography tokens.
Loading state handled.

Definition of Done

A recorded font plan: licensed families/weights, runtime-appropriate async loading with fallback, integration into the typography scale, and handled loading state.

Related Skills

mobile-design-system, mobile-theme, mobile-accessibility, mobile-performance

Related Knowledge

../../../knowledge/ (typographic identity).

Related References

../../../references/mobile/screens/ when populated.

Context Loading Guidance

Requires: typography scale, font files/licenses, runtime.
Does not require: the whole app source, unrelated references, every mobile skill.
May load: mobile-design-system for typography tokens.
Stop when: the font plan is recorded.

Token Efficiency Guidance

Keep to the required families/weights; integrate via tokens rather than restating typography.