Results for “design-brief”

HTML-as-medium design for hi-fi prototypes, pitch decks, and motion exports (PPTX/PDF). USE WHEN the user asks for a one-pager, pitch deck, visual deck, capture deck, export deck to PDF or PowerPoint, or HTML visuals from pursuit intel. Builds numbered slide HTML under pursuits/{slug}/05_visuals/ and exports via vendored Node scripts (export_deck_pdf.mjs, export_deck_pptx.mjs). DO NOT USE FOR Word/Excel office docs (use renderers) or proposal prose (use proposal-generator).

Analyzes a plan file and converts it into an interactive HTML explainer with brief and full modes, featuring dedicated diagrams and source links.

Canonical repo-local DESIGN.md workflow for product, UI/UX, and frontend decision source of truth

Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability.

Tone down overly bold or visually aggressive designs. Reduces intensity while maintaining design quality and impact.

Choose and apply high-quality frontend visual direction for websites, apps, dashboards, redesigns, landing pages, portfolios, and UI polish. Use when prompts mention design taste, anti-slop UI, redesign, premium visual design, minimalist, brutalist, legacy style inheritance, design direction, or the old taste-skill/gpt-tasteskill/soft-skill/brutalist-skill/minimalist-skill/redesign-skill skills.

Anti-slop frontend design skill for building NEW landing pages, portfolios, and UI from a brief. Reads the brief and existing brand context first, infers a design direction from three configurable dials (variance, motion, density), and ships interfaces that don't look templated or default-AI. Use when starting a new page/UI with no existing identity to preserve, or when asked to design something "that doesn't look like every other AI landing page." For auditing and upgrading an EXISTING UI, use `taste-redesign` instead — this skill is for the moment before code exists. Triggers on: "build a landing page", "design a portfolio", "make this not look generic/templated/AI-generated", "anti-slop", starting UI work with a brief but no established identity yet. Also owns component-library selection (which package for toasts, dropdowns, charts, drag-and-drop, state, etc.) — use this instead of hand-rolling a component or guessing at a dependency. Source: github.com/Leonxlnx/taste-skill (taste-skill, the main v2 varian

Audits an EXISTING UI/codebase for generic AI patterns and applies targeted craft fixes — layout, interactivity, content, iconography, and code quality — without discarding the project's own identity. Use when a UI looks flat, generic, or "AI-slop" and there is code to improve, not build from scratch. Triggers on: "improve the design", "looks generic", "not polished enough", "redesign this", "elevate the UI", "it looks boring", "make it better looking", "apply taste", "design review". Works with any CSS framework. For designing a NEW project's identity from a brief, use `taste-skill` instead — this skill only upgrades what's already built. Source: github.com/Leonxlnx/taste-skill (redesign-skill), restored to the full checklist + the project-identity rule the earlier port had dropped.