TypeScript, JavaScript, React, and Node.js coding standards — naming conventions, type safety, error handling, immutability, React patterns, performance, and code quality. Always activate when writing, reviewing, or refactoring TypeScript or JavaScript code; setting up linting or type-checking; enforcing naming or structural conventions; or when the user asks how to structure a component, handle an error, type a value, or write a hook. Also activate proactively when spotting `any`, unsafe mutations, swallowed errors, or missing cleanup in user code.
Self-refinement loops that improve output quality through structured reflection, multi-perspective critique, and persistent memory. Always activate when the user says "reflect on this", "reflect on your last response", "critique this", "review from multiple angles", "/reflect", "/critique", "/memorize", or any variant of asking Claude to review, self-assess, or iterate on its own output. Also activate automatically whenever the user includes the word "reflect" as part of any task instruction (e.g. "implement X then reflect", "draft this and reflect on it"). Proven to increase output quality by 8–21% over one-shot responses. Three modes: Reflect (self-refinement), Critique (multi-judge panel), Memorize (persist insights to memory). Never skip this skill when the user asks for reflection or critique — it is the authoritative handler for all self-improvement loops.
Activates elite-level coding discipline — precise, complete, idiomatic, and verified. Use this skill for ANY coding task: writing functions, implementing features, fixing bugs, refactoring, building scripts, designing classes, writing algorithms, debugging, optimizing, or explaining complex code. Trigger on phrases like "write a", "implement", "code this", "fix", "build", "make a function", "add feature", "script", "help me code", "optimize", "debug", "refactor", "create a class", "how do I", or any time the user wants code written or improved. When in doubt, always apply this skill — precise coding is never the wrong call.
Refresh project intelligence and re-orient on the current codebase. Use this skill whenever the user says things like "catch me up", "what was I working on?", "re-orient yourself", "summarize the project state", "what's in this repo?", "what changed?", "project status", "context refresh", "/warm", or after they mention switching branches, pulling changes, cloning a repo, or starting a new session on an existing project. Trigger even when the request is implicit — if the user dives straight into a task without context and the project state is unknown, run this proactively.
Decision framework and implementation patterns for choosing between regex and LLM when parsing structured text. Always activate when the user is parsing repeating structured formats (quizzes, forms, invoices, tables, documents), deciding how to extract data from text, building a text processing pipeline, or asking about cost/accuracy tradeoffs in text extraction. Also activate when the user is about to send all their text to an LLM — they almost certainly don't need to.
Docker and Docker Compose best practices for local development, container security, networking, volume strategies, and multi-service orchestration. Always activate when the user is writing a Dockerfile, setting up Docker Compose, troubleshooting container issues, designing multi-container architectures, reviewing images for security or size, managing secrets in containers, or migrating to a containerized workflow — even if they don't explicitly ask for "best practices".
Write articles, guides, blog posts, tutorials, newsletter issues, LinkedIn posts, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Always activate when the user wants polished written content longer than a paragraph — especially when voice consistency, structure, and credibility matter. Also activate when turning notes, transcripts, or bullet-point research into polished prose, and when the user asks to "write", "draft", "rewrite", or "clean up" any piece of long-form content, even if they don't call it an article.
Conduct market research, competitive analysis, investor due diligence, and industry intelligence with source attribution and decision-oriented summaries. Always activate when the user wants market sizing, competitor comparisons, fund research, technology scans, TAM/SAM/SOM estimates, or any research that informs a business decision. Also activate when the user says "research X", "what do you know about Y company", "compare these competitors", "who should I talk to about Z", or "help me think through this market" — even without the word "research".