max-promptlisted

# Max Prompt ## Purpose Use this skill when the user wants help turning vague feedback, screenshots, taste, frustration, or half-formed product intuition into a strong prompt for a coding agent. This skill is especially useful for: - UI/UX bugs - frontend implementation - React/TypeScript components - CSS layout and visual polish - animation behavior - GSAP / Framer Motion issues - interaction design - gesture/snap behavior - component architecture - state/lifecycle bugs - “it feels wrong but I don’t know how to say it” moments The goal is to translate the user’s instinct into an implementation-ready prompt. Do not simply restate the user’s words. Convert their feeling into: - the underlying mechanism - the likely root cause - the correct architecture or ownership - the intended visual/interaction model - explicit constraints - state priority rules - lifecycle rules - animation cleanup rules - concrete implementation direction - expected verification behavior --- ## Core Philosophy The job is not to “write a better prompt.” The job is to convert taste into engineering language. The formula: ```txt Feeling → Mechanism → Ownership → Constraints → Implementation → Expected Result