api-mocking-skill
Scaffold API mocking infrastructure using Mountebank and Testcontainers for reliable integration testing.
SKILL.md
| Name | api-mocking-skill |
| Description | Scaffold API mocking infrastructure using Mountebank and Testcontainers for reliable integration testing. |
🌟 VibesPro — From Idea to Working Software, Without the Wait
💡 The Problem Everyone Feels, But Few Solve
You have an idea. Six weeks later, you're still explaining it.
Right now, organizations waste an average of 40% of development time on miscommunication, rework, and knowledge loss. Domain experts describe what they need, developers interpret it differently, and by the time code ships—requirements have already changed.
The gap between what you imagine and what you get shouldn't take months.
What if you could describe what you need—and actually get it?
🚀 VibesPro: Your Ideas, Made Real
VibesPro is a Generative Development Environment—infrastructure that transforms how your organization builds software.
Instead of waiting for developers to interpret requirements, you describe what you need conversationally. Instead of hoping institutional knowledge survives employee turnover, your decisions become reusable building blocks. Instead of starting every project from scratch, proven patterns compound automatically.
The result? Working software in hours, not quarters. Knowledge that grows, never leaves.
✨ What Changes for You
Before VibesPro
| The Pain | What It Costs |
|---|---|
| Requirements lost in translation | Weeks of rework after launch |
| "Works on my machine" chaos | Delayed deployments, frustrated teams |
| Knowledge locked in senior developers | Risk every time someone leaves |
| Inconsistent implementations | Technical debt from day one |
| Waiting through development queues | Missed market windows |
After VibesPro
| The Shift | What You Gain |
|---|---|
| Describe once, generate correctly | Hours to first working version |
| Reproducible environments | Deploy anywhere with confidence |
| Organizational memory that compounds | Knowledge survives and grows |
| Standards enforced automatically | Quality without policing |
| Self-serve prototyping | Test ideas before committing resources |
🎯 Who Thrives With VibesPro
Product Managers & Domain Experts
You understand the business better than anyone—but translating that into technical specs feels like playing telephone. With VibesPro, you articulate what you need in plain language, see a proposal, and watch it become working software. No more waiting for developer availability. No more "that's not what I meant" after weeks of work.
"I described our new order management flow before lunch. By afternoon, I was testing a working prototype."
Technical Leaders & Architects
You've solved the same problems across multiple projects—but that knowledge stays trapped in your head or scattered across Confluence pages no one reads. VibesPro turns your architectural decisions into executable patterns that every future project inherits automatically. Your expertise scales without your constant presence.
"Our API conventions, our security patterns, our testing standards—they're not documentation anymore. They're infrastructure."
Compliance & Security Teams
You need audit trails. You need traceability. You need to prove that decisions connect to implementations. VibesPro generates complete evidence chains from requirement to code to test—automatically. No more chasing developers for documentation after the fact.
"Every line of generated code links back to the decision that created it. Audits went from weeks to hours."
Development Teams
You want to build features, not the same boilerplate for the hundredth time. VibesPro eliminates the repetitive scaffolding and lets you focus on the logic that matters. Architectural consistency is handled. You just build.
"I stopped writing CRUD endpoints. Now I describe the domain and the system builds them with our exact conventions."
🧠 How It Actually Works
1. You Describe What You Need
Not code. Not technical specifications. Just what you're trying to accomplish:
"I need to track customer orders with status updates and send notifications when orders ship."
2. The System Proposes a Plan
VibesPro's AI team (architect, product specialist, quality guardian) translates your request into a concrete proposal—what will be built, how it fits your existing patterns, what tests will verify it works.
3. You Review and Approve
Nothing happens without your sign-off. You see exactly what will be generated before it's generated. Adjust, refine, or approve.
4. Working Software Materializes
The system scaffolds implementations using your organization's proven patterns—not generic templates, but your standards, your conventions, your quality requirements.
5. Your Knowledge Compounds
Every decision, every successful pattern gets captured. Next time someone needs similar functionality, the system remembers—and builds even faster.
🔒 Built for Regulated Industries
For organizations where compliance isn't optional, VibesPro provides what auditors require:
| Requirement | How VibesPro Delivers |
|---|---|
| Audit trail | Every artifact links to its originating decision |
| Change control | All modifications flow through validated generators |
| Reproducibility | Same inputs produce identical outputs—always |
| AI governance | AI operates within validated boundaries, not arbitrary code invention |
| Evidence | Traceability matrix generated automatically; specs stay synchronized |
🏃 Get Started in 5 Minutes
# 1. Generate your personalized environment
copier copy gh:GodSpeedAI/VibesPro my-project
# 2. Set up dependencies
cd my-project && just setup
# 3. Start building
just dev
⚡ Important: Don't clone the repository—use Copier to generate an environment customized to your project.
Once running, you'll interact conversationally. Describe what you need. Review proposals. Watch working software appear.
📚 Go Deeper
Getting Started
- Quick Start Guide — Complete setup walkthrough
- Environment Guide — Understanding your workspace
For Builders
- Technical Architecture — How the pieces fit together
- Generator Development — Creating custom patterns
- AI Workflow Reference — Full capabilities
Governance & Security
- Specification Framework — How decisions become code
- Security Guidelines — Policies and guardrails
- Observability Stack — Monitoring and insights
CI/Development
Run CI locally before pushing:
./scripts/ci-local.sh lint # Quick lint check (~45s)
./scripts/ci-local.sh typecheck # Type checking (~1-2m)
./scripts/ci-local.sh test # All tests (~5-10m)
./scripts/ci-local.sh all # Full CI suite
./scripts/ci-local.sh docker # Full CI parity with Docker
See .github/workflows/README.md for full CI documentation.
🗺️ Where We're Heading
Now Building
- 🧠 Enhanced conversational pattern definition
- 📊 Automated architecture validation
- 🎯 Context-aware recommendations
- 🔄 Real-time collaboration on specifications
On the Horizon
- 🌐 Community pattern marketplace
- 🎨 Domain accelerators (auth, e-commerce, analytics)
- 🔌 Extension system for custom capabilities
- 🌍 Multi-cloud infrastructure patterns
🤝 Join the Movement
VibesPro is open source because transforming how software gets built shouldn't require a vendor lock-in.
- 🐛 Found a problem? Open an issue
- 💡 Have an idea? Start a discussion
- 📝 Want to improve docs? Every clarity improvement helps
- 🔧 Ready to contribute? See CONTRIBUTING.md
📜 Licensing: Simple and Fair
VibesPro Itself: MPL 2.0
The VibesPro infrastructure is open source under MPL 2.0. Modifications to VibesPro's files must remain open. Commercial licensing available for closed-source embedding.
What You Build: Entirely Yours
Everything you generate with VibesPro belongs to you—completely. No restrictions, no royalties, no licensing obligations on your output. Use it commercially, modify it, license it however you want.
VibesPro is MPL 2.0. Your software is yours.
See LICENSE for full details.
🚦 Ready?
copier copy gh:GodSpeedAI/VibesPro my-project
cd my-project && just setup && just dev
Your ideas. Your domain. Your pace.
Stop waiting weeks for what should take hours. Stop losing knowledge when people leave. Stop rebuilding the same patterns project after project.
Start building infrastructure that remembers, adapts, and accelerates.
When your organization's knowledge becomes executable, everything changes.