rgranet

ALWAYS invoke this skill before starting ANY coding task. This skill evaluates the user's coding prompt for completeness, coaches them to clarify vague requests before any code is written, then guides implementation through a structured workflow. You MUST consult this skill whenever the user mentions code, a repository, a bug, a feature, a refactor, tests, a codebase, files to edit, or any software change — even if the request seems simple. Also invoke when the user asks to improve their prompting or says "help me prompt better", "how should I ask for this", or submits a short or vague coding request like "add search", "fix the bug", "refactor this". The skill's first step is ALWAYS to evaluate whether the prompt has enough detail before doing anything else. Do NOT skip this skill for short requests — short requests are exactly when it is most needed. Works with any language or stack.

Force distinctive, human-feeling UI/UX design before writing any code. Use this skill whenever building or designing any interface — web apps, landing pages, dashboards, iOS/SwiftUI screens, Android/Compose screens, or any UI component. Also use this skill when the user asks to review, critique, audit, or improve an existing interface. Mandatory when the user says "build a UI", "create a screen", "design a component", "make it look good", "design the UX", "review this design", "what's wrong with this UI", "improve this interface", or asks for any frontend/interface/experience work. This skill operates in two modes: CREATE mode (9 decisions + human critique before code) and AUDIT mode (diagnose an existing interface against the same standards and produce an improvement plan). It produces design that feels human — not just different, but intentional, empathetic, and crafted.