agentleFS
wagtailwagtail/bakerydemo/.agents/skills/frontend-tooling-maintenance/SKILL.md

frontend-tooling-maintenance

Skill1.1k starsChanged 3 months agoBSD-3-ClauseView on GitHub

Maintain or upgrade bakerydemo frontend linting, formatting, and theme-related tooling with minimal churn

Trending

More talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 1 mentionMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 1 mentionAug 2026: 1 mentionSep 2026: 1 mentionOct 2026: 8 mentionsNov 2026: 1 mention
Dec 2025Jun 2026Nov 2026
Mentions a month of the wagtail/bakerydemo repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about wagtail/bakerydemo

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

See all 58

Talked about on GitHub, Stack Overflow and Bluesky (58 times).

On GitHub · 50

45 more on GitHub
  • In this repositoryOne other file it gives its agents.

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 7 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this skill for bakerydemo frontend tooling tasks such as Prettier, Stylelint, ESLint, prek integration, and small native-CSS theme …

    line 9
  2. Distinctive:

    Keep changes minimal and reviewable.

    line 15
  3. Very specific:

    Prefer the repo's actual commands and workflows: make lint, make format, npm run ..., prek.

    line 16
  4. Distinctive:

    When adopting stricter lint rules, use incremental overrides rather than forcing large unrelated CSS rewrites in one PR.

    line 17
  5. Distinctive:

    Run repo-wide frontend checks with:

    line 22
  6. Distinctive:

    Run targeted checks when only a few files changed or repo-wide tooling is noisy:

    line 26
  7. Very specific:

    Use make lint or make format when you need the broader project-level workflow, not only frontend checks.

    line 31
  8. Distinctive:

    Run the smallest targeted lint commands needed for confidence.

    line 35
  9. Distinctive:

    If repo-wide tooling is mid-migration, document any blocked checks and run focused file-level validation instead.

    line 36
  10. Distinctive:

    Keep theme tokens for text, surfaces, borders, and links separate from fixed effect tokens such as overlays, gradients, shadows, and …

    line 41

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

Overview

Use this skill for bakerydemo frontend tooling tasks such as Prettier, Stylelint, ESLint, prek integration, and small native-CSS theme infrastructure updates.

Methodology

Preferred approach

  • Keep changes minimal and reviewable.
  • Prefer the repo's actual commands and workflows: make lint, make format, npm run ..., prek.
  • When adopting stricter lint rules, use incremental overrides rather than forcing large unrelated CSS rewrites in one PR.

Useful commands

  • Install frontend dependencies with npm ci.
  • Run repo-wide frontend checks with:
    • npm run lint:css
    • npm run lint:js
    • npm run lint:format
  • Run targeted checks when only a few files changed or repo-wide tooling is noisy:
    • npx stylelint bakerydemo/static/css/main.css
    • npx stylelint --fix bakerydemo/static/css/main.css
    • npx eslint bakerydemo/static/js/main.js
    • npx prettier --check bakerydemo/static/css/main.css bakerydemo/static/js/main.js
  • Use make lint or make format when you need the broader project-level workflow, not only frontend checks.

Quality checks

  • Run the smallest targeted lint commands needed for confidence.
  • If repo-wide tooling is mid-migration, document any blocked checks and run focused file-level validation instead.

Pitfalls

  • Local environment directories such as uvenv/ inside the repo can confuse glob-based frontend scripts.
  • Keep theme tokens for text, surfaces, borders, and links separate from fixed effect tokens such as overlays, gradients, shadows, and inverse-on-image text.

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.