# Claude Code & Cursor Skills Library

> 143 open, battle-tested agent skills from real production builds. Every skill is a plain SKILL.md file, free to copy into Claude Code, Cursor, Gemini CLI, or AGENTS.md.

Every skill human-reviewed. No runtime downloads, no secrets, attributed sources. All skills MIT licensed.

Formats per skill:

- Claude Code: raw SKILL.md, saved to .claude/skills/<slug>/SKILL.md
- Cursor: converted .mdc rule with alwaysApply false, saved to .cursor/rules/<slug>.mdc
- Gemini CLI and other agents: raw SKILL.md, saved to .agents/skills/<slug>/SKILL.md
- AGENTS.md: the body pasted as a `## Skill: <name>` section

Repo: https://github.com/TechTideOhio/techtide-lovable-skills.

## Skills

- SEO & AEO (25)
  - [ai-seo](https://alexcinovoj.com/skills/ai-seo.md): Optimize content to be cited by AI search engines and assistants (AI Overviews, ChatGPT, Perplexity, Claude, Gemini, Copilot). Use when the user says AI SEO, AEO, GEO, LLMO, answer engine optimization, AI citations, AI visibility, llms.txt, or "show up in AI answers". Not for traditional technical or on-page audits: use seo-audit. Not for structured data implementation: use schema. Not for building the content plan itself: use content-strategy. Tags: seo. Size: 6.7 KB.
  - [claude-seo](https://alexcinovoj.com/skills/claude-seo.md): SEO analysis orchestrator, routes audits to the right specialist skill and merges results into one scored report. Use when the user says "SEO audit", "analyze my site's SEO", "SEO health", or asks a broad SEO question with no obvious specialist. Not for narrow jobs you can route directly: schema goes to claude-seo-schema, sitemaps to claude-seo-sitemap, crawl/CWV to claude-seo-technical, intent fit to claude-seo-sxo. Tags: claude, seo. Size: 4.3 KB.
  - [claude-seo-backlinks](https://alexcinovoj.com/skills/claude-seo-backlinks.md): Backlink profile analysis: referring domains, anchor text distribution, toxic link detection, competitor link gap. Use when the user says backlinks, link profile, referring domains, anchor text, toxic links, link gap, link building, disavow, or backlink audit. Not for keyword clustering or content architecture: use claude-seo-cluster. Not for building the overall SEO strategy: use claude-seo-plan. Tags: claude, seo, backlinks. Size: 6.5 KB.
  - [claude-seo-cluster](https://alexcinovoj.com/skills/claude-seo-cluster.md): SERP-overlap topic clustering for content architecture: group keywords by shared Google top-10 results, design hub-and-spoke clusters with internal link matrices, output briefs and a cluster map. Use when the user says topic cluster, content cluster, pillar page, hub and spoke, keyword grouping, or content architecture. Not for backlink analysis: use claude-seo-backlinks. Not for the overall SEO strategy document: use claude-seo-plan. Not for optimizing a single page: use claude-seo-page. Tags: claude, seo, cluster. Size: 6.5 KB.
  - [claude-seo-competitor-pages](https://alexcinovoj.com/skills/claude-seo-competitor-pages.md): Build SEO comparison and alternatives pages ("X vs Y", "alternatives to X", category roundups) with feature matrices, schema, and honest competitor data. Use when the user says "comparison page", "vs page", "alternatives page", "X vs Y", or "alternative to". Not for full content briefs on other page types (use claude-seo-content-brief) or generating hundreds of comparison pages from data (use claude-seo-programmatic). Tags: claude, seo, competitor, pages. Size: 4.6 KB.
  - [claude-seo-content-brief](https://alexcinovoj.com/skills/claude-seo-content-brief.md): Generate competitive SEO content briefs with competitor gap scoring, per-section word counts, keyword placement, and meta tags. Handles new-page briefs and improve-existing-page briefs. Use when the user says "content brief", "content outline", "blog brief", "writing brief", or "outline for". Not for site-wide strategy or content calendars (use claude-seo-plan) or comparison pages specifically (use claude-seo-competitor-pages). Tags: claude, seo, content, brief. Size: 5.5 KB.
  - [claude-seo-dataforseo](https://alexcinovoj.com/skills/claude-seo-dataforseo.md): Pull live SEO data through the DataForSEO MCP server, including SERPs, keyword metrics, backlinks, on-page audits, competitor domains, business listings, and LLM mention tracking. Use when the user says "dataforseo", "live SERP", "keyword volume", "backlink data", "competitor data", or "AI visibility check". Not for Google first-party data like Search Console, CrUX, or GA4 (use claude-seo-google) or maps-platform analysis (use claude-seo-maps). Tags: claude, seo, dataforseo. Size: 5.4 KB.
  - [claude-seo-drift](https://alexcinovoj.com/skills/claude-seo-drift.md): Capture baselines of SEO-critical page elements, diff current state against them, and classify regressions by severity. Git for on-page SEO. Use when the user says "SEO drift", "baseline", "did anything break", "SEO regression", "before and after", or "deployment check". Not for one-off page audits with no baseline (use claude-seo-page) or full technical crawls (use claude-seo-technical). Tags: claude, seo, drift. Size: 4.8 KB.
  - [claude-seo-flow](https://alexcinovoj.com/skills/claude-seo-flow.md): Run the FLOW operating loop for evidence-led SEO, Find then Leverage then Optimize then Win, routing each stage to the right analysis and keeping recommendations tied to evidence. Use when the user says "FLOW", "FLOW framework", "evidence-led SEO", or asks where to start an SEO engagement. Not for executing a single specialized audit directly (go straight to claude-seo-page, claude-seo-geo, claude-seo-local, or claude-seo-technical). Tags: claude, seo, flow. Size: 4.4 KB.
  - [claude-seo-geo](https://alexcinovoj.com/skills/claude-seo-geo.md): Audit and optimize content for AI search surfaces, including Google AI Overviews and AI Mode, ChatGPT search, and Perplexity, covering citability, structure, crawler access, and brand mention signals. Use when the user says "GEO", "AI Overviews", "AI search", "LLM optimization", "AI citations", or "AI visibility". Not for local AI visibility specifics (use claude-seo-local) or pulling live LLM mention data (use claude-seo-dataforseo). Tags: claude, seo, geo. Size: 6.0 KB.
  - [claude-seo-google](https://alexcinovoj.com/skills/claude-seo-google.md): Pull Google first-party SEO data via Search Console, PageSpeed Insights, CrUX, Indexing API, GA4, YouTube Data, Knowledge Graph, and Cloud NLP. Real field data for Core Web Vitals, indexation, search performance, and organic traffic. Use when the user says "Search Console", "GSC", "PageSpeed", "CrUX", "field data", "URL inspection", "GA4 organic", "LCP", "INP", or "CLS". Not for third-party SERP, keyword, or backlink data (use claude-seo-dataforseo). Tags: claude, seo, google. Size: 5.3 KB.
  - [claude-seo-local](https://alexcinovoj.com/skills/claude-seo-local.md): Audit local SEO signals on a business website, including GBP integration, reviews, NAP consistency, citations, LocalBusiness schema, location pages, and local link signals, with business-type and industry detection. Use when the user says "local SEO", "GBP", "map pack", "citations", "NAP", "service area", or "multi-location". Not for maps-platform data like geo-grids and GBP API audits (use claude-seo-maps) or general AI visibility (use claude-seo-geo). Tags: claude, seo, local. Size: 6.1 KB.
  - [claude-seo-maps](https://alexcinovoj.com/skills/claude-seo-maps.md): Analyze a business's presence on maps platforms, including geo-grid rank tracking, GBP profile audits via API, cross-platform review intelligence, NAP verification across Google/Bing/Apple/OSM, competitor radius mapping, and schema generation. Use when the user says "geo-grid", "maps analysis", "GBP audit", "review velocity", "competitor radius", "Share of Local Voice", or "SoLV". Not for on-website local SEO signals (use claude-seo-local) or AI search visibility (use claude-seo-geo). Tags: claude, seo, maps. Size: 6.1 KB.
  - [claude-seo-page](https://alexcinovoj.com/skills/claude-seo-page.md): Deep SEO analysis of a single page, covering on-page elements, content quality, technical meta tags, schema, images, and CWV risk flags, with a scored report. Use when the user says "analyze this page", "check page SEO", "page analysis", or provides one URL for review. Not for site-wide crawls or indexability audits (use claude-seo-technical), regression tracking against a baseline (use claude-seo-drift), or AI-surface scoring (use claude-seo-geo). Tags: claude, seo, page. Size: 5.0 KB.
  - [claude-seo-plan](https://alexcinovoj.com/skills/claude-seo-plan.md): Build a strategic SEO plan for a new or existing site, covering discovery, competitive analysis, site architecture, content strategy, and a phased implementation roadmap with KPIs. Use when the user says "SEO plan", "SEO strategy", "SEO roadmap", "content calendar", or "site architecture". Not for a single page brief (use claude-seo-content-brief), pages generated at scale (use claude-seo-programmatic), or executing audits on a live site (use claude-seo-page or claude-seo-technical). Tags: claude, seo, plan. Size: 5.0 KB.
  - [claude-seo-programmatic](https://alexcinovoj.com/skills/claude-seo-programmatic.md): Plan and audit SEO pages generated at scale from data sources, enforcing quality gates against thin content, doorway patterns, and index bloat. Use when the user says "programmatic SEO", "pages at scale", "template pages", "generated pages", or "data-driven pages". Not for one-off page audits (use claude-seo-page), site strategy (use claude-seo-plan), or hand-built comparison pages (use claude-seo-competitor-pages). Tags: claude, seo, programmatic. Size: 5.8 KB.
  - [claude-seo-schema](https://alexcinovoj.com/skills/claude-seo-schema.md): Detect, validate, and generate Schema.org structured data as JSON-LD. Use when the user says "schema", "structured data", "rich results", "JSON-LD", or "markup". Not for full technical audits: use claude-seo-technical. Not for site-wide SEO scoring or orchestration: use claude-seo. Tags: claude, seo, schema. Size: 4.3 KB.
  - [claude-seo-sitemap](https://alexcinovoj.com/skills/claude-seo-sitemap.md): Analyze existing XML sitemaps or generate new ones, validating format, URLs, and structure. Use when the user says "sitemap", "generate sitemap", "sitemap issues", or "XML sitemap". Not for full crawl or indexability audits: use claude-seo-technical. Not for structured data: use claude-seo-schema. Tags: claude, seo, sitemap. Size: 3.8 KB.
  - [claude-seo-sxo](https://alexcinovoj.com/skills/claude-seo-sxo.md): Search Experience Optimization, reads the SERP backwards to find page-type mismatches, derive user stories, and score pages per persona. Use when the user says "SXO", "why isn't my page ranking", "intent mismatch", "SERP analysis", "persona scoring", or "page type mismatch". Not for technical health checks: use claude-seo-technical. Not for full-site audits: use claude-seo. Tags: claude, seo, sxo. Size: 4.6 KB.
  - [claude-seo-technical](https://alexcinovoj.com/skills/claude-seo-technical.md): Technical SEO audit across nine categories, crawlability through Core Web Vitals to JS rendering. Use when the user says "technical SEO", "crawl issues", "robots.txt", "Core Web Vitals", "site speed", or "security headers". Not for schema generation: use claude-seo-schema. Not for sitemap work: use claude-seo-sitemap. Not for intent or SERP fit: use claude-seo-sxo. Tags: claude, seo, technical. Size: 4.6 KB.
  - [competitors](https://alexcinovoj.com/skills/competitors.md): Create competitor comparison and alternative pages that rank for competitive terms and help evaluators decide. Use when the user says "vs page", "alternative page", "comparison page", "[Product] vs [Product]", or "[Product] alternative". Covers four page formats. Not for researching the competitors themselves: use competitor-profiling. Not for internal battle cards: use a sales-enablement skill. Tags: competitors. Size: 4.8 KB.
  - [programmatic-seo](https://alexcinovoj.com/skills/programmatic-seo.md): Plan and build SEO pages at scale from templates plus data: location, comparison, integration, template, and directory pages. Use when the user says "programmatic SEO", "pSEO", "generate 100 pages", "location pages", or "[keyword] + [city] pages". Not for the claude-seo pipeline implementation of pSEO: use claude-seo-programmatic. Not for auditing existing pages: use seo-audit. Not for site-wide URL and linking design: use site-architecture. Tags: programmatic, seo. Size: 5.3 KB.
  - [schema](https://alexcinovoj.com/skills/schema.md): Implement and validate schema.org structured data as JSON-LD for rich results. Use when the user says "schema markup", "structured data", "JSON-LD", "rich snippets", "FAQ schema", "product schema", or wants star ratings or enhanced listings in Google. Not for full SEO diagnostics: use seo-audit. Not for AI answer engine optimization: use ai-seo. Not for planning page hierarchy or breadcrumb structure: use site-architecture. Tags: schema. Size: 4.7 KB.
  - [seo-audit](https://alexcinovoj.com/skills/seo-audit.md): Diagnose and prioritize SEO issues across crawlability, indexation, technical health, on-page, and content quality. Use when the user says "SEO audit", "why am I not ranking", "traffic dropped", "core web vitals", "crawl errors", or anything vague like "my SEO is bad". Not for pages at scale: use programmatic-seo. Not for structured data: use schema. Not for AI answer engines: use ai-seo. Not for page hierarchy planning: use site-architecture. Tags: seo, audit. Size: 5.4 KB.
  - [site-architecture](https://alexcinovoj.com/skills/site-architecture.md): Plan or restructure a website's page hierarchy, navigation, URL structure, and internal linking. Use when the user says "sitemap", "site structure", "information architecture", "navigation design", "URL structure", "what pages do I need", or "how should I organize my site". Not for XML sitemaps or indexation problems: use seo-audit. Not for structured data markup: use schema. Not for deciding what content to create: use content-strategy. Tags: site, architecture. Size: 4.8 KB.
- Sales & RevOps (20)
  - [cold-email](https://alexcinovoj.com/skills/cold-email.md): Write B2B cold emails and follow-up sequences that get replies. Use when the user says "cold outreach", "prospecting email", "outbound email", "SDR email", "follow-up sequence", or "nobody's replying to my emails". Not for warm or lifecycle email: use a lifecycle-emails skill. Not for partner pitches: use co-marketing. Not for building the prospect list itself: use a prospecting skill. Tags: cold, email. Size: 4.6 KB.
  - [contract-and-proposal-writer](https://alexcinovoj.com/skills/contract-and-proposal-writer.md): Draft jurisdiction-aware business documents, freelance contracts, proposals, SOWs, NDAs, and MSAs, as structured Markdown with docx conversion. Covers US (Delaware), EU, UK, and DACH. Use when drafting a client contract, proposal, SOW, NDA, or MSA. Not a substitute for legal counsel, drafts require attorney review. Not for reviewing or negotiating third-party paper. Not for outreach copy: use cold-email. Tags: contract, and, proposal, writer. Size: 4.7 KB.
  - [deal-to-invoice](https://alexcinovoj.com/skills/deal-to-invoice.md): Convert an accepted proposal into a live payment link, a booked kickoff, a delivery checklist, and a recorded deal in one pass. Use the moment a prospect says yes to a proposal, or when the user says "they accepted", "send the invoice", "set up the deal", or "get kickoff scheduled". Not for writing the proposal itself: use contract-and-proposal-writer. Not for outbound eligibility checks: use do-not-contact. Tags: deal, invoice. Size: 5.9 KB.
  - [do-not-contact](https://alexcinovoj.com/skills/do-not-contact.md): Suppression gate consulted before any outbound touch: merges disqualified leads, manual exclusions, bounces, and imported exclusion lists into one do-not-contact list with a live check. Use before promoting discovered leads, drafting outreach, sending email or LinkedIn requests, or resurfacing old leads. A hit drops the candidate; a missing or stale list halts the run. Not for batch send approval itself: use a send-gate skill. Not for post-acceptance deal work: use deal-to-invoice. Tags: not, contact. Size: 5.7 KB.
  - [gumroad-api](https://alexcinovoj.com/skills/gumroad-api.md): Manage Gumroad products, sales, offer codes, licenses, subscribers, variants, and webhooks through the REST API v2. Use when checking sales data, creating discount codes, toggling or updating products, verifying license keys, pulling subscriber lists, or wiring sale webhooks. Not for creating new products or any browser-only flow: the API cannot create products, use gumroad-browser for that. Tags: gumroad, api. Size: 4.9 KB.
  - [gumroad-browser](https://alexcinovoj.com/skills/gumroad-browser.md): Drive the Gumroad web UI with browser automation to create products, upload files, configure checkout, and publish. Use when the user says "set up my store," "create a Gumroad product," "upload to Gumroad," or any Gumroad task the API cannot do. Not for post-creation management (offer codes in bulk, sales data, license keys): use gumroad-api. Tags: gumroad, browser. Size: 4.4 KB.
  - [inbound-triage](https://alexcinovoj.com/skills/inbound-triage.md): Classify inbound LinkedIn DMs and comments, then draft a short qualifying reply in the operator's voice. Use when a prospect DMs, replies, or leaves a substantive comment and you need to sort buyer from audience without pitching. Not for outbound first-touch: use cold-email. Not for designing the content that attracted them: use linkedin-carousel-generator or linkedin-design. Tags: inbound, triage. Size: 4.2 KB.
  - [offers](https://alexcinovoj.com/skills/offers.md): Design or fix the offer itself: value framing, bonus stack, guarantee, scarcity, naming, payment structure. Use when the user says "build an offer", "irresistible offer", "value stack", "risk reversal", "why isn't my offer converting", or sells services, courses, coaching, or high-ticket B2B. Not for price levels, tiers, or value metrics: use pricing. Not for the sales page: use a copywriting skill. Not for the launch moment: use a launch skill. Tags: offers. Size: 5.7 KB.
  - [proposal-builder](https://alexcinovoj.com/skills/proposal-builder.md): Turn discovery-call notes into a one-page proposal with one specific scope, price, timeline, and a yes/no next step. Use when the user says "write the proposal", "turn these call notes into a proposal", or after any discovery call. Not for contract terms and legal language: use contract-and-proposal-writer. Not for decks and battle cards: use sales-enablement. Not for designing what you sell: use offers. Tags: proposal, builder. Size: 4.6 KB.
  - [prospecting](https://alexcinovoj.com/skills/prospecting.md): Build a verified, scored prospect list from an ICP, across B2B SaaS, general B2B, or local small-business motions. Use when the user says "build a prospect list", "find leads", "target account list", "find local businesses", or "who should we go after". Not for writing the outreach: use cold-email. Not for deep research on one account: use competitor-profiling. Not for defining positioning and ICP from scratch: use product-marketing. Tags: prospecting. Size: 5.6 KB.
  - [revops](https://alexcinovoj.com/skills/revops.md): Design the systems that connect marketing to revenue: lead lifecycle stages, scoring, routing, pipeline stage management, handoff SLAs, deal desk, and RevOps metrics. Use when the user says RevOps, lead scoring, lead routing, MQL, SQL, pipeline stages, deal desk, or leads aren't getting to sales. Not for CRM dedup and record cleanup: use sales-data-hygiene. Not for outbound sequences: use sales-cadence. Not for pricing decisions: use pricing. Tags: revops. Size: 5.9 KB.
  - [sales-asset-producer](https://alexcinovoj.com/skills/sales-asset-producer.md): Produce conversion-focused sales and investor collateral: pitch decks, one-pagers, comparison sheets, case studies, and demo scripts. Use when the user asks for a pitch deck, sell sheet, product overview, competitive comparison, case study, or investor materials. Not for single-image social graphics: use viral-asset-templates. Not for LinkedIn carousels: use linkedin-carousel-generator. Not for video builds: use remotion-social-clips. Tags: sales, asset, producer. Size: 4.4 KB.
  - [sales-cadence](https://alexcinovoj.com/skills/sales-cadence.md): Design multi-channel outbound cadences: touch count, spacing, channel mix, step content, A/B tests, and benchmarks. Use when reply rates are low, touchpoint count or spacing is unclear, sequence performance plateaus, or the user asks for a full outbound cadence. Not for one-off cold email copy: use cold-email. Not for deliverability, warmup, or spam problems: use sales-deliverability. Not for enriching the contact list: use sales-enrich. Tags: sales, cadence. Size: 5.4 KB.
  - [sales-data-hygiene](https://alexcinovoj.com/skills/sales-data-hygiene.md): CRM data quality: audits, deduplication, normalization, decay management, and ongoing hygiene automation. Use when the CRM is full of duplicates, records are stale or inconsistent, fields are missing, or you need a data quality audit before a campaign. Not for one-time enrichment of a prospect list or waterfall setup: use sales-enrich. Not for lifecycle stages, scoring, or routing design: use revops. Not for suppression lists: use do-not-contact. Tags: sales, data, hygiene. Size: 5.6 KB.
  - [sales-deal-inspect](https://alexcinovoj.com/skills/sales-deal-inspect.md): Inspect a single deal: health scorecard, MEDDPICC gap analysis, stakeholder map, risk patterns, and a prioritized action plan. Use when a deal feels stuck or at risk, the real decision-maker is unclear, the champion went quiet, or a deal review needs prep. Not for portfolio-level pipeline design or stage definitions: use revops. Not for CRM record quality: use sales-data-hygiene. Not for writing the outreach itself: use sales-cadence or cold-email. Tags: sales, deal, inspect. Size: 5.1 KB.
  - [sales-deliverability](https://alexcinovoj.com/skills/sales-deliverability.md): Email deliverability for outbound: SPF/DKIM/DMARC setup, mailbox and domain warmup, inbox placement, reputation monitoring, blacklist recovery, list hygiene. Use when emails land in spam, open rates crater, bounce rates spike, a domain gets blacklisted, or a new mailbox needs warming. Not for cadence content and sequencing: use sales-cadence. Not for finding or verifying contacts in bulk: use sales-enrich. Not for suppression policy: use do-not-contact. Tags: sales, deliverability. Size: 5.5 KB.
  - [sales-enablement](https://alexcinovoj.com/skills/sales-enablement.md): Create sales collateral reps actually use: pitch decks, one-pagers, objection docs, ROI calculators, demo scripts, playbooks, persona cards, proposals. Use when the user says sales deck, one-pager, leave-behind, objection handling, talk track, sales playbook, or help my sales team. Not for public competitor comparison pages: use competitors. Not for marketing site copy: use copywriting. Not for outbound emails: use cold-email. Not for lead lifecycle systems: use revops. Tags: sales, enablement. Size: 5.5 KB.
  - [sales-enrich](https://alexcinovoj.com/skills/sales-enrich.md): Enrich contacts and companies with verified emails, phones, and firmographics: single-record, batch, auto, and waterfall enrichment with credit budgeting and compliance checks. Use when records lack emails or phones, a list needs enriching before a campaign, credits burn too fast, or one provider's coverage is thin. Not for CRM dedup and ongoing hygiene: use sales-data-hygiene. Not for building lists from scratch: use prospecting. Not for send-side reputation: use sales-deliverability. Tags: sales, enrich. Size: 5.5 KB.
  - [send-gate](https://alexcinovoj.com/skills/send-gate.md): The single approval choke point between drafted outreach and an actual send. Use when a batch of drafted messages (cold email, LinkedIn DMs, connection requests, follow-ups) is ready to go out. Runs suppression, dedupe, and daily caps, then holds everything for explicit human approval. Never sends anything itself. Not for drafting copy: use cold-email. Not for follow-up timing: use sales-cadence. Not for suppression list upkeep: use do-not-contact. Tags: send, gate. Size: 5.9 KB.
  - [venture-studio-guardrails](https://alexcinovoj.com/skills/venture-studio-guardrails.md): Hard business guardrails for client work: proposals, SOWs, scoping, pricing structures, payment terms, discovery calls, hiring, and contractor agreements. Use whenever creating any client-facing deliverable or engagement structure, or when the user mentions scope, SOW, retainers, payment schedules, or client boundaries. If in doubt, check. Not for writing the proposal copy itself: use proposal-builder or contract-and-proposal-writer; this skill is the filter it passes through. Tags: venture, studio, guardrails. Size: 5.8 KB.
- Marketing & Growth (19)
  - [ab-testing](https://alexcinovoj.com/skills/ab-testing.md): Design and run statistically valid A/B tests and build a growth experimentation program: hypotheses, sample sizes, variant design, analysis, ICE-prioritized backlogs. Use when the user mentions split tests, experiments, statistical significance, "which version is better," or experiment velocity. Not for generating page-level optimization ideas: use cro. Not for tracking implementation: use analytics. Not for writing variant copy: use copywriting. Tags: testing. Size: 5.9 KB.
  - [analytics](https://alexcinovoj.com/skills/analytics.md): Set up, improve, or audit analytics tracking and measurement. Use when the user mentions GA4, Google Analytics, GTM, tag manager, conversion tracking, event tracking, UTM parameters, tracking plan, Mixpanel, Segment, attribution, "are my events firing", or "how do I measure this". Not for experiment design or A/B test measurement: use ab-testing. Not for organic traffic analysis: use seo-audit. Not for conversion optimization work that consumes this data: use cro. Tags: analytics. Size: 5.2 KB.
  - [co-marketing](https://alexcinovoj.com/skills/co-marketing.md): Find co-marketing partners, score partnership fit, and plan joint campaigns. Use when the user says "co-marketing", "partner marketing", "joint campaign", "who should we partner with", "cross-promotion", or "co-brand". Not for customer referral or affiliate programs: use a referrals skill. Not for outbound prospect email: use cold-email. Not for planning your own content calendar: use content-strategy. Tags: marketing. Size: 4.2 KB.
  - [competitor-profiling](https://alexcinovoj.com/skills/competitor-profiling.md): Research competitors from their URLs and produce structured, comparable profile documents backed by scraped pages, reviews, and SEO data. Use when the user says "competitor research", "competitor analysis", "profile this competitor", "competitive intelligence", or "competitor deep dive". Not for building comparison or alternative pages from profiles: use competitors. Not for sales battle cards: use a sales-enablement skill. Tags: competitor, profiling. Size: 4.6 KB.
  - [copywriting](https://alexcinovoj.com/skills/copywriting.md): Write persuasive marketing copy for web pages, including homepage, landing, pricing, feature, and about pages, headlines, CTAs, and value propositions. Use when the user says "write copy for", "rewrite this page", "headline help", "value proposition", or "make this more compelling". Not for polishing existing copy: use copy-editing. Not for page structure and conversion diagnosis: use cro. Not for cold outreach: use cold-email. Tags: copywriting. Size: 4.4 KB.
  - [cro](https://alexcinovoj.com/skills/cro.md): Diagnose why a marketing page or form is not converting and deliver prioritized fixes. Use when the user says "CRO", "this page isn't converting", "improve conversions", "form abandonment", "low conversion rate", or shares a page URL asking for feedback. Not for writing the replacement copy: use copywriting. Not for line-editing existing copy: use copy-editing. Not for gathering the underlying customer insight: use customer-research. Tags: cro. Size: 5.0 KB.
  - [customer-research](https://alexcinovoj.com/skills/customer-research.md): Gather and synthesize what customers actually say, feel, and struggle with, from transcripts, surveys, tickets, reviews, and online communities, into themes, personas, and voice-of-customer quote banks. Use when the user says "customer research", "analyze transcripts", "VOC", "build personas", "JTBD", "review mining", or "why do customers churn". Not for writing copy from the findings: use copywriting. Not for page fixes: use cro. Tags: customer, research. Size: 5.2 KB.
  - [directory-submissions](https://alexcinovoj.com/skills/directory-submissions.md): Plan and execute product submissions to startup, SaaS, AI, agent/MCP, and review directories for backlinks, domain rating, and discovery, including Product Hunt launches and G2/Capterra review drives. Use when the user says "directory submissions", "submit to Product Hunt", "backlinks from directories", "list my product", or "launch directories". Not for AI citation work on your own pages: use ai-seo. Not for editorial backlink outreach: use claude-seo-backlinks. Tags: directory, submissions. Size: 5.7 KB.
  - [emails](https://alexcinovoj.com/skills/emails.md): Design automated email sequences, welcome series, nurture flows, onboarding emails, re-engagement campaigns. Use when the user says "email sequence", "drip campaign", "welcome series", "lifecycle emails", "email automation", or "what emails should I send". Not for cold outbound: use cold-email. Not for the lead magnet that feeds the list: use lead-magnets. Not for interactive capture tools: use free-tools. Tags: emails. Size: 4.6 KB.
  - [free-tools](https://alexcinovoj.com/skills/free-tools.md): Plan and evaluate free marketing tools (calculators, generators, graders, analyzers) that earn leads, links, and traffic. Use when the user says "engineering as marketing", "free tool", "ROI calculator", "grader", "audit tool", or "should I build a tool for leads". Not for downloadable content offers (ebooks, checklists, templates): use lead-magnets. Not for the nurture emails after capture: use emails. Tags: free, tools. Size: 4.7 KB.
  - [launch](https://alexcinovoj.com/skills/launch.md): Plan product launches, feature announcements, and go-to-market moments across owned, rented, and borrowed channels. Use when the user says "launch", "Product Hunt", "GTM plan", "announcement", "beta launch", "waitlist", or "we're about to ship". Not for the nurture emails after signup: use emails. Not for the gated asset that builds the waitlist: use lead-magnets. Not for partner-led campaigns: use co-marketing. Tags: launch. Size: 4.8 KB.
  - [lead-magnets](https://alexcinovoj.com/skills/lead-magnets.md): Plan lead magnets (checklists, templates, guides, swipe files) that capture emails and qualify leads. Use when the user says "lead magnet", "gated content", "content upgrade", "opt-in", "freebie", or "what should I give away for emails". Not for interactive tools like calculators and graders: use free-tools. Not for the nurture sequence after capture: use emails. Not for the launch moment itself: use launch. Tags: lead, magnets. Size: 4.8 KB.
  - [marketing-loops](https://alexcinovoj.com/skills/marketing-loops.md): Design and schedule recurring marketing workflows an agent runs on a cadence, with triggers, self-checks, and stop conditions. Use when the user says "marketing loop", "automate my marketing", "weekly marketing review", "churn watch", "ad fatigue check", or "run this every week". Not for one-off tactics: use a marketing-plan or channel skill. Not for experiment design: use ab-testing. Tags: marketing, loops. Size: 5.1 KB.
  - [marketing-plan](https://alexcinovoj.com/skills/marketing-plan.md): Build a 12-month marketing plan structured by AARRR, customized to budget, team, and funding stage. Use when the user says "marketing plan", "growth plan", "GTM plan", "90-day marketing roadmap", or "fractional CMO plan". Not for positioning and ICP capture: run product-marketing first. Not for single-channel execution: use the channel skill (emails, programmatic-seo, pricing, referrals). Tags: marketing, plan. Size: 5.1 KB.
  - [pricing](https://alexcinovoj.com/skills/pricing.md): Design SaaS pricing and monetization: value metric, tier structure, price points, freemium, price increases, pricing-page layout. Use when the user says "how much should I charge", "pricing tiers", "freemium", "value metric", "willingness to pay", or "my pricing is wrong". Not for offer construction (bonuses, guarantees, scarcity) on services, courses, or high-ticket B2B: use offers. Not for testing price changes: use ab-testing. Tags: pricing. Size: 5.0 KB.
  - [product-marketing](https://alexcinovoj.com/skills/product-marketing.md): Create or update the product marketing context document (.agents/product-marketing.md) that captures positioning, ICP, personas, competitors, and voice for every other marketing skill to reference. Use when the user says "set up marketing context", "positioning", "ICP", "who is my target audience", or at the start of any marketing project. Not for building the full plan: use marketing-plan. Not for interviewing customers: use a customer-research skill. Tags: product, marketing. Size: 5.6 KB.
  - [public-relations](https://alexcinovoj.com/skills/public-relations.md): Earned media for software products: find journalists, pitch stories, newsjack trending news, answer press requests, build a press page. Use when the user says press, PR (media, not pull requests), press release, pitch a journalist, get featured, media list, HARO, newsjacking, or op-ed. Not for directory listings: use directory-submissions. Not for product launches: use launch. Not for social engagement: use social. Not for prospect outreach: use cold-email. Tags: public, relations. Size: 5.2 KB.
  - [referrals](https://alexcinovoj.com/skills/referrals.md): Design, launch, and optimize referral and affiliate programs that turn customers into acquisition channels. Use when the user says referral program, affiliate program, ambassador, refer a friend, viral loop, word of mouth, or affiliate payout. Not for launch-week virality tactics: use launch. Not for the nurture emails themselves: use emails. Not for partner co-marketing campaigns: use co-marketing. Tags: referrals. Size: 5.2 KB.
  - [social](https://alexcinovoj.com/skills/social.md): Create, repurpose, and schedule social content for LinkedIn, X, Instagram, TikTok, and Facebook, plus engagement routines and performance review. Use when the user says "LinkedIn post", "thread", "content calendar", "what should I post", "repurpose this", "Reels", "Shorts", or "grow my following". Not for overall content planning: use content-strategy. Not for earned media: use public-relations. Not for LinkedIn carousel design and export: use linkedin-carousel-generator. Tags: social. Size: 5.5 KB.
- Agent Ops & Meta (17)
  - [agent-recipe-builder](https://alexcinovoj.com/skills/agent-recipe-builder.md): Design a reusable multi-skill recipe, a documented loop blueprint that sits between a one-off skill and a scheduled automation. Use when turning a workflow (lead enrichment, newsletter issue, SEO refresh, proposal generation) into a repeatable agent loop, or before promoting any workflow to a schedule. Not for auditing existing automations: use automation-audit-ops. Not for verifying a recipe's output: use behavior-validator. Tags: agent, recipe, builder. Size: 4.5 KB.
  - [agent-self-evaluation](https://alexcinovoj.com/skills/agent-self-evaluation.md): Self-rate completed work on five axes (accuracy, completeness, clarity, actionability, conciseness) with cited evidence per score. Use after multi-file code changes, multi-step workflows, long debugging sessions, or written analysis, or when asked "rate yourself". Not for proving external behavior works: use behavior-validator. Not for comparing agents head to head. Tags: agent, self, evaluation. Size: 5.0 KB.
  - [ai-tool-directive](https://alexcinovoj.com/skills/ai-tool-directive.md): Write structured directives for AI coding tools so fixes remove old code, respect scope, and verify. Use when delegating technical work to another AI assistant, especially when past attempts layered new code on old, missed scope, or failed to stick. Not for integrating AI provider APIs into a product: use ai-provider-integration. Tags: tool, directive. Size: 4.1 KB.
  - [automation-audit-ops](https://alexcinovoj.com/skills/automation-audit-ops.md): Evidence-first inventory and overlap audit of automations, scheduled jobs, CI workflows, connectors, and agent loops. Use when the user asks what automations exist, what is live, what is broken, or what overlaps, before fixing anything. Not for designing new loops: use agent-recipe-builder. Not for proving a single workflow's output works: use behavior-validator. Tags: automation, audit, ops. Size: 4.6 KB.
  - [build-loop](https://alexcinovoj.com/skills/build-loop.md): Drive a captured goal to 100% completion through a bounded implement-verify loop with hard caps and halt-on-ambiguity. Use when the user says loop until done, keep building, autonomous build, drive to completion, don't stop until it's done. Requires .lovable/goal.json. Not for defining the goal or acceptance criteria: run goal-capture first. Tags: build, loop. Size: 6.2 KB.
  - [context-budget](https://alexcinovoj.com/skills/context-budget.md): Audit agent context window overhead across skills, agent instructions, MCP tool schemas, and rules, then produce ranked token-savings recommendations. Use when the user says "context budget", "token overhead", "session feels sluggish", "do I have room for more MCP servers", or after adding many components. Not for improving one skill's content quality: use a skill-authoring skill. Not for runtime cost/billing analysis. Tags: context, budget. Size: 4.3 KB.
  - [dispatching-parallel-agents](https://alexcinovoj.com/skills/dispatching-parallel-agents.md): Split independent problems across parallel subagents with focused, self-contained prompts, then integrate their results. Use when 2+ tasks share no state and no ordering, like unrelated test failures across different files or independent subsystem bugs. Not for related failures where one fix may cascade: investigate those in one thread. Not for adversarial review of a single decision: use doubt-driven-development. Not for trimming your own context: use context-budget. Tags: dispatching, parallel, agents. Size: 4.8 KB.
  - [goal-capture](https://alexcinovoj.com/skills/goal-capture.md): Turn a vague request into a machine-checkable goal file with verifiable acceptance criteria, non-goals, guardrails, and an iteration budget, mirrored into roadmap items. Use when the user says set a goal, define done, acceptance criteria, capture the goal, or asks to keep building until done with no goal file present. Not for executing the goal: use build-loop. Tags: goal, capture. Size: 5.3 KB.
  - [loop-run-log](https://alexcinovoj.com/skills/loop-run-log.md): Record a standardized run log after any recurring agent loop or multi-step workflow: trigger, inputs, actions, evidence, blockers, next trigger. Use when designing, running, reviewing, or debugging recurring automations, outreach loops, publishing loops, or refresh loops. Not for validating that the work itself succeeded: use behavior-validator. Not for planning the day's loop stack: use morning. Tags: loop, run, log. Size: 4.4 KB.
  - [lovable-native-packaging-bridge](https://alexcinovoj.com/skills/lovable-native-packaging-bridge.md): Package and review skills, rules, and prompt kits for Lovable's native workspace-skill surface with evidence-backed promotion decisions. Use when importing, expanding, or auditing skills targeted at Lovable, or deciding whether third-party material may be promoted into the library. Not for converting a Lovable prototype into a production repo (use techtide-lovable-production-handoff) or hardening UI generation prompts (use techtide-v0-ui-prompt-hardener). Tags: lovable, native, packaging, bridge. Size: 4.4 KB.
  - [morning](https://alexcinovoj.com/skills/morning.md): Render the user's morning brief as a single styled HTML page (day-as-terrain drawing plus needs-attention and resolved lists), or set it up as a recurring weekday task. Use only when the user explicitly asks to run, see, or schedule their morning brief, or invokes /morning. Not for answering a one-off question about today's schedule: answer that directly. Tags: morning. Size: 7.0 KB.
  - [skill-eval-runner](https://alexcinovoj.com/skills/skill-eval-runner.md): Run regression checks across a skills directory after imports, edits, or bulk updates. Catches missing frontmatter, slug mismatches, oversized bodies, broken local links, and risky executable patterns. Use after any change that touches multiple skills. Not for vetting third-party skills before import: use skill-intake-quarantine. Not for deep security analysis of scripts: use skill-security-auditor. Tags: skill, eval, runner. Size: 4.2 KB.
  - [skill-intake-quarantine](https://alexcinovoj.com/skills/skill-intake-quarantine.md): Quarantine and vet any third-party skill, agent recipe, plugin, or automation repo before it enters the skills library. Classifies each candidate as copy, adapt, rewrite, reject, or reference-only. Use before importing, installing, or recommending outside material. Not for scanning scripts for malicious behavior: use skill-security-auditor. Not for post-import regression checks: use skill-eval-runner. Tags: skill, intake, quarantine. Size: 5.3 KB.
  - [skill-security-auditor](https://alexcinovoj.com/skills/skill-security-auditor.md): Audit third-party skills, agent repos, scripts, and plugins for unsafe behavior, then issue a risk verdict with evidence. Use before running or importing any outside code or skill, and when checking for install hooks, secret reads, obfuscation, or prompt injection. Not for the overall intake decision: use skill-intake-quarantine. Not for post-import regression checks: use skill-eval-runner. Not for hardening your own app code: use security-and-hardening. Tags: skill, security, auditor. Size: 5.3 KB.
  - [subagent-driven-development](https://alexcinovoj.com/skills/subagent-driven-development.md): Execute an implementation plan by dispatching fresh subagents per task with reviews between tasks. Use when you have an approved plan with mostly independent tasks and want to execute in the current session. Not for writing the plan: use writing-plans. Not for tightly coupled tasks that need one continuous context: execute manually. Requires an isolated workspace: use using-git-worktrees first. Tags: subagent, driven, development. Size: 7.0 KB.
  - [windows-exec](https://alexcinovoj.com/skills/windows-exec.md): Run Python scripts and PowerShell reliably through a Windows MCP that enforces a hard 60-second timeout: detached processes, file-based output, polling, and killing hung processes. Use before any Windows command that could exceed 10 seconds, or when a previous command timed out or hung. Not for Linux/macOS shells or for Gumroad UI flows (use gumroad-browser). Tags: windows, exec. Size: 5.1 KB.
  - [writing-skills](https://alexcinovoj.com/skills/writing-skills.md): Create and edit skills using TDD applied to process documentation, baseline an agent failing without the skill before writing it. Use when creating a new skill, editing an existing one, or verifying a skill changes behavior before deployment. Not for auditing third-party skills for malicious content: use skill-security-auditor. Not for batch-scoring existing skills: use skill-eval-runner. Tags: writing, skills. Size: 5.7 KB.
- Quality & Security (13)
  - [behavior-validator](https://alexcinovoj.com/skills/behavior-validator.md): Verify apps, CLIs, API routes, artifacts, and automations from the user-facing surface, not from implementation claims. Use when checking whether something actually works, catching false-success states, missing side effects, or workflow regressions. Not for visual and layout QA in a real browser: use browser-visual-qa. Not for rating output quality: use agent-self-evaluation. Tags: behavior, validator. Size: 4.7 KB.
  - [browser-visual-qa](https://alexcinovoj.com/skills/browser-visual-qa.md): Autonomous visual and interaction QA on real UI in a real browser: drive the page like a user, capture screenshots and accessibility snapshots, diff against baselines, read console errors and Core Web Vitals. Use to verify frontend work before calling it done, or to catch layout breakage, dead states, and regressions. Not for backend or non-visual behavior checks: use behavior-validator. Not for CI pipeline setup: use ci-cd-and-automation. Tags: browser, visual. Size: 5.6 KB.
  - [cross-domain-audit-synthesis](https://alexcinovoj.com/skills/cross-domain-audit-synthesis.md): Merge independent engineering audits (security, types, performance, velocity) into one prioritized, time-boxed remediation roadmap with a defensible first PR. Use when multiple audit reports need sequencing into a single plan. Not for producing an individual audit: run domain audits first, e.g. design-system-drift for UI decay metrics. Tags: cross, domain, audit, synthesis. Size: 4.0 KB.
  - [design-system-drift](https://alexcinovoj.com/skills/design-system-drift.md): Measure design system decay in a frontend codebase with five quantified metrics: hardcoded colors, component reinvention, token adoption, context provider bloat, accessibility gap. Use when auditing UI consistency, sizing a refactor, or proving drift with numbers. Not for merging multiple audits into one roadmap: use cross-domain-audit-synthesis. Not for building new marketing pages: use awwwards-2026. Tags: design, system, drift. Size: 4.8 KB.
  - [money-path-halt-go](https://alexcinovoj.com/skills/money-path-halt-go.md): Mandatory HALT-GO review for any diff touching money surfaces, checkout, payment intents, webhooks, payouts, refunds, ledgers, balances, orders, or invoices, on a Stripe/Paddle + Supabase stack. Use whenever a change touches those code paths or tables, however small. Blocks ship until every gate passes. Not for general schema rules (use supabase-schema-discipline) or the broader pre-ship security sweep (use rls-security-gate). Tags: money, path, halt. Size: 5.5 KB.
  - [observability-and-instrumentation](https://alexcinovoj.com/skills/observability-and-instrumentation.md): Instrument features with structured logs, metrics, traces, and alerts so production behavior is diagnosable from telemetry alone. Use when shipping anything that runs in production, adding logging or alerting, or when incidents took too long to diagnose. Not for diagnosing a live failure: use systematic-debugging. Not for fixing measured slowness: use performance-optimization. Not for launch-day monitoring gates: use shipping-and-launch. Tags: observability, and, instrumentation. Size: 6.2 KB.
  - [performance-optimization](https://alexcinovoj.com/skills/performance-optimization.md): Profile-first performance work: find the real bottleneck, fix it, prove the improvement. Use when Core Web Vitals or load times miss targets, users report slowness, a change may have regressed performance, or perf budgets exist. Not for adding the telemetry that detects slowness: use observability-and-instrumentation. Not for general debugging of wrong behavior: use systematic-debugging. Tags: performance, optimization. Size: 5.1 KB.
  - [rls-security-gate](https://alexcinovoj.com/skills/rls-security-gate.md): Pre-ship security gate for Supabase-backed apps enforcing RLS on every table, client/server secret zoning, and fail-closed webhooks. Use before shipping any change that adds or modifies tables, policies, server functions, secrets, or webhook handlers. Not for authoring migrations (use supabase-schema-discipline), money-specific review (use money-path-halt-go first), or full-codebase sweeps (use supabase-codebase-audit). Tags: rls, security, gate. Size: 5.6 KB.
  - [security-and-hardening](https://alexcinovoj.com/skills/security-and-hardening.md): Threat-model and harden web application code. Use when handling user input, authentication, sessions, file uploads, webhooks, secrets, third-party integrations, or LLM features, and when reviewing code for injection, XSS, SSRF, or access control gaps. Not for launch readiness and rollout: use shipping-and-launch. Not for auditing third-party skill packages: use skill-security-auditor. Tags: security, and, hardening. Size: 6.2 KB.
  - [supabase-codebase-audit](https://alexcinovoj.com/skills/supabase-codebase-audit.md): Systematic six-domain audit of an existing Supabase codebase covering RLS, edge functions, realtime, type safety, dead code, and CI/CD. Use when onboarding to a Supabase project, before a refactor or rebuild decision, after an incident, or for a periodic health review. Not for gating a single diff before ship (use rls-security-gate) or writing new migrations (use supabase-schema-discipline). Tags: supabase, codebase, audit. Size: 4.7 KB.
  - [supabase-schema-discipline](https://alexcinovoj.com/skills/supabase-schema-discipline.md): Rules for Supabase schema changes, structure plus GRANTs plus RLS plus policies in one migration, idempotency keys on side-effect tables, and no destructive migration without explicit confirmation. Use whenever creating or altering tables, columns, policies, functions, or triggers. Not for the pre-ship diff gate (use rls-security-gate), money-flow review (use money-path-halt-go), or auditing an existing schema (use supabase-codebase-audit). Tags: supabase, schema, discipline. Size: 5.6 KB.
  - [verification-before-completion](https://alexcinovoj.com/skills/verification-before-completion.md): Run the proving command and read its output before claiming anything works, passes, or is done. Use before saying complete, fixed, or passing, before commits, PRs, and task handoffs, and before trusting any subagent's success report. Not for finding why something fails: use systematic-debugging. Not for writing the tests themselves: use test-driven-development. Tags: verification, before, completion. Size: 4.4 KB.
  - [web-accessibility-wcag](https://alexcinovoj.com/skills/web-accessibility-wcag.md): Ship interactive UI to WCAG 2.1 AA, keyboard operability, focus management, ARIA name/role/state, and contrast, built on Radix primitive patterns. Use when building or reviewing dialogs, menus, tabs, comboboxes, tooltips, and forms, or when a surface must work without a mouse. Not for general stack conventions: use ui-engineering-stack-rules. Not for browser-matrix verification runs: use browser-visual-qa. Tags: web, accessibility, wcag. Size: 5.8 KB.
- Methodology & Process (13)
  - [brainstorming](https://alexcinovoj.com/skills/brainstorming.md): Turn a raw idea into an approved design before any code exists. Use before creating features, building components, adding functionality, or modifying behavior, whenever intent and requirements are not yet pinned down. Not for writing the implementation plan: use writing-plans after the design is approved. Not for validating finished work: use behavior-validator. Tags: brainstorming. Size: 5.8 KB.
  - [doubt-driven-development](https://alexcinovoj.com/skills/doubt-driven-development.md): Subject every non-trivial decision to a fresh-context adversarial review before it stands, while course-correction is still cheap. Use when correctness beats speed: unfamiliar code, production or security-sensitive logic, irreversible operations, or any confident claim that is cheaper to verify now than debug later. Not for post-hoc PR review: use a code review skill. Not for splitting independent work across agents: use dispatching-parallel-agents. Tags: doubt, driven, development. Size: 6.7 KB.
  - [executing-plans](https://alexcinovoj.com/skills/executing-plans.md): Execute a written implementation plan task by task with verification at every step. Use when a plan file exists and the work is now implementation, especially in a fresh session. Not for writing the plan: use writing-plans. Not for designing the feature: use brainstorming. Not for merge, PR, or cleanup decisions after the last task: use finishing-a-development-branch. Tags: executing, plans. Size: 4.2 KB.
  - [git-workflow-and-versioning](https://alexcinovoj.com/skills/git-workflow-and-versioning.md): Git discipline for every code change: atomic commits, short-lived branches, trunk-based flow, semver, tags, and changelogs. Use when committing, branching, resolving conflicts, organizing parallel work, cutting a release, or choosing a version bump. Not for the end-of-branch merge/PR/cleanup decision: use finishing-a-development-branch. Not for UI implementation itself: use frontend-ui-engineering. Tags: git, workflow, and, versioning. Size: 5.8 KB.
  - [product-pivot-research](https://alexcinovoj.com/skills/product-pivot-research.md): Six-phase method for rebuilding a failed or stalled product into a defensible V2, from failure analysis through migration map. Use when a product has stalled, the user says "pivot", "rebuild", "V2", "start over", or asks whether to salvage an existing codebase. Not for building a planned feature slice (use vertical-slice-builder) or auditing a live codebase's health (use supabase-codebase-audit). Tags: product, pivot, research. Size: 4.4 KB.
  - [receiving-code-review](https://alexcinovoj.com/skills/receiving-code-review.md): Discipline for responding to code review feedback: verify against the codebase before implementing, push back with evidence, no performative agreement. Use when review comments arrive on your work, before implementing any reviewer suggestion, or when feedback seems unclear or wrong. Not for asking for a review of your own work: use requesting-code-review. Not for performing a review of someone else's code. Tags: receiving, code, review. Size: 5.8 KB.
  - [requesting-code-review](https://alexcinovoj.com/skills/requesting-code-review.md): Dispatch a fresh-context reviewer subagent against a commit range before merging or moving on. Use when a task or feature is complete, before merge to main, after fixing a complex bug, or when stuck and needing fresh eyes. Not for handling the feedback you get back: use receiving-code-review. Not for final branch cleanup and merge mechanics: use finishing-a-development-branch. Tags: requesting, code, review. Size: 4.8 KB.
  - [source-driven-development](https://alexcinovoj.com/skills/source-driven-development.md): Ground every framework-specific implementation decision in current official documentation, with citations the user can check. Use when writing framework or library code where correctness depends on version, when building boilerplate that will be copied, or when the user asks for verified, documented patterns. Not for version-independent logic or renames. Not for planning documents: use writing-plans. Not for debugging existing failures: use systematic-debugging. Tags: source, driven, development. Size: 6.2 KB.
  - [spec-driven-development](https://alexcinovoj.com/skills/spec-driven-development.md): Write and gate a specification before any code exists. Use when starting a project or feature, when requirements are vague or only a rough idea, when a change spans multiple files, or before an architectural decision. Not for one-line fixes with self-contained scope. Not for the implementation plan itself: use writing-plans after the spec is approved. Tags: spec, driven, development. Size: 5.5 KB.
  - [systematic-debugging](https://alexcinovoj.com/skills/systematic-debugging.md): Find root cause before proposing any fix. Use on any bug, test failure, build failure, performance problem, or unexpected behavior, especially under time pressure or after a previous fix did not stick. Not for writing the failing test that reproduces the bug: use test-driven-development. Not for claiming the fix worked: use verification-before-completion. Tags: systematic, debugging. Size: 5.7 KB.
  - [test-driven-development](https://alexcinovoj.com/skills/test-driven-development.md): Write a failing test before any implementation code, for every feature and bugfix. Use when implementing new behavior, fixing bugs, or refactoring. Not for root-cause hunting on a mystery failure: use systematic-debugging first. Not for the final done-claim: use verification-before-completion. Exceptions (throwaway prototypes, generated code, config) need explicit human sign-off. Tags: test, driven, development. Size: 5.3 KB.
  - [using-git-worktrees](https://alexcinovoj.com/skills/using-git-worktrees.md): Set up an isolated workspace before feature work, preferring native platform worktree tools with a manual git worktree fallback. Use before executing implementation plans or any work that should not touch the current checkout. Not for writing the plan itself: use writing-plans. Not for task execution mechanics: use subagent-driven-development after the workspace exists. Tags: using, git, worktrees. Size: 5.1 KB.
  - [writing-plans](https://alexcinovoj.com/skills/writing-plans.md): Turn an approved spec into a task-by-task implementation plan an engineer with zero codebase context can execute. Use when you have a spec or requirements for a multi-step task, before touching code. Not for producing the spec: use brainstorming or spec-driven-development first. Not for executing the plan: use subagent-driven-development or executing-plans after the plan is saved. Tags: writing, plans. Size: 6.0 KB.
- Design & Motion (9)
  - [awwwards-2026](https://alexcinovoj.com/skills/awwwards-2026.md): Build editorial, award-tier public pages: opinionated type, asymmetric layout, one motion moment per viewport, ruthless copy reduction on a web-standards floor. Use when creating or restyling landing, marketing, portfolio, pricing, about, or blog index pages, or when asked for premium, editorial, studio-quality design. Not for internal app UI (admin, dashboard, settings, console, API routes). Not for measuring decay in an existing UI: use design-system-drift. Tags: awwwards, 2026. Size: 7.1 KB.
  - [design-engine](https://alexcinovoj.com/skills/design-engine.md): Generate on-brand visual assets with AI image models: surreal editorial graphics for social posts, quote cards, newsletter headers, and memes, produced as scored candidates with a selection record. Use when the user says "make a post graphic", "newsletter header", "image for this hook", or "brand visuals". Not for LinkedIn carousel decks: use linkedin-carousel-generator or linkedin-design. Not for templated meme-format batches: use viral-asset-templates. Tags: design, engine. Size: 5.0 KB.
  - [linkedin-carousel-generator](https://alexcinovoj.com/skills/linkedin-carousel-generator.md): Generate export-ready LinkedIn carousels as a single interactive HTML file with swipe preview and per-slide 1080x1080 PNG download. Use when the user asks for a carousel, LinkedIn slides, a swipeable post, or "make me slides." Not for banners, single post images, or other static LinkedIn assets: use linkedin-design. Not for newsletter copy: use inkwell. Tags: linkedin, carousel, generator. Size: 5.4 KB.
  - [linkedin-design](https://alexcinovoj.com/skills/linkedin-design.md): Create LinkedIn visual assets (banners, post images, PDF carousels, infographics, profile cards) via Canva MCP or code-generated PNG/PDF, with correct dimensions, safe zones, and mobile rules. Use when the user wants any static graphic destined for LinkedIn. Not for interactive HTML carousels with per-slide PNG export: use linkedin-carousel-generator. Not for video: use remotion-social-clips. Tags: linkedin, design. Size: 5.0 KB.
  - [premium-motion-ui](https://alexcinovoj.com/skills/premium-motion-ui.md): Build high-end animated marketing and product UI with Magic UI and Aceternity patterns on Motion (formerly Framer Motion): marquees, bento grids, animated beams, spotlight backgrounds, text reveals, scroll-linked motion. Use when a page needs crafted polish or a signature animated moment. Not for award-tier full-site art direction: use awwwards-2026. Not for responsive layout fundamentals: use mobile-first-responsive. Not for 3D scenes: use build-3d-website. Tags: premium, motion. Size: 5.5 KB.
  - [remotion-social-clips](https://alexcinovoj.com/skills/remotion-social-clips.md): Build short-form programmatic videos (product demos, explainers, reels, announcement clips) with Remotion, React components rendered to MP4. Use when the user wants a demo video, animated explainer, LinkedIn or Instagram video, promo clip, or motion graphics. Not for editing recorded talking clips into a captioned vertical video: use tiktok-forge. Not for static graphics: use viral-asset-templates. Tags: remotion, social, clips. Size: 4.3 KB.
  - [techtide-v0-ui-prompt-hardener](https://alexcinovoj.com/skills/techtide-v0-ui-prompt-hardener.md): Turn vague UI intent into a hardened v0 generation prompt with explicit data shapes, all five UI states, accessibility constraints, and a handoff review. Use when writing or fixing prompts for v0 or similar UI generators, or when generated UI keeps missing states and constraints. Not for taking prototypes to production (use techtide-lovable-production-handoff) or bootstrapping Replit apps (use techtide-replit-fullstack-bootstrap). Tags: techtide, prompt, hardener. Size: 4.4 KB.
  - [tiktok-forge](https://alexcinovoj.com/skills/tiktok-forge.md): Turn 3-5 short talking clips (~5s each) into a finished 1080x1920 TikTok with word-pop captions, emoji accents, stinger cards between clips, branded end cards, a beat bed, and a cover image. Use when the user says "make a TikTok," uploads short vertical talking clips for an edit, or wants a Reel or Short from the same inputs. Not for programmatic motion-graphics videos from scratch: use remotion-social-clips. Tags: tiktok, forge. Size: 6.5 KB.
  - [viral-asset-templates](https://alexcinovoj.com/skills/viral-asset-templates.md): Layout blueprints for single-image social graphics: stat callouts, comparison graphics, feature spotlights, testimonial cards, before/after, announcements, and mini infographics. Use when the user wants a graphic, post image, social card, or any one-slide visual. Not for multi-slide carousels: use linkedin-carousel-generator. Not for decks or one-pagers: use sales-asset-producer. Not for video: use remotion-social-clips. Tags: viral, asset, templates. Size: 3.9 KB.
- Content & Publishing (8)
  - [beehiiv](https://alexcinovoj.com/skills/beehiiv.md): Subscribe contacts to a Beehiiv newsletter publication via the Beehiiv v2 API, from forms, scripts, or automations. Use when pushing email addresses into Beehiiv, adding subscribers programmatically, or wiring a signup form to a publication. Not for publishing to Ghost, Substack, or Listmonk: use ghost-publisher, substack-publisher, or listmonk-publisher. Not for writing the newsletter content: use copywriting or emails. Tags: beehiiv. Size: 4.4 KB.
  - [content-strategy](https://alexcinovoj.com/skills/content-strategy.md): Plan content strategy, pick pillars, and prioritize topics backed by customer research. Use when the user says "content strategy", "what should I write about", "topic clusters", "editorial calendar", "content pillars", or "blog strategy". Not for writing individual pieces: use a copywriting skill. Not for SEO audits: use claude-seo. Not for competitor comparison pages: use competitors. Tags: content, strategy. Size: 4.5 KB.
  - [copy-editing](https://alexcinovoj.com/skills/copy-editing.md): Edit and improve existing marketing copy through focused sequential passes. Use when the user says "edit this copy", "review my copy", "tighten this up", "polish this", "too wordy", "sharpen the messaging", or "refresh this content". Not for writing new copy from scratch: use copywriting. Not for page structure or conversion strategy: use cro. Not for gathering customer language first: use customer-research. Tags: copy, editing. Size: 4.3 KB.
  - [ghost-publisher](https://alexcinovoj.com/skills/ghost-publisher.md): Deploy and publish on Ghost, the open-source CMS with built-in newsletter and memberships. Use when moving a publication off a hosted platform, publishing via the Ghost Admin API, or deciding whether Ghost is the right migration target. Not for a lightweight self-hosted list without a CMS: use listmonk-publisher. Not for hosted newsletter operations: use beehiiv. Tags: ghost, publisher. Size: 3.9 KB.
  - [inkwell](https://alexcinovoj.com/skills/inkwell.md): Ghostwrite AI-newsletter content (full issue, lead story, tool roundup, essay, subject line, hook) in the voice of a named top AI newsletter such as The Rundown, TLDR AI, The Batch, One Useful Thing, or SemiAnalysis. Use when the user wants newsletter or AI-news copy, or says "write this like <writer>." Not for LinkedIn carousels (use linkedin-carousel-generator) or general marketing copy. Tags: inkwell. Size: 5.6 KB.
  - [listmonk-publisher](https://alexcinovoj.com/skills/listmonk-publisher.md): Deploy and operate Listmonk, the self-hosted open-source newsletter engine, as a sovereign email list with custom segmentation. Use when evaluating or running a self-hosted list, wiring an SMTP relay, or deciding hosted vs self-hosted newsletter infrastructure. Not for a full CMS with memberships and a website: use ghost-publisher. Not for hosted newsletter operations, monetization, and ad network: use beehiiv. Tags: listmonk, publisher. Size: 4.3 KB.
  - [medium-publisher](https://alexcinovoj.com/skills/medium-publisher.md): Publish long-form articles to Medium via browser automation, with canonical URLs pointing back to your own domain. Use when the user says "post to Medium", "republish on Medium", or "syndicate this article". Not for newsletter platforms: use beehiiv, substack-publisher, ghost-publisher, or listmonk-publisher. Not for writing the article itself: use a content or copywriting skill. Tags: medium, publisher. Size: 4.3 KB.
  - [substack-publisher](https://alexcinovoj.com/skills/substack-publisher.md): Prepare Substack-ready long-form drafts and publish them through the web editor, since Substack has no official public write API. Use for essays over 1000 words, builder stories that benefit from Substack's network, or paid-subscription content. Not for unattended API publishing: use beehiiv or ghost-publisher. Not for mirroring posts to email lists: use listmonk-publisher on the RSS feed. Tags: substack, publisher. Size: 4.0 KB.
- Build & Implementation (6)
  - [frontend-ui-engineering](https://alexcinovoj.com/skills/frontend-ui-engineering.md): Build production-quality UI: components, layouts, state, accessibility, and polish that does not look AI-generated. Use when building or modifying user-facing interfaces, creating components, implementing responsive layouts, or fixing visual and UX issues. Not for commit and branch discipline around the change: use git-workflow-and-versioning. Not for pure design review without code. Tags: frontend, engineering. Size: 5.1 KB.
  - [mobile-first-responsive](https://alexcinovoj.com/skills/mobile-first-responsive.md): Build and audit mobile-first responsive UI in React + Tailwind + shadcn/ui. Use when creating any new page or surface, or when the user says "mobile", "responsive", "touch", "breakpoints", "safe area", "works on phones", or reports a phone-only layout bug. Not for desktop-only admin consoles (confirm that scope first), and not for 3D canvas tuning: use build-3d-website. Tags: mobile, first, responsive. Size: 4.7 KB.
  - [shadcn-component-architecture](https://alexcinovoj.com/skills/shadcn-component-architecture.md): Build and extend UI with the shadcn/ui copy-paste registry pattern on Radix primitives, cva variants, and CSS-variable tokens. Use when scaffolding a component library, adding or theming shadcn components, wiring design tokens, or extending variants. Not for auditing token drift across an existing system: use design-system-drift. Not for responsive layout strategy: use mobile-first-responsive. Tags: shadcn, component, architecture. Size: 5.7 KB.
  - [techtide-replit-fullstack-bootstrap](https://alexcinovoj.com/skills/techtide-replit-fullstack-bootstrap.md): Bootstrap a Replit full-stack project with an explicit app contract, env variable model, smoke-test loop, and a planned migration path to a durable repo. Use when starting or restructuring a Replit project, or writing a Replit bootstrap prompt. Not for extracting a Lovable prototype (use techtide-lovable-production-handoff) or UI-generation prompt specs (use techtide-v0-ui-prompt-hardener). Tags: techtide, replit, fullstack, bootstrap. Size: 3.9 KB.
  - [ui-engineering-stack-rules](https://alexcinovoj.com/skills/ui-engineering-stack-rules.md): House conventions for the frontend stack, Next.js App Router, React 19, TypeScript strict, Tailwind tokens, shadcn/ui, and Motion. Use before writing any React so output reads as authored by one team, and when bootstrapping a new frontend. Not for accessibility rules: use web-accessibility-wcag. Not for component API design: use shadcn-component-architecture. Not for animation craft: use premium-motion-ui. Not for verification runs: use browser-visual-qa. Tags: engineering, stack, rules. Size: 5.6 KB.
  - [vertical-slice-builder](https://alexcinovoj.com/skills/vertical-slice-builder.md): Build one user-visible feature slice end-to-end, spec, plan, build, verify, pin, with routes, server functions, schema, and RLS shipped together. Use when the user provides a slice spec or says "build this slice", "ship this feature", "do the next slice". Not for cross-cutting refactors, schema-only work (use supabase-schema-discipline), or product-direction resets (use product-pivot-research). Tags: vertical, slice, builder. Size: 4.4 KB.
- 3D & Games (5)
  - [build-3d-game](https://alexcinovoj.com/skills/build-3d-game.md): Architecture for multi-mechanic, persistent 3D browser games in React Three Fiber: system/view separation, fixed-timestep loop, AI state machines, instancing, cloud saves. Use when building open-world exploration, gathering loops, mounts, enemy AI, inventory, or leaderboards. Not for marketing 3D heroes: use build-3d-website. Not for world polish or character/horse systems: use high-end-browser-western and high-end-character-and-horse. Tags: build, game. Size: 6.1 KB.
  - [build-3d-website](https://alexcinovoj.com/skills/build-3d-website.md): Build interactive 3D marketing sites with React Three Fiber and drei: 3D heroes, floating objects, tilt cards, scroll-driven scenes, WebGL showcases. Use when asked for a 3D landing page, WebGL hero, immersive explorer, or a premium wow page, or on mentions of three.js, R3F, tilt card. Not for playable games with mechanics, AI, or saves: use build-3d-game. Tags: build, website. Size: 4.6 KB.
  - [high-end-browser-western](https://alexcinovoj.com/skills/high-end-browser-western.md): Research-to-production workflow for a polished browser 3D open world on React, Three.js, R3F, and Supabase: benchmarking, one deeply polished map, narrative, license-checked assets, performance budgets. Use when building a systemic open-world web game or judging browser 3D experiences. Not for engine mechanics (loop, ECS, saves): use build-3d-game. Not for character or horse systems: use high-end-character-and-horse. Not for marketing scenes: use build-3d-website. Tags: high, end, browser, western. Size: 7.0 KB.
  - [high-end-character-and-horse](https://alexcinovoj.com/skills/high-end-character-and-horse.md): Build production-grade playable characters and rideable horses for browser 3D games: frozen rig contracts, modular parts, material budgets, animation state machines, hoof IK, rider sync, validated persistence, selection UX. Use when a project needs character selection or customization, a hero horse, or mounted locomotion. Not for world, map, or asset-sourcing strategy: use high-end-browser-western. Not for engine loop discipline: use build-3d-game. Tags: high, end, character, and. Size: 8.5 KB.
  - [react-three-webgl](https://alexcinovoj.com/skills/react-three-webgl.md): React Three Fiber and drei implementation reference: scenes, cameras, lighting, GLTF loading, scroll-linked 3D, post-processing, performance budgets, fallbacks. Use when writing or reviewing R3F/three.js code for a hero object, configurator, 3D data viz, or ambient background. Not for the end-to-end 3D marketing site workflow: use build-3d-website. Not for playable games with mechanics or saves: use build-3d-game. Tags: react, three, webgl. Size: 5.2 KB.
- Architecture (4)
  - [ai-provider-integration](https://alexcinovoj.com/skills/ai-provider-integration.md): Contracts for integrating paid AI/ML providers behind swappable adapters: typed interfaces, idempotent job lifecycle, cost reservation, retry classes, health monitoring. Use when adding a model vendor, wiring paid generation APIs, handling provider webhooks, or tracking per-generation spend. Not for writing prompts that direct AI coding tools: use ai-tool-directive. Tags: provider, integration. Size: 4.8 KB.
  - [api-and-interface-design](https://alexcinovoj.com/skills/api-and-interface-design.md): Design stable interfaces that are hard to misuse. Use when creating REST or GraphQL endpoints, defining type contracts between modules, designing component props, or changing any public interface. Not for retiring or breaking an existing contract: use deprecation-and-migration. Not for provider adapter patterns around paid AI APIs: use ai-provider-integration. Tags: api, and, interface, design. Size: 4.8 KB.
  - [deprecation-and-migration](https://alexcinovoj.com/skills/deprecation-and-migration.md): Plan and execute the removal of old systems, APIs, or features and migrate consumers safely to replacements. Use when sunsetting a feature, replacing a library or service, consolidating duplicate implementations, or deciding whether to maintain or kill legacy code. Not for recording the decision rationale: use documentation-and-adrs. Not for reviewing the replacement's code quality: use a code review skill. Tags: deprecation, and, migration. Size: 5.3 KB.
  - [documentation-and-adrs](https://alexcinovoj.com/skills/documentation-and-adrs.md): Record architecture decision records, inline documentation, API docs, READMEs, and changelogs that capture why decisions were made. Use when making an architectural choice, changing a public API, shipping a feature, or when the same explanation keeps getting repeated. Not for deciding whether to remove a system: use deprecation-and-migration. Not for adversarial review of the decision itself: use doubt-driven-development. Tags: documentation, and, adrs. Size: 5.0 KB.
- Delivery & Handoff (4)
  - [ci-cd-and-automation](https://alexcinovoj.com/skills/ci-cd-and-automation.md): Set up and enforce CI/CD pipelines: quality gates, test runners in CI, deployment strategies, rollback. Use when creating or modifying build and deploy pipelines, adding automated checks, or debugging CI failures. Not for writing the tests themselves: use test-driven-development. Not for diagnosing an app bug CI surfaced: use systematic-debugging. Not for branch and merge mechanics: use git-workflow-and-versioning. Tags: and, automation. Size: 6.1 KB.
  - [finishing-a-development-branch](https://alexcinovoj.com/skills/finishing-a-development-branch.md): Close out a completed development branch: verify tests, then present merge, PR, keep, or discard options and execute the choice with safe worktree cleanup. Use when implementation is done and the work needs integrating. Not for executing the plan itself: use executing-plans. Not for commit and branching discipline during development: use git-workflow-and-versioning. Tags: finishing, development, branch. Size: 5.1 KB.
  - [shipping-and-launch](https://alexcinovoj.com/skills/shipping-and-launch.md): Prepare and execute production launches with pre-launch checks, feature flags, staged rollout, monitoring, and a rollback plan. Use when deploying to production, planning a canary or beta, migrating data, or writing a rollback strategy. Not for hardening code against vulnerabilities: use security-and-hardening. Not for CI pipeline setup: use ci-cd-and-automation. Tags: shipping, and, launch. Size: 6.0 KB.
  - [techtide-lovable-production-handoff](https://alexcinovoj.com/skills/techtide-lovable-production-handoff.md): Convert a Lovable prototype into a repo-owned production candidate by inventorying, replacing mocks, and adding tests and deployment gates. Use when a prototype needs to leave Lovable for a real repo, CI, and production. Not for starting new Replit projects (use techtide-replit-fullstack-bootstrap), hardening v0 UI prompts (use techtide-v0-ui-prompt-hardener), or packaging skills for Lovable (use lovable-native-packaging-bridge). Tags: techtide, lovable, production, handoff. Size: 4.2 KB.

HTML index: https://alexcinovoj.com/skills