vibe-research-before-design SKILL.md skillA
vibe-research-before-design from ash1794/vibe-engineering is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ash1794/vibe-engineering/vibe-research-before-design@git:20260925.f6554ffPins git:20260925.f6554ff in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ash1794/vibe-engineering
- Path
plugins/vibe-engineering/skills/vibe-research-before-design/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260925.f6554ff, committed Sep 25, 2026
- Size
- 3,628 bytes
- Repository stars
- 165
- License
- MIT
Researches real projects, papers, and documented failures before proposing a new feature, architecture, or technology choice. Use for design decisions with multiple valid approaches, not for implementing an existing spec or fixing a known bug.
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
# vibe-research-before-design Other people's documented failures count as observed failure. Before proposing a design, find out how others solved the same problem and where it broke for them. ## When to Use This Skill - Designing a new feature, subsystem, or architecture - Choosing between technologies, frameworks, or patterns - Making a decision with long-term consequences that is expensive to reverse - The user asks "how should we build X?" - You're about to say "I recommend..." for a design choice ## When NOT to Use This Skill - Implementing an already-designed spec (the research was done at design time) - Fixing a bug with a known approach - Routine or mechanical changes with one obvious correct solution - The user has already chosen the technology and wants implementation - The decision was already researched and recorded (check `vibe-decision-journal` first) ## Steps 1. **Frame the question** — What exactly is being decided? What are the hard constraints (scale, latency, cost, team skills, existing stack)? 2. **Decompose** into sub-problems that can be researched independently. …
Read the whole file at its exact version.
How to install
mdr add ash1794/vibe-engineering/vibe-research-before-design@sha256:019aea1725cc7964The line at the top of this page pins the label git:20260925.f6554ff, 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_rl7iintd7wmvq2ol)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 25, 2026.
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 (3628 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
ash1794/vibe-engineering · 165 stars · license MIT · pushed 2026-10-07 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_rl7iintd7wmvq2ol GET https://markdownregistry.com/api/v1/resolve?ref=ash1794/vibe-engineering/vibe-research-before-design GET https://markdownregistry.com/api/v1/blob/019aea1725cc79646086f2c5af69090a1ef8beed1851e0d6a0608558c0df6461
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: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.