agentleFS
PydanticKnown publisherpydantic/pydantic-handlebars/CLAUDE.md

pydantic-handlebars

CLAUDE.md24 starsChanged 9 months agoMITView on GitHub

Handlebars template engine for composing LLM prompts, built on Pydantic. Templates may be untrusted. All context data is serialized to JSON-safe types via pydantic_core.to_jsonable_python before rendering — the template engine only sees dicts, lists, strings, numbers, bools, and None. Enforce depth limits for nesting. Tests are ported from https://github.com/handlebars-lang/handlebars.js/tree/master/spec. When adding new features, find the corresponding JS spec tests and port them. Use assert render(template, context) == expected pattern. No test classes — standalone functions only.

The file

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

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

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Only runtime dependency is pydantic (2.0+)

    line 14
  2. Very specific:

    All implementation modules are private (_tokenizer.py, etc.)

    line 16
  3. Distinctive:

    No imports inside functions

    line 23

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

pydantic-handlebars

Handlebars template engine for composing LLM prompts, built on Pydantic.

Quick Reference

  • make all — format, lint, typecheck, test with coverage
  • make test — run tests (parallel with pytest-xdist)
  • make lint — ruff format check + ruff check
  • make typecheck — pyright strict mode

Code Rules

  • Only runtime dependency is pydantic (2.0+)
  • 100% test coverage required
  • All implementation modules are private (_tokenizer.py, etc.)
  • Public API is exported from __init__.py
  • Tests are ported from the Handlebars.js spec suite — maintain 1:1 correspondence
  • Single quotes for code, double quotes for docstrings
  • Google-style docstrings
  • Python 3.10+ (use X | Y union syntax in annotations, but isinstance(x, (X, Y)) in runtime checks)
  • No except Exception — catch specific types
  • No imports inside functions

Architecture

  1. Tokenizer (_tokenizer.py) → Token stream
  2. Parser (_parser.py) → AST (_ast_nodes.py)
  3. Compiler (_compiler.py) → Output string

Security

Templates may be untrusted. All context data is serialized to JSON-safe types via pydantic_core.to_jsonable_python before rendering — the template engine only sees dicts, lists, strings, numbers, bools, and None. Enforce depth limits for nesting.

Testing

Tests are ported from https://github.com/handlebars-lang/handlebars.js/tree/master/spec. When adding new features, find the corresponding JS spec tests and port them. Use assert render(template, context) == expected pattern. No test classes — standalone functions only.

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.