library-goals Cursor ruleA
library-goals from reactive/data-client is a Cursor rule: instructions the Cursor agent follows in that repo.
mdr add reactive/data-client/.cursor/rules/library-goals.mdc@git:20261025.e0cfa7ePins git:20261025.e0cfa7e in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- Cursor rule
- Repository
- reactive/data-client
- Path
.cursor/rules/library-goals.mdc- Versions recorded
- 2
- Latest version
- git:20261025.e0cfa7e, committed Oct 25, 2026
- First version recorded
- Jul 4, 2026
- Size
- 746 bytes
- Repository stars
- 2,040
- License
- Apache-2.0
Consider project goals when changing library code.
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
# Library Goals Alignment When editing library code in `packages/*`, read [GOALS.md](../../GOALS.md) and weigh changes against it. It is the source of truth for project priorities — do not rely on a summary of it. - Evaluate design decisions (new APIs, abstractions, dependencies) against the goals before implementing. - When goals conflict for a given change (e.g. bundle size vs. performance), resolve the trade-off using the priorities expressed in GOALS.md, and note the reasoning (in a PR, under its GOALS impact section). - If a requested change works against the goals, say so and propose an alternative that stays aligned.
Read the whole file at its exact version.
How to install
mdr add reactive/data-client/.cursor/rules/library-goals.mdc@sha256:cde186aa5507ec2eThe line at the top of this page pins the label git:20261025.e0cfa7e, 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_tbyvkthdmnnj5g54)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Jul 4, 2026 and Oct 25, 2026, about one every 112 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261025.e0cfa7e latest | 2026-10-25 | e0cfa7e | 746 B | A | view · diff |
| git:20260704.ae8efa1 | 2026-07-04 | ae8efa1 | 704 B | A | view |
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (746 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
reactive/data-client · 2,040 stars · license Apache-2.0 · pushed 2026-11-01 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_tbyvkthdmnnj5g54 GET https://markdownregistry.com/api/v1/resolve?ref=reactive/data-client/.cursor/rules/library-goals.mdc GET https://markdownregistry.com/api/v1/blob/cde186aa5507ec2e45e1e9a4ab0a06506e444dd511219bbf0c9dadc1c6bd0b17
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.