drvoss
- 109 skills
- 0 followers
- 6 hours ago last updated
- ▌ SEO · drvossUse when the user wants better search visibility, SEO remediation, schema markup, sitemap/robots work, or keyword mapping — audits and implements technical SEO, on-page optimization, Core Web Vitals, and structured data
- ▌ Triage · drvossUse when a single issue or external-contributor pull request needs structured triage — classify it, verify the claim if needed, request missing information, and leave a durable brief or close-out note in the tracker.
- ▌ UX Audit · drvossUse when a page or component needs a structured UX audit — quick scan applies 6 Krug-inspired usability checks; deep audit covers 15 design dimensions with Jobs/Ive philosophy
- ▌ Council · drvossUse when a decision has multiple credible paths and no obvious winner — convene a four-voice council (Architect, Skeptic, Pragmatist, Critic) for structured adversarial deliberation before choosing
- ▌ Handoff · drvossUse when work is changing sessions, agents, or machines and the next pass needs a compact handoff document with current state, open questions, and next steps instead of raw chat history.
- ▌ Release · drvossUse when a sprint or feature is complete and ready to ship — tags the version, generates GitHub Release notes, runs rollout or smoke verification, and publishes to npm/PyPI/Docker registries.
- ▌ QA Review · drvossUse when reviewing or planning QA strategy for a feature, PR, or release so test coverage, test quality, reliability, and defect reporting are handled as a coherent engineering discipline instead of ad hoc checks.
- ▌ Grill Me · drvossUse when a plan still has hidden assumptions — default to one question at a time for dependent branches, batch only truly independent questions when it saves real round-trips, and keep stress-testing the plan until dependencies, risks, and decisions are explicit before implementation starts
- ▌ LLM Wiki · drvossUse when research or domain knowledge keeps getting rediscovered across sessions — build a supplementary markdown wiki that compounds synthesized knowledge without replacing GitHub or committed project guidance
- ▌ Review · drvossUse when you want to check whether a code change follows the repository's documented conventions (Standards) and aligns with the originating issue or PRD (Spec) — compared against a pinned git reference
- ▌ Create Prd · drvossUse when you're ready to define a feature before building it — generates a structured PRD using Jobs-to-be-Done thinking, success metrics, and explicit scope boundaries.
- ▌ To Issues · drvossUse when a plan, spec, or PRD must become an actionable backlog — break it into thin dependency-aware issues that each deliver a verifiable vertical slice
- ▌ Wayfinder · drvossUse when a task is too large or ambiguous to finish in one session — build a destination-centric plan with a breadth-first triage pass, an explicit Deferred/out-of-scope section, and a confirmation gate before implementation starts
- ▌ E2e Testing · drvossUse when you need end-to-end tests for critical user flows that unit tests can't cover — scaffolds Playwright/Cypress tests from the happy path through edge cases.
- ▌ Cost Audit · drvossUse when AI inference costs are growing unexpectedly, when comparing model choices by cost/quality ratio, or when optimizing token usage across a multi-model pipeline — produces an actionable cost reduction plan
- ▌ Diagnose · drvossUse when a bug or performance issue is still fuzzy — build the fastest feedback loop first, rank the leading hypotheses, and instrument only what narrows the search
- ▌ Zoom Out · drvossUse when you are lost in local code details — step one abstraction level up, map the owning modules and callers, and restate the system in project vocabulary
- ▌ Eval Harness · drvossUse when you need to evaluate an LLM pipeline or AI feature systematically — sets up an eval harness with test cases, scoring rubrics, and pass/fail tracking rather than one-off manual spot-checks
- ▌ AI Visibility · drvossUse when you want your product to surface in AI-generated answers (ChatGPT, Perplexity, Gemini) — creates llms.txt, optimizes structured data, and configures AI crawler access for GEO.
- ▌ Implement · drvossUse when starting implementation work from a PRD, spec, or set of issues — to follow a structured TDD → validate → review → commit loop.
- ▌ Prototype · drvossUse when a design question is still fuzzy — build a throwaway logic or UI prototype that answers one question fast, stays easy to run, and is meant to be deleted or absorbed.
- ▌ Test Coverage · drvossUse when test coverage falls below target or a new module has no tests — identifies untested code paths and writes targeted unit or integration tests to close the coverage gap.
- ▌ Interview Me · drvossUse when a request is underspecified and you need to discover what the user actually wants before writing a plan, spec, or code - default to one question at a time when later questions depend on earlier answers, switch to a numbered batch only for independent high-latency clarifications, attach your current hypothesis, and stop only after the intent is explicitly confirmed.
- ▌ Sprint Retro · drvossUse at the end of a sprint to run a data-driven retrospective — analyzes session history and git metrics to surface what shipped, what slowed you down, and concrete improvements.
- ▌ Security Scan · drvossUse when you want a quick security pass on code changes or dependencies — checks OWASP Top 10 patterns, runs dependency audits, and surfaces critical vulnerabilities with targeted fixes.
- ▌ Deep Research · drvossUse when a question requires comprehensive evidence gathering from multiple sources, systematic synthesis, and traceable citations — produces a structured research brief rather than a quick answer
- ▌ Outside Voice · drvossUse when you need an independent second opinion before, during, or after implementation — run challenge, consult, or review mode in a direct builder-to-builder voice
- ▌ Code Review · drvossUse when reviewing code changes for quality, correctness, and security — runs a structured checklist with severity-rated findings
- ▌ Code Tour · drvossUse when a user asks for a code tour, onboarding walkthrough, architecture tour, or PR tour — creates persona-targeted, step-by-step `.tour` files with real file and line anchors
- ▌ Launch Strategy · drvossUse when you're preparing to launch a product or feature publicly — builds a structured checklist covering positioning, distribution, messaging, and success metrics from private beta to GA.
- ▌ Security Audit · drvossUse when a codebase needs a formal security audit beyond a quick scan — applies OWASP Top 10 and STRIDE threat modeling from a CSO perspective to surface systemic vulnerabilities.
- ▌ Content Strategy · drvossUse when you need a content plan to grow organic traffic for a product or new area — produces keyword research, topic clusters, and a content calendar targeting your category.
- ▌ React Vitest · drvossUse when adding or improving tests in a React project that uses Vitest — covers component testing with Testing Library, mocking hooks, and coverage configuration.
- ▌ Tdd Workflow · drvossUse when starting a new feature or function to write failing tests first, then implement the minimal code to pass (Red→Green→Refactor)
- ▌ Doc Update · drvossUse when code has changed and documentation may be out of date — identifies stale docs, finds gaps between implementation and docs, and applies targeted updates.
- ▌ Browser Devtools · drvossUse when verifying frontend behavior at runtime — DOM validation, network inspection, performance profiling with browser DevTools
- ▌ Commit Workflow · drvossUse when you're about to commit (especially with a mixed diff) to stage changes, split into atomic commits, and write Conventional Commit messages with emoji
- ▌ Grill With Docs · drvossUse when a plan must be stress-tested against the codebase's existing language and decisions — grill it against current docs, glossary terms, and ADRs before implementation begins
- ▌ Sprint Workflow · drvossUse when starting a new feature, refactor, or multi-step dev task — runs the full sprint cycle (Think → Plan → Build → Review → Test → Ship → Monitor) using Copilot CLI's plan/autopilot modes.
- ▌ Cpp Debugging · drvossUse when a C++ failure involves memory lifetime, undefined behavior, native crashes, or debugger-only state — debug with symbols, sanitizers, and platform-native debuggers before patching symptoms
- ▌ Nestjs Prisma · drvossUse when building a NestJS application with Prisma — covers PrismaService setup as an injectable singleton, repository pattern integration, and testing with Prisma mocks.
- ▌ Nextjs Prisma · drvossUse when working on a Next.js App Router project that uses Prisma as the ORM — covers server component data fetching, singleton client setup, and type-safe query patterns.
- ▌ Skill Creator · drvossUse when you want to create a new SKILL.md file — describe a workflow and this skill generates a properly structured, frontmatter-complete SKILL.md that follows this repository's conventions
- ▌ Agent Governance · drvossUse when designing or reviewing an AI agent system that needs policy-based access controls, intent classification, tool-level rate limiting, trust scoring for multi-agent workflows, or append-only audit trails.
- ▌ Input Validation · drvossUse when writing or reviewing code that processes user input — validates and sanitizes to prevent SQL injection, XSS, CSRF, and other injection attacks. NOT when the code path doesn't touch user-supplied data.
- ▌ Secret Detection · drvossUse when you suspect API keys, tokens, or passwords are hardcoded in source code or committed to git history — scans and guides safe removal without breaking existing integrations.
- ▌ Prompt Optimizer · drvossUse when a rough prompt, vague idea, or task description needs to become a finished copy-pasteable prompt for a chat-based LLM - rewrite it into one ready-to-send prompt with no blanks, no placeholders, and a clear output shape.
- ▌ Refactor Clean · drvossUse when code has grown complex, duplicated, or cluttered — clean up structure and remove dead code without changing observable behavior
- ▌ Product Capability · drvossUse when engineering needs testable, implementable technical requirements — not a PRD but a capability spec with acceptance criteria, task breakdown, and traceability from requirement to implementation ticket
- ▌ Agent Owasp Check · drvossUse when auditing an AI agent system against the OWASP Agentic Security Initiative Top 10 — checks tool access, prompt boundaries, memory handling, and operational safeguards across the agent pipeline.
- ▌ Deployment Canary · drvossUse when a release has been deployed to a limited audience and must be observed before full rollout — defines success signals, watch windows, rollback triggers, and investigate handoffs.
- ▌ Agent Supply Chain · drvossUse when auditing an AI agent plugin, skill bundle, or MCP tool package for supply chain integrity — generate deterministic SHA-256 manifests, detect modified or untracked files, flag unpinned dependencies, and gate promotion to production.
- ▌ Pr Security Review · drvossUse when reviewing a pull request for security issues — automatically analyzes the diff for vulnerabilities, hardcoded secrets, injection risks, and broken access control before merging
- ▌ Fix Build Errors · drvossUse when a build, compilation, or type-check fails — diagnose the error, identify root cause, and apply the minimal fix to get green
- ▌ Fix Github Issue · drvossUse when you have a GitHub Issue number or link and want it resolved end-to-end — reads the issue, locates the bug, applies a fix, writes tests, and opens a PR from the terminal.
- ▌ Evaluate Repository · drvossUse when you need a comprehensive health scorecard of a codebase — scores security, code quality, test coverage, documentation, and AI agent governance across 7 dimensions with a prioritized remediation plan.
- ▌ Gha Security Review · drvossUse when reviewing GitHub Actions workflows for exploitable vulnerabilities — finds pwn-request patterns, expression injection, credential escalation, config poisoning, and supply chain risks, and reports only HIGH and MEDIUM confidence findings with concrete attack paths.
- ▌ Conventional Branch · drvossUse when creating or validating a Git branch name so the branch follows a conventional type/description format, matches the work being done, and starts from the right base branch.
- ▌ Using Git Worktrees · drvossUse when you need multiple branches checked out at once — create isolated working directories for parallel development without cloning the repository repeatedly
- ▌ MCP Builder · drvossUse when you need to build a new MCP server — plan the tool surface, implement the server, register it in Copilot CLI, inspect the config, and test the tools end to end.
- ▌ Scope Guard · drvossUse when a task must stay inside a narrow file or directory boundary, or when risky commands need an explicit stop rule — define the writable surface first so the agent does not drift.
- ▌ Threat Model Analyst · drvossUse when a repository, system, or major change needs a structured STRIDE-A threat model — map architecture, data flows, trust boundaries, abuse cases, and prioritized findings, or update an existing model with a change-focused diff.
- ▌ Team Planner · drvossUse when a task is too large or multi-domain for a single agent — assemble a specialist team, assign work via SQL tracking, dispatch with /fleet or task tool, and synthesize results
- ▌ Add To Changelog · drvossUse when you've shipped a feature, fix, or breaking change and need to update CHANGELOG.md — follows Keep a Changelog format and syncs version numbers across package manifests.
- ▌ Feature Prioritization · drvossUse when you have a backlog of features and need to rank them for the next sprint — scores each feature using Impact × Confidence × Effort matrix with SQL tracking for transparent prioritization.
- ▌ Implementation Review · drvossUse after an implementation pass lands — compare the original task spec or handoff against the delivered diff, classify each requested item, and produce an actionable follow-up report.
- ▌ Context Prime · drvossInvoke when starting a session (or resuming after a break) on a repo before making changes, to load live project context (structure, recent commits, test status)
- ▌ Ide Switching · drvossUse when moving between VS Code and Copilot CLI in the same session — transfers context between environments so you don't lose state when switching from editor to terminal.
- ▌ MCP Ecosystem · drvossUse when Copilot CLI's built-in tools do not cover a service you need — for example PostgreSQL, Redis, Jira, Slack, or an internal API — and you need to add an MCP server beyond the default GitHub MCP. NOT when the built-in tools already cover the task.
- ▌ Context Engineering · drvossUse when designing prompts or agent tasks to optimize information delivery — minimize noise, maximize signal for AI agents
- ▌ API Documentation · drvossUse when source code has changed and API docs are stale, or a new endpoint lacks documentation — generates accurate docs from implementation, not guesswork.
- ▌ Document Generate · drvossUse when a feature, module, or whole project needs missing documentation created from scratch - read the codebase, map the public surface with Diataxis (tutorial/how-to/reference/explanation), and generate the missing docs with cross-links.
- ▌ Security Bounty Hunter · drvossUse when the goal is practical vulnerability discovery for responsible disclosure or bounty submission — focuses on remotely reachable, exploitable issues that qualify for real reports rather than a broad best-practices review
- ▌ Copilot Memory · drvossUse when you need to understand, review, or curate GitHub Copilot's repository-level memory — the persistent facts Copilot reuses across CLI, cloud agent, and code review for the same repository
- ▌ Fleet Parallel · drvossUse when you need to run the same task across many files, components, or contexts in parallel — triggers /fleet mode for batch refactoring, mass testing, or bulk review. NOT when sequential order matters.
- ▌ Stack Detector · drvossScan the current project's tech stack (package.json, config files, lockfiles) and recommend the most relevant skills and rules from this collection for the detected technologies.
- ▌ Systematic Debugging · drvossUse when a bug is non-obvious or has resisted quick fixes — applies a 4-phase root cause analysis to find and permanently resolve the issue rather than patching symptoms
- ▌ Receiving Code Review · drvossUse when you have just received code review feedback (human or agent) and are about to act on it — verify each item against the codebase before implementing, and push back with technical reasoning instead of performative agreement
- ▌ Opportunity Solution Tree · drvossUse when you need to ensure every feature in the backlog connects to a measurable business outcome — applies Teresa Torres' OST framework to map outcomes → opportunities → solutions → experiments.
- ▌ Doubt Driven Development · drvossUse when a non-trivial decision should not stand without a fresh-context challenge - isolate the artifact and contract, run an adversarial review before committing, and reconcile the findings while change is still cheap.
- ▌ Background Agent · drvossUse when a task is too long to block the current session or should run autonomously — delegates to a cloud background agent via & or /delegate so work can continue on GitHub while you keep moving locally, not in a local async PowerShell session.
- ▌ Ecosystem Intake · drvossUse when monitoring a curated ecosystem source and you need to turn new items into concrete adopt/adapt/reject backlog candidates — combines GitHub-native reading with SQL triage and repository-fit scoring.
- ▌ Github Actions Efficiency · drvossUse when auditing GitHub Actions workflows for efficiency — reducing CI minutes, cutting costs, eliminating redundant runs, or optimizing caching and concurrency.
- ▌ Actions Debugging · drvossUse when a GitHub Actions workflow fails — diagnose the run log, identify the root cause, and apply a targeted fix
- ▌ Knowledge Curator · drvossUse when repeated lessons, pitfalls, or decisions should move from temporary session context into durable project guidance — curate what to keep, what to discard, and where it belongs.
- ▌ Plan Mode Mastery · drvossUse when starting a complex multi-step task to create an approved plan, track todos in SQL, and execute with checkpoints
- ▌ Spec Driven Development · drvossUse before starting any non-trivial feature to write a technical spec first — prevents misaligned implementation and scope creep
- ▌ Autopilot Patterns · drvossUse when you're ready to let Copilot execute a multi-step plan autonomously — configures appropriate guardrails, handles plan-to-autopilot transitions, and sets safety boundaries.
- ▌ Github Code Search · drvossUse when you need real-world implementation examples or cross-repository context — search GitHub's global code index with the built-in MCP tools and reuse the results as grounded context.
- ▌ Github Pr Workflow · drvossUse when creating, updating, or managing pull requests — automates the full PR lifecycle (open, review requests, labels, merge) via GitHub MCP
- ▌ Session Management · drvossUse when a task spans multiple steps or sessions and needs structured state tracking — leverages the built-in SQLite session database for todos, dependencies, and batch operation progress.
- ▌ Task Intake Router · drvossUse when a request arrives and the right execution path is unclear — routes the work to the correct mode, agent type, model tier, and delegation pattern before implementation starts.
- ▌ API And Interface Design · drvossUse when defining a public API, CLI, webhook, or SDK surface — lock the contract first so compatibility, validation, and versioning stay intentional instead of accidental
- ▌ Performance Optimization · drvossUse when performance is a real concern — measure first, isolate the bottleneck, and prove the improvement instead of guessing
- ▌ Architecture Decisions · drvossUse when making significant, hard-to-reverse technical decisions to document context, rationale, and consequences as Architecture Decision Records (ADRs)
- ▌ Agentic Engineering · drvossUse when designing or decomposing a task for agent execution — applies 15-minute task units, eval-first loops, and explicit input/output contracts so agents work reliably without implicit state
- ▌ Github Issue Triage · drvossUse when you have a backlog of unorganized GitHub Issues — bulk-reads, labels, prioritizes, and assigns issues at scale using Copilot's built-in GitHub MCP tools.
- ▌ Deprecation And Migration · drvossUse when removing old APIs, migrating to new patterns, or cleaning up legacy code — treats code as liability and follows a structured removal process
- ▌ Source Driven Development · drvossUse when implementing framework-specific or library-specific code — verify non-trivial APIs against official documentation before writing them, and record the source in task notes, docs, or the PR.
- ▌ Cross Session Memory · drvossUse when you need to recover context, decisions, or artifacts across multiple Copilot CLI sessions — search prior session history and resume with the right files, notes, and state.