mpa-strict-rules Cursor ruleB
mpa-strict-rules from realistsec/mpa-first-guidelines is a Cursor rule: instructions the Cursor agent follows in that repo.
mdr add realistsec/mpa-first-guidelines/.cursor/rules/mpa-strict-rules.mdc@git:20251205.13d7a30Pins git:20251205.13d7a30 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 13 of 14 checks passed
- Kind
- Cursor rule
- Repository
- realistsec/mpa-first-guidelines
- Path
.cursor/rules/mpa-strict-rules.mdc- Versions recorded
- 1
- Latest version
- git:20251205.13d7a30, committed Dec 5, 2025
- Size
- 14,650 bytes
- Repository stars
- 11
- License
- MIT
MPA-First Development Mandate - Strict rules for building performant, resilient Multi-Page Applications.
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
# AI Coding Agent Guidelines: The MPA-First Mandate ## Introduction: Why We Build This Way For over a decade, web development has trended towards complex, JavaScript-heavy Single-Page Applications (SPAs). The promise was a slick, "app-like" user experience. The reality, in most cases, has been bloated, fragile, and over-engineered websites that are slow to load, difficult to maintain, and hostile to users and search engines. This document outlines a return to a more resilient, performant, and durable web. We are intentionally choosing a **Multi-Page Application (MPA)** architecture. The guiding principle is to **use the platform**. We build upon the native strengths of HTML, CSS, and the browser itself, which have evolved significantly. Modern features like CSS View Transitions and Speculation Rules now provide the fluid user experience that once required megabytes of JavaScript, but without the performance penalty. …
Read the whole file at its exact version.
How to install
mdr add realistsec/mpa-first-guidelines/.cursor/rules/mpa-strict-rules.mdc@sha256:ce04e6b23707c5a0The line at the top of this page pins the label git:20251205.13d7a30, 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_slq6qdsfaqqxbsna)
1 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in realistsec/mpa-first-guidelines/.cursor/rules/mpa-strict-rules.mdc since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of mpa-strict-rules.mdc from somewhere else? Ask it: where did my mpa-strict-rules.mdc come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Dec 5, 2025.
Watch this file (sign in, one email per new version)
Installed this file, say at mpa-strict-rules.mdc? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- fail: No script tag (matched: <script)
- pass: Size between 200 bytes and 200 KB (14650 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
Starting a new one? Use the Cursor rule starter on mdpantry, which passes every one of these checks and says what to change in it.
Source
realistsec/mpa-first-guidelines · 11 stars · license MIT · pushed 2025-12-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_slq6qdsfaqqxbsna GET https://markdownregistry.com/api/v1/resolve?ref=realistsec/mpa-first-guidelines/.cursor/rules/mpa-strict-rules.mdc GET https://markdownregistry.com/api/v1/blob/ce04e6b23707c5a0cdc2b214d568f10652d56a125e1aa86dc15236b301763e8a
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: Cursor rules vs AGENTS.md · which agent file does what.