Specialized knowledge for writing modern high-quality CSS. Trigger this skill when starting a new CSS project/file, when the user asks about new CSS features (e.g. Masonry, View Transitions, Container Queries, Scroll-driven animations), or requests refactoring of legacy styles to modern standards.
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance…
Turn a product or marketing URL, pasted script, or brief into a product launch / promo video — SaaS promos, feature reveals, product demos, app and company launches. Use when the user wants to market, launch, promote, or reveal a product; the default for any commercial URL. Site tours / showcases of a website route…
This skill should be used when the user asks for "deep research", "research team", "comprehensive analysis", "research report", "investigate thoroughly", "compare X vs Y in depth", or needs synthesis across multiple sources with verification. It spawns a coordinated team of researcher agents across multiple rounds…
Fan out a batch of autopilot-queued issues to parallel background worktree subagents — each runs /autopilot at the build model from its 'model:' label — with a gating review at Opus 5 or above and never below the build (Opus reviews Sonnet and Opus builds, Fable reviews Fable builds).
End-user browser automation with cmux. Use when you need to open sites, inspect or interact with browser surfaces, wait for page state, and extract data without stealing focus.
Native Neovim config idioms and conventions — use whenever writing, reviewing, or modifying any Neovim configuration that uses Neovim's built-in conventions WITHOUT a plugin manager framework (no lazy.nvim, packer, etc.). Covers directory structure, vim.pack plugin management, lsp/ auto-discovery, plugin/ loading…
Guide for setting up automated npm package releases via GitHub Actions using Trusted Publishing (OIDC). Use when creating release workflows, publishing to npm, or troubleshooting CI/CD publish failures.
A local email tool for reading, searching, sorting, and tagging mail stored on the computer. It uses notmuch to index messages and afew to apply tags and suggest filtering rules.
Bootstrap a workstation with the dotfiles framework. Takes a GitHub user / owner+repo / explicit clone URL and runs dot init (which shells out to chezmoi) with the right safety prompts. Honors the active agent profile (ask / plan / apply / audit) so it defaults to dry-run in safer modes and full apply in apply.
Walden drafts and maintains feature specs in .walden/specs/ with a gated workflow: EARS requirements, design documents, implementation tasks, and execution of approved tasks. Use when the user asks for Walden, a feature spec, requirements, a design doc, an implementation plan, or work from an existing .walden/specs/…
Plan a new objective end-to-end in this repo's docs/mbo Management-By-Objective system — turn a GitHub issue or a gss draft-PR worktree into consistent design/spec/plan artifacts and track it in docs/mbo/index.md. Use this whenever the user wants to START planning or designing a new feature, skill, CLI, or service…
Bootstraps a deep-sky object (DSO) astrophotography project from raw acquisition frames (own rig, not a smart telescope), AND generates a complete, polished HTML documentation page, a processing checklist, an AstroBin post JSON, a PixInsight process icon set (XPSM), and a ready-to-paste PixInsight project Description…
Draft or update clear, reviewer-centered pull request descriptions. Use when the user asks for a PR description/body, GitHub PR body, PR summary, context-first PR narrative, to update an existing PR description, or to turn commits/diffs into a consistent PR narrative. Do not use for commit messages unless the user is…
Inventory of the CLI tools actually installed on this machine (aqua/mise/nix) and which one to reach for per task — search, structural rewrite, structured data, diff, HTTP, profiling, VCS, k8s, security, docs, media. Use when picking a command-line tool, when a POSIX default (grep/find/sed/curl/wc) feels clumsy, when…
Standalone code review for any scope — PR number, branch, file paths, or current changes. Synthesizes intent, runs 11 parallel specialized agents, and presents actionable findings with a verdict. For PR scope, optionally posts the review to GitHub with inline comments.
Principles for writing, changing, and testing code, covering readability at every scale, abstraction and naming, interfaces, comments and documentation, tests as maintained code, and standards of evidence for claims about code behavior.
Write a Japanese technical article for Zenn or Qiita in aiya000's own writing style, learned from his past articles, with the target platform decided from the current directory. Use when the user asks to write, draft, or rewrite a tech article, blog post, or note, or invokes /write-tech-note.
USE FOR: Verifying technical claims, comparing options, and investigating unfamiliar libraries/APIs/tools with cited, confidence-rated evidence. DO NOT USE FOR: implementation, opinion without evidence, or tasks better served by a narrower repo-specific skill (e.g. data-platform, dev-platform-workflow).
Write or revise text in Nithin Bekal's voice: Slack messages, PR descriptions, docs, emails, review comments, and technical notes. Use for practical, concise, low-drama writing grounded in concrete details.
★not rated 11 1mo agoA52 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: