.cursorrules Cursor ruleA
.cursorrules from dongduong2001/pudo-code-system is a Cursor rule: instructions the Cursor agent follows in that repo.
mdr add dongduong2001/pudo-code-system/cursor/.cursorrules@git:20260522.5ad7a14Pins git:20260522.5ad7a14 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- Cursor rule
- Repository
- dongduong2001/pudo-code-system
- Path
cursor/.cursorrules- Versions recorded
- 2
- Latest version
- git:20260522.5ad7a14, committed May 22, 2026
- First version recorded
- May 4, 2026
- Size
- 972 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
# PUDO Methodology Rules Legacy Cursor rule file. Prefer the Project Rules templates in `cursor/.cursor/rules/*.mdc` for current Cursor versions. Keep this file for older Cursor workspaces that still read `.cursorrules`. Always follow the PUDO (Plan -> Understand -> Develop -> Optimize) framework. ## 1. Plan - Do not generate implementation code right away. - Propose an implementation plan first. - Explicitly outline scope, constraints, and success criteria. ## 2. Understand - Read related files and context before writing code. - Match existing code patterns, naming conventions, and architecture. ## 3. Develop - Work step-by-step. - Write tests alongside feature code. - Provide code snippets that are complete and correctly handle edge cases. ## 4. Optimize - Self-review your code before finishing. - Check for performance bottlenecks, dead code, and missing documentation. Embrace iterative loops: if an approach fails during Develop, pause and re-Plan.
Read the whole file at its exact version.
How to install
mdr add dongduong2001/pudo-code-system/cursor/.cursorrules@sha256:e1c17bd5d0436de2The line at the top of this page pins the label git:20260522.5ad7a14, 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_omuxcvrmtegxeaiy)
2 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 dongduong2001/pudo-code-system/cursor/.cursorrules 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 .cursorrules from somewhere else? Ask it: where did my .cursorrules 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 2 versions of this file, between May 4, 2026 and May 22, 2026, about one every 18 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260522.5ad7a14 latest | 2026-05-22 | 5ad7a14 | 972 B | A | view · diff |
| git:20260504.dbc0bbb | 2026-05-04 | dbc0bbb | 775 B | A | view |
Installed this file, say at .cursorrules? 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
- pass: Size between 200 bytes and 200 KB (972 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
dongduong2001/pudo-code-system · 5 stars · license MIT · pushed 2026-11-16 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_omuxcvrmtegxeaiy GET https://markdownregistry.com/api/v1/resolve?ref=dongduong2001/pudo-code-system/cursor/.cursorrules GET https://markdownregistry.com/api/v1/blob/e1c17bd5d0436de2341b5ae51545330a8e1f8f7bcc7b57977776efaba57f7eac
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.
More from dongduong2001/pudo-code-system
Every file in dongduong2001/pudo-code-system