arch-explain skillA
arch-explain is agent-read markdown (skill) from baristaze/swe_guidelines: Explain how the guideline applies to a question, a file, or a change, citing the sections and lenses that govern it. Use when onboarding or before a cross-layer change..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# arch-explain
Answer a question about the architecture with the guideline as the
source of truth, not with general opinion. The guideline is at
`${CLAUDE_SKILL_DIR}/../../architecture.md` and the lens catalog at
`${CLAUDE_SKILL_DIR}/../../lenses/`. If either is missing, stop and
say the installation is incomplete.
## Input
`$ARGUMENTS` is one of:
- a question ("where does rate limiting live?", "can a manager call a
service?");
- a path to a file or folder in the current repository ("explain what
rules apply to `om/orders/impl/manager.py`");
- a description of a change ("I want to add a nightly cleanup").
Empty arguments mean: give the guided tour, every section in the order
of the guideline's Contents, two sentences each, then the eight lens
groups in one line each.
## Procedure
1. Read the guideline's Contents (the table of contents under its
first heading) and the lens group table in `lenses/README.md`.
2. Find the sections and subsections that govern the question. Read
them in full; quote the `Principle` callouts verbatim when they
answer the question directly.
3. Find the lenses that a reviewer would apply. Name them by id.
…Read the whole file at its exact version.
How to install
mdr add baristaze/swe_guidelines/arch-explain@git:20260922.e4ae97cmdr add baristaze/swe_guidelines/arch-explain@sha256:d8bb9f2fb24a5abbPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_3ykw73of6er4amzz)
2 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260922.e4ae97c latest | 2026-09-22 | e4ae97c | 2,175 B | A | view · diff |
| git:20260920.bf97909 | 2026-09-20 | bf97909 | 2,260 B | A | view · diff |
| git:20260916.1dc31a5 | 2026-09-16 | 1dc31a5 | 2,260 B | A | view · diff |
| git:20260915.0f7c469 | 2026-09-15 | 0f7c469 | 2,164 B | A | view · diff |
| git:20260915.6033a4d | 2026-09-15 | 6033a4d | 1,899 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (2175 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
baristaze/swe_guidelines · 86 stars · license MIT · pushed 2026-09-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_3ykw73of6er4amzz GET https://markdownregistry.com/api/v1/resolve?ref=baristaze/swe_guidelines/arch-explain GET https://markdownregistry.com/api/v1/blob/d8bb9f2fb24a5abbfcd15b3b4b924f16507677a4df108e8c500448352be27e87
Your agent 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.