llm-friendly-context is agent-read markdown (skill) from shinpr/claude-code-workflows: Clarifies inputs, outputs, success criteria, decisions, and unresolved conditions so downstream consumers can execute without guessing. Use when writing or revising LLM-facing prompts, handoffs, planning artifacts, reviews, reports, or generated instructions..
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
# LLM-Friendly Context
The goal is stable downstream execution: the next consumer should know what to read, what to do, what counts as success, and which unresolved decisions can change the result.
## Core Rules
1. **Use positive, executable instructions**
- State what the next consumer should do.
- Convert quality policies into positive criteria.
- Keep a prohibition only when it protects an irreversible boundary or shipped contract. Name the protected condition and the allowed action.
- Example: "Preserve existing public API behavior across the documented compatibility cases."
2. **Make vague instructions concrete**
- Replace subjective terms with observable conditions, paths, commands, schemas, examples, or decision rules.
- Terms that often need clarification when they leave a decision to the next consumer: `appropriate`, `proper`, `related`, `existing behavior`, `optional`, `as needed`, `if needed`, `per convention`, unresolved alternatives, `TBD`, `placeholder`.
3. **Specify output shape**
- Use the sections, fields, table columns, JSON keys, or checklist items the consumer uses.
…
Pin 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.
GET https://markdownregistry.com/api/v1/artifacts/art_svnvn3c5454c3z56
GET https://markdownregistry.com/api/v1/resolve?ref=shinpr/claude-code-workflows/llm-friendly-context
GET https://markdownregistry.com/api/v1/blob/cd77586a3bb3a25f784629f7169a41a01dd7a60f8321cfb254d1ead5af2334fb
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.
shinpr/claude-code-workflows · dev-skills/skills/coding-principles/SKILL.md · Language-agnostic coding principles for maintainability, readability, and quality. Use when implementing features…
shinpr/claude-code-workflows · dev-skills/skills/documentation-criteria/SKILL.md · Determines which of PRD, ADR, UI Spec, Design Doc, and Work Plan a change requires, and where each is stored. Use when…
shinpr/claude-code-workflows · dev-skills/skills/external-resource-context/SKILL.md · Records where resources outside the repository live (design source, design system, API schema, IaC source, secret…
shinpr/claude-code-workflows · dev-skills/skills/integration-e2e-testing/SKILL.md · Integration and E2E test design principles, ROI calculation, test skeleton specification, and review criteria. Use when…
shinpr/claude-code-workflows · dev-skills/skills/requirement-convergence/SKILL.md · Separates the outcome a change must produce from the requirements proposed to reach it, records what the user excluded…
shinpr/claude-code-workflows · dev-skills/skills/test-implement/SKILL.md · Implements React/TypeScript unit, integration, and browser E2E tests with the repository's configured runner, mocks…
shinpr/claude-code-workflows · dev-skills/skills/testing-principles/SKILL.md · Language-agnostic testing principles including TDD, test quality, coverage standards, and test design patterns. Use…
shinpr/claude-code-workflows · dev-skills/skills/typescript-rules/SKILL.md · React/TypeScript frontend development rules including type safety, component design, state management, and error…
