Explorar skills
15.291 skills encontradas
Alerta por categoría
Recibe nuevas skills de Design e Frontend todos los lunes
continuous-discovery-habits
Product discovery framework based on Teresa Torres'' "Continuous Discovery Habits". Use this skill whenever the user is doing product discovery work — even if they do not explicitly say "OST," "Teresa Torres," or "discovery." Triggers include: (1) building, critiquing, or restructuring an opportunity solution tree, (2) identifying, organizing, or prioritizing customer opportunities, (3) designing
browser-audit
Run a pre-deploy browser audit of a live, preview, or local web page for accessibility, SEO, Lighthouse quality, and critical UX issues. Use when asked to audit a page/site before deployment, check WCAG 2.2 AA, WAI-ARIA, Lighthouse, accessibility, SEO, contrast, keyboard navigation, focus states, semantic HTML, forms, alt text, headings, ARIA attributes, best practices, or browser-visible web qual
github-repo-launch-page
Use this skill when creating, auditing, or redesigning a public GitHub repository so the repository is easy to understand, trust, share, install, and contribute to. Use together with github-repo-product-naming whenever naming, renaming, positioning, repo slug, About description, or product identity matters.
escaping-build-trap
Product management framework based on Melissa Perri''s "Escaping the Build Trap". Use this skill whenever the user is discussing product strategy, roadmap construction, product team maturity, or symptoms of feature-factory behavior — even if they do not explicitly say "build trap" or "outcome-driven." Triggers include: (1) diagnosing whether a team is stuck shipping features without measuring outc
paper-to-code
Convert Paper designs into production-ready websites with animations. Use when the user wants to build a website from a Paper design, convert Paper frames to code, implement a landing page from Paper, or says "build this from Paper", "convert my Paper design", "paper to code". Reads designs via Paper MCP, generates React + Tailwind + Framer Motion code with responsive breakpoints and polished scro
office-pdf
Create polished PDF deliverables, fill PDF forms, inspect fillable PDF fields, or reformat existing text/Markdown/PDF content into a designed PDF. Use when final output is PDF and visual quality, form fields, cover pages, or print-ready layout matter. Do not use for knowledge extraction or casual PDF reading; use docling-skill or lightweight pdf tooling for those.
positioning-and-pitch
Framework based on April Dunford''s "Obviously Awesome" and "Sales Pitch". Use this skill whenever the user is discussing how to describe, frame, differentiate, sell, or talk about their product — even if they do not explicitly say "positioning," "pitch," or "messaging." Triggers include: (1) defining or evaluating product positioning using the five-component framework, (2) translating positioning
react-flow-best-practices
Best practices for writing, reviewing, and refactoring React Flow / @xyflow/react v12 canvases. Use when work touches React Flow components, custom nodes, custom edges, handles, node data typing, viewport controls, MiniMap/Background/Panel usage, NodeToolbar, NodeResizer, or workflow-builder review tasks.
sales-pitch
Framework based on April Dunford''s "Sales Pitch". Use this skill whenever the user is discussing sales conversations, pitch decks, demos, buyer messaging, or stalled deals — even if they do not explicitly say "sales pitch," "positioning," or "Dunford." Triggers include: (1) structuring a B2B sales conversation that builds buyer confidence rather than pushing features, (2) developing a pitch narra
figma-pencil-fsd-tailwind4
Convert Figma or Pencil designs into production-ready frontend code using Feature-Sliced Design and Tailwind CSS v4. Use when translating designs into code, extracting tokens, mapping UI to FSD layers (shared / entities / features / widgets / pages / app-shell / app), enforcing Server vs Client boundaries when applicable, or validating design-to-code fidelity.
pencil-to-code
Convert Pencil `.pen` design files and named Pencil node IDs into production frontend code. Use when asked to implement, migrate, reproduce, or refine a Pencil/Figma-like visual design in code, especially for responsive artboards, glassmorphism, typography matching, background image layers, design tokens, or visual fidelity debugging against Pencil node IDs.
claude-md-doctor
Audit and improve CLAUDE.md files. Use when rules aren't working, context is bloated, or after learning a lesson that should become a rule.