claude-hud
claudeReal-time statusline HUD for Claude Code - context health, tool activity, agent tracking, and todo progress
2 commands
包含 superpowers-zh 中文技能集(20 个)、harness-cc 编码工作流引擎、planning-with-files 计划管理、ponytail 代码精简(6 个)、doc/pptx 文档处理技能、statusline 状态栏、通用配置模板和 MCP 配置
Plugin animus from marketplace animus-marketplace in jovetickop/my-claude-code-plugin-pack. Commands read from the repo's manifest — 1 month ago.
brainstorming在任何创造性工作之前必须使用此技能——创建功能、构建组件、添加功能或修改行为。在实现之前先探索用户意图、需求和设计。
chinese-code-review中文 review 沟通参考——话术模板、分级标注(必须修复/建议修改/仅供参考)、国内团队常见反模式应对。仅在用户显式 /chinese-code-review 时调用,不要根据上下文自动触发。
chinese-commit-conventions中文 commit 与 changelog 配置参考——Conventional Commits 中文适配、commitlint/husky/commitizen 中文模板、conventional-changelog 中文配置。仅在用户显式 /chinese-commit-conventions 时调用,不要根据上下文自动触发。
chinese-documentation中文文档排版参考——中英文空格、全半角标点、术语保留、链接格式、中文文案排版指北约定。仅在用户显式 /chinese-documentation 时调用,不要根据上下文自动触发。
chinese-git-workflow国内 Git 平台配置参考——Gitee、Coding.net、极狐 GitLab、CNB 的 SSH/HTTPS/凭据/CI 接入差异与镜像同步配置。仅在用户显式 /chinese-git-workflow 时调用,不要根据上下文自动触发。
dispatching-parallel-agents当面对 2 个以上可以独立进行、无共享状态或顺序依赖的任务时使用
docUse when the task involves reading, creating, or editing `.docx` documents, especially when formatting or layout fidelity matters; prefer `python-docx` plus the bundled `scripts/render_docx.py` for visual checks.
executing-plans当你有一份书面实现计划需要在单独的会话中执行,并设有审查检查点时使用
finishing-a-development-branch当实现完成、所有测试通过、需要决定如何集成工作时使用——通过提供合并、PR 或清理等结构化选项来引导开发工作的收尾
tdd-workflow面向通用 C++/Qt 开发的 TDD 工作流指南,使用 /tdd-workflow 显式调用
harness-cc复杂任务的编码工作流技能。输入 PRD+方案文档,自动拆解为可执行任务列表,按状态机逐个推进,验收后提交。支持 C++/Qt、Python、Node.js、Rust、Go。
integrate-to-animus当用户要求将新的技能/工具/配置集成到 animus 插件包时使用。例如"把XXX集成到插件包中"、"添加YYY到插件"、"把ZZZ打包到工具包
mcp-builderMCP 服务器构建方法论 — 系统化构建生产级 MCP 工具,让 AI 助手连接外部能力
planning-with-filesImplements Manus-style file-based planning to organize and track progress on complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when asked to plan out, break down, or organize a multi-step project, research task, or any work requiring 5+ tool calls. Supports automatic session rec
ponytail-auditWhole-repo audit for over-engineering. Like ponytail-review, but scans the entire codebase instead of a diff: a ranked list of what to delete, simplify, or replace with stdlib/native equivalents. Use when the user says "audit this codebase", "audit for over-engineering", "what can I delete from this
ponytail-debtHarvest every `ponytail:` comment in the codebase into a debt ledger, so the deliberate shortcuts and deferrals ponytail leaves behind get tracked instead of rotting into "later means never". Use when the user says "ponytail debt", "/ponytail-debt", "what did ponytail defer", "list the shortcuts", "
ponytail-gainShow ponytail's measured impact as a compact scoreboard: less code, less cost, more speed, from the benchmark medians. One-shot display, not a persistent mode, and not a per-repo number. Trigger: /ponytail-gain, "ponytail gain", "what does ponytail save", "show ponytail impact", "ponytail scoreboard
ponytail-helpQuick-reference card for all ponytail modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /ponytail-help, "ponytail help", "what ponytail commands", "how do I use ponytail".
ponytail-reviewCode review focused exclusively on over-engineering. Finds what to delete: reinvented standard library, unneeded dependencies, speculative abstractions, dead flexibility. One line per finding: location, what to cut, what replaces it. Use when the user says "review for over-engineering", "what can we
ponytailForces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before
pptxUse this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); e
receiving-code-review收到代码审查反馈后、实施建议之前使用,尤其当反馈不明确或技术上有疑问时——需要技术严谨性和验证,而非敷衍附和或盲目执行
requesting-code-review完成任务、实现重要功能或合并前使用,用于验证工作成果是否符合要求
subagent-driven-development当在当前会话中执行包含独立任务的实现计划时使用
systematic-debugging遇到任何 bug、测试失败或异常行为时使用,在提出修复方案之前执行
test-driven-development在实现任何功能或修复 bug 时使用,在编写实现代码之前
using-git-worktrees当需要开始与当前工作区隔离的功能开发,或在执行实现计划之前使用——通过原生工具或 git worktree 回退机制确保隔离工作区存在
using-superpowers在开始任何对话时使用——确立如何查找和使用技能,要求在任何响应(包括澄清性问题)之前调用 Skill 工具
verification-before-completion在宣称工作完成、已修复或测试通过之前使用,在提交或创建 PR 之前——必须运行验证命令并确认输出后才能声称成功;始终用证据支撑断言
workflow-runner在 Claude Code / OpenClaw / Cursor 中直接运行 agency-orchestrator YAML 工作流——无需 API key,使用当前会话的 LLM 作为执行引擎。当用户提供 .yaml 工作流文件或要求多角色协作完成任务时触发。
writing-plans当你有规格说明或需求用于多步骤任务时使用,在动手写代码之前
writing-skills当创建新技能、编辑现有技能或在部署前验证技能是否有效时使用
Real-time statusline HUD for Claude Code - context health, tool activity, agent tracking, and todo progress
2 commands
Matt Pocock's agent skills for real engineering (grilling, spec/ticket flows, TDD, code review, domain modelling and more).
39 skills
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
15 skills · hooks
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.
6 skills
tasteskill 2.5.1: professional company websites at the figma.com and x.ai level, with one section per screen, real photographs, real product UI, effects kept for tech and gaming pages, and a real-browser checker and finish gate.
1 skill
5 skills + 35 modes + Material Passport pipeline. Includes v3.6.7 cross-model audit gate and v3.6.8 generator-evaluator contract.
5 skills · 16 commands · 4 agents · hooks
Claude Skills for Obsidian
6 skills
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.