YosefHayim

Optimize Chrome Web Store listing SEO (name, short description/summary, Overview) and marketing-site GEO using official Chrome/Google guidance plus free Google APIs. Use when the user asks for CWS SEO, Chrome Web Store listing optimization, store title/summary/description copy, keyword research for extensions, Featured eligibility copy, or GEO/AEO for an extension landing page.

Direct a cinematic, viral-ready trailer for any project — reads the repo's own docs to derive the story, consults ChatGPT (GPT-5.5 Thinking) over ai-browser-bridge to write the transcript + storyboard, batch-generates the keyframes as ChatGPT images, animates them with Higgsfield or Flow/Veo, produces voiceover + music (ElevenLabs → Higgsfield → local synth), and assembles a 9:16 master + 16:9/1:1/4:5 platform cuts with ffmpeg — behind two planpage approval gates. Use when the user wants a trailer, promo, launch/teaser/hype video, commercial, sizzle reel, or cinematic short for a project to post on LinkedIn/YouTube/Instagram/TikTok, or says "make a trailer", "make a promo", "cinematic video", or "make it go viral". For a portfolio blog cover image use write-a-post; for store/marketing copy use cws-listing-seo.

Use when refreshing, rewriting, syncing, or creating repository agent instruction files such as AGENTS.md, CLAUDE.md, GEMINI.md, Cursor rules, Kiro steering, Roo rules, Codex instructions, or root project context docs.

Audits a website or web app against web-platform best practices and ships the fixes, across seven dimensions — semantic HTML + ARIA landmarks, accessibility, images/fonts, performance, security headers (CSP/HSTS), SEO metadata, and machine-readability for AI agents (llms.txt, schema.org JSON-LD, crawler access, Google's agent-ready rules). Runs a zero-dep static scanner over a project, guides the agent's semantic pass, and provides copy-paste fixes (llms.txt + security-header templates) plus authoritative sources (MDN, web.dev, W3C APG, llmstxt.org). Use when the user wants to check or improve a site's best practices, accessibility, security headers, CSP, semantic HTML, SEO/meta tags, structured data, schema.org, or make a site agent-ready or AI-crawler-friendly. For the deep Core Web Vitals CI gate (Lighthouse CI, CrUX), defer to web-perf-ci.

Reviews code and repo structure for over-engineering, then removes the excess so the code does exactly what it needs and no more. The over-engineering companion to deslop (deslop makes code readable; deslop-v2 makes it lean). Use when the user says "deslop-v2", "over-engineered", "too much abstraction", "over-abstracted", "simplify this", "why is this so complicated", "flatten this", "too many wrappers/layers/folders", "this feels like too much", or asks to cut needless indirection, `??` fallbacks, nested ternaries, pass-through wrappers, single-use helpers, grab-bag returns, or deep folder/package nesting.

Grill the user on how a NEW/greenfield project is built — code style, structure docs, and CLI — then render an HTML plan and, on approval, write CODE-STYLE.md + a formatter config and refresh the AGENTS.md digest. Ensures PROJECT.md/CONTEXT.md/LANGUAGE.md exist (create if missing, validate if present) and grills real code idioms + formatting, not just architecture. Use when setting up or reorganizing a new project, when there is little/no code, or when defining coding style, structure, or CLI conventions from scratch. For an existing codebase, use grill-me-code-style-with-docs instead.

Coach the user WHILE building or fixing code in a repo that has a code-style.rules.json — at each real style/structure decision, explain the concept concisely (KISS) in terms they already know, show two concrete variants, make them confirm the direction before writing, then teach the mechanism and link the exemplar it mirrors. High-friction on judgment calls; silent on anything Biome already enforces. Grounds "where the business logic goes" in PROJECT.md / CONTEXT.md. Use when writing a feature/fix and the user wants to LEARN their own architecture as we go, not just delegate — or says "coach me", "teach me as we build", "grill me while we code". For reviewing a finished diff instead, use grill-me-code-style-review; to CREATE the ruleset, grill-me-code-style.

Review a large changeset (a branch, working tree, or PR — tens to hundreds of files) against a repo's code-style.rules.json so the user can trust it WITHOUT reading every diff, and LEARN the architecture from a short teaching report instead. Runs Biome (+ its grit plugins) to auto-fix the mechanical/structural channels across all files, then fans out sub-agents over the diff to check only the judgment-channel rules + the user's original intent, and returns a deviations-only report that opens with a layer/flow map of what changed and teaches the "why" behind each finding. Use when reviewing/auditing a big diff, a PR, or an AI-generated changeset, or the user says "review this", "can I trust this diff", "audit these changes". To coach while building, use grill-me-code-style-coach; to create the ruleset, grill-me-code-style.

Use when adding or changing a build, storage, credentials, submit, or compute backend in launch-store — implement one of the five provider interfaces and register it, without touching the pipeline.

Use when finishing or verifying a change to launch-store — run the full typecheck, lint, test, build, and docs gate that must be green before a change is done or a PR merges.

Use when adding teaching text for a concept or step in launch-store — add it to the single glossary source that feeds both `launch explain` and the `--explain` step expansions.

Use when adding a new top-level `launch` command or subcommand — wire it as thin commander code and regenerate the docs the CLI surface drives.

TypeScript best practices distilled from Matt Pocock's TotalTypeScript.com. Naming conventions, generics usage, type inference, config settings, and practical patterns for production TypeScript code.

Automatically extract reusable patterns from Claude Code sessions and save them as learned skills for future use.

Instinct-based learning system that observes sessions via hooks, creates atomic instincts with confidence scoring, and evolves them into skills/commands/agents. v2.1 adds project-scoped instincts to prevent cross-project contamination.

Render a skill's plan, review gate, quiz, poll, or report as a beautiful, self-contained INTERACTIVE HTML page via the open-source planpage package (Preact → static HTML + local post-back so the user can Approve / Adjust / flip decisions in the browser and the choice comes back to the agent). Use whenever a skill needs an approval gate, decision review, preference poll, teach/coach surface, storyboard/image grid, or shareable before/after report — author with planpage instead of hand-rolling HTML.