CLAUDE.md@evals/rules/contexts/coreA
CLAUDE.md@evals/rules/contexts/core from patrickserrano/lacquer is a CLAUDE.md file: the standing instructions Claude Code reads in that repo.
mdr add patrickserrano/lacquer/evals/rules/contexts/core/CLAUDE.md@git:20260925.a6a93b6Pins git:20260925.a6a93b6 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- CLAUDE.md file
- Repository
- patrickserrano/lacquer
- Path
evals/rules/contexts/core/CLAUDE.md- Versions recorded
- 2
- Latest version
- git:20260925.a6a93b6, committed Sep 25, 2026
- First version recorded
- Sep 24, 2026
- Size
- 2,999 bytes
- Repository stars
- 5
- License
- MIT
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Core engineering rules (all projects) ## Git and workspace safety - Work in a git worktree under `.worktrees/`; keep build output in that worktree. - Before briefing or starting work, run `lacquer decisions` and `lacquer decisions --fleet`; quote the operator's words verbatim. - Never push directly to main. Use atomic commits and a pull request. - Never force-push or rebase a pushed branch. Do not bypass hooks, CI or branch protection (`--force`, `--force-with-lease`, `--no-verify`, `--admin`). - Never merge with failing or pending required checks. After updating a branch, verify the required checks ran again and passed on its new head. - Never commit or log secrets. Commit examples, not credentials; sensitive server keys never belong in a client binary or bundle. ## Verification - Deliver code proven to work: compile/build, update related tests, and run them. Pre-existing failures need fixing or explicit guidance, not a workaround. - **prove the check can fail**: feed known-bad input or mutate the implementation, confirm a named test rejects it, restore it, then confirm the test passes. A skipped check, zero selected tests, or an unreadable result is not a pass. …
Read the whole file at its exact version.
How to install
mdr add patrickserrano/lacquer/evals/rules/contexts/core/CLAUDE.md@sha256:dfd48bce7890707fThe line at the top of this page pins the label git:20260925.a6a93b6, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_24ryvn37cf5ztjy7)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Sep 24, 2026 and Sep 25, 2026, more than one a day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260925.a6a93b6 latest | 2026-09-25 | a6a93b6 | 2,999 B | A | view · diff |
| git:20260924.3718684 | 2026-09-24 | 3718684 | 2,869 B | A | view |
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (2999 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
patrickserrano/lacquer · 5 stars · license MIT · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_24ryvn37cf5ztjy7 GET https://markdownregistry.com/api/v1/resolve?ref=patrickserrano/lacquer/evals/rules/contexts/core/CLAUDE.md GET https://markdownregistry.com/api/v1/blob/dfd48bce7890707fb966e1c55c3ebbfb7d8aa588a07042da41a45579ff12c635
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: what a CLAUDE.md file is · keeping AGENTS.md and CLAUDE.md in sync · which agent file does what.