agentleFS
wagtailwagtail/bakerydemo/AGENTS.md

bakerydemo

AGENTS.md1.1k starsChanged 3 months agoBSD-3-ClauseView on GitHub

Additional guidance for AI coding agents working on bakerydemo. bakerydemo is a Wagtail demo site for learning and showcasing common patterns. The codebase is organized as a multi-app demo project: For render or template-focused Django tests, prefer the test settings: This avoids manifest-staticfiles issues from bakerydemo.settings.dev.

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
  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 32,671 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repositoryOne other file it gives its agents.

The file

We split this AGENTS.md into the rules it gives an agent

8 rules. About 0 are common, 5 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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:

    When implementing theming, prefer built-in CSS and browser features such as light-dark() and color-scheme instead of a more complex custom …

    line 38
  2. Distinctive:

    Keep visual effect tokens (for example overlays, gradients, inverse-on-image text) separate from general page theme tokens.

    line 39
  3. Distinctive:

    Prefer focused model and page setup over loading the full demo fixture, unless the fixture itself is under test.

    line 44
  4. Very specific:

    When testing search, remember bakerydemo/search/views.py intentionally hard-codes the searchable page models for the demo.

    line 45
  5. Very specific:

    If fixture content changes, follow the documented fixture export and formatting steps in CONTRIBUTING.md.

    line 50
  6. Distinctive:

    Avoid unnecessary fixture changes in unrelated pull requests.

    line 51
  7. Distinctive:

    Keep changes tightly scoped to the issue being worked on.

    line 55
  8. Distinctive:

    Call out any areas that need careful visual or editorial review.

    line 57

≈ “Common” is an estimate: at least 1 in 5 of the 41,581 AGENTS.md 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
AGENTS.md

AGENTS Instructions

Additional guidance for AI coding agents working on bakerydemo.

Project overview

bakerydemo is a Wagtail demo site for learning and showcasing common patterns.

The codebase is organized as a multi-app demo project:

  • bakerydemo/base/ for shared models, blocks, fixtures, and tests
  • bakerydemo/blog/, breads/, locations/, recipes/, people/, search/ for feature-specific apps
  • bakerydemo/templates/ and bakerydemo/static/ for site-wide templates and frontend assets

Key commands

npm ci            # Install frontend dependencies
make lint         # Ruff, djhtml, curlylint, frontend linting
make format       # Ruff, djhtml, frontend formatting/fixes
./manage.py check # Run Django system checks
./manage.py test  # Default local test run
prek install      # Install local git hooks

For render or template-focused Django tests, prefer the test settings:

env DJANGO_SETTINGS_MODULE=bakerydemo.settings.test ./manage.py test

This avoids manifest-staticfiles issues from bakerydemo.settings.dev.

Frontend workflow

  • JavaScript is intentionally minimal and framework-free.
  • CSS is plain vanilla CSS, no Sass.
  • When implementing theming, prefer built-in CSS and browser features such as light-dark() and color-scheme instead of a more complex custom theme system.
  • Keep visual effect tokens (for example overlays, gradients, inverse-on-image text) separate from general page theme tokens.

Testing guidance

  • Render tests should generally live in bakerydemo/<app>/tests/.
  • Prefer focused model and page setup over loading the full demo fixture, unless the fixture itself is under test.
  • When testing search, remember bakerydemo/search/views.py intentionally hard-codes the searchable page models for the demo.

Demo data and content

  • The main demo fixture lives in bakerydemo/base/fixtures/bakerydemo.json.
  • If fixture content changes, follow the documented fixture export and formatting steps in CONTRIBUTING.md.
  • Avoid unnecessary fixture changes in unrelated pull requests.

Pull request guidance

  • Keep changes tightly scoped to the issue being worked on.
  • Explain the "why" of the change, not only the implementation.
  • Call out any areas that need careful visual or editorial review.
  • Tell us how to test the changes.

Bakerydemo-specific pitfalls

  • Be careful when changing theme tokens: some existing tokens are used for fixed visual effects and should not become theme-dependent.
  • The repo may have ongoing frontend-tooling migration work; if Stylelint or pre-commit config is mid-transition, prefer targeted checks and report the limitation clearly.

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.