vibe-interaction

Define UI interaction specifications by mapping granular element behaviors and state machines. This prevents Vibe Coding rework by enforcing a strict taxonomy and zero-ambiguity documentation for every page layout and navigation logic.

Document loading, empty, and error states by applying a standardized state-matrix methodology. This defines granular UI interaction specifications, ensuring agent workflows receive a zero-ambiguity blueprint for every element behavior.

Standardize UI taxonomy for complex dashboards by enforcing an 11-keyword taxonomy, such as navigate, modal, and drawer. This ensures implementation consistency by defining exactly what happens when a user interacts with an element.

Yes, you can generate an interaction document from an existing product specification. By reading the idea.md file in your current directory, the skill outputs a detailed interaction blueprint defining all page layouts and module behaviors.

No, vibe-interaction does not require specific UI frameworks like shadcn to define workflows. It applies standardized interaction design and state-matrix methodology to any established product idea to create zero-ambiguity documentation.

AI-generated UI lacks consistency without zero-ambiguity interaction documentation because element behaviors remain undefined. Forcing a precise, granular definition of how users interact with every page prevents the common cycle of AI rework.