vibe-briefing-skills

Turns a rough idea into a validated design through one-question-at-a-time dialogue, before any code is written. Use at the very start of anything new or fuzzy: a new feature, app, page, component, or behaviour change, and when the user says 'I want to build', 'I have an idea', 'let us design', 'help me think this through', or the requirements are unclear. This is the DESIGN stage, before writing-plans. Do not use once a design is already agreed.

Builds a feature from an existing written plan, one task at a time, verifying each step and committing before moving on. Use when a plan already exists and the user says 'build it', 'implement the plan', 'start building', 'work through the plan', or 'make it'. This is the BUILD stage after writing-plans. Stops and asks instead of guessing when blocked.

The visual stack and design rules for this Flask app. Tailwind CSS plus DaisyUI inside Jinja templates, a shared base.html layout, a restrained palette, and two non-generic fonts. Use whenever building, styling, or restyling any page, template, view, navbar, form, card, button, or layout in this Flask/Jinja project, or when the user says 'make it look good', 'design the page', 'style this', 'the UI', or 'make it prettier'. Keeps every screen consistent and intentional.

Creates distinctive, production-grade frontend interfaces with a strong aesthetic point of view, avoiding generic 'AI slop' looks. Use for taste-level visual decisions on any component, page, app, or interface, including typography and font pairing, colour and theme, layout and composition, motion, and breaking out of templated defaults. Use when the user says 'make it look good', 'it looks generic', 'it looks boring', 'design something distinctive', or wants high design quality. Pairs with flask-ui-design, which sets the stack; this sets the taste.

The locked backend contract for the VIBEBRIEF daily AI briefing app, all-Oracle and in-database. Use whenever building or changing any backend route, database call, summary, embedding, memory, story-linking, or search, or the Oracle and Agent Memory wiring. Pins the connection, Select AI generation, and the Oracle AI Agent Memory (oracleagentmemory) four-memory model so voice-driven changes cannot break the data layer. The frontend (look, layout, copy) is NOT governed by this skill and stays free to change.

Breaks an agreed design or spec into a bite-sized, step-by-step build plan with exact files, code, and verification steps. Use after the design is settled and before building, when the user says 'make a plan', 'break this down', 'what are the steps', 'plan the build', or 'turn this into tasks'. This is the PLAN stage between brainstorming and executing-plans. Do not use to write the actual feature code, only the plan.