SkillMedev
- 361 skills
- 0 followers
- 1 day ago last updated
- ▌ Resume Writer · skillmedevBuilds an ATS-optimized resume from scratch or raw career notes, then exports a clean .docx. Use when someone needs to write or rebuild a resume.
- ▌ Resume Reviewer · skillmedevCritiques an existing resume against a scored rubric, rewrites the weakest bullets, runs a keyword gap analysis, and exports a .docx review. Use when someone wants honest feedback on a resume they already have.
- ▌ Trend Educator · skillmedevTurns a raw Instagram trend-scout report into a plain-language briefing that teaches WHY each trend is working - the algorithm mechanics, audience psychology, and format dynamics behind it - and surfaces specific opportunity angles as a screenshot-ready trend card. Use when someone asks "explain these trends to me", "why is this format blowing up", "turn this trend report into a briefing", or has instagram-trend-scout output and needs to understand it before creating. Do NOT use to gather the trend data itself - use instagram-trend-scout instead; do NOT use to draft the actual post - use instagram-post-builder instead; do NOT use for statistical trend detection in business or product data - use trend-analysis instead.
- ▌ Instagram Trend Scout · skillmedevResearches what is currently working on Instagram for a niche using web search only - no API or login - and returns a structured scouting report of top content, winning Reel and carousel formats, reusable hook patterns, content gaps, and an engagement benchmark with honest confidence labels. Use when someone asks "what's trending on Instagram for my niche", "scout Reels formats for home baristas", "what hooks are working right now", or is starting a weekly content cycle and wants signals before creating. Do NOT use for explaining why trends work in plain language - use trend-educator instead; for drafting the actual post, use instagram-post-builder.
- ▌ Instagram Post Builder · skillmedevInteractively builds a complete, copy-paste-ready Instagram post package - three hook variants using distinct patterns, a caption body, one clear CTA, a 15-20 hashtag set across reach tiers, alt text, and a visual direction with shot list or slide breakdown - through a one-question-at-a-time interview, optionally grounded in a trend-educator briefing. Use when someone says "write an Instagram post for my launch", "build the full post package for this reel", "put together a carousel with hooks and hashtags", or reaches the build stage after trend-educator. Do NOT use for finding what is trending - use instagram-trend-scout instead; for a single caption without the full package - use social-caption-writer; for planning a month of content - use social-content-calendar.
- ▌ Regulatory Scanner · skillmedevMaps which regulations apply to a product or business across every operating jurisdiction, translates them into concrete obligations, and produces a prioritized compliance-gap table. Use when someone asks "what regulations apply to my product", "are we GDPR or CCPA exposed", "run a compliance gap analysis", or is entering a new market or handling a new data type. Do NOT use for drafting the legal documents themselves - use terms-of-service instead. Do NOT use for assembling SOC 2 audit evidence - use soc2-evidence-helper instead. Do NOT use for patent landscape questions - use patent-prior-art instead.
- ▌ Terms Of Service · skillmedevDrafts plain-English Terms of Service and Privacy Policies for SaaS products using a clause-by-clause checklist, flagging every business decision and lawyer-review item explicitly. Use when someone asks "write terms of service for my app", "I need a privacy policy", "draft my ToS", "what sections does a SaaS ToS need", or is preparing legal pages before launch. Do NOT use for employee offer letters, NDAs, or employment agreements - use employment-contract instead. Do NOT use for assessing which regulations apply to a product or market - use regulatory-scan instead.
- ▌ Employment Contract Review · skillmedevReviews an employment agreement clause by clause, flags deviations from market-standard terms - non-compete scope, IP assignment breadth, cause definitions, equity mechanics - and produces a review table with recommended asks, explicitly bounded as not legal advice. Use when someone asks "can you review my offer letter", "is this non-compete normal", "what does this IP assignment clause mean", "should I push back on this severance term", or has an employment agreement in hand before signing. Do NOT use for negotiating the compensation number itself - use salary-negotiation instead - or for drafting a company's terms of service or privacy policy - use terms-of-service instead.
- ▌ Linear Workflow · skillmedevConfigures a Linear team end to end - team structure, minimal workflow states, cycles, a small label taxonomy, a daily triage rotation, and priority SLAs with breach views. Use when someone asks "set up Linear for my team", "how should we structure teams and labels in Linear", "our Linear backlog is a mess", or "how do we handle inbound bugs in Linear". Do NOT use for writing the tickets themselves - acceptance criteria, story points, Definition of Ready - use jira-ticket-writer instead (its ticket anatomy applies to Linear issues too). For deciding sprint scope and capacity, use sprint-planning.
- ▌ Notion Database Designer · skillmedevDesigns Notion databases that scale - one entity per database, deliberate property types, two-way relations with rollups, audience-specific views, and row templates - with explicit decision rules for relation vs rollup vs formula. Use when someone asks "design a Notion database for my projects", "should this be a relation or a rollup", "my Notion workspace is a junk drawer", or "set up a tasks and projects system in Notion". Do NOT use for building a full personal knowledge-management method with capture and review habits - use second-brain instead. For SQL or application database schemas, use database-schema.
- ▌ Jira Ticket Writer · skillmedevWrites ready-to-build Jira stories with user-story summaries, Given/When/Then acceptance criteria, subtasks, and story-point guidance, checked against INVEST and a Definition of Ready. Use when someone asks "write a Jira ticket for this", "turn these meeting notes into a story", "are these acceptance criteria testable", "should I split this story", or "how many points is this". Do NOT use for configuring Linear teams, cycles, labels, or triage workflows - use linear-workflow instead. For deciding what fits in the sprint, use sprint-planning.
- ▌ Remotion Setup · skillmedevScaffolds a new Remotion video project wired for Claude Code Agent Skills - Node check, create-video scaffold, skills install, folder conventions, Google Fonts, and a smoke-test render. Use whenever someone wants to start making videos with Remotion and Claude, even just "make product videos with Claude."
- ▌ Remotion Render · skillmedevRenders a Remotion composition to MP4 and runs the edit-and-re-render loop - CLI render commands, 1080p/4K/9:16 presets, concurrency tuning, codec selection, batch variants from a JSON data file, and Lambda for cloud rendering. Use when someone says "render this Remotion video", "export the composition to MP4", "the animation is too fast, fix and re-render", "batch render one video per customer", or "move rendering to Lambda". Do NOT use for authoring or restructuring scenes, animations, or components - use remotion-compose instead; do NOT use for project scaffolding and initial setup - use remotion-setup instead. This skill owns everything from a finished composition to a delivered file.
- ▌ Remotion Compose · skillmedevTurns a natural-language video brief into a complete, ready-to-preview Remotion composition - extracts duration, scenes, brand colors, aspect ratio, and real copy; plans the frame budget; and writes data-driven React/TypeScript using useCurrentFrame, interpolate, spring, AbsoluteFill, and Sequence, registered in Root.tsx. Use when someone says "build a 20-second product demo video", "animate a feature walkthrough", "write the Remotion code for this marketing clip", or wants a scene-by-scene composition they can scrub in Studio. Do NOT use for rendering, iterating, or batching the finished MP4 - use remotion-render instead - or for installing and scaffolding the project - use remotion-setup instead.
- ▌ Technical Spec Writer · skillmedevWrites engineering design docs and RFCs that align a team before code - TL;DR, background, goals and explicit non-goals, quantified requirements, a concrete end-to-end design with failure modes, alternatives considered, rollout plan, and open questions surfaced at the top for reviewers. Use when an engineer asks "write a design doc for this feature", "turn my approach into an RFC", "reviewers keep asking why didn't you just X", or a project needs alignment before implementation. Do NOT use for designing the API contract itself - use api-design instead; for user-facing product documentation, use help-documentation.
- ▌ Product Roadmap · skillmedevTurns product strategy into a themed Now/Next/Later roadmap with explicit trade-offs, confidence levels, and no committed dates beyond one quarter. Use when someone asks "build our product roadmap", "turn these priorities into a roadmap", "execs want committed ship dates for next year", or needs to communicate direction without over-promising. Do NOT use for company-wide annual operating plans - use annual-plan instead; for defining the goals a roadmap serves, use okr-builder; for scheduling work inside a sprint, use sprint-planning.
- ▌ Sprint Planning · skillmedevFacilitates sprint planning end to end - backlog refinement checks against a Definition of Ready, a one-sentence sprint goal, capacity math from velocity and PTO, story selection and team commitment, task breakdown, and flagged risks with owners. Use when a team asks "plan our next sprint", "how much should we commit to", "write a sprint goal", or keeps blowing sprint forecasts. Do NOT use for running the retrospective after the sprint ends - use sprint-retro-facilitator instead.
- ▌ User Flow Mapper · skillmedevMaps a feature's complete user flow in text notation - happy path first, then decision branches, error and empty states with recovery, edge cases, and re-engagement - and flags the top risks before design or build. Use when someone asks "map the user flow for onboarding", "what error states are we missing", "diagram the signup flow", or is scoping any multi-step feature. Do NOT use for screen-level interaction and component behavior specs - use prototype-spec instead; for cross-channel customer stages spanning weeks or months, use lifecycle-journey-map.
- ▌ Data Storyteller · skillmedevTurns data and charts into a decision-driving narrative structured as headline finding, trend, implication, and recommended action - with finding-led chart titles, context for every number, annotation guidance, and honest flags on any conclusion the data cannot support. Use when someone says "turn these numbers into a story", "what's the takeaway from this data", "help me present these results to leadership", or has charts but no narrative. Do NOT use for compressing a long document into a one-pager - use executive-summary instead - or for running the analysis that produces the findings - use eda-playbook instead.
- ▌ Power Bi Dax · skillmedevWrites correct, fast DAX measures with proper filter context, time intelligence on a marked date table, and VertiPaq-friendly patterns, diagnosing slow visuals down to the storage-vs-formula engine split. Use when someone asks "why does my DAX measure return the wrong total", "write a YTD or year-over-year measure", "my Power BI report is slow", "CALCULATE isn't doing what I expect", or "measure vs calculated column". Do NOT use for Tableau calculated fields and dashboard design - use tableau-best-practices instead; for writing warehouse SQL and turning query results into findings - use sql-to-insights instead; for Excel or Google Sheets financial models - use spreadsheet-model-builder instead.
- ▌ SQL To Insights · skillmedevTurns SQL query results into a decision-ready business narrative - headline finding, drivers, recommendation - plus the right chart choice for the data shape. Use when someone asks "what does this data actually mean", "summarize these query results for the exec team", "what chart should I use for this", or pastes a result set and wants the so-what for a non-technical audience. Do NOT use to diagnose or speed up the query itself - use sql-query-optimizer instead; do NOT use to build a full multi-part narrative presentation around an analysis - use data-story instead; do NOT use for open-ended exploration of an unfamiliar dataset - use eda-playbook instead.
- ▌ Tableau Best Practices · skillmedevBuilds Tableau dashboards that compute correct numbers at the right grain and stay fast - LOD expressions, filter-order pipeline, extract strategy, and mark-count control. Use when someone asks "why is my Tableau number different from SQL", "FIXED vs INCLUDE vs EXCLUDE", "my dashboard takes 30 seconds to load", "table calc or LOD", or is designing a workbook others will consume. Do NOT use for Power BI or DAX measures - use power-bi-dax instead; for narrative presentation of findings use data-story; for KPI selection and review cadence use kpi-scoreboard-and-cadence; for static table layout and formatting use data-table-design.
- ▌ Icon System · skillmedevDesigns or audits an icon set so every glyph shares one grid, stroke weight, corner language, naming convention, and export pipeline, and delivers the written icon spec engineering builds against. Use when someone asks "our icons look inconsistent", "set up an icon grid", "how should we name icons", "audit this icon set", "prep our SVGs for handoff", or is commissioning new icons and needs the rules first. Do NOT use for a single logo mark - use logo-brief-writer instead; for delivering full design specs beyond icons, use design-handoff-doc.
- ▌ Prototype Spec · skillmedevTurns a static design into a numbered, testable, dev-ready specification covering every state, interaction, breakpoint, motion detail, and edge case the mockup cannot show. Use when someone asks "write the spec for this screen", "engineering keeps asking what happens when", "document the interactions before handoff", "what states does this component need", or a build came back wrong because behavior was never written down. Do NOT use for the motion token details themselves - use motion-spec instead; for verifying a finished build against the spec, use design-qa-checklist.
- ▌ Animation System · skillmedevBuilds a coherent UI motion system - a duration token scale, named easing curves, choreography rules, and a per-component mapping - so every transition in the product draws from one vocabulary instead of ad-hoc values. Use when someone asks "define our motion tokens", "our animations feel inconsistent", "what duration should this modal use", "set up easing standards", or is starting a design system and needs the motion layer. Do NOT use to spec the motion of one specific component or flow - use motion-spec instead; for animated type treatments, use kinetic-typography.
- ▌ Color Accessibility · skillmedevAudits and repairs color palettes against WCAG contrast thresholds - 4.5:1 for body text, 3:1 for large text and UI components, 7:1 for AAA - and makes them safe for color-blind users, delivering a verified pairing table. Use when someone asks "does this color pass contrast", "make my brand color accessible", "is this palette color-blind safe", "why did my contrast check fail", or is remediating color findings from an audit. Do NOT use to invent a brand palette from scratch - use color-palette-builder instead; for a full accessibility review beyond color, use accessibility-audit.
- ▌ Tdd Expert · skillmedevDrive development with strict Red-Green-Refactor discipline - write one failing test, write the minimum code to pass it, refactor on green - including test-list planning and a worked kata cycle. Use when someone asks "write this test-first", "do TDD on this feature", "help me practice red-green-refactor", "write a failing test for this bug", or wants tests to drive a new module's design. Do NOT use for adding tests to existing untested legacy code before a refactor - use characterization-test-writer instead - or for designing shared fixtures and factories - use test-data-builder instead.
- ▌ Typescript Strict Mode · skillmedevWrite and review TypeScript as if strict mode plus the hardening flags (noUncheckedIndexedAccess, exactOptionalPropertyTypes) are enforced, and migrate loose codebases to full strictness flag by flag without breaking the build. Use when someone asks "how do I get rid of any", "turn on strict mode in an existing project", "is this type assertion safe", "why does tsc say possibly undefined", or when writing new TypeScript that must pass a strict compiler. Do NOT use for migrating between language or runtime versions - use language-version-migrator instead.
- ▌ Changelog Generator · skillmedevGenerate or update a repository CHANGELOG.md in Keep a Changelog format from git history - grouping commits since the last tag into Added/Changed/Deprecated/Removed/Fixed/Security, rewriting them as user-facing entries, and recommending the semantic version bump. Use when someone asks "generate a changelog from the git log", "update CHANGELOG.md for this release", "what version bump does this release need", or "turn these commits into release notes". Do NOT use for writing benefit-first product announcement changelogs for end users from release notes - use changelog-writer instead; this skill produces the versioned CHANGELOG.md file that lives in the repo.
- ▌ Code Review Checklist · skillmedevRun a systematic multi-pass code review - correctness, design, security, performance, tests - and report findings ordered by severity with concrete, respectful suggestions. Use when someone asks "review this PR", "review this diff", "what's wrong with this change", or wants a pre-merge quality gate on a branch. Do NOT use for a security-only deep audit of a change - use secure-code-review instead - or for writing the ticket or tracking artifact that describes the change - use jira-ticket-writer instead.
- ▌ Ghostwriter · skillmedevAnalyzes an author's writing samples, builds an explicit quantified voice profile, and produces new content indistinguishable from the author's own hand. Use when someone asks "write this in my voice", "ghostwrite my newsletter", "make this sound like me", "draft the next chapter the way I would write it", or supplies writing samples plus a brief for a new piece. Do NOT use for drafting a persuasive opinion piece to pitch to a publication - use op-ed-writer instead. Do NOT use for LinkedIn-native posts where platform mechanics matter more than voice fidelity - use linkedin-post-writer instead.
- ▌ Manuscript Reviser · skillmedevUse when revising fiction prose that ALREADY EXISTS - a second/third-draft pass on a chapter or scene, a continuity or POV-consistency check, fixing a scene that drags, cutting dead weight, or tightening overwritten prose at the line level. Do NOT use to draft a brand-new scene from nothing (use Fiction Scene Writer), to build or mimic an author's voice (use Ghostwriter), or for neutral encyclopedic prose (use Wikipedia Style Writer); to outline or re-architect the plot at the beat level, use Story Structure Architect.
- ▌ Fiction Scene Writer · skillmedevWrites individual fiction scenes with goal-conflict-turn structure, sensory grounding, interiority, and subtext-driven dialogue - then notes the turn accomplished and one craft choice so the writer can learn from it. Use when someone asks "write this scene for my novel", "my dialogue feels flat", "make this moment more immersive", or has plot beats that need dramatizing on the page. Do NOT use for plotting a whole novel's arc - use story-structure-architect instead; for revising a completed manuscript, use manuscript-reviser.
- ▌ Story Structure Architect · skillmedevUse when plotting or outlining a novel or screenplay, structuring its acts/chapters/sequences, fixing a sagging middle or broken pacing, mapping a character arc onto plot beats, planting setups and their payoffs, or deciding scene order. Produces the macro architecture - arc, beat sheet, tension curve - not prose. Do NOT use to write the actual prose of a scene (use Fiction Scene Writer, which sits downstream of this), to establish or mimic a narrative VOICE (use Ghostwriter), or to write a non-fiction book proposal or pitch (use Book Proposal).
- ▌ Stock Photo Apis · skillmedevIntegrates the Unsplash, Pexels, and Pixabay APIs in code - auth, search endpoints, rate limits, attribution, hotlinking versus caching rules, and the compliance obligations that get apps deactivated when skipped. Use when someone says "integrate the Unsplash API", "pull images from Pexels in my app", "build an image picker on a stock photo API", "how do I trigger the Unsplash download endpoint", or is wiring stock imagery into a CMS, blog pipeline, or placeholder service. Do NOT use to choose a source by hand or write a search brief - use stock-photo-finder instead; do NOT use to decide whether a license permits a use or a release is needed - use image-license-rights instead; do NOT use to art-direct results - use visual-asset-curation instead.
- ▌ Find The Right Stock Photo · skillmedevSource the right stock photograph for a brief by picking the best library and crafting the search. Use when you need a real photo or image for a hero, blog post, ad, slide, mockup, social post, or thumbnail and you are not sure where to look or what to search, or when someone says "find me a photo of...", "where do I get images for this", "I need a hero image", or "good free stock photos for X". It covers free libraries (Unsplash, Pexels, Pixabay), curated and boutique sources (Stocksy, Stills, Death to Stock), broad paid catalogs (Adobe Stock, Shutterstock, iStock), and editorial archives (Getty, AP, Reuters). Do NOT use to decide whether a license actually permits your use or whether you need a release -> use image-license-rights; do NOT use to fetch images programmatically in code -> use stock-photo-api; do NOT use to art-direct a cohesive set or fix a cliched look -> use visual-asset-curation.
- ▌ Image License Usage Rights · skillmedevDecides whether a specific image use is legally permitted, what the license obligates, and whether a model or property release is required - covering CC0 and Creative Commons variants, Unsplash/Pexels/Pixabay terms, royalty-free vs rights-managed, standard vs extended tiers, editorial-use-only, and AI-image caveats - and delivers a per-image license record. Use when someone asks "is this free for commercial use", "do I need to credit the photographer", "can I put this on merchandise", "what is royalty-free vs rights-managed", "is editorial-use-only a problem", or "do I need a model release", or is about to publish, advertise, or sell anything containing a stock image. Do NOT use to find or search for a photo - use stock-photo-finder instead; do NOT use to fetch images via an API with attribution rules - use stock-photo-api instead.
- ▌ Visual Asset Curation · skillmedevArt-direct a set of stock images so they look intentional and on-brand instead of like stock, and choose and sequence the final picks. Use when you have candidate images and need to decide which ones, in what order, and why a set "looks cheap" or "like stock", or when someone says "these don't feel cohesive", "make this look less like stock photos", "pick the best images for this page", or "why does this look generic". It covers spotting the stock-cliche tells, defining a visual system (palette, light, tone, angle), curating a set to consistency, choosing compositions that hold text overlays, and a color-grade pass to unify a mismatched set. Do NOT use to find or search for images -> use stock-photo-finder; do NOT use to check licensing or releases -> use image-license-rights; do NOT use to fetch images via an API -> use stock-photo-api.
- ▌ Content Brief · skillmedevBuilds an SEO content brief a writer can execute without guesswork - primary and semantic keywords, search intent, recommended format matched to the SERP, title, H1, meta description, a full H2/H3 outline, word-count guidance derived from ranking pages, internal links with anchors, featured-snippet opportunities, CTA, and the content gap competitors miss. Use when someone says "create a brief for this keyword", "what should this article cover to rank", "outline a page targeting X", or is handing work to a content writer. Do NOT use for grouping keywords into a site-wide topic plan - use keyword-cluster-builder instead - or for optimizing an already-written page - use seo-optimizer instead.
- ▌ Case Study Builder · skillmedevTurn a customer win into a credible case study - interview-driven raw material, a challenge-solution-results arc, and a quantified results section with real customer quotes. Use when someone asks "write a case study from this customer call", "turn this win into a customer story", "what should I ask the customer in the interview", or "make our results section stronger". Do NOT use for collecting short standalone quotes or review snippets - testimonial capture is upstream raw material for this skill. Do NOT use for packaging finished case studies into battlecards and sales collateral - use sales-enablement-kit instead.
- ▌ Email Newsletter Pro · skillmedevWrite recurring email newsletters - subject lines that earn the open, preview text that extends them, a body structure readers finish, and cadence rules that keep the list healthy. Use when someone asks "write my newsletter", "give me subject line options", "why is my open rate dropping", "should I send weekly or monthly", or "help me structure this issue". Do NOT use for automated onboarding or behavior-triggered sequences - use email-drip-builder instead. Do NOT use for inbox placement and spam-folder problems - use email-deliverability instead.
- ▌ Tweet Thread Builder · skillmedevTurn one idea into a tight tweet thread - a hook that earns the click, one beat per post, and momentum to a single CTA. Use when someone asks "turn this into a thread", "write a thread about my launch", "why did my thread flop", or "give me hook options for this". Do NOT use for LinkedIn-format posts - use linkedin-post-writer instead. Do NOT use for adapting one finished piece across many platforms - use content-repurposing instead.
- ▌ Testimonial Capture Interview · skillmedevRuns customer interviews engineered to produce usable testimonials and case-study raw material - a question sequence that elicits before/after specifics and real numbers, a permission and approval workflow, quote-editing ethics (tighten but never fabricate), and a soundbite extraction procedure. Use when a user says "get a testimonial from this customer", "interview our customer for a case study", "our testimonials are all vague praise, help me get better ones", "draft interview questions for a customer success story", or "can I edit this customer quote". Do NOT use for turning the raw material into the finished case study - use case-study-builder instead - or for research interviews with subject-matter experts where the goal is learning, not marketing material - use expert-interview instead.
- ▌ Pandas Expert · skillmedevWrites correct, vectorized pandas for cleaning, joining, reshaping, and aggregating tabular data, with validated joins and deliberate dtype and missing-data handling. Use when someone asks "why did my merge duplicate rows", "how do I clean this CSV in pandas", "my groupby numbers look wrong", "this apply is too slow", or is transforming a DataFrame for analysis or a pipeline. Do NOT use for first-pass profiling of an unfamiliar dataset - use eda-playbook instead; for data too large for one machine use spark-jobs; for answering business questions directly in SQL use sql-to-insights.
- ▌ Funnel Analysis · skillmedevBuilds conversion funnels from raw event data with drop-off attribution, segment comparison, and significance testing, and delivers a filled funnel table with a diagnosed bottleneck and next action. Use when someone asks "where are users dropping off", "why did checkout conversion fall this week", "build a signup-to-activation funnel", or "is mobile converting worse than desktop". Do NOT use for rewriting page copy or layout to lift a known weak step - use landing-page-cro instead; for decomposing active-user growth into new, retained, resurrected, and churned - use growth-accounting instead; for choosing which events to instrument and which product metrics to track - use product-analytics instead; for designing and reading a controlled experiment - use ab-test-analyzer instead.
- ▌ A B Test Analyzer · skillmedevAnalyzes an A/B experiment to a defensible verdict - sample-size and minimum-detectable-effect math, two-proportion significance testing with confidence intervals, and checks for the traps that fake a win (peeking, sample ratio mismatch, multiple comparisons). Use when someone asks "is this test significant", "did variant B win", "how long should I run this experiment", "what sample size do I need", or shows experiment results and asks whether to ship. Do NOT use for logging and organizing ML training runs - use experiment-tracking instead; for causal questions without a randomized experiment use causal-inference; for general funnel or metric investigation use funnel-analysis or product-analytics.
- ▌ Revenue Modeling · skillmedevBuilds SaaS revenue models - a reconciling MRR/ARR bridge, cohort retention forecasting, a driver tree from leads to new ARR, and base/upside/downside scenarios. Use when someone asks "model my ARR for next year", "what will MRR be if churn doubles", "build a revenue forecast for the board", "why doesn't my MRR bridge tie out", or "what NRR do we need to hit our plan". Do NOT use for sizing the market opportunity - use market-sizing instead; for CAC, LTV, and payback analysis use unit-economics; for a full P&L or headcount-driven operating model use fpa-model; for cash timing and runway use cash-flow-forecast.
- ▌ Customer Analytics · skillmedevTurns transaction data into cohort retention, lifetime value, RFM segments, and churn predictions tied to concrete actions. Use when someone asks "what's our customer LTV", "build a cohort retention table", "which customers are about to churn", "how do repeat purchase rates look by cohort", or "who should we target with a win-back offer". Do NOT use for event-level product usage and feature adoption analysis - use product-analytics instead; for defining market segments for positioning and messaging - use segmentation-strategy instead; for designing the interventions that reduce churn once at-risk customers are identified - use churn-reduction instead; for step-by-step conversion drop-off - use funnel-analysis instead.
- ▌ Motion Spec · skillmedevSpecifies animation and motion precisely - duration, easing curve, trigger, and intent - for accurate engineer implementation. Use when handing off transitions, micro-interactions, or loading states.
- ▌ Responsive Spec · skillmedevSpecifies responsive behavior across breakpoints - layout reflow, content priority, touch targets, and fluid-versus-stepped scaling rules - precisely enough for engineers to implement directly. Use when someone asks "how should this work on mobile", "spec the breakpoints", "write the responsive rules for this page", or is adapting a single-viewport design for multi-device use. Do NOT use for static measurements inside one frame - use redline-annotation instead; for the overall handoff package with flows and edge cases, use design-handoff-doc.
- ▌ Design Handoff Doc · skillmedevWrites a complete design handoff document covering components, design tokens, interaction states, and edge cases for engineering implementation. Use when handing off a feature or screen to developers.
- ▌ Redline Annotation · skillmedevProduces precise redline annotations - spacing, sizing, type, color, radius, z-order, and behavior notes in a consistent, scannable notation - that engineers can build from without asking questions. Use when someone asks "redline this screen", "spec this component", "annotate the spacing for handoff", or is preparing design files for development. Do NOT use for the overall handoff document with flows, edge cases, and acceptance criteria - use design-handoff-doc instead; for animation timing and easing, use motion-spec; for breakpoint behavior, use responsive-spec.
- ▌ Design QA Checklist · skillmedevRuns an ordered design QA pass over an implemented UI - layout, type, color, states, motion, content - against the design spec, with concrete tolerances and a filed defect list. Use when someone asks "QA this build against the designs", "does the implementation match Figma", "is this ready for design sign-off", or before releasing a UI change. Do NOT use for critiquing the design itself - use design-critique instead; for a full WCAG conformance audit, use accessibility-audit; for writing the spec the build is checked against, use design-handoff-doc.
- ▌ Market Sizing · skillmedevBuilds a defensible TAM/SAM/SOM market-sizing model with bottom-up and top-down triangulation and a low/base/high sensitivity range. Use when someone asks "how big is the market", "calculate my TAM", "size this opportunity", is preparing an investor deck market slide, or needs to defend a market number under diligence. Do NOT use for revenue projections of an existing business - use revenue-modeling instead.
- ▌ Pricing Strategy · skillmedevSet or revise pricing for any product by triangulating value, competition, and cost floor into a recommended structure, price points, and a test plan. Use when someone asks "what should I charge", "how do I price my product", "are we priced too low", "should we go usage-based or flat", or is preparing a repricing or a new-product launch. Do NOT use for designing SaaS tier ladders, value metrics, and expansion packaging in detail - use saas-pricing instead; for gym front-end offers and guarantees use gym-pricing-and-guarantees; for checking whether the resulting price produces healthy CAC payback use unit-economics.
- ▌ Landing Page Copy · skillmedevWrite landing-page copy section by section - hero, social proof, features-as-benefits, objections, CTA - leading with one promise and proving it down the page. Use when someone asks "write my landing page", "improve my hero headline", "what should the homepage say", "turn these features into benefits", or is shipping a new page for a launch or campaign. Do NOT use for testing and optimizing an existing page's conversion rate - use landing-page-cro instead; for the one-line claim itself use positioning-statement; for the full message ladder use messaging-hierarchy.
- ▌ Go To Market Planner · skillmedevBuild a sequenced go-to-market plan - beachhead ICP, positioning, one or two channels, and dated milestones - instead of a scattershot launch. Use when someone asks "how do I take this to market", "what's my GTM strategy", "which channel should I start with", "who should I sell to first", or is planning a new product or a new market entry. Do NOT use for the dated launch-week timeline and asset checklist - use launch-plan-sequencer instead; for Product Hunt copy and day-of tactics use product-hunt-launch; for deep persona research use icp-persona-builder.
- ▌ Competitive Intelligence · skillmedevMap competitors across positioning, product, pricing, proof, and weaknesses, then turn the research into sales-ready battlecards with an update cadence. Use when someone asks "what are our competitors doing", "build a battlecard", "how do we compare to X", "why are we losing deals to X", or before a pricing or positioning decision. Do NOT use for designing long-term defensibility strategy - use competitive-moat instead; for a public comparison landing page use comparison-page-builder; for rep-facing objection scripts beyond the battlecard use objection-handler.
- ▌ Vc Pitch Email · skillmedevWrites cold investor outreach under 100 words - a subject line built on the company's strongest verifiable metric, a personalized why-them opening line, traction before the ask, and a low-friction meeting request - delivered as three subject options, the email body with word count, and a follow-up line for five days later. Use when a founder asks "write a cold email to this VC", "how do I get an investor meeting", "pitch my seed round over email", or is starting investor outreach. Do NOT use for choosing which investors to contact - use investor-targeting instead - or for post-investment monthly updates - use investor-update-writer instead - or for non-investor sales outreach - use cold-email-craft instead.
- ▌ Series A Readiness · skillmedevAudits whether a seed-stage company clears the Series A bar - benchmark metrics, narrative, team, and data room - and produces a red/yellow/green readiness scorecard with a 90-day gap-closing plan. Use when a founder asks "am I ready for Series A", "what metrics do I need to raise an A", "what goes in a Series A data room", "should I raise now or wait two quarters", or is deciding when to open an A process. Do NOT use for a general pre-pitch hygiene check at any stage - use fundraise-readiness-audit instead - or for choosing which round to raise at all - use fundraising-stage-selector instead.
- ▌ Term Sheet Explainer · skillmedevDecodes every clause of a VC term sheet into plain English, marks each term founder-favorable, market-standard, or investor-favorable, and flags deviations in priority order. Use when a founder asks "what does liquidation preference mean", "is this term sheet normal", "explain participating preferred", "what is the option pool shuffle", or receives a term sheet and needs to understand it before responding. Do NOT use for planning counters, trades, and negotiation strategy - use term-sheet-negotiation instead; do NOT use for choosing between a SAFE and a priced round - use safe-vs-priced-round instead.
- ▌ Fundraising Narrative · skillmedevBuilds the five-beat narrative spine - origin, insight, wedge, traction, vision - that answers why now, why you, and why this before any deck exists. Use when a founder says "help me craft my fundraising story", "investors don't get what we do", "what's our narrative for this round", or has metrics and a product but no story that survives a partner meeting. Do NOT use for turning the story into slides - use pitch-deck-builder instead; do NOT use for deciding stage, amount, or valuation - use fundraising-stage-selector instead.
- ▌ Investor Update Writer · skillmedevDrafts a monthly or quarterly investor update - TL;DR, consistent metric block (revenue, growth rate, burn, runway), highlights, honest lowlights, a specific ask, and next-period priorities - in a repeatable one-screen format. Use when someone asks "write my investor update", "what should go in my monthly update", "how do I tell investors about a bad month", or when a founder is due to report to their cap table. Do NOT use for updates to internal teams, executives, or non-investor stakeholders - use stakeholder-update instead. Do NOT use for crafting the fundraising story for new investors - use fundraising-narrative instead.
- ▌ Github Actions · skillmedevDesigns and hardens GitHub Actions CI/CD - pipelines that hit a sub-10-minute PR feedback budget through caching and parallelism, with least-privilege security and safe deploy gates. Use when someone asks "why is my CI so slow", "how do I cache node_modules properly", "set up a deploy workflow", "is pull_request_target safe here", or wants a workflow written or reviewed. Do NOT use for provisioning the cloud infrastructure the pipeline deploys to - use terraform-expert instead; do NOT use for Vercel-specific deploy flows - use vercel-deploy-pipeline instead; for secret storage policy beyond CI, use secrets-hygiene.
- ▌ Terraform Expert · skillmedevWrites safe, modular, idiomatic Terraform - remote state layout, module structure, plan-review discipline, version pinning, and blast-radius control. Use when someone asks "structure my Terraform repo", "how should I split state between environments", "terraform plan wants to destroy and recreate my database", "should I use count or for_each", or "how do I import existing infrastructure". Do NOT use for CI pipeline authoring in GitHub Actions - use github-actions instead; for Kubernetes manifests the infrastructure hosts, use kubernetes-basics; for managing app secrets outside IaC, use secrets-hygiene.
- ▌ Kubernetes Basics · skillmedevWrites production-ready Kubernetes manifests - Deployments with correct resource requests/limits, readiness/liveness/startup probes, PodDisruptionBudgets, safe rollouts, and graceful shutdown. Use when someone asks "write a Deployment for my service", "my pods keep getting OOMKilled", "why do I get 502s during deploys", "what should my resource limits be", or "why did my pod restart in a loop". Do NOT use for local multi-container development environments - use docker-compose-wizard instead; for CI/CD pipelines that deploy to the cluster, use github-actions; for the Terraform that provisions the cluster itself, use terraform-expert.
- ▌ Observability Stack · skillmedevInstruments systems with the three pillars - structured logs, RED/USE metrics, and distributed traces - correlated by one trace ID, with cardinality budgets and symptom-based alerts. Use when someone asks "how should I instrument this service", "what metrics should I emit", "why is my metrics bill exploding", "set up OpenTelemetry for my stack", or "we can't tell which service is slow". Do NOT use for tuning an existing noisy pager or alert thresholds - use alert-tuning instead; for defining SLO error-budget policy, use error-budget-policy; for the incident process when alerts fire, use sev-triage and postmortem-writer.
- ▌ Docker Compose Wizard · skillmedevProduces production-minded docker-compose configurations - pinned images, healthchecks with real intervals, health-gated startup ordering, named volumes, explicit networks, and env-file secrets - plus the matching .env.example. Use when someone asks "write a compose file for this stack", "why does my app start before the database is ready", "how do I add a healthcheck", "my compose setup works on my machine but not in CI", or is reviewing a docker-compose.yml before it ships. Do NOT use for orchestrating across multiple hosts or cluster workloads - use kubernetes-basics instead; for provisioning the underlying cloud infrastructure - use terraform-expert instead; for CI pipelines that build and push the images - use github-actions instead; for auditing how secrets are stored and rotated - use secrets-hygiene instead.
- ▌ Skill Tester · skillmedevEmpirically tests a skill with subagent scenarios to verify it fires on the right prompts, stays silent on the wrong ones, and performs its job when loaded. Use when validating a new or modified SKILL.md before publishing - "test this skill", "does this trigger correctly", "verify the skill works". Do NOT use to statically grade or rewrite skill quality (use skill-auditor) - this runs live behavioral tests.
- ▌ Skill Auditor · skillmedevUse when reviewing, grading, auditing, or improving a whole existing skill or pack - judging whether a skill is good, fixing one that misfires or won't activate, or driving one or many skills to a quality bar. Audits to an absolute A+ bar and hands back ship-ready SKILL.md rewrites, not a report the user must act on. Do NOT use when tightening only a description or trigger in isolation - use skill-description-writer instead; do NOT use when authoring a brand-new skill from scratch - use skill-creator instead.
- ▌
- ▌ Skill Pack Curator · skillmedevDesigns the membership and structure of a skill pack - persona, member selection, install sequence, cross-links, and what to add or cut. Use when someone asks "which skills should go in this skill pack", "design the membership of a new skill pack", "decide which skills to add or cut from a pack", or is turning a vertical (an industry or role) into a coherent bundle. Do NOT use to grade or rewrite a finished pack to a quality bar (use skill-auditor) - this designs composition.
- ▌ Skill Description Writer · skillmedevWrites the description field that makes a skill fire reliably - WHAT it does, WHEN to invoke it with quoted user phrasing, and what it is NOT for. Use when drafting or improving only the description or trigger of a SKILL.md or catalog entry - "this skill never fires", "fix this description", "write the frontmatter description". Do NOT use to author a whole skill (use skill-creator) or to grade/audit one (use skill-auditor).
- ▌ REST API Design · skillmedevDesigns REST API surfaces - resource naming, HTTP method and status-code semantics, error shapes, pagination, and filtering - and delivers an endpoint spec a consumer can build against without asking questions. Use when someone asks "how should I name this endpoint", "what status code should this return", "should this be PUT or PATCH", "how do I paginate this list", or is reviewing an API before it ships to external consumers. Do NOT use for planning breaking-change rollouts and deprecation windows - use api-versioning-strategist instead; for GraphQL type and resolver design - use graphql-schema instead; for generating client SDKs from an existing spec - use api-client-generator instead; for designing inbound webhook endpoints - use webhook-receiver-hardener instead.
- ▌ Process Documentation · skillmedevDocuments recurring processes as step-by-step SOPs with decision points, edge cases, and a named owner, so anyone can run the process correctly without asking. Use when someone asks "write an SOP for this", "document our onboarding process", "this only lives in one person's head", or wants to delegate a recurring task safely. Do NOT use for incident-response or on-call operational runbooks - use runbook-writer instead; for customer-facing product documentation, use help-documentation.
- ▌ Whitepaper Writer · skillmedevStructures and writes authoritative B2B whitepapers - a standalone executive summary, a data-sized problem statement, methodology, evidence-driven findings, recommendations, and a soft call to action - flagging every claim that needs a real citation. Use when a marketer asks "write a whitepaper on this topic", "turn our research into a lead-gen asset", "make this credible enough for executives", or a draft reads like a product pitch instead of analysis. Do NOT use for customer-story-driven proof - use case-study-builder instead; for policy audiences, use policy-brief.
- ▌ User Facing Changelog · skillmedevTranslates raw engineering release notes - commits, tickets, PR titles - into a user-facing changelog grouped as New, Improved, and Fixed, with a highlights section on top, benefit-first phrasing in the user's vocabulary, bugs described by their symptoms, and internal-only churn cut and flagged. Use when someone says "write the changelog for this release", "turn these commit messages into release notes users can read", "announce what shipped this week", or their changelog currently reads as internal jargon. Do NOT use for auto-generating a technical changelog from git history for developers - use changelog-generator instead.
- ▌ Help Documentation · skillmedevWrites user-facing help-center articles - verb-first how-to guides, symptom-organized troubleshooting pages, and FAQs - with one task per article, exact UI labels, and a stated success result. Use when someone asks "write a help article for...", "document how users reset their password", "turn these support tickets into a troubleshooting page", or "our help center articles are confusing, rewrite this one". Do NOT use for internal team procedures and SOPs - use process-doc instead; for on-call operational runbooks, use runbook-writer; for internal knowledge-base articles aimed at support agents, use kb-article-writer.
- ▌ Hiring Scorecard Builder · skillmedevBuilds structured interview scorecards tied to role-specific signals to reduce bias and improve calibration. Use when opening a new role or auditing an existing interview loop for consistency.
- ▌ Eng Status Rollup · skillmedevRolls up engineering team status into an exec-ready written update with exactly three sections - progress in outcomes, risks with likelihood and mitigation, and asks with owners and deadlines - scannable in under 90 seconds. Use when someone asks "write my weekly eng update", "summarize team status for leadership", "turn these standup notes into an exec update", or is prepping for a leadership sync. Do NOT use for updates to external or cross-functional stakeholders on a project - use stakeholder-update instead - for public incident communication - use status-page-update - or for monthly investor letters - use investor-update-writer instead.
- ▌ Team Health Check · skillmedevAssesses a team's health across three independent dimensions - delivery, morale, and clarity - using observable signals from the last 8 weeks, then maps each red or yellow signal to one manager action with a 2-week horizon. Use when a manager asks "is my team okay", "how do I tell if morale is slipping", "we keep missing sprints and I don't know why", or wants a quarterly team health review. Do NOT use for facilitating a single sprint retrospective - use sprint-retro-facilitator instead - for structuring individual 1:1s - use 1on1-agenda - or for defining how a new team works together - use team-charter instead.
- ▌ Tech Debt Prioritizer · skillmedevInventories tech debt and ranks it economically - scoring each item 1-3 on cost of delay (the interest rate) and leverage (the principal unblocked), multiplying into a priority index, and packaging the winners into a leadership proposal framed on business impact. Use when someone asks "which tech debt should we tackle first", "help me build a case for refactoring to leadership", "our backlog of debt is huge, where do we start", or is preparing quarterly planning. Do NOT use for finding and removing unused code - use dead-code-eliminator instead - for auditing third-party dependency risk - use dependency-risk-audit - or for planning the sprint the work lands in - use sprint-planning instead.
- ▌ Sprint Retro Facilitator · skillmedevStructures and facilitates sprint retrospectives with a timeboxed agenda, format selection, anti-blame ground rules, and owned action items that actually close. Use when someone asks "help me run our retro", "our retros produce the same actions every sprint", "what format should this retrospective use", or "how do I get the team to say what they're really thinking". Do NOT use for incident postmortems with a timeline and root-cause analysis - use postmortem-writer instead. For diagnosing chronic team dysfunction beyond one sprint, use team-health-check; for planning the next sprint's scope, use sprint-planning.
- ▌ Performance Review Writer · skillmedevWrites fair, specific, evidence-based performance reviews and ratings. Use when drafting or preparing for calibration to reduce recency bias and vague praise or criticism.
- ▌ Win Back Campaign · skillmedevDesigns segmented win-back email sequences for dormant users - dormancy tiers, a three-beat sequence with a single proportional incentive, and a suppression rule - and measures success by re-activation, not opens. Use when someone says "our users went quiet", "design a win-back campaign", "how do I re-engage lapsed customers", "should we email people who haven't logged in for months", or lifecycle messaging has stopped landing with a lapsed segment. Do NOT use for recovering an unfinished checkout - use abandoned-cart-sequence instead. Do NOT use for diagnosing and fixing why active customers cancel - use churn-reduction instead. Do NOT use for building always-on onboarding or nurture flows - use email-drip-builder instead.
- ▌ Email Drip Builder · skillmedevDesigns automated onboarding and activation drip sequences with behavior-gated sends, exit triggers on conversion, and per-email jobs and timing. Use when someone asks "build an onboarding email sequence", "design a drip campaign for new signups", "why isn't our onboarding flow activating users", or is extending an existing drip series. Do NOT use for recurring content newsletters - use email-newsletter-pro; for recovering abandoned checkouts use abandoned-cart-sequence; for re-engaging dormant users use win-back-campaign; for cold outreach to prospects use outreach-sequence-designer or cold-email-craft.
- ▌ Email Deliverability · skillmedevAudits and protects sender reputation and inbox placement for permissioned marketing and lifecycle email - SPF, DKIM, and DMARC authentication, domain warmup, bounce and complaint thresholds, and engagement sunsetting - and delivers a scored deliverability audit checklist with a remediation order. Use when someone asks "why are my newsletters going to spam", "how do I set up SPF, DKIM, and DMARC", "is my bounce rate too high", "should I send marketing from a subdomain", or is launching a new sending domain or auditing an existing opted-in email program. Do NOT use for cold outbound infrastructure - lookalike sending domains, mailbox pools, per-mailbox volume caps - use cold-email-deliverability instead; do NOT use to write the emails themselves - use email-drip-builder or email-newsletter-pro instead.
- ▌ Lifecycle Journey Map · skillmedevBuilds a customer lifecycle journey map with behavioral entry/exit criteria per stage, one goal and one signal per stage, message briefs, and dead-zone flags. Use when someone asks "map our customer lifecycle", "where are the gaps in our lifecycle emails", "what should we send at each stage", or is aligning a team on lifecycle messaging strategy. Do NOT use to write the actual email sequence - use email-drip-builder for onboarding drips, win-back-campaign for dormant users, or push-notification-copy for push messages; this skill produces the map those campaigns are built on.
- ▌ Segmentation Strategy · skillmedevBuilds a behavioral segmentation system for lifecycle messaging - RFM-based segments, event-driven membership triggers, one next action per segment, size audits, and send-time suppression rules. Use when someone asks "how should I segment my users", "our emails get ignored, who should get what", "how do I message at-risk users differently", or is personalizing lifecycle campaigns to cut unsubscribes and lift click-through. Do NOT use for building ad-platform audiences - use audience-targeting instead; for narrative customer personas use user-persona or icp-persona-builder; for mapping the full lifecycle stages and journeys use lifecycle-journey-map.
- ▌ Push Notification Copy · skillmedevWrites push and in-app notification copy that survives lock-screen truncation, ties every send to a user-specific trigger, deep-links to the exact destination, and respects frequency caps. Use when someone asks "write a push notification for this event", "why is our push opt-out rate rising", "draft re-engagement push copy", or is planning lifecycle, transactional, or re-engagement notifications. Do NOT use for implementing the delivery pipeline, tokens, or notification infrastructure - use push-notification-wirer instead; for deciding which lifecycle stage should send push at all, start with lifecycle-journey-map.
- ▌ Budget Pacing · skillmedevPaces and reallocates ad budget across channels through the month to hit both CAC and volume targets, with daily tolerance bands, a reallocation reserve, and escalation red lines. Use when someone asks "are we pacing to spend the budget", "we're overspending and it's only the 12th", "should I move budget from Meta to Google mid-month", "how do I spend the rest of the budget without wrecking CAC", or is managing live campaign spend at month start or month end. Do NOT use for explaining why last month's spend missed plan - use budget-vs-actual instead - or for auditing whether the channels themselves are worth funding - use paid-acquisition-audit instead.
- ▌ Landing Page Cro · skillmedevImproves an existing landing page's conversion rate through evidence-first CRO - audit heatmaps and recordings, write structured hypotheses, prioritize with ICE scoring, and run one-variable tests to statistical significance. Use when someone asks "why isn't my landing page converting", "audit this page before we scale spend", "which A/B test should we run first", or after a CVR drop or ahead of a paid-traffic push. Do NOT use for writing a new landing page from scratch - use landing-page-copy instead. Do NOT use for auditing the ad accounts sending the traffic - use paid-acquisition-audit instead. Do NOT use for reading the results of a finished experiment - use ab-test-analyzer instead.
- ▌ Audience Targeting · skillmedevBuilds and refines audience and segment targeting for paid campaigns - first-party audience construction, lookalike expansion, exclusion lists, platform sizing floors, and saturation diagnosis - and delivers a filled targeting matrix per campaign. Use when someone asks "who should I target with these ads", "why is my ad set stuck in learning", "my CPMs keep rising but conversions are flat", "should I use a 1% or 5% lookalike", or is launching a campaign, diagnosing poor reach quality, or expanding into a new customer segment. Do NOT use for auditing an entire paid program's structure and spend efficiency - use paid-acquisition-audit instead; do NOT use for defining the ideal customer profile itself - use icp-persona-builder instead; do NOT use for market segmentation strategy outside paid media - use segmentation-strategy instead.
- ▌ Ad Creative Testing · skillmedevDesigns a disciplined ad creative testing system with hooks, isolated variables, and statistical rigor. Use when setting up a testing pipeline or when creative performance is declining.
- ▌ Marketing Attribution · skillmedevGuides selection and honest application of a marketing attribution model, surfacing common measurement traps. Use when evaluating channel ROI, auditing tracking, or choosing between attribution models.
- ▌ Paid Acquisition Audit · skillmedevAudits paid acquisition channels for wasted spend and untapped scaling headroom - computing break-even ROAS from gross margin, flagging creative fatigue and saturation, and producing a ranked action list with a dollar impact per item. Use when someone asks "where is my ad budget being wasted", "should I scale this campaign", "why did ROAS drop", or is preparing a budget review or planning to increase paid spend. Do NOT use for designing new creative experiments - use ad-creative-testing instead; for assigning cross-channel conversion credit, use marketing-attribution.
- ▌ Vercel AI Gateway · skillmedevRoute every LLM call through one unified API on Vercel - plain "provider/model" strings via the AI SDK, automatic provider routing and model fallbacks, observability and per-key cost tracking, and zero data retention. Use when you ask "how do I add an LLM to my Vercel app", "route OpenAI and Anthropic through one API", "add model failover / fallback", "track LLM cost and spend on Vercel", "set a budget per API key", "switch providers without changing code", "AI_GATEWAY_API_KEY", or "stop installing @ai-sdk/openai and @ai-sdk/anthropic separately". Do NOT use for general AI SDK app code (chat UI, tool calling, structured output) - that is the AI SDK itself; do NOT use for deploy config, env wiring, or edge/runtime choice - use vercel-deploy-pipeline, vercel-env-management, and vercel-edge-and-isr instead; do NOT use to rate-limit or block abusive AI traffic - use vercel-firewall-and-botid; and do NOT use for app-level latency/caching tuning of the route - use next-on-vercel-perf.
- ▌
- ▌ Vercel Rendering And Caching · skillmedevChoose a rendering, runtime, and caching strategy on Vercel - Fluid Compute as the default runtime (Edge Functions are deprecated), ISR/PPR, Next.js 16 Cache Components ('use cache', cacheLife, cacheTag, updateTag, revalidateTag), and the Vercel Runtime Cache API (getCache, expireTag, invalidateByTag) with tag-based invalidation. Use when someone asks "should this page be static or server rendered on Vercel", "how do I set up ISR in Next.js", "revalidate this page on demand", or "why is my Vercel page serving stale content" - including streaming vs PPR decisions, caching an API response across regions, and migrating off unstable_cache. Do NOT use to set env vars (use vercel-env-management), wire git/preview/promote deploys (use vercel-deploy-pipeline), route LLM calls (use vercel-ai-gateway), or block bots/rate-limit (use vercel-firewall-and-botid). For pure Core-Web-Vitals/bundle tuning, hand to next-on-vercel-perf.
- ▌ Vercel Env Management · skillmedevManage environment variables across Vercel environments and keep local .env in sync - vercel env pull/add/rm/ls, per-environment values (development/preview/production + custom), sensitive secrets, OIDC tokens for keyless cloud access, and the NEXT_PUBLIC build-time inlining gotcha. Use when someone says "sync my .env", "vercel env pull", "set a secret on Vercel", "my env var is undefined in production", "different API key per environment", "why is my NEXT_PUBLIC var stale", or "connect to AWS/GCP without storing keys". Do NOT use when the task is the deploy/promote/rollback flow - use vercel-deploy-pipeline; for routing AI provider keys through one gateway - use vercel-ai-gateway; for runtime/region/caching config (ISR, Fluid Compute) - use vercel-edge-and-isr; for blocking bots or WAF rules - use vercel-firewall-and-botid; for bundle/runtime speed tuning - use next-on-vercel-perf.