Results for “pattern”

Plans and audits SEO pages generated at scale from data sources, covering template design, URL patterns, internal linking, thin content safeguards, and index bloat prevention.

Extract and analyze competitor advertising from public ad libraries (Facebook Ad Library, Google Ads Transparency Center, TikTok, LinkedIn). Identifies messaging patterns, creative formats, pain points targeted, and positioning gaps. Use for competitive intelligence, campaign planning, and creative inspiration.

Design high-converting marketing emails with layout patterns, subject line formulas, and deliverability rules. Covers welcome sequences, promotional emails, transactional templates, and mobile optimization.

Analyzes Mintlify's design system, documenting its dual-mode aesthetic of atmospheric marketing heroes and dense developer documentation surfaces, including color tokens, typography hierarchy, and layout patterns.

Documents the PlayStation marketing design system with three alternating canvas modes, PlayStation SST typography at weight 300, and a restrained chrome vocabulary where imagery occupies 60-90% of each section.

Analyzes recent Claude Code chat history to identify coding patterns, development gaps, and areas for improvement, curates relevant learning resources from HackerNews, and sends a personalized growth report to Slack DMs.

Analyze and recreate the visual design language of Voltagent, a developer-focused AI agent engineering platform, including its dark canvas, electric-green accent, typography system, and layout patterns.

Selects pricing models (subscription, usage-based, value-based, freemium, hybrid), analyzes willingness-to-pay survey data with Van Westendorp PSM, and designs Good/Better/Best packaging tiers with anti-pattern detection.

Discovers competitors via search API, deeply researches each with a multi-lane pattern, and compiles an HTML report with overview, per-competitor deep dives, feature/pricing matrix, and mentions feed.

Extracts and analyzes competitors' ads from ad libraries (Facebook, LinkedIn, etc.) to understand what messaging, problems, and creative approaches are working, helping inspire and improve your own ad campaigns.

Klaviyo API and developer integration expertise. Event tracking, SDKs, webhooks, rate limits, OAuth, catalog sync, and code patterns. Use when the user asks about Klaviyo API, integrating with Klaviyo, tracking events, building custom integrations, webhook handling, or developer implementation. For marketing strategy, flow optimization, and campaign auditing, see the klaviyo-analyst skill.

Layer 4 of the keyword research pipeline. Spawns a "skeptical SEO" adversarial sub-agent to argue against every survivor of Layers 1-3. Catches mechanical-classifier blind spots — wrong SERP intent, hidden link-graph gauntlets, AIO trajectory shifts, vanity-rank metrics. Same pattern as quality-check's adversarial draft read, applied to keyword selection.

Google and Meta paid media account structure evaluation. Audits campaign/ad set architecture against conversion volume minimums, budget thresholds, and targeting overlap. Identifies over-segmentation, under-segmentation, budget fragmentation, and structural anti-patterns blocking algorithmic learning. Provides consolidation roadmaps with migration plans. Use when inheriting accounts, quarterly health checks, or before scaling budgets.

Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas. Use when asked to "weekly retro", "what did we ship", or "engineering retrospective". Proactively suggest at the end of a work week or sprint. (gstack)

Composite skill — full SEO + Accessibility audit of a website or webapp in one workflow. Chains audit-website (squirrelscan SEO + tech + perf scan) + seo-audit (SEO framing) + playwright-best-practices (axe-core a11y) + ui-audit (design-system accessibility patterns) → reconciled severity-ranked report split by SEO vs A11y vs Both. Use for periodic site health checks, pre-launch audits, or when search rankings drop.

Executable documentation governance with compound engineering and abductive learning. Enforces the Seven Laws through type compilation, schema validation, and hookify-based enforcement. Implements programmatic compound engineering where K' = K ∪ crystallize(assess(τ)) for monotonic knowledge growth. Integrates abstracted abductive learning (OHPT protocol) for systematic debugging and pattern extraction. Trigger when writing code, debugging, establishing governance, or when mentioned vibecode, compound, abductive, or executable documentation. Self-validating and homoiconic.

Set your brand voice and tone so every AI output sounds like you, not like generic AI. Names the voice pillars, the tone by context, the words you use and the ones you never do, and gives sample lines the model can pattern-match. Feeds the voice layer of the context repo so every skill writes in your voice. Fire on "define our brand voice", "brand and tone", "how should we sound", "voice guide", "make it sound like us", or the start of building a GTM context repo.

Use when the user wants to clone, replicate, rebuild, reverse-engineer, or copy any website — or says 'make a copy of this site', 'rebuild this page', 'pixel-perfect clone'. Reverse-engineers one or more sites in one shot: extracts assets, CSS, and content section-by-section, then proactively dispatches parallel builder agents in worktrees as it goes (foreman pattern, not inspect-then-build). Provide one or more target URLs as arguments; requires browser automation (Chrome MCP/Playwright/Browserbase/Puppeteer). Pixel-perfect fidelity default: visual layout, styling, components, responsive design, mock data — NOT real backend/auth/real-time/SEO/accessibility unless specified.

Strip AI-generated tells from a draft and rewrite it in Heath's personal voice (GTM Juice). Fire whenever the user asks to "humanize", "de-AI", "clean up", "rewrite in my voice", "make this sound like me", "kill the AI tells", or "polish this draft". Also fires as the mandatory final pass inside juice-content-dispatch — every LinkedIn post, newsletter, and video script drafted there must run through this skill before the Notion write. Applies the 29-pattern Wikipedia "Signs of AI writing" catalog (em dashes, significance inflation, promotional language, rule of three, synonym cycling, inline-header lists, sycophantic tone, hyphenated word pairs, persuasive-authority tropes, signposting, etc.), then applies a hardcoded Heath-voice calibration: self-implicating first, failure-derived, plain declaratives over bumper-sticker aphorisms, no bow-tied endings, never Mixmax corporate brand voice. Forked from blader/humanizer (MIT).