alexanderop
- 95 skills
- 0 followers
- 3 hours ago last updated
- ▌ Typescript Best Practices · alexanderop bundleTypeScript best practices. Use when reading or editing any .ts or .tsx file.
- ▌ Principle Foundational Thinking · alexanderopApply before writing logic: choosing core types and data structures, sequencing scaffold-vs-feature work, asking what concurrent actors share. Get the data structures right so downstream code becomes obvious.
- ▌ Principle Redesign From First Principles · alexanderopApply when integrating a new requirement into an existing design. Redesign as if the requirement had been a foundational assumption from day one, instead of bolting it on.
- ▌ Code Simplifier · alexanderopSimplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise.
- ▌ Screenshotting Apps · alexanderop bundleGenerates annotated screenshot documentation for web apps and websites — local dev servers or live sites. Use when asked to "screenshot the app", "document the app", "visual docs", "screenshot documentation", "show me the app", "screenshot <url>", or "document this website".
- ▌ Nuxt Content · alexanderopUse when answering questions about OR implementing features with Nuxt Content (queries, MDC components, document-driven mode), especially when uncertain about current API - Nuxt Content is frequently updated with breaking changes, so fetch current documentation from llms.txt before responding to ensure accuracy over training data
- ▌ Blog Generator · alexanderop bundleGenerates a self-contained, deeply-technical "deep dive" blog post as a single offline-capable HTML file — AstroPaper aesthetic, light/dark toggle, Mermaid diagrams (CDN), Shiki syntax highlighting (CDN ESM). Use when the user types "$blog" or "$blog-post", asks to "write a blog post", "deep dive blog", "generate a blog post about how X works", "explain X in a blog post so I can rebuild it", "in-depth post about", or wants a long-form publishable HTML article reverse-engineering a codebase, library, or architecture (not a quick summary, not an interactive walkthrough).
- ▌ Good Docs Writer · alexanderop bundleTurn a topic into a structured blog-post draft for a developer audience, using The Good Docs Project templates as the structural backbone. Classifies the post intent (explainer, walkthrough, recipe, quickstart, debug story, release post, cheat sheet) via an internal index, fetches the matching Good Docs template (bundled locally from gitlab.com/tgdp/templates), then adapts it to blog voice (hook, narrative, takeaways, CTA). TRIGGER on: "good-docs-writer", "write a blog post about X", "draft a blog post on X", "blog post for X", or the explicit form "$good-docs-writer <intent> <topic>".
- ▌ HTML Presentation · alexanderop bundleGenerate a self-contained HTML presentation file from a topic or markdown content. This skill should be used when asked to "create an HTML presentation", "make slides as HTML", "generate a standalone presentation", "present about X as HTML", or when the user wants a portable presentation file they can open in any browser. Distinct from the blog presentation skill — this produces a standalone HTML file, not an Astro blog post.
- ▌ Vue AI Assistant · alexanderop bundleAnswer questions about Vue or AI using alexop.dev as the primary knowledge source. Use this skill whenever the user asks about Vue 3, composables, Pinia, Vitest, VueUse, SSR, local-first Vue, GraphQL in Vue, browser AI, Transformers.js, embeddings, AI-assisted development workflows, or asks what Alex Opalic has written about these topics. Always fetch https://alexop.dev/llms.txt first, then delegate the deep research to runSubagent before answering.
- ▌ Vue · alexanderop bundleVue 3 Composition API, script setup macros, reactivity system, and built-in components. Use when writing Vue SFCs, defineProps/defineEmits/defineModel, watchers, or using Transition/Teleport/Suspense/KeepAlive.
- ▌ Antfu · alexanderop bundleAnthony Fu's opinionated tooling and conventions for JavaScript/TypeScript projects. Use when setting up new projects, configuring ESLint/Prettier alternatives, monorepos, library publishing, or when the user mentions Anthony Fu's preferences.
- ▌ QA Explore · alexanderop bundleExploratory browser QA — drive agent-browser through a real UI flow, capture screenshots and console output, then produce a structured markdown report with TC-## test cases, pass/fail verdicts, defects, risks and a ship recommendation. Use this whenever the user says "qa this", "verify like a qa engineer", "exploratory test", "manually verify in browser", "drive the browser and check X works", or asks for a QA report on a change. Prefer this over just running automated tests when the user explicitly wants hands-on, real-browser verification.
- ▌ Research · alexanderopDeep research on a technical problem using parallel subagents for web docs, Stack Overflow, and codebase exploration, saving a markdown report to docs/research/. Use when the user says "research X", "investigate X", "find out how X works", or needs evidence-based recommendations before implementing.
- ▌ Clone Repo · alexanderopVendor a library's source code into the current repo as a git subtree under `repos/<name>/`, then wire it into AGENTS.md as reference material so coding agents read real source instead of fighting stale docs. Use when the user types "$clone-repo <url>", "/clone-repo <url>", "vendor <url>", "clone <url> as a subtree", "add <url> as reference for the agent", "feed <url> to the agent", "just clone the repo <url>", or otherwise asks to set up a third-party repo as agent-readable context.
- ▌ Orchestrated Review · alexanderop bundleOrchestrated multi-agent code review modeled on Cloudflare's system. Risk-tiers the diff, filters noise, fans out specialist reviewers (security, performance, code quality, docs, tests, release, AGENTS.md), and consolidates everything through a coordinator judge pass into one structured verdict. Use for "orchestrated review", "multi-agent code review", "deep review", "review like Cloudflare", "thorough AI code review", or to review a GitHub PR with severity-graded findings and an approve/block decision.
- ▌ Harden Github Actions · alexanderopWhenever you create or substantially edit a GitHub Actions workflow (.github/workflows/*.yml), run `uvx zizmor --persona pedantic` on it and fix every finding before considering the file done. Use this any time you add a new workflow, paste a template workflow (e.g. the Claude GitHub App, a marketplace action, a generated CI/CD file), or change `uses:`, `permissions:`, or trigger blocks — even if the user didn't mention security or zizmor. A workflow that hasn't been run through the pedantic audit is not finished.
- ▌ Nuxt UI · alexanderop bundleBuild UIs with @nuxt/ui v4 — 125+ accessible Vue components with Tailwind CSS theming. Use when creating interfaces, customizing themes to match a brand, building forms, or composing layouts like dashboards, docs sites, and chat interfaces.
- ▌ Screenshot Test · alexanderopAdd a screenshot (visual regression) browser test for a canvas feature. Use when asked to "add a screenshot test for X", "visual test for X", "screenshot test X", "add a browser test with screenshots", or when the user wants to verify how something renders on the canvas.
- ▌ Vueuse Functions · alexanderop bundleApply VueUse composables where appropriate to build concise, maintainable Vue.js / Nuxt features.
- ▌
- ▌ Writing Plans · alexanderop bundleUse when you have a spec or requirements for a multi-step task, before touching code
- ▌ Executing Plans · alexanderopUse when you have a written implementation plan to execute in a separate session with review checkpoints
- ▌ Systematic Debugging · alexanderop bundleUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes
- ▌ Subagent Driven Development · alexanderop bundleUse when executing implementation plans with independent tasks in the current session
- ▌
- ▌ Prd · alexanderopGenerate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out.
- ▌
- ▌
- ▌ Ralph · alexanderop bundleConvert PRDs to prd.json format for Ralph autonomous execution. Use when you have an existing PRD and need to convert it to Ralph's JSON format. Triggers on: convert this prd, turn this into ralph format, create prd.json, ralph json, run ralph on this.
- ▌
- ▌ Vue Newsletter · alexanderop bundleGenerate a comprehensive Vue/Nuxt newsletter by researching 25+ sources in parallel. Use when asked to "create newsletter", "vue news", "what's new in vue", "nuxt updates", or "generate vue newsletter". Aggregates GitHub releases, Hacker News, Reddit, dev.to, official blogs, Vue-specific newsletters, podcasts, and key Vue personalities into a curated weekly digest.
- ▌
- ▌ Conversation Search · alexanderop bundleSearch past Claude Code conversation history. Use when asked to recall, find, or search for anything from previous conversations - including content discussed, links shared, problems solved, topics covered, things posted, or work done together. Triggers include "what did we do today", "summary of our work", "what did we work on", "from our conversations", "what did we discuss", "which X was about Y", "recall when we", "find where we talked about", "search history", "what did I share/post/send you about", "how did we fix", or any reference to past sessions or collaborative work.
- ▌ Lfg · alexanderopAutonomous end-to-end pipeline — takes a problem description, plans, implements, tests, reviews, and ships with minimal user interaction. Use when the user says 'lfg', 'just do it', 'ship it end to end', or wants the full pipeline run autonomously.
- ▌ Test · alexanderopWrite tests from a plan's acceptance criteria — before or after implementation. Use when the user says 'write tests', 'test this', 'TDD', or wants to create tests for a planned feature.
- ▌ Work · alexanderop bundleExecute an implementation plan step by step with testing and commits. Use when the user says 'implement this', 'build this', 'start working', 'execute the plan', or wants to turn a plan into working code.
- ▌ Cplan · alexanderopResearch the codebase and create a structured implementation plan. Use when the user says 'plan this', 'create a plan', 'how should we implement', or wants to turn a feature description into a structured implementation plan.
- ▌ Deepen · alexanderopEnhance an existing plan with parallel research agents for depth, best practices, and implementation details. Use when the user says 'deepen the plan', 'research more', or when a plan has high-risk dimensions that need more investigation.
- ▌ Compound · alexanderop bundleDocument a solved problem as reusable institutional knowledge with parallel research. Use when the user says 'document this', 'compound', 'save learnings', or wants to capture a solution for future reference.
- ▌ Simplify · alexanderopReview changed code for reuse, quality, and efficiency — fix issues before review. Use when the user says 'simplify', 'clean up', 'review the code', or wants to improve code quality before formal review.
- ▌ Brainstorm · alexanderopExplore requirements and approaches through collaborative dialogue before writing a right-sized requirements document and planning implementation. Use for feature ideas, problem framing, when the user says 'let's brainstorm', or when they want to think through options before deciding what to build.
- ▌ Git Commit · alexanderopCreate a git commit with a clear, value-communicating message. Use when the user says "commit", "commit this", "save my changes", "create a commit", or wants to commit staged or unstaged work. Produces well-structured commit messages that follow repo conventions when they exist, and defaults to conventional commit format otherwise.
- ▌ Create Agent · alexanderopScaffold a new custom agent — reviewers, researchers, or workflow agents. Use when asked to create, scaffold, or add a new agent.
- ▌ Git Worktree · alexanderopManage Git worktrees for isolated parallel development. Use when the user wants to work on multiple features in parallel, review code in isolation, or needs a clean workspace. Handles creating, listing, switching, and cleaning up worktrees.
- ▌ Document Review · alexanderopReview requirements or plan documents using parallel persona agents that surface role-specific issues. Use when a requirements document or plan document exists and the user wants to improve it, or when invoked by /cplan for quality gating.
- ▌ Git Commit Push Pr · alexanderopCommit, push, and open a PR with an adaptive, value-first description. Use when the user says "commit and PR", "push and open a PR", "ship this", "create a PR", "open a pull request", or wants to go from working changes to an open pull request in one step. Also handles "update the PR description" or "refresh the PR description".
- ▌ How · alexanderop bundleUse for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live", "which package owns this", "is this the right layer"). Explains subsystem architecture, runtime flow, onboarding mental models. Use why for motivation.
- ▌ Why · alexanderop bundleUse for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.
- ▌ Arena · alexanderopSpawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for /arena, 'arena this', 'throw it in the arena', or when one attempt at a non-trivial artifact would lock in the wrong shape.
- ▌ Swarm · alexanderopFan out N parallel workers, drain them, and return one report. Use for /swarm, 'swarm this', or parallel coverage, races, gauntlets, and exploration.
- ▌ Teach · alexanderopExplain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.
- ▌ Recall · alexanderopReconstruct your recent working context from your own chat history, live state, and the shared record (user reports, prior fixes, incidents), then hand back a tight current-state brief. Use for 'recall my work on X', 'catch me up', 'what have I been working on', 'where did I leave off', before starting or resuming work.
- ▌ Reflect · alexanderop bundleSpawn three parallel review subagents over the active transcript, surface learnings, and route each to a concrete edit on an existing skill. Use when the user says reflect.
- ▌ Architect · alexanderop bundleSketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for /architect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape.
- ▌ Automate Me · alexanderopUse for "automate me", "create/update/refresh my -mode skill", "turn/capture my preferences or working style into a skill", or wanting agents to follow how the user works. Drafts or revises a personal -mode skill via create-skill + unslop, optionally pulling fresh evidence from recent transcripts.
- ▌ Interrogate · alexanderop bundleUse for "interrogate", "adversarial review", "multi-model review", "challenge this", "stress test this code", "find blind spots", or "tear this apart". Multiple LLM reviewers challenge changes from independent angles.
- ▌ Make Bot UI · alexanderopUse when building a custom UI (page, dashboard, buttons) that should wake a Grok Bot over a webhook, when the user must provide a webhook sender key, or when exposing that UI on Tailscale.
- ▌ No Comments · alexanderopSpawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.
- ▌ Poteto Mode · alexanderop bundlepoteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work. Use for poteto, /poteto-mode, or requests to work in this style.
- ▌ Setup Pstack · alexanderopDetect the active agent harness and configure which models pstack uses per role. Writes ~/.pstack/models.md, which the skills read as an override on the harness defaults. Use for /setup-pstack, "configure pstack models", or changing pstack's model choices.
- ▌ Figure It Out · alexanderopDesign an auditable playbook when no narrower one fits: a large migration, an ambitious multi-part change, or work a human reviews after stepping away. Scales rigor to the task, runs a hypothesis loop, and logs decisions via show-me-your-work. Use for /figure-it-out, 'figure it out', a large migration, or when no narrower playbook applies.
- ▌ Show Me Your Work · alexanderop bundleKeep a reviewable decision trail for long-running or unattended work: a TSV log with one row per decision (what, why, evidence, result). Local by default; commit it when a reviewer needs the trail to trust the result. Use for /show-me-your-work, autonomous or multi-phase runs, or work a human reviews after stepping away.
- ▌ Create Verification Skill · alexanderop bundleGenerate a project-local verification skill that drives your app the way a user does — any language, framework, or platform. Use for /create-verification-skill, "make a control skill for this repo", or when a project has no scripted way to prove UI/CLI/service behavior.
- ▌ Maintain Verification Skill · alexanderopPeriodic pass that keeps a project's verification skill and feature map honest: parallel source readers per feature, one live session driving every feature, at most one PR of proven corrections. Use for /maintain-verification-skill or "audit the verify skill".
- ▌ Principle Compose Vue Components · alexanderopApply when building or refactoring Vue components. Design accessibility first, organize by responsibility, and express layout variants through composition.
- ▌ Principle Test Behavior Not Implementation · alexanderopApply when you write, change, or keep a test. Call the code the way its users do and assert the result they observe against a literal expected value. If the test would still pass when every imported function returns undefined, rewrite the assertion or delete the test.
- ▌
- ▌ Mermaid · alexanderop bundleMust read guide on creating/editing mermaid charts with validation tools and syntax reference for all diagram types
- ▌ Daily Note · alexanderop bundleCreate or update today's private journal entry. Use when asked to "daily note", "journal", "log today", "morning pages", or "capture thoughts".
- ▌ Moc Curator · alexanderop bundleSuggest MOC updates and new MOCs based on semantic clustering. Use when asked to "curate MOCs", "update maps", "find clusters", "what MOCs need updating", or "organize my notes".
- ▌ Adding Notes · alexanderop bundleCreate a note from any resource: URL, book, podcast, article, video, GitHub repo, Reddit thread, PDF, quote, or raw idea. Trigger on "add", "save", "capture", "note this", "take notes on", or any request to record content in the knowledge base.
- ▌ Asking Notes · alexanderopQuery your Second Brain with keyword search. Use when asked to "ask my notes", "what do I know about", "query my knowledge", "/ask", or when the user has a question that their notes might answer.
- ▌ Adding Tweets · alexanderopAdd tweets to the Second Brain. Use when the user provides a Twitter/X URL and pasted tweet content, asking to "add a tweet", "save this tweet", or "capture this tweet".
- ▌ Linking Notes · alexanderopDiscover and add wiki-links between notes. Use when asked to "find connections", "link this note", "what should I link to", or "connect my notes".
- ▌ Managing Tags · alexanderopManage and consolidate tags. Use when asked to "clean up tags", "consolidate tags", "tag audit", "merge tags", or "rename tag".
- ▌ Weekly Review · alexanderopSummarize the past week's daily journal entries. Use when asked to "weekly review", "review the week", "summarize this week", or "week summary".
- ▌ Writing Style · alexanderopWriting guidelines for clear, economical prose. Reference this skill when creating or enhancing note content.
- ▌ Monthly Review · alexanderopAggregate weekly summaries into a monthly overview. Use when asked to "monthly review", "review the month", "summarize this month", or "month summary".
- ▌ Enhancing Notes · alexanderopEnhance book notes with Blinkist-style summaries. Use when asked to "enhance notes", "improve book notes", "add key insights", "expand notes", or "make notes better". Adds Core Message, Key Insights, Notable Quotes, and Who Should Read sections via parallel web research.
- ▌ Enhancing Talks · alexanderop bundleEnhance talk notes with Blinkist-style summaries and timestamps. Use when asked to "enhance talk", "improve talk notes", "add timestamps", "blinkist-style talk summary", or "make talk notes better". Adds Core Message, Key Insights with timestamps, Talk Structure, Notable Quotes, Who Should Watch, and Action Items via transcript analysis.
- ▌ Exploring Graph · alexanderopAnalyze the knowledge graph for insights. Use when asked to "analyze connections", "graph report", "show hubs", "find orphans", or "knowledge map".
- ▌ Reviewing Notes · alexanderopAudit notes for quality issues. Use when asked to "review notes", "check content quality", "audit my knowledge base", or "find broken links".
- ▌ Mermaid Diagrams · alexanderopGenerate Mermaid diagrams (flowcharts, sequence, class, state, ER, C4, mindmaps, gitgraph). Use when asked to create diagrams, visualize processes, document architecture, or explain systems visually. Triggers include "diagram", "flowchart", "sequence diagram", "class diagram", "state diagram", "ER diagram", "C4", "mindmap", "gitgraph", "visualize", "draw".
- ▌ Demo 2 1 Features · alexanderopDemo skill showing all Claude Code 2.1 features. Use when asked to "demo 2.1" or "show new skill features".
- ▌ Enhancing Authors · alexanderopEnhance author profiles by filling missing fields. Use when asked to "enhance author", "complete author profile", "find author info", or "update author details". Fills bio, avatar, website, and social links via parallel web research.
- ▌ Summarizing Topic · alexanderopSynthesize knowledge on a topic from multiple notes. Use when asked "what do I know about X", "summarize topic", "synthesize notes on", or "overview of".
- ▌
- ▌ Weekly Newsletter · alexanderop bundleGenerate a weekly newsletter summarizing resources added last week. Use when asked to "weekly newsletter", "newsletter", "what did I add this week", "generate newsletter", or "Monday newsletter".
- ▌ Managing Blog Ideas · alexanderopCreate and develop blog post ideas. Use when asked to "create a blog idea", "start a blog post", "expand blog outline", "develop this post idea", "update blog draft", or "list blog ideas".
- ▌ Using Git Worktrees · alexanderopUse when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
- ▌ Debugging · alexanderopDebug issues in the Second Brain Nuxt 4 + @nuxt/content v3 project. Use for any bug, test failure, or unexpected behavior.
- ▌ Creating Obsidian Templates · alexanderopCreate Obsidian templates for the Second Brain vault. Use when asked to "create a template", "make a template for", "add an Obsidian template", or "template for X".
- ▌ Walkthrough · alexanderop bundleGenerates a self-contained HTML file with an interactive, clickable Mermaid diagram (flowchart or ER diagram) that explains how a codebase feature, flow, architecture, or database schema works. Designed for fast onboarding — each walkthrough is a visual mental model readable in under 2 minutes. TRIGGER this skill when ANY of these match: - The prompt starts with or contains "$walkthrough" (explicit trigger — always activate, even if no topic follows) - The user asks to "walk me through", "walkthrough", "trace the code path", "explain this flow", "show how X works", "how does X work step by step", "explain the architecture", "visualize the data model", "show the data structures", "show the relationships" - The user wants a visual/interactive explanation of code, flows, pipelines, or schemas When triggered, ALWAYS generate a walkthrough HTML file — never respond with just text. If "$walkthrough" is used with no topic, generate an overview walkthrough of the entire project.
- ▌ Publish Skill · alexanderop bundleCreates a new GitHub repository for a Claude Code skill with proper README and directory structure. Use when you want to package and publish a skill so others can install it. Triggers on "publish skill", "publish this skill", "create skill repo", "package skill", "share this skill".