agentleFS
AlexaysAlexays/Lilo/site/AGENTS.md

Lilo / site

AGENTS.md58 starsChanged 10 days agoMITView on GitHub

These rules apply to site/, alongside the repository's AGENTS.md. Read README.md for the source layout and deployment details.

  • 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 33,315 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 repository6 other files it gives its agents.

The file

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

9 rules. About 0 are common, 2 are distinctive, and 7 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.

  • 7

    Very specific

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

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

    Before changing Astro APIs or configuration, consult the Astro Docs MCP server (https://mcp.docs.astro.build/mcp) and check compatibility …

    line 7
  2. Distinctive:

    Keep strict TypeScript and the existing Ultracite Astro lint/format presets enabled.

    line 9
  3. Very specific:

    Keep the website statically rendered for Cloudflare.

    line 13
  4. Very specific:

    Use component-scoped <style> tags for component rules.

    line 16
  5. Very specific:

    Keep shared page structure in src/layouts/Layout.astro and reusable UI in src/components/.

    line 17
  6. Distinctive:

    Use semantic HTML with one main landmark containing the page heading, a working skip link, and the shared footer outside main.

    line 23
  7. Very specific:

    Use astro:assets for content images that benefit from optimization.

    line 25
  8. Very specific:

    Run commands from the repository root through Make.

    line 31
  9. Very specific:

    Run make validate before reporting completion, as required by the root rules.

    line 33

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

Astro website

These rules apply to site/, alongside the repository's AGENTS.md. Read README.md for the source layout and deployment details.

Documentation and tooling

  • Before changing Astro APIs or configuration, consult the Astro Docs MCP server (https://mcp.docs.astro.build/mcp) and check compatibility with the version in package.json. If MCP is unavailable, use the official docs.
  • Build on the existing project. When an official integration is needed, follow the documented astro add workflow; install other packages with npm. Expose these operations through the root Makefile, extending it when necessary, and commit the dependency and lockfile changes together.
  • Keep strict TypeScript and the existing Ultracite Astro lint/format presets enabled. Fix diagnostics without weakening the checks.

Components, scripts and styles

  • Keep the website statically rendered for Cloudflare. Use .astro components and build-time frontmatter for content; add framework islands only when an interaction needs them, choosing the least eager hydration directive that supports the feature.
  • Define a Props interface for components that accept props. Keep browser APIs in client scripts; frontmatter runs at build time for this site.
  • Use normal <script> tags so Astro handles TypeScript, bundling and deduplication. Keep small behaviors in their .astro component; put reusable browser modules in src/ as .ts. Do not add authored JavaScript in public/ or custom compilation endpoints. Reserve is:inline for cases that require unprocessed output and comply with the site's CSP.
  • Use component-scoped <style> tags for component rules. Keep shared tokens, resets and site-wide styles in src/styles/global.css; use :global() only for selectors that intentionally cross component boundaries.
  • Keep shared page structure in src/layouts/Layout.astro and reusable UI in src/components/. Navigation should render one set of links that adapts to the viewport.
  • Public pages pass their top and closing copy to Layout.astro, which owns the main landmark, PageHero.astro and PageEnd.astro. Use PageSection.astro for body sections. Keep frame, gutter and section spacing in those shared components; do not duplicate or override their design in page files.

Content, assets and accessibility

  • Maintain the English and French routes together. Shared website copy belongs in both locales in src/lib/i18n.ts; translate route content in both page files. Preserve language alternates, canonical URLs, section anchors and browser-language routing.
  • Use semantic HTML with one main landmark containing the page heading, a working skip link, and the shared footer outside main. Give icon controls accessible names and preserve keyboard operation, focus visibility and navigation without JavaScript.
  • Respect Reduce Motion, support light and dark appearances, and keep Lilo's existing color tokens. Demos and animations must do no background work while unused.
  • Use astro:assets for content images that benefit from optimization. Files needing stable URLs, such as favicons, can stay in public/. Give images dimensions and appropriate alt text; hide decorative SVGs from assistive technology.
  • Preserve public/_headers, including the script CSP. Use set:html only with trusted repository content or sanitized HTML, and escape serialized JSON for its HTML context.
  • Edit sources rather than dist/ or .astro/. Markdown copies, FAQ metadata and the website's release notes are generated from their documented sources.

Verification

  • Run commands from the repository root through Make. Use make site-fix for formatting when needed, then make site-check site-test. astro check is required because TypeScript alone does not check .astro templates.
  • For layout or interaction changes, check both languages at desktop and mobile widths, keyboard behavior, appearance changes and navigation without JavaScript in a browser. Add regression coverage for behavior that could break; avoid mock browser tests that reproduce the implementation.
  • Run make validate before reporting completion, as required by the root rules. Report any failing gate accurately even when the website checks pass.

Astro references: AI development, components, client scripts, scoped styles and TypeScript.

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.