agentleFS
moeru-aimoeru-ai/airi/.agents/skills/enforce-rules-for-fonts/SKILL.md

enforce-rules-for-fonts

Skill51k starsChanged 3 days agoMITView on GitHub

Enforce AIRI's font rules. Use when you write, change, or review Vue templates, styles, UnoCSS configuration, canvas or WebGL text, SVG text, loading screens, or any code that sets a font. Also use when a design, a screenshot, or a request names a font family, or when you are about to add `font-family`, `@font-face`, a Google Fonts link, or a font package.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projectsWeek of Nov 8: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Who's talking about moeru-ai/airi

The biggest 5 of 96 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 96

Talked about on GitHub, Bluesky, YouTube, Hacker News and the web (96 times).

On GitHub · 50

45 more on GitHub

On Bluesky · 32

27 more on Bluesky

On YouTube · 10

5 more on YouTube

On Hacker News · 3

On the web · 1

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 2 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read these files before you choose a font.

    line 19
  2. Very specific:

    Use font-mono for code, logs, IDs, and tabular technical values.

    line 25
  3. Very specific:

    Do not add a font family, a @font-face rule, a Google Fonts or CDN link, or a new @fontsource or font package.

    line 26
  4. Very specific:

    Do not write a font-family literal in <style>, inline styles, or TypeScript.

    line 27
  5. Very specific:

    If code needs a font string outside CSS classes, copy the stack of an existing family from uno.config.ts.

    line 28
  6. Very specific:

    Do not use a system stack, such as ui-monospace or system-ui, as the first family.

    line 29
  7. Distinctive:

    When a design or a screenshot shows another font, map it to the nearest existing family.

    line 30

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

Enforce AIRI Font Rules

AIRI uses a fixed set of font families. Each extra family adds download size, breaks the offline Electron build, and makes the apps look inconsistent. Use only the families that the repository already defines.

Find the existing families

SourceContent
uno.config.ts, theme.fontFamilyThe stacks for font-sans, font-mono, font-sans-rounded, font-cute, font-cuteen, and font-cutejp
uno.config.ts, presetWebFontsFontsThe web font classes, for example font-serif, font-quicksand, font-urbanist, font-comfortaa, font-jura, font-gugi, font-m-plus-rounded, font-quanlai, and font-xiaolai
packages/unocss-preset-fontsThe bundled families quanlai, departure, and xiaolai
apps/*/src/**/main.tsThe @fontsource and @proj-airi/font-* imports that load the files

Read these files before you choose a font. The list in this skill can be out of date. The files are the source of truth.

Rules

  • Inherit the host font by default. Most controls do not need a font class.
  • To change a font, use an existing UnoCSS class, for example font-mono or font-sans-rounded.
  • Use font-mono for code, logs, IDs, and tabular technical values.
  • Do not add a font family, a @font-face rule, a Google Fonts or CDN link, or a new @fontsource or font package.
  • Do not write a font-family literal in <style>, inline styles, or TypeScript. Use the UnoCSS class.
  • If code needs a font string outside CSS classes, copy the stack of an existing family from uno.config.ts. Examples are canvas ctx.font, SVG text, Three.js text, and PDF or image export. Put the stack in one shared constant near the renderer.
  • Do not use a system stack, such as ui-monospace or system-ui, as the first family. Existing stacks already end with system fallbacks.
  • When a design or a screenshot shows another font, map it to the nearest existing family. Tell the user which family you used.

When you change existing code

In each component or style that you change, replace a font-family literal that names a family outside the list with the matching UnoCSS class. Do not edit other files only for this rule.

Exceptions

You can use a font outside the list only in these cases:

  • A scenario or story reproduces the chrome of an operating system or a third-party product, for example a macOS window frame.
  • The user explicitly asks for a new font.

For a new font, stop and ask the user first. Give the reason, the license, the file size, the CJK and other subsets that it needs, and how the Electron app loads it offline. After approval, add it to uno.config.ts or packages/unocss-preset-fonts, and load it in each app that uses it. Then mark any remaining literal with a // NOTICE: comment.

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.