claude

agent-skills-zh-CN

Agent Skills 简体中文版:24 个给 AI coding agent 的正式工程 skill,涵盖规格、规划、实现、测试、审查到发布。

0 on GitHubby VictorLinv1.0.0updated 1 month agodevelopment
/

Plugin agent-skills-zh-CN from marketplace agent-skills-zh-CN in Hayatelin/agent-skills-zh-CN. Commands read from the repo's manifest — 1 month ago.

What it installs

Skills (24)

  • api-and-interface-design

    引导设计稳定的 API 与接口。Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.

  • browser-testing-with-devtools

    通过 Chrome DevTools MCP 在真实浏览器中测试。Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be

  • ci-cd-and-automation

    自动化 CI/CD pipeline 的构建。Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.

  • code-review-and-quality

    运行多面向的 code review。Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.

  • code-simplification

    为了可读性而简化代码。Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.

  • context-engineering

    优化 agent 的 context 设置。Use when starting a new session, when agent output quality degrades, when switching between tasks, or when you need to configure rules files and context for a project.

  • debugging-and-error-recovery

    引导系统性的根因调试。Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing.

  • deprecation-and-migration

    管理淘汰(deprecation)与迁移(migration)。Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when deciding whether to maintain or sunset existing code.

  • documentation-and-adrs

    记录决策与文档。Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.

  • doubt-driven-development

    让每个非平凡的决策在定案前,都先经过一次 fresh-context 的对抗性审查。Use when correctness matters more than speed, when working in unfamiliar code, when stakes are high (production, security-sensitive logic, irreversible operations), or any time a confident output would be cheaper to verify now than to debug later.

  • frontend-ui-engineering

    打造 production 质量、无障碍、响应式的用户接口。适用于创建或修改接口与页面、创建组件、实现布局、符合 WCAG 无障碍要求、管理状态,或当产出需要具备 production 质感、而非一眼就看出是 AI 生成的时候。Use when building or modifying interfaces and pages, creating components, implementing layouts, meeting WCAG accessibility requirements, managing state, or when the output needs to look

  • git-workflow-and-versioning

    创建有纪律的 git 工作流程。任何代码变更都适用。适用于 commit、开分支、解冲突,或需要把工作组织成多条平行进行的工作流时。也适用于发版、决定语意化版本号要跳哪一级、打 tag 或撰写 changelog。Use when making any code change. Use when committing, branching, resolving conflicts, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a

  • idea-refine

    通过结构化的发散与收敛思考,把粗糙的点子精炼成锋利、可运行的概念。适用于点子还很模糊、想在投入计划前压力测试假设、或想先扩大选项再收敛到其中一个的时候。Triggers on "ideate", "refine this idea", or "stress-test my plan".

  • incremental-implementation

    以增量方式交付变更。Use when implementing any feature or change that touches more than one file. Use when you're about to write a large amount of code at once, or when a task feels too big to land in one step.

  • interview-me

    挖出用户真正想要的,而不是他们以为自己应该要的。做法是一次一题的访谈,直到对背后意图有约 95% 的信心。Use when an ask is underspecified ("build me X" without "for whom" or "why now"), when the user explicitly invokes ("interview me", "grill me", "are we sure?", "stress-test my thinking"), or when you catch yourself silently filling in ambiguous re

  • observability-and-instrumentation

    为代码加上仪器化,让正式环境的行为可见、可诊断。Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence it works. Use when production issues are reported but you can't tell what happened from the available data.

  • performance-optimization

    对前端、后端、查询与数据库进行应用程序性能优化。Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks.

  • planning-and-task-breakdown

    把工作拆解成有顺序的任务。Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.

  • security-and-hardening

    强化代码以抵御漏洞。Use when handling user input, authentication, data storage, or external integrations. Use when building any feature that accepts untrusted data, manages user sessions, or interacts with third-party services.

  • shipping-and-launch

    为正式上线做好准备。适用于准备部署到 production、需要上线前检查清单、构建监控、规划分阶段发布,或需要回滚策略的时候。Use when preparing to deploy to production. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.

  • source-driven-development

    让每个实现决策都有官方文档为依据。Use when you want authoritative, source-cited code free from outdated patterns. Use when building with any framework or library where correctness matters.

  • spec-driven-development

    先写规格再写程序。Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea.

  • test-driven-development

    以测试驱动开发。Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.

  • using-agent-skills

    探索并调用 agent skills。Use when starting a session or when you need to discover which skill applies to the current task. 这是统管其他所有 skill 如何被探索与调用的 meta-skill。

View source on GitHub

Similar plugins

superpowers

claudecodex

Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques

15 skills · hooks

obra/superpowers 316,836

context7

claudecodex

Up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your coding agent's context.

1 MCP server

upstash/context7 64,709

Build powerful, stateful CLI interfaces for any GUI application using the cli-anything harness methodology.

5 commands

HKUDS/CLI-Anything 58,665

Automates browser interactions for web testing, form filling, screenshots, and data extraction

12 skills

vercel-labs/agent-browser 50,373

Use Alibaba Open Code Review from local Codex.

2 skills

alibaba/open-code-review 50,068

slidev

claude

Claude Code skill for creating and presenting Slidev slidedecks

1 skill

slidevjs/slidev 49,452

Maintain agent-skills-zh-CN?

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.

claude & codex pluginslisted