Clarifies inputs, outputs, success criteria, decisions, and unresolved conditions so downstream agents can execute without guessing. Use when writing or revising LLM-facing prompts, handoffs, planning artifacts, reviews, reports, or generated instructions.
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
# LLM-Friendly Context
The goal is stable downstream execution: the next agent should know what to read, what to do, what counts as success, and which unresolved decisions can change the result.
This skill governs the clarity of LLM-facing output — prompts, handoffs, and generated artifacts. The caller supplies the artifact type and any artifact-specific template or input contract; include only the information its consumer uses to decide, act, or verify. Use a declared contract's field names and value meanings when the consumer branches on them.
## Core Rules
1. **Use positive, executable instructions**
- State what the next agent should do
- Convert quality policies into positive criteria
- Example: "Preserve existing public API behavior across the documented compatibility cases."
- Keep a prohibition only when it protects an irreversible boundary or a shipped contract; then name the protected condition and the allowed action alongside it
2. **Make vague instructions concrete**
- Replace subjective terms with observable conditions, paths, commands, schemas, examples, or decision rules
…
The line at the top of this page pins the label git:20260923.86a3d79, 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.
GET https://markdownregistry.com/api/v1/artifacts/art_doqpnzy63ljbmiso
GET https://markdownregistry.com/api/v1/resolve?ref=shinpr/ai-coding-project-boilerplate/llm-friendly-context
GET https://markdownregistry.com/api/v1/blob/77e365cd4e1995a68af07431da08f38979a0746f77b692e11bbbfa6d3d6a1659
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.
shinpr/ai-coding-project-boilerplate · .claude/skills-en/documentation-criteria/SKILL.md · Determines which PRD, ADR, UI Spec, Design Doc, and Work Plan a change requires and where each is stored. Use when…
shinpr/ai-coding-project-boilerplate · .claude/skills-en/frontend-typescript-rules/SKILL.md · Applies React/TypeScript type safety, component design, and state management rules. Use when implementing React…
shinpr/ai-coding-project-boilerplate · .claude/skills-en/frontend-typescript-testing/SKILL.md · Designs frontend tests using the repository's configured React test and browser harnesses, including RTL, MSW, Vitest…
shinpr/ai-coding-project-boilerplate · .claude/skills-en/implementation-approach/SKILL.md · Selects implementation strategy (vertical slice, horizontal, or hybrid) with risk assessment. Use when planning feature…
shinpr/ai-coding-project-boilerplate · .claude/skills-en/integration-e2e-testing/SKILL.md · Selects and designs the smallest integration/E2E test set that proves accepted behavior at an observable boundary. Use…
shinpr/ai-coding-project-boilerplate · .claude/skills-en/requirement-convergence/SKILL.md · Separates the outcome a change must produce from the requirements proposed to reach it, records what the user excluded…
shinpr/ai-coding-project-boilerplate · .claude/skills-en/skill-optimization/SKILL.md · Evaluates and optimizes skill file quality using 9 content patterns and 10 editing principles. Use when creating…
