Explore skills
Showing 65881–65910 of 71536 skills
When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' or wants to avoid repeating foundational information across marketing tasks. Creates `.claude/product-marketing-context.md` that other marketing skills reference.
cbbkrd-tech/jl-finishes
Stars: 0Claude CodeCodexWhen the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy. Also use when the user mentions 'referral,' 'affiliate,' 'ambassador,' 'word of mouth,' 'viral loop,' 'refer a friend,' or 'partner program.' This skill covers program design, incentive structure, and growth optimization.
cbbkrd-tech/jl-finishes
Stars: 0Claude CodeCodexWhen the user wants to add, fix, or optimize schema markup and structured data on their site. Also use when the user mentions "schema markup," "structured data," "JSON-LD," "rich snippets," "schema.org," "FAQ schema," "product schema," "review schema," or "breadcrumb schema." For broader SEO issues, see seo-audit.
cbbkrd-tech/jl-finishes
Stars: 0Claude CodeCodexWhen the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' or wants to avoid repeating foundational information across marketing tasks. Creates `.claude/product-marketing-context.md` that other marketing skills reference.
cbbkrd-tech/jl-finishes
Stars: 0Claude CodeCodexCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
cbbkrd-tech/jl-finishes
Stars: 0Claude CodeCodexSync environment variables from local .env to a Vercel project and trigger redeploy. Use this skill whenever the user wants to update Vercel env vars, fix a missing API key on production, sync .env to Vercel, redeploy after env changes, or says something like "update Vercel env", "add key to Vercel", "env not working on prod", "redeploy Vercel".
cbbkrd-tech/jl-finishes
Stars: 0Claude CodeCodexFetch YouTube video transcripts using youtube-transcript-api with residential proxy (DataImpulse) to bypass YouTube's cloud IP blocks. Use when the user wants to get a transcript/captions from a YouTube video URL or video ID. Also handles bulk channel downloads: if the user provides a YouTube channel URL and a number of recent videos, fetch all transcripts and save to a JSON file.
cbbkrd-tech/jl-finishes
Stars: 0Claude CodeCodexInterview users to define and verify a software project plan through a structured conversation. Collects project description, MVP scope, user roles, features, tech stack, integrations, and deployment preferences. Asks minimal clarifying questions grouped logically, provides tailored recommendations after each answer, and produces a verified project plan summary. Use when a user wants to plan a new software project, define MVP scope, choose a tech stack, or create a project brief.
hfadhlullah/Tanya
Stars: 0Claude CodeCodexDesign and revise UI/UX like a senior designer. Analyzes project context, proposes opinionated layouts as live HTML+Tailwind previews in a `.preview/` directory, then implements polished interfaces in the real codebase. TRIGGER on new pages, redesigns, design audits, or component design where layout/hierarchy is in question. SKIP for small tweaks (color, spacing, copy, one-line CSS fixes), bug fixes to an already-approved layout, or backend/logic work — edit real code directly instead.
hfadhlullah/Tanya
Stars: 0Claude CodeCodexInterview users to define and verify a software project plan through a structured conversation. Collects project description, MVP scope, user roles, features, tech stack, integrations, and deployment preferences. Asks minimal clarifying questions grouped logically, provides tailored recommendations after each answer, and produces a verified project plan summary. Use when a user wants to plan a new software project, define MVP scope, choose a tech stack, or create a project brief.
hfadhlullah/Tanya
Stars: 0Claude CodeCodexDesign and revise UI/UX like a senior designer. Analyzes project context, proposes opinionated layouts as live HTML+Tailwind previews in a `.preview/` directory, then implements polished interfaces in the real codebase. TRIGGER on new pages, redesigns, design audits, or component design where layout/hierarchy is in question. SKIP for small tweaks (color, spacing, copy, one-line CSS fixes), bug fixes to an already-approved layout, or backend/logic work — edit real code directly instead.
hfadhlullah/Tanya
Stars: 0Claude CodeCodexInterview users to define and verify a software project plan through a structured conversation. Collects project description, MVP scope, user roles, features, tech stack, integrations, and deployment preferences. Asks minimal clarifying questions grouped logically, provides tailored recommendations after each answer, and produces a verified project plan summary. Use when a user wants to plan a new software project, define MVP scope, choose a tech stack, or create a project brief.
hfadhlullah/Tanya
Stars: 0Claude CodeCodexDesign and revise UI/UX like a senior designer. Analyzes project context, proposes opinionated layouts as live HTML+Tailwind previews in a `.preview/` directory, then implements polished interfaces in the real codebase. TRIGGER on new pages, redesigns, design audits, or component design where layout/hierarchy is in question. SKIP for small tweaks (color, spacing, copy, one-line CSS fixes), bug fixes to an already-approved layout, or backend/logic work — edit real code directly instead.
hfadhlullah/Tanya
Stars: 0Claude CodeCodexModern, interactive alternative to `/do` — clarify intent up front, then take a task end-to-end with an AI review gauntlet (codex debate → lens debate (lowy ⇄ hickey) → code-police → CI → evidence). ONLY invoke when the user explicitly types `/be` or `$be`; never auto-select from a natural-language request.
srid/smriti
Stars: 0Claude CodeCodexReview code for quality, simplicity, and common mistakes before declaring work complete.
srid/smriti
Stars: 0Claude CodeCodexIteratively study and apply elegant coding patterns. Each iteration - understand the code, research what simple and elegant code looks like, apply learnings, verify with CI. Use as a standalone refactoring pass or when the user asks to make code more elegant, simple, or idiomatic.
srid/smriti
Stars: 0Claude CodeCodexAudit code for correctness and rigor — logic errors, silent error swallowing, wishful thinking, and unjustified fallbacks. This is not a style review; it's a logic review. Use when you want a focused correctness audit separate from the full code-police pass.
srid/smriti
Stars: 0Claude CodeCodexEvaluate code (especially LLM-generated) for structural simplicity using Rich Hickey's "Simple Made Easy" framework. Use this skill whenever reviewing a PR, diff, or code snippet for accidental complexity — particularly when the code was generated by an AI coding assistant and line-by-line review isn't feasible. Also use when the user asks about complecting, simplicity vs. easiness, structural coupling, or concept deduplication. Trigger on phrases like "is this simple", "does this complect", "review for complexity", "structural analysis", or any reference to Hickey, Simple Made Easy, or grey-box review.
srid/smriti
Stars: 0Claude CodeCodexEvaluate architecture and module boundaries for volatility-based decomposition using Juval Lowy's framework (from "Righting Software", building on Parnas 1972). Use when reviewing module splits, service boundaries, new abstractions, or any decomposition decision. Trigger on phrases like "where should this boundary be", "how to split this", "module boundaries", "encapsulate change", "volatility", or references to Lowy, Parnas, or "Righting Software". Complements /hickey (interleaved concerns) with a different lens (change encapsulation).
srid/smriti
Stars: 0Claude CodeCodexIterative measurement-driven improvement loop. Measure, profile, mutate, re-measure, commit. Works for performance, bundle size, complexity, test coverage — anything quantifiable. Use when the user wants to systematically improve a metric through repeated cycles of profiling and targeted changes.
srid/smriti
Stars: 0Claude CodeCodexEnter talk mode — conversation and research, no repo changes. ONLY invoke when the user explicitly types `/talk` or `$talk`; never auto-select from a natural-language question or design discussion.
srid/smriti
Stars: 0Claude CodeCodexCheck and process messages from autonomous AILANG agents. Use when starting a session, after agent handoffs, or when checking for completion notifications.
diegosouzapw/awesome-omni-skill
Stars: 67Claude CodeCodexMaintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
diegosouzapw/awesome-omni-skill
Stars: 67Claude CodeCodexTrack and optimize agent specialization during methodology development. Use when agent specialization emerges (generic agents show >5x performance gap), multi-experiment comparison needed, or methodology transferability analysis required. Captures agent set evolution (Aₙ tracking), meta-agent evolution (Mₙ tracking), specialization decisions (when/why to create specialized agents), and reusability assessment (universal vs domain-specific vs task-specific). Enables systematic cross-experiment learning and optimized M₀ evolution. 2-3 hours overhead per experiment.
diegosouzapw/awesome-omni-skill
Stars: 67Claude CodeCodexAnalyze a codebase and recommend Claude Code automations (hooks, subagents, skills, plugins, MCP servers). Use when user asks for automation recommendations, wants to optimize their Claude Code setup, mentions improving Claude Code workflows, asks how to first set up Claude Code for a project, or wants to know what Claude Code features they should use.
diegosouzapw/awesome-omni-skill
Stars: 67Claude CodeCodexUse this skill when creating or updating a pull request in the TTA.dev repository. Covers PR title format, description template, review expectations, and pre-submit checklist. Invoke when the user says "create a PR", "open a pull request", "submit my changes", or "make a PR".
theinterneti/TTA.dev
Stars: 0Claude CodeCodexUse this skill when making git commits in the TTA.dev repository. Enforces Conventional Commits format and pre-commit quality checks. Invoke when the user says "commit", "git commit", "save changes", "commit my work", or asks how to commit code.
theinterneti/TTA.dev
Stars: 0Claude CodeCodexAsk which skill or flow fits your situation. A router over the skills in this repo.
MaksymilianCzadowski/skills
Stars: 0Claude CodeCodexReview the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
MaksymilianCzadowski/skills
Stars: 0Claude CodeCodexDiagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
MaksymilianCzadowski/skills
Stars: 0Claude CodeCodex