Recently, a new type of vibe coding enhanced projects/tools has emerged.

CN
3 hours ago

Recently, a new category of vibe coding-enhanced projects/tools has emerged, among which Superpowers, spec-kit, openSpec, and BMAD are the most famous, garnering thousands of stars on GitHub in just a few months.

I spent some time researching and testing them. Here are my suggestions:

  1. Tools like codex, claude code, and open code are already very powerful. Remember that the first step is to make good use of them; they basically meet 90% of the demand scenarios. Don't be swayed by certain media outlets that intentionally downplay their effectiveness to highlight the usefulness of these enhanced tools.

  2. If you are creating small tools for personal use or making some modifications, there is no need to fuss over these.

  3. If you currently only have some ideas without specific details, I recommend starting with Superpowers. It will help brainstorm and gradually refine your project.

  4. Spec-kit and BMAD are suitable for larger, more complex projects. They tend to write more complex documentation standards from the outset. They are also suitable for team collaboration, long-term project maintenance, and iteration.

  5. OpenSpec is more suitable for making modifications to existing projects. However, if the changes are small and the project is not large, using tools like claude code is sufficient. Many people have a situation where they use different models and IDEs. For example, I might use opus4.5 for writing projects and codex for bug fixing. Sometimes, when antigravity acts up, I might use cursor. In such cases, their coding styles and writing methods may differ significantly, and that's when you should consider using OpenSpec or finding a skill.

  6. Superpowers

Superpowers is more suitable for building projects from scratch. It is a complete software development workflow, more like an "external brain" and "multi-functional tool belt" for current AI coding, or to put it more simply, it assembles various professional skills.

It can be installed on claude code, codex, and open code. After installation, it can be used in three scenarios:

  1. The first step: "Brainstorming"

This is suitable for the initial stage of a project when you only have a preliminary idea. You can discuss it with it. It will ask you some questions to clarify the project.

  1. The second step: Writing a plan

Based on the design from the previous step, it breaks down the work into manageable small tasks. Its tasks are often smaller and more detailed than those self-divided by current tools like claude code and cursor.

  1. The third step: Executing the plan

It assigns new sub-agents for each task and conducts a two-phase review (first checking compliance with standards, then checking code quality), or executes in batches and sets manual checkpoints.

Even if you don't use Superpowers, the skills in its GitHub repository are worth learning from and referencing. It contains a dozen well-designed skills that cover various stages of development.

  1. Spec-kit

Spec-kit is an SDD (Specification Driven Development) framework launched by the official GitHub team. It is the most structured and resembles an "industrial-grade standard." Its characteristics are normative and detailed. It is suitable for more complex projects, multi-person collaboration, or projects that require long-term maintenance.

Its specification documents also have the highest requirements and the most quantity among all SDDs. In simple terms, it believes that in the AI era, since code will be replaced by AI, the most important thing should be to shift from writing AI code to defining specifications.

Spec-kit also follows the process of defining rules, making plans, executing plans, and testing. The biggest highlight that distinguishes spec-kit from other frameworks is that it requires you to maintain an http://CONSTITUTION.md in the project root directory (or define it in .cursorrules).

-- Technical stack rules: For example, "Must use Tailwind CSS, CSS Modules are prohibited."

-- *Code style: "All backend interfaces must include exception handling blocks and return standard JSON format."

-- Directory structure: "All business logic must be written in the services/ directory, and the Controller layer is only responsible for forwarding."

  1. OpenSpec

OpenSpec is also an SSD, but it is lighter compared to spec-kit. It focuses on "incremental changes," with the core idea being: Since projects are constantly evolving, AI should not have to read hundreds of lines of complete documentation every time, but should only focus on "what has changed this time."

In addition to being lighter, it has a very high Token efficiency (Token-Efficient): By adopting an "incremental (Delta)" model, AI only needs to read and process segments related to the current change, rather than the entire massive document. This can save a lot of API overhead when dealing with large legacy projects (Brownfield Projects) and reduce AI's "hallucinations."

It is more suitable for scenarios where changes are made while working, and it supports "reverse specification": If the current project does not have documentation, OpenSpec allows AI to first read the existing code and reverse-engineer the initial specification document.

  1. BMAD

BMAD is an open-source development methodology launched by BMAD Code Org. If OpenSpec and spec-kit are specific "toolkits," then BMAD is more like a "modern AI software engineering textbook."

In fact, BMAD is different from the three mentioned above; it is more suitable to be used alongside engineering tools like claude code. It has over 12 domain expert agents and 34 workflows internally.

It aims to solve a core contradiction: How to make AI work like a mature development team in large-scale, complex enterprise-level projects, rather than like an intern who can only write code snippets.

Its drawback is that it is too heavy, suitable for generating extremely robust code, and is ideal for fields with high security requirements such as finance and SaaS. It is not suitable for personal or small projects.

免责声明:本文章仅代表作者个人观点,不代表本平台的立场和观点。本文章仅供信息分享,不构成对任何人的任何投资建议。用户与作者之间的任何争议,与本平台无关。如网页中刊载的文章或图片涉及侵权,请提供相关的权利证明和身份证明发送邮件到support@aicoin.com,本平台相关工作人员将会进行核查。

Share To
APP

X

Telegram

Facebook

Reddit

CopyLink