screenshot-to-component

Grills the user about a planned feature or code change before any code is written. It reads the relevant code and docs first so every question is specific to the repo, asks one decision at a time with a recommended answer, works through scope, behaviour, edge cases, data, failure modes and rollout, then writes a SPEC.md with numbered requirements, Given/When/Then acceptance criteria tied to them and a test plan, checked by a linter that flags vague words and untraced requirements. Use when the user asks to grill or interview them about a feature, pressure-test an implementation plan, write a spec or PRD for a change, or turn a rough feature request into testable requirements before coding.

Designs and writes new Agent Skills (SKILL.md) from a described workflow. It produces a precise trigger description, a step-by-step workflow, rules, an output format, optional helper scripts, and a README, then checks the new skill before handing it over. Use when the user wants to create, write, improve, or package an agent skill, SKILL.md, Claude skill, or reusable agent workflow.

Researches and writes SEO-optimized, genuinely helpful blog articles, covering keyword and search-intent analysis, competitor outline gaps, title and meta description, headings, FAQ, internal links, and schema, in the brand's voice and following Google's helpful-content and E-E-A-T principles. Use when the user asks to write a blog post or article, do SEO content, or rank for a keyword.

Roasts a GitHub profile with humor, then gives genuinely useful advice. It analyzes public repos, stars, languages, missing descriptions and licenses, abandoned projects, lazy commit messages, and activity with a data script, and produces a shareable scorecard and a glow-up plan. Use when the user asks to roast, rate, review, or improve a GitHub profile, or asks "what does my GitHub say about me".

Rewrites a repository's README into a polished, star-worthy page with badges, a hero tagline, demo section, quickstart, features, usage, and contributing info. Use when the user asks to improve, rewrite, polish, or "glow up" a README, or when a repo has a missing or weak README.

Scans an AI agent's instruction and tool-config files (CLAUDE.md, AGENTS.md, skills, slash commands, subagents, Cursor and Cline rules, hooks, MCP server configs) for prompt injection, hidden Unicode or HTML-comment instructions, exfiltration commands, and risky permissions or unpinned MCP packages, then recommends what to remove or quarantine. Use when the user installs third-party skills or plugins, clones an unfamiliar repo, adds an MCP server, or asks whether their agent setup is safe to trust.

Reviews a pull request or local branch diff like a senior engineer, covering correctness, security, performance, naming, and missing tests, and produces prioritized, actionable comments (optionally posted to GitHub). Use when the user asks to review a PR, a diff, a branch, or "check my changes before I push".

Brutally honest but constructive critique of a landing page's copy, UX, design, and conversion. Gives a scored roast plus a prioritized fix list and rewritten headline and CTA options, working from a URL, screenshot, or the page's source code. Use when the user asks to roast, review, critique, or improve the conversion of a landing page, homepage, or pricing page.

Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.

No description in the SKILL.md.

Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".

tasteskill 2.5.1, the anti-slop frontend skill. Builds professional company websites at the level of figma.com and x.ai: plain copy in a voice of its own, one system, one section per screen, equal edges, real photographs and real product UI (licensed stand-in photographs when the client has none; a product render only when the brief asks for 3D), a hero entrance and one or two dealt moments on every page, shader effects and scenes only on tech, gaming and software pages, quiet micro-interactions, and a checker and finish gate that enforce it in a real browser. Use this whenever you build, design, redesign, restyle, polish or review a landing page, company, product, shop, cafe, hotel, studio, SaaS, AI, developer-tool or game site, as static HTML/CSS or inside an existing React, Next.js, Vue, Svelte, Astro or Tailwind project, or when the user says a page looks generic, templated or "AI-made".

React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.

UI/UX design intelligence for web, mobile, and desktop. This skill should be used when designing, building, reviewing, or fixing interfaces, including pages, components, design systems, accessibility, interaction, responsive layout, typography, color, charts, and stack-specific UI implementation. Searchable local data: 80 searchable styles (51 active), 192 product palettes and reasoning profiles, 74 font pairings, 120 UX guidelines, 105 icons, 17 GSAP presets, 25 chart types, and 22 stacks.