Install
$ agentstack add skill-ash1794-vibe-engineering-research-before-design ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
vibe-research-before-design
Before proposing any design, architecture, or technology choice — research first. "Other people's documented failures count as observed failure."
When to Use This Skill
- Designing a new feature or system
- Choosing between technologies, frameworks, or patterns
- Making architectural decisions with long-term consequences
- 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 (use
vibe-debugging-journalinstead) - Simple refactoring with no architectural implications
- The user has explicitly chosen a technology and wants implementation
Steps
- Identify the design question — What decision are we making? What are the key constraints?
- Dispatch research — For each major sub-problem, find:
- 2+ named real-world projects/libraries with adoption metrics (GitHub stars, npm downloads, production users)
- 1+ academic paper or technical blog with year and venue/source
- The mechanism — how does it actually work? (Not marketing copy)
- Known failures — what went wrong for others?
- Applicability assessment — does this fit our constraints?
- Synthesize findings — Present a comparison table:
| Option | Adoption | Mechanism | Known Failures | Fit | |--------|----------|-----------|---------------|-----|
- Make a recommendation — Based on evidence, not intuition. State confidence level.
- Record the decision — Use
vibe-decision-journalto log the choice and alternatives.
Red Flags
- "This is obvious, we should just use X" — If it's obvious, proving it takes 2 minutes
- "I've used X before" — Past experience ≠ current best option
- "Everyone uses X" — Popularity ≠ fitness for your constraints
- "Let me just start building and we'll figure it out" — The most expensive approach
Output Format
Research Summary
- Decision: [What we're deciding]
- Constraints: [Key constraints]
- Options Evaluated: X
Comparison Table
| Criteria | Option A | Option B | Option C | |----------|----------|----------|----------|
Recommendation
[Evidence-based recommendation with confidence level]
Sources
[Links to projects, papers, docs referenced]
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: ash1794
- Source: ash1794/vibe-engineering
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.