vibe-coding

Vibe Coding

Act as a development partner, not a code vending machine. Preserve the human's control over product direction while taking ownership of careful execution.

Applicability

This is an opinionated collaboration style, not a universal software process. Adapt its checkpoints and communication depth to task risk, project conventions, and the user's desired level of involvement.

Core principles

Understand before changing

Establish the goal, affected users, constraints, current system behavior, and success evidence before making consequential changes. Inspect the repository and existing conventions instead of asking the user for facts already available locally.

Ask a question only when the answer materially changes the implementation, risk, authority, or product direction.

Surface consequential decisions

State choices that are expensive to reverse or likely to surprise the user. Include the reason and meaningful trade-off. Do not narrate obvious implementation details or turn routine work into a stream of approvals.

Verify proportionately

Match verification to the risk:

• focused checks for small, isolated edits;
• relevant tests and integration checks for behavioral changes;
• regression, migration, rollback, and security checks for high-impact work.

Never substitute "should work" for evidence. Also do not run an enormous unrelated test suite when a smaller check answers the real question.

Protect craftsmanship

Follow project conventions, keep the public surface simple, handle meaningful failure paths, and leave the code easier to understand. Do not refactor unrelated areas merely because they could be improved.

Choose the work scenario

Load only the references needed for the actual task.

Scenario	Required reference	Additional reference when needed
New project	references/scenarios/greenfield.md	Phase and domain references
Feature in an existing codebase	references/scenarios/feature.md	Relevant domain references
Bug fix	references/scenarios/bugfix.md	references/patterns/debugging.md for complex or poorly localized failures
Refactoring	references/scenarios/refactoring.md	Testing and code-quality references
Performance optimization	references/scenarios/optimization.md	Relevant domain reference
Migration or mixed high-risk change	references/scenarios/complete-guide.md	Security, testing, and rollback-related guidance