Add SpecVibe: Spec-driven development framework

[badideal-2046]

What is SpecVibe?

SpecVibe is an executable, spec-driven development framework for building production-ready AI-native applications. It integrates directly into Claude Code, OpenClaw, and Cursor as a structured skill.

What it covers

• 7-stage development workflow: Specify → Plan → Test → Implement → Review → Document → Deploy
• 11 reference guides covering backend, frontend, security (OWASP 2025), testing, DevOps, and more
• 4 ready-to-use templates for specifications, API contracts, deployment checklists, and IDE rules

Link

https://github.com/badideal-2046/SpecVibe

Summary by CodeRabbit

• Documentation
  • Added two README entries referencing SpecVibe—one under Sponsorships and one under Other rules—describing it as an executable, spec-driven framework for building production-ready AI-native applications and aligning with best practices. Noted duplicate placement across sections for visibility.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ff308cc and 6a07c20.

📒 Files selected for processing (1)

• README.md

🚧 Files skipped from review as they are similar to previous changes (1)

• README.md

---

📝 Walkthrough

Walkthrough

Two bullet entries for SpecVibe were added to README.md: one under the Sponsorships section and one under the Other rules section, both describing SpecVibe as an executable, spec-driven framework for building production-ready AI-native applications aligned with 2026 best practices. (Lines changed: +2)

Changes

Cohort / File(s)	Summary
README Documentation README.md	Added two bullets for SpecVibe: one in the Sponsorships section and one in the Other rules section; both describe SpecVibe as an executable, spec-driven framework for building production-ready AI-native applications aligned with 2026 best practices.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 SpecVibe hops into view,
In sponsorships and rules it's true,
A spec-driven scaffold, neat and spry,
Two small notes beneath the sky,
Hooray — production-ready, oh my! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: adding SpecVibe, a spec-driven development framework, which aligns with the PR's primary objective of introducing this new tool to the repository.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@README.md`:
- Line 280: The README entry for "SpecVibe" is malformed and out of order; edit
the list under the "### Other" section to replace the incorrect "- *
[SpecVibe](https://...)" line with a properly formatted markdown list item like
"- [SpecVibe](<relative-path-to-SpecVibe>)", move that item so it appears
alphabetically with the other entries in "### Other", and ensure the link uses a
correct relative path to the SpecVibe directory/file in this repo (verify and
fix the target if needed).

---

ℹ️ Review info

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between fc2ce04 and ff308cc.

📒 Files selected for processing (1)

• README.md