nushell-optimize
|
deja-history
Search the user's past AI coding sessions. Use when they say things like 'didn't we fix this before', 'what did we decide about X', or before re-debugging an error that may already be solved.
go-pitfalls
>
taskfile-optimize
Taskfile(go-task) 最佳实践与模式，适用于新增/修改 Taskfile.yml、设计任务结构、保证幂等与可维护性、使用 vars/status/preconditions/summary/wildcard 等特性。遇到 Taskfile 设计、重构或排错时使用。
zzz
>
verify-chain
验证链 — 角色对抗式技术文章交叉验证。写完IT文章后，Critic 提取关键断言并生成核查问题，多个 Verifier SubAgent 独立上下文联网验证，Repairer 自动修复。用于规避 AI 幻觉、知识过时、信息遗漏。
yatl-tasks
Track multi-session work with dependencies using yatl (Yet Another Task List). Use when work spans multiple sessions, has dependencies, or requires persistent context across compaction cycles. For simple single-session linear tasks, TodoWrite remains appropriate.
semantic-commit
Generate semantic commit messages from staged changes. Use when committing code to produce consistent, well-structured commit messages following conventional commit format.
software-design-laws
Use this skill when the user asks to evaluate a software design, architecture, API, service boundary, platform abstraction, planning tradeoff, or code-quality question against named software engineering laws or explicit design principles such as Conway's Law, Hyrum's Law, Brooks's Law, YAGNI, Gall's Law, Postel's Law, CAP, or leaky abstractions. Do not use for ordinary PR review or generic critique unless named laws/principles are requested or principal-engineer-review explicitly composes it as a design lens.
executive-summary
Create formal executive summaries from GitHub conversations or meeting transcripts. Use when generating leadership-ready summaries that distill key decisions, alternatives, outcomes, and next steps from complex conversations or meetings. Supports GitHub issues/PRs and transcript URIs (Zoom, Teams, etc.). Outputs are saved to Executive Summaries/ with date-organized structure, and source inputs are archived to Transcripts/ with matching naming.
markdown-to-standalone-html
Convert Markdown documents (*.md files) to self-contained HTML files with embedded images. Use when you need a portable, offline-friendly single HTML file from Markdown—ideal for blog posts, essays, reports, or any content that should work without external dependencies.
dependency-safety
Prevents unnecessary dependency installation and audits unavoidable packages. Use before adding, installing, upgrading, or recommending dependencies, packages, libraries, gems, npm modules, pip packages, crates, GitHub Actions, CLIs, or package-manager commands.
header-image-prompt
Generate an AI art prompt for a blog post or GitHub discussion header image. Interactive skill that reads the content, interviews the user about their vision, and produces a ready-to-use prompt for any AI image generation tool. Use when the user says "header image", "create a header", "generate art for my post", or similar.
pr-handoff
Prepare GitHub pull requests for review and follow up on PR review comments. Use before any PR creation or update, including "open a PR", "create a PR", "make a pull request", `gh pr create`, writing/updating a PR body, requesting review, handling Copilot or human review feedback, resolving comments, or asking whether a branch is ready to review. Includes rubber ducking, semantic commits, PR body/review guidance, 5-minute Copilot feedback follow-up scheduling, and work-repo vs personal-project boundaries.
plan-stress-test
Stress-test plans, designs, proposals, and implementation strategies by interviewing the user one decision at a time. Use when the user says "stress test this", "interview me", "improve this plan", "challenge this plan", "poke holes in this", or wants plan refinement.
principal-engineer-review
Reviews PRs, local diffs, and code-adjacent design changes from a principal engineer standpoint. Use for high-signal review, MVP scope control, maintainability, security-aware review, reuse of existing primitives, avoiding premature optimization, and deciding what must change before merge. When a review turns into architecture/API/platform design and named laws would sharpen the critique, compose with software-design-laws as an optional lens.
d2-diagrams
Create, modify, and render D2 diagrams using the d2 CLI. Use when the user asks for diagrams, architecture visuals, ERDs, sequence diagrams, flowcharts, grid layouts, or any declarative diagramming task. Trigger phrases include "d2 diagram", "create a diagram", "architecture diagram", "sequence diagram", "ERD", "flowchart", "draw", "visualize".
roundtable
Run a multi-model roundtable for architecture decisions, ambiguous tradeoffs, strategy questions, investigation framing, or when the user asks for multiple model perspectives. Fans prompts out to several models, critiques disagreement, and synthesizes consensus plus dissent. Not for fleet mode.
ollama-imagegen
Generate images locally using Ollama's x/z-image-turbo model. Use when the user asks to generate an image, create art, make a picture, or produce a visual. Trigger phrases include "generate an image", "create a picture", "make art", "image of", "draw me", "visualize", "photo of", "illustration of".
brain
Complete operating system for jonmagic's second brain — search, create, capture, commit, and maintain Brain content. Use for any Brain operation: search, daily projects, bookmarks, weekly notes, meetings, sessions, catch-ups, commits, frontmatter, and context loading.
gemini
Shell out to Gemini CLI from Claude for any task. Use when asked to "pipe content to Gemini", "get Gemini perspective", "use gemini CLI", "run headless AI task", "parallel analysis with Gemini", or "get second opinion from Gemini". Useful for alternative perspectives, batch processing, or leveraging Gemini 2.5 Pro capabilities alongside Claude.
vsdevshell
Enter the Visual Studio Developer environment in the current PowerShell session via the VsDevShell module (MSBuild/CL toolchain env vars).
ship-cli
Work management system replacing built-in todos with tracked tasks and stacked changes
cleanup-agent-team-node-processes
|-
pr-ruancat-repo
>-
release-ai-plugins
>-
clone-ruancat-repo
>-
do-long-task
>-
get-git-branch
>-
sync-local-global-agents-skills
>-
use-other-model
>-
use-pnpm
>-
init-playwright
>-
init-pure-admin-iconify
>-
init-shadcn-docs-nuxt
>-
init-release-base-relizy-and-bumpp
>-
git-commit
>-
init-ai-md
>-
init-claude-code-statusline
>-
init-prettier-git-hooks
>-
init-simple-memorix
>-
init-vscode
>-
openspec-ff-change
Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.
openspec-new-change
Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.
openspec-onboard
Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.
openspec-sync-specs
Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.
openspec-verify-change
Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
package-linter
校验和规范化 monorepo 中 Node 包的 package.json、tsup.config.ts、tsconfig.json 配置。在创建新包、修改包配置、审查包规范合规性、初始化新的工作区子包时使用。触发关键词：新建包、创建包、package.json、tsup 配置、包校验、包规范、初始化子包。
skill-hardening-from-incidents
Use when upgrading, hardening, or creating skills from reports, incident reviews, historical lessons, agent-team feedback, or repeated workflow failures
add-favicon
>-
Page 1274 of 1714 · 85663 results
