niahere

Generate images using OpenAI (default) or Gemini. Use when asked to generate, create, or make images. Supports text-to-image and image editing with reference images.

Plans, audits, and implements scalable programmatic SEO systems with URL inventory, intent mapping, metadata, schema, internal linking, sitemaps, ISR/static rendering, and quality gates. Use when the user mentions 'programmatic SEO,' 'pSEO,' '100k pages,' 'generate SEO pages,' 'scaled landing pages,' 'template pages,' 'SEO page factory,' 'dynamic SEO routes,' 'sitemap shards,' 'keyword cannibalization,' 'doorway pages,' or 'thin content at scale.' Does not replace general SEO audits, AI SEO citation work, or llms.txt tasks unless PSEO scale is central.

Use when setting up, deploying, or debugging Nia's Twilio-based channels: voice (phone), SMS, and WhatsApp. All three share one Twilio number, one webhook server, and one set of credentials under channels.twilio. Covers config schema, cloudflared named-tunnel setup, Twilio Console webhook wiring, `nia phone` CLI, `place_call` / `send_message` MCP tools, the WhatsApp Sandbox 24h customer-service window, and the shared TwilioWebhookServer's dedup + rate-limit middleware. Trigger on mentions of "phone", "call", "voice", "sms", "whatsapp", "twilio", "realtime", "media stream", "cloudflared", or when deploying Nia to a new machine and a Twilio surface needs to come up.

Persistent task management via Beads CLI (bd). Use when user mentions tasks, todos, issues, or tracking work. Check `which bd` first — if missing, offer: `npm install -g @beads/bd`. All commands: run from `$BEATS_DIR` (for example `~/.niahere/beads`) and use `bd <command>`. Always label: `--label project:<project-name>`. Run `bd --help` or `bd help --all` for available commands. Not for ephemeral in-conversation tracking.

QA test a web application using Playwright. Use when asked to "qa", "QA", "test this site", "find bugs", "dogfood", "verify frontend behavior", "check UI rendering", "test user flows", "debug visual issues", "take a snapshot", "take a screenshot", "browser automation", "Playwright MCP", "ref system", or review quality of any web app (local or deployed). Five modes: diff-aware (auto on feature branches), full (systematic exploration), quick (30-second smoke test), single-page (verify one page or component), regression (compare against baseline). Produces structured report with health score, screenshots, and repro steps. Uses Playwright MCP tools or CLI fallback. Includes Playwright MCP reference (tool selection, ref system, token optimization, session management).

Transcribe or subtitle audio/video files using whisper.cpp (whisper-cpp), with a default medium model path and ffmpeg-based extraction.

Create beautiful, performant SVG animations and illustrations. Use this skill when the user asks to create SVG graphics, icons, illustrations, animated logos, path animations, morphing shapes, loading spinners, or any animated SVG content. Covers SMIL animations, CSS-driven SVG animation, path drawing effects, shape morphing, motion paths, gradients, masks, and filters.

Review pull requests, code diffs, and changes for correctness, design, security, performance, and style. Use when asked to 'review this PR,' 'review my changes,' 'check this diff,' or before merging code. Also use for pre-landing safety checks before shipping. Language-aware — adapts to the project's stack, idioms, and conventions.

When the user wants to optimize conversions at any stage of the funnel — marketing pages, signup flows, or post-signup onboarding. Also use when the user mentions 'CRO,' 'conversion rate optimization,' 'this page isn't converting,' 'improve conversions,' 'low conversion rate,' 'bounce rate,' 'signup conversions,' 'registration friction,' 'signup form optimization,' 'people aren't signing up,' 'signup abandonment,' 'onboarding flow,' 'activation rate,' 'user activation,' 'first-run experience,' 'empty states,' 'users sign up but don't use the product,' 'time to value,' 'nobody completes setup,' 'reduce signup dropoff,' or 'this page needs work.' Use this even if the user just shares a URL and asks for feedback.

Guide for building frontend UIs, web pages, dashboards, and any user-facing interface with intentional design (not AI slop). Also covers creating and maintaining DESIGN.md files — the universal design language that captures a project's complete visual identity (colors, typography, spacing, layout, components) in structured markdown. Use when: building HTML pages, landing pages, dashboards, web apps, creating a design system, extracting design tokens, making a DESIGN.md, auditing design consistency, or any task involving a project's visual language.

Create or improve AI agent skills with proper progressive disclosure, description optimization, and router patterns. Use when building a new skill, updating an existing one, merging related skills into a router, auditing skill quality, or improving skill activation rates. Also use when the user mentions 'create a skill,' 'write a skill,' 'new skill,' 'skill template,' 'improve this skill,' 'skill isn't triggering,' 'merge these skills,' or 'skill architecture.'

Use this skill for App Store Connect CLI (`asc`) usage, including install/auth setup, command families, CI/CD integration, and troubleshooting for releases, builds, TestFlight, metadata, signing, finance, and analytics workflows.

Consult OpenAI Codex CLI for a second opinion on plans, tests, code review, and more. Use this skill automatically whenever a second perspective would strengthen your output — especially for architectural plans, code review, test strategy, and debugging.

When the user wants to plan a content strategy, decide what content to create, figure out what topics to cover, or needs marketing ideas, growth tactics, and brainstorming. Also use when the user mentions 'content strategy,' 'what should I write about,' 'content ideas,' 'blog strategy,' 'topic clusters,' 'content planning,' 'editorial calendar,' 'content marketing,' 'content roadmap,' 'what content should I create,' 'blog topics,' 'content pillars,' 'I don't know what to write,' 'marketing ideas,' 'growth ideas,' 'how to market,' 'marketing strategies,' 'marketing tactics,' 'ways to promote,' 'ideas to grow,' 'what else can I try,' 'I don't know how to market this,' 'brainstorm marketing,' or 'what marketing should I do.' For writing individual pieces, see copywriting. For SEO-specific audits, see seo. For social media content specifically, see the marketing skill's social-content mode.

When the user wants to write, rewrite, edit, review, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says 'write copy for,' 'improve this copy,' 'rewrite this page,' 'marketing copy,' 'headline help,' 'CTA copy,' 'value proposition,' 'tagline,' 'subheadline,' 'hero section copy,' 'above the fold,' 'this copy is weak,' 'make this more compelling,' 'help me describe my product,' 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,' 'make this better,' 'copy sweep,' 'tighten this up,' 'this reads awkwardly,' 'clean up this text,' 'too wordy,' or 'sharpen the messaging.' For email copy, see the email skill.

When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," or "find out why customers churn/convert/buy." Use for both analyzing existing research assets AND gathering new research from online sources. For writing copy informed by research, see copywriting. For acting on research to improve pages, see cro.

Create, read, edit, or manipulate Word (.docx) and PowerPoint (.pptx) documents. Use when the user mentions 'Word doc,' '.docx,' 'presentation,' 'slides,' 'deck,' '.pptx,' 'report,' 'memo,' 'letter,' 'pitch deck,' or any task involving office documents. Covers creation from scratch, editing existing files, XML manipulation, tracked changes, images, formatting, and design. Do NOT use for PDFs, spreadsheets, or Google Docs.

Write any kind of email: cold outreach, prospecting, follow-up sequences, drip campaigns, lifecycle emails, nurture sequences, onboarding emails, welcome series, re-engagement emails, or email automation. Use when the user mentions 'cold email,' 'cold outreach,' 'prospecting email,' 'outbound email,' 'email to leads,' 'reach out to prospects,' 'sales email,' 'follow-up email sequence,' 'SDR emails,' 'nobody is replying to my emails,' 'how do I write a cold email,' 'email sequence,' 'drip campaign,' 'nurture sequence,' 'onboarding emails,' 'welcome sequence,' 're-engagement emails,' 'email automation,' 'lifecycle emails,' 'trigger-based emails,' 'email funnel,' 'email workflow,' 'what emails should I send,' 'welcome series,' or 'email cadence.'

Stamp a GitHub PR with an LGTM approval comment. Use when someone wants to approve, stamp, or give a thumbs-up to a pull request.

When the user wants help with marketing, growth, GTM, or getting users. Covers pricing strategy, competitor comparison pages, social media content, product launches, and churn prevention. Also use when the user mentions 'marketing,' 'growth,' 'GTM,' 'go-to-market,' 'how to get users,' 'marketing strategy,' 'pricing,' 'competitor page,' 'vs page,' 'alternative page,' 'social media,' 'LinkedIn post,' 'Twitter thread,' 'launch,' 'Product Hunt,' 'churn,' 'cancel flow,' 'dunning,' 'retention,' 'failed payments,' or 'how do I market this.' For copywriting, CRO, SEO, email, content strategy, and customer research, use the dedicated top-level skills.

Unified plan review skill with three lenses. Use when reviewing a plan, strategy, or decision — whether from a CEO/founder strategic perspective, engineering rigor perspective, or minimalist entrepreneur perspective. Triggers: plan review, review my plan, challenge this plan, gut-check, simplify this, scope check, 10-star product, architecture review, test coverage review, edge cases, minimalist review, business decision review.

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 "retro", "retrospective", "how did the week go", or "review my commits".

When the user wants to improve search visibility — traditional SEO audits, AI search optimization, or llms.txt creation. Use when the user mentions 'SEO,' 'technical SEO,' 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'generative engine optimization,' 'LLM optimization,' 'AI Overviews,' 'optimize for ChatGPT,' 'optimize for Perplexity,' 'AI citations,' 'AI visibility,' 'zero-click search,' 'LLM mentions,' 'optimize for Claude/Gemini,' 'SEO audit,' 'why am I not ranking,' 'SEO issues,' 'on-page SEO,' 'meta tags review,' 'SEO health check,' 'my traffic dropped,' 'lost rankings,' 'not showing up in Google,' 'site isn't ranking,' 'Google update hit me,' 'page speed,' 'core web vitals,' 'crawl errors,' 'indexing issues,' 'llms.txt,' 'llms-full.txt,' 'LLM-aware indexing,' 'AI retrieval,' or 'my SEO is bad.'

Comprehensive Shopify app skill. Use when scaffolding a new Shopify app, choosing tech stack, setting up extensions, billing, webhooks, planning app store launch, preparing an app store listing, writing submission copy, or filling out the Partner Dashboard form.

Use this skill for Cloudflare Wrangler CLI usage, project setup, development, deployment, secrets, observability, pages/R2/Queues/D1 workflows, and CI/CD authentication. Trigger for `wrangler` command guidance and official command references.

The iterative optimization pattern (Karpathy Loop / autoresearch). Reference for running autonomous experiment loops on any target: modify → score → keep or revert → repeat. Use when running multiple iterations of improvement against a measurable metric — code benchmarks, prompt quality, copy effectiveness, config tuning, or any scorable target. Also known as "autoresearch." Use this skill to understand the pattern and discipline. For orchestration (scheduling, user confirmation, job setup), see the "optimize" skill.

Schedule or run an iterative optimization pass on code, prompts, copy, or any scorable target. Use when user asks to "optimize this", "run experiments", "autoresearch this", "iterate on this overnight", "can this be better", or proactively suggest after completing work that could benefit from further iteration. Also use when a job wants to self-optimize something within its own run. Handles spec confirmation, scoring setup, job scheduling, and result delivery. For the loop discipline itself, references the optimization-loop skill.

Use this skill for AWS CLI usage, command references, and common workflows (S3, DynamoDB, IAM, STS, SSO, Lambda, CloudWatch, OpenSearch). Trigger this for questions about what `aws` commands do, which subcommands to use, and where to find authoritative docs.

Use when user wants to interact with Google Workspace APIs (Gmail, Drive, Calendar, Sheets, Docs, Chat, Admin) from the command line using `gws`. Also use when setting up Google Workspace CLI, OAuth for Google APIs, or automating Google Workspace tasks. Check `which gws` first — if missing, offer install.

Completion guard that prevents premature task abandonment. Use when wrapping up any non-trivial task, before claiming work is "done", or when you catch yourself writing a summary instead of finishing the work. Also use when the user says "don't stop early", "finish everything", "make sure it's actually done", or "verify completion". Adapted from github.com/blader/taskmaster.

Best practices for Remotion — programmatic video creation in React. Use when working with Remotion code, creating video compositions, adding animations, captions, audio, or rendering video.

YC-style office hours. Two modes — Startup: six forcing questions that expose demand reality, status quo, desperate specificity, narrowest wedge, observation, and future-fit. Builder: design thinking for side projects, hackathons, and learning. Use when asked to "brainstorm", "I have an idea", "help me think through this", "office hours", or "is this worth building".

Explore a GitHub repository from a link by cloning locally first, then inspecting files and history. Use when a task includes a GitHub repo URL or owner/repo and code-level analysis is needed. Prefer local clone into /tmp before using web pages.

Render CLI for deploying and managing services, databases, and blueprints on Render. Use when user mentions render, deploying to render, render services, or render databases. Check `which render` first — if missing, offer: `brew install render` (macOS) or curl installer. Covers deploys, services, SSH, psql, blueprints, and CI workflows.

Modal CLI for serverless GPU/cloud compute. Use when user mentions modal, deploying to modal, running GPU workloads, or serverless Python functions. Check `which modal` first — if missing, offer: `pip install modal && modal setup`. Covers run/serve/deploy, apps, containers, secrets, volumes, and workspace management.

Atomic Slack primitives for agents. Send, reply, DM, read history, threads, list channels/users, search, react. Use when you need to interact with Slack.

This skill should be used when the user asks to "generate a Nia image", "create a profile picture for Nia", "update Nia's avatar", "make a new Nia photo", or needs to generate images of Nia with consistent identity using Gemini image generation.