Design any system from scratch into a rigorous System Design Doc. Generic fallback when no topic-specific playbook fits. Sensors and evals gate.
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
Produce a System Design Doc for an arbitrary system. Follow guides/pipeline.md for retry and approval.
Ask once if missing: system in 1-2 sentences, scale target (users / QPS / data / latency SLO),
internal vs web-scale, known constraints.
**Route first.** If the problem matches a topic playbook under
`.claude/agents/system-architect/skills/{topic}/SKILL.md` (e.g. search-engine), use that skill
instead, it carries a canned reference architecture. This generic skill is the fallback when no
topic fits.
Compute feature_id = {YYYY-MM-DD}-{slug}.
Read:
- guides/design-method.md (the method and the canon)
- guides/writing-style.md
- guides/templates/system-design.md
- guides/pipeline.md
- guides/examples/good-system-design-example.md
- .claude/shared/context-strategy.md § `/system-design:design`
Existing system → ground current architecture first with semble + repowise context (probe `.claude/scripts/context-tools.sh {repo}`). Greenfield → skip.
Generate the SDD: walk all 13 stages of the template. Every non-functional claim carries a number.
Show back-of-envelope math. Name a trade-off per major choice. Mermaid for flow and architecture.
…
The line at the top of this page pins the label git:20261005.0119af1, 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.
A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (1619 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
GitHub
pierry/harness-kit · 4 stars · license MIT · pushed 2026-10-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_7xaydjlv4d6bsdqh
GET https://markdownregistry.com/api/v1/resolve?ref=pierry/harness-kit/design
GET https://markdownregistry.com/api/v1/blob/5ada7894acc7aef64667a6dedc3410cda27699daf545621c816427e35de9f655
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.
pierry/harness-kit · .claude/agents/product-manager/skills/prd/SKILL.md · Generate a Product Requirements Document for an team squad. Business-facing artifact. Sensors and evals gate.
pierry/harness-kit · .claude/agents/product-manager/skills/prp/SKILL.md · Generate a Product Requirements Prompt for engineering handoff. Needs an approved PRD. Sensors, link validation, and…
pierry/harness-kit · .claude/agents/staff-software-engineer/skills/backend/SKILL.md · Backend engineering conventions for team. Java/Kotlin servers. Project conventions in .claude/conventions/backend.md…
pierry/harness-kit · .claude/agents/staff-software-engineer/skills/mobile/SKILL.md · Mobile engineering conventions for team. iOS and Android. Project conventions in .claude/conventions/mobile.md override…
pierry/harness-kit · .claude/agents/staff-software-engineer/skills/web/SKILL.md · Web frontend engineering conventions for team. Vue.js stack. Project conventions in .claude/conventions/web.md override…
pierry/harness-kit · .claude/agents/system-architect/skills/review/SKILL.md · Adversarial design review of a System Design Doc. Interrogates the staff questions, finds the cost-explosion and…
pierry/harness-kit · .claude/agents/system-architect/skills/search-engine/SKILL.md · Design a web-scale search engine (crawler, processing, indexing, query serving). Topic playbook from the System Design…
jeremylongshore/tons-of-skills-marketplace · plugins/ai-agency/hyperflow/skills/design/SKILL.md · Use when the user wants the visual/experiential design of a product done systematically — a design system, a screen, a…
sethgammon/citadel · skills/design/SKILL.md · Generates and maintains a design manifest for visual consistency. In existing projects, reads current styles and…
adityaraj0421/naksha-studio · skills/design/SKILL.md · Assembles a virtual design team to produce production-quality UI, UX, visual, social media, email, and data output. A…
ericrisco/rsc-harness · skills/design/SKILL.md · Use when designing, polishing or auditing a web UI or landing page — visual concept, type/color/spacing/motion tokens…
