content-design skillA
content-design is agent-read markdown (skill) from vmobifystudio/app-dev-team: Use when writing or reviewing any string a user reads — labels, buttons, empty states, errors, permission prompts, onboarding, notifications. Invoked by ux-architect and product-designer while specifying screens, and by product-manager when a clarification turns out to be a copy decision. Triggers the moment a placeholder string would ship..
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
# Content design The interface is mostly words. Words written last, by whoever was implementing, are the ones users actually read. ## Buttons and labels - **A button says what happens when you press it.** `Save changes`, not `OK`. `Delete 3 photos`, not `Confirm`. - **A destructive button names what is destroyed and whether it comes back.** "This cannot be undone" belongs in the dialog, not in the button. - Sentence case throughout. Never end a button label with a full stop. - `Cancel` means "nothing happens". Never label a button `Cancel` when something happens. ## Errors — three parts, always 1. **What happened**, in the user's terms, not the system's. 2. **Whether their data is safe.** This is the question they are actually asking. 3. **What to do next**, as an action they can take right now. `Something went wrong` fails all three. `Couldn't save — your note is still here. Retry when you're back online.` passes all three in one line. **Never show an error code without also showing prose**, and never show raw exception text. ## Empty states An empty state is not a blank screen with an apology. It says what belongs here, why it is empty …
Read the whole file at its exact version.
How to install
mdr add vmobifystudio/app-dev-team/content-design@git:20260729.071181emdr add vmobifystudio/app-dev-team/content-design@sha256:74fdc33e865e7e5fPin 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_hipna7k5filvftxl)
1 badge views in 30 days
Versions
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 (2745 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
vmobifystudio/app-dev-team · 4 stars · license MIT · pushed 2026-09-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_hipna7k5filvftxl GET https://markdownregistry.com/api/v1/resolve?ref=vmobifystudio/app-dev-team/content-design GET https://markdownregistry.com/api/v1/blob/74fdc33e865e7e5fa30af0d046f1ae0b9de11efee2a32e5f6fafa50a3997bd52
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.
More from vmobifystudio/app-dev-team
Every file in vmobifystudio/app-dev-team