Loading...
Loading...
Found 505 Skills
When the user wants to plan, script, produce, or optimize App Store Preview videos or Google Play promo videos — the autoplay videos that show in App Store/Play Store search and product pages. Use when the user mentions "App Preview", "preview video", "app store video", "promo video", "Play Store video", "video poster frame", "YouTube promo for Play Store", "30 second app video", "video script", "video specs", or "should I add a preview video". For static screenshots, see screenshot-optimization. For A/B testing the video, see ab-test-store-listing. For broader creative briefs, see screenshot-optimization (covers stills).
Use when writing David Laub's public-facing, non-manuscript prose. Covers the LinkedIn About section, technical blog posts announcing a tool or a result, project READMEs, and release notes. Sets the voice, the per-genre specs, and the mechanical guardrails against LLM writing tells.
Clone a website — two modes. SNAPSHOT = a faithful, self-contained offline copy of a page (HTML+CSS+JS+images in one file, exact bytes, SingleFile-style). RECONSTRUCT = AI reverse- engineer the page into a clean editable Next.js/Tailwind codebase (design tokens → component specs → parallel builders → visual-diff QA, the ai-website-cloner-template method). Use when the user wants to "clone this site", copy a page's design/UI + interactions, mirror a layout, save offline, or rebuild a site as editable code. Built-now-adapt-later: snapshot builtin works now; faithful live capture + the reconstruct pipeline are one-config engine adapters.
Define project UI/UX design specs and output design-spec.md, review existing interfaces and deliver prioritized fix recommendations, or compile design rules for specific surfaces. Use when the user asks for a design system, design spec, or full UI review; simple questions about a single color, font size, or button size get a direct answer.
Crée et fait évoluer des spécifications UI maquettées en HTML + Tailwind CSS : écrans desktop et mobile annotés, parcours, règles fonctionnelles, points ouverts et journal des itérations, pour itérer sur une application ou un outil avant les développements. Si l'interface n'est pas encore validée, propose d'abord trois propositions qui diffèrent par la disposition (navigation, organisation des écrans) et par le thème (couleurs, typographie, formes), à choisir ou combiner. Peut aussi partir d'un site ou d'un code existant pour reprendre son style et spécifier de nouvelles fonctionnalités. Utiliser dès que la personne parle de maquettes, wireframes, specs UI, spécifications fonctionnelles avec écrans, prototype d'interface, parcours à maquetter, charte ou direction graphique pour une app, ou nouvelle fonctionnalité à maquetter sur un site existant, même sans prononcer le mot « specs ». Aussi pendant les développements, pour tenir les specs à jour avec l'implémentation (statut des écrans, écarts).
Analyses a third-party system's API or file specification against Factorial's integrations framework and produces a detailed integration mapping document — the integration domain (payroll or finance), every capability in that domain with its verdict (fully, partially or not supported), the vendor endpoints to use for each, and the field-by-field mapping between Factorial's API and the vendor's. Use whenever someone shares a vendor API spec, OpenAPI/Swagger file, developer-portal link, integration guide or file layout and wants to know what we could build against it, how to map it, whether an integration is feasible, or asks for integration scoping, a fit-gap assessment or a field mapping. Use it even for informal asks ("can we integrate with this?", "how would new hires map to their API?") and partial specs.
Use this skill whenever you are about to create ANY chart, graph, plot, dashboard, or data visualization, in ANY output medium (HTML/React artifact, inline SVG, matplotlib/plotly/d3/Recharts, PNG). Read it BEFORE writing the first line of chart code, choosing chart colors, building a stat tile / KPI row, or laying out a dashboard. Teaches a design-system-agnostic method - form heuristic, color formula with a runnable validator, mark specs, interaction rules. Default palette in references/palette.md.
The transformation / before-after content format — structure a credible, honest, satisfying transformation (fitness, beauty, business results, skill progress, makeovers, client glow-ups, product before/after). Use when someone wants a before/after, a transformation post, a client-results reveal, a progress/journey story, or a makeover. Most powerful format AND most abused/distrusted — honesty is the edge; FTC enforcement is live. Uses the SHIFT framework. Reads brand-profile + social-proof-and-testimonials (consent + FTC substantiation) + short-form-video-script first. Agent structures + specs; human/tool produces the real media; WoopSocial publishes. Never stages/exaggerates the before, hides aids, cherry-picks, or fabricates a result; "results not typical" alone is insufficient — disclose the actual typical result; consent + YMYL required. Distinct from social-proof-and-testimonials, short-form-video- script, infographic-and-data-viz, and storytelling-and-narrative.
Safe GitHub Issues read/write via gh — labels, related-issue discovery, blockers. Specs stay on GitHub.
Cria o PRD (Product Requirements Document) em docs/prd.md guiando o processo de elicitação de requisitos de forma interativa e estruturada. Use esta skill sempre que o usuário quiser documentar os requisitos de um projeto ou feature, escrever o PRD, definir goals, functional/non-functional requirements, UI goals, technical assumptions e a lista de SPECs de alto nível. Acione após uma sessão de grill-me com entendimento estabelecido, ou quando o usuário disser "cria o PRD", "documenta os requisitos", "vamos escrever o PRD", "quero o PRD" ou qualquer variação. Também acione quando um novo projeto ou feature precisa ser formalizado em documento antes de partir para arquitetura ou código. NÃO detalha as SPECs — cada SPEC é uma spec, detalhada depois por to-spec e quebrada em tickets por to-tickets.
Draws product-design figures and one-page readouts, dashboards and status updates as text with block (░▒▓█) and box-drawing characters - research and survey results, funnels and A/B tests, UX flows and state machines, roadmaps, screen wireframes, design-system docs, handoff and QA checklists, motion specs and moving diagrams. Use for an ASCII or Unicode diagram, text wireframe, sparkline or bar chart in Markdown, a PR, a ticket or a doc; a design review deck; a report or audit as a PDF; or turning a text wireframe into an HTML prototype or components from the project's design system. Draws from a small JSON spec with real, sourced data and exports Markdown, MDX, HTML, SVG, PNG and PDF.
The Instagram Reels publish-mechanics skill -- distinct from reels-script (the script), instagram-seo (the keyword caption), and platform-specs-and-validation (cross-platform validation). Use when someone has a finished Reel and needs to publish it correctly: specs, cover, safe zone, publish settings. It gets the Reel OUT the way Instagram displays it: 9:16 spec-clean video, the safe zone that survives the feed and profile-grid crops, a custom grid-safe cover (chosen before publish, can't edit after), the keyword caption, and audio. Uses the FRAME framework. Reads brand-profile + the Reel asset first. The agent specs the publish settings, cover brief, and specs/safe-zone checklist, and advises audio/tags. WoopSocial publishes postType REEL + video + caption + cover on a schedule; trending audio, Share-to-Feed, tags, and Reel Insights stay native/in-app; the video/cover come from other tools. Remove other-platform watermarks; metrics never fabricated.