lucasyhzhu-debug
UserIndex of Lucas Zhu's open-source Claude Code skills
Categories
Indexed Skills (11)
ai-seo
When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. Also use when the user mentions '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,' 'how do I show up in AI answers,' 'LLM mentions,' 'optimize for Claude/Gemini,' 'llms.txt,' 'OKF,' 'Open Knowledge Format,' 'knowledge bundle,' or 'agent-readable site.' Use this whenever someone wants their content to be cited or surfaced by AI assistants and AI search engines. For traditional technical and on-page SEO audits, see seo-audit. For structured data implementation, see schema.
seo-audit
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "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," or "indexing issues." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo.
ai-seo
When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. Also use when the user mentions '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,' 'how do I show up in AI answers,' 'LLM mentions,' 'optimize for Claude/Gemini,' 'llms.txt,' 'OKF,' 'Open Knowledge Format,' 'knowledge bundle,' or 'agent-readable site.' Use this whenever someone wants their content to be cited or surfaced by AI assistants and AI search engines. For traditional technical and on-page SEO audits, see seo-audit. For structured data implementation, see schema.
seo-audit
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "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," or "indexing issues." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo.
auditing-site-navigation
Use when auditing a website's navigation, information architecture, or usability, or when overhauling it and intending to claim a measurable before/after improvement. Also use when scoring a site per-persona, or dispatching UI fixes to parallel agents.
crafting-portfolio-essays
Use when writing, editing, or reviewing personal essays, portfolio copy, or magazine-style longform where authorial voice matters. Triggers on words like essay, voice, tone, longform, portfolio writing, magazine, deck/dek, pull quote, "in my voice", "make it sound like me". Especially relevant when AI-averaged prose would be the failure mode.
fresh
Use when the user wants a prompt, plan, or message to execute exactly when the next Claude 5-hour usage-limit window resets — e.g. "/fresh <prompt|file> [--clear]", "run this at my next reset", "start the plan when my limit resets", "queue this for when usage resets". Also when rate-limited and wanting work to auto-start the moment quota returns.
proofing-room
Use when someone wants to review, proof, comment on, mark up, draw on, or collect feedback on an HTML page, static site, landing page, slide deck, or generated report — and feed that feedback back to an agent. Drops a self-contained wrapper onto any HTML so reviewers pin comments, edit copy in place, and draw boxes/arrows/freehand marks to show what they mean, then export an anchored JSON (plus a replay file an agent screenshots) an agent can action. No backend, no build step. Triggers include "add review/proofing mode", "let me comment on this page", "let me draw on this slide", "show you exactly where this goes", "collect feedback on this HTML", "make this markup-able", or "turn review notes into a JSON for an agent".
shipshape
Review implementation plans from the perspective of two senior engineers (Staff and Principal) to catch issues before a single line of code gets written
triple-persona-review
Use when reviewing a draft (essay, pitch deck, marketing copy, ADR, README, talk script, proposal) for cross-audience editorial pressure — dispatches three calibrated reader personas in parallel and consolidates their feedback into a prioritised editing report. Triggers on phrases like "review my draft", "what would my audience think", "is this ready to ship", "audience review", "persona review", "editorial pressure-test", "triple review". Personas pull from a reusable library and are calibrated over rounds.
higgsfield-brief-to-pipeline
Use when you have a brief of desired outputs plus a folder/set of reference images and want Claude to design and run an optimal Higgsfield generation workflow — for product/spec/scene/booth/ad/character image (or video) batches where credit cost and fidelity-to-spec both matter. Triggers: "here's a brief and some references", "make these deliverables from this folder", "design the higgsfield workflow", "render this to spec cheaply".
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.