vibe-implement

Enforce alignment between interaction, architecture, design, and implementation phases.

113|12|Updated May 19, 2026

Search Tags:#tdd #implementation #nextjs #alignment #cloudbase #vibe-coding

Ready to run

npx skills add https://github.com/idiotLeoLYJ/Daliu-Awesome-Skills --skill vibe-implement

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: vibe-implement
Source: https://github.com/idiotLeoLYJ/Daliu-Awesome-Skills/tree/main/plugins/qima/skills/vibe-implement
Command: npx skills add https://github.com/idiotLeoLYJ/Daliu-Awesome-Skills --skill vibe-implement

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the common Vibe Coding failure point where generated code drifts from the original design, interaction, and architectural intent. It enforces a strict alignment gate between documentation and implementation.

Core Features & Use Cases

Alignment Gatekeeping: Ensures no code is written unless interaction, architecture, design, and prototypes are fully aligned and verified.
Atomic Verification: Breaks down complex requirements into testable, atomic验收项 (acceptance criteria) to ensure every UI element matches the design system.
Use Case: When you are ready to turn your validated prototypes and architecture into a production-ready application, use this skill to manage the implementation lifecycle while ensuring 100% compliance with your design tokens and interaction logic.

Quick Start

Use the vibe-implement skill to begin the implementation phase for the current project by validating the alignment of all design and architecture documents.

Frequently Asked Questions about vibe-implement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I prevent code drift from design and architecture documents during implementation?▼

To prevent code drift during implementation, use a strict alignment gate that verifies interaction, architecture, design, and prototypes are fully synchronized before any production-ready code is written. This ensures no orphan or missing features occur.

How to apply test-driven development to align validated prototypes with production code?▼

To apply test-driven development to validated prototypes, break down complex requirements into atomic acceptance criteria. This enforces strict alignment, ensuring every UI element matches the design system before transitioning to production-ready code.

What is an alignment gate in Vibe Coding workflows?▼

An alignment gate in Vibe Coding workflows is a checkpoint that enforces strict synchronization between interaction, architecture, design, and implementation phases. It manages the transition from validated prototypes to production-ready code using atomic acceptance criteria.

Do I need to sync interaction.md and architecture.md before writing production code?▼

Yes, you need to fully synchronize interaction.md, architecture.md, design.md, and the prototypes directory before writing production code. This full synchronization acts as the alignment gate to ensure no orphan or missing features.

Can I use atomic verification for UI elements in a Next.js application?▼

Yes, you can use atomic verification to break down complex requirements into testable atomic acceptance criteria for your Next.js application. This ensures every UI element matches your design system and interaction logic.

What happens if my prototypes directory is not fully aligned with my design documents?▼

If your prototypes directory is not fully aligned with design documents, the implementation phase is blocked. The alignment gate requires full synchronization of interaction, architecture, design, and prototypes to guarantee no orphan or missing features.