- Skills
- 17
- 仓库
- 1
- 职业覆盖
- 5
- 场景覆盖
- 5
- Stars
- ★ 1
JinsYin 的 Skills 17
write-great-skill
Workflow and quality bar for agent skills: draft, polish, compress, verify, ship. Use whenever creating or editing a skill (`SKILL.md`, `references/`, `rules/`), or when project conventions route root `CLAUDE.md`/`AGENTS.md` edits here, even if the user only says “改一下这个 skill”.
write-fspec
Derive the 功能规格说明书 (functional spec) from the product prototype and keep it versioned under products/fspec/: Flyway-style V files plus a merged CURRENT.md. Use when a prototype is finalized, changed or backfilled, when a draft V is confirmed or CURRENT.md lags, or when the user mentions 功能规格, 功能规格说明书 or fspec. Not for the feature spec (.scratch/*/spec.md) or DESIGN.md.
version-release
Cut a SemVer release — bump every module's version in lockstep, promote CHANGELOG.md, commit, tag, push to origin. Args `major|minor|patch|<x.y.z>`; none → level inferred from `[Unreleased]`, confirmed with user. Invoke only on explicit request: the user, another skill, or a project convention asking for a release.
ui-ux-best-practices
UI/UX rules for Chinese-language React/Vue admin consoles and their product/design specs. Use when designing, building, reviewing, or refactoring forms, lists, modals/drawers, destructive actions, copy, formats, or console layout.
spring-boot-best-practices
Spring Boot 3 + Java 21 + MyBatis Plus 项目的编码规范与架构纪律。涵盖分层依赖、国密 SM2/SM3/SM4、MyBatis Plus 实体与主键策略、多方言数据库迁移、R/RList/RPage 响应包装、DTO 职责边界、鉴权框架选型（Spring Security / Sa-Token）与声明式权限校验、命名约定、模块 README 文档要求。在编写、审查或重构 Spring Boot 后端代码时使用——尤其是新增 Controller/Service/Mapper、定义 Entity 或 DTO、写数据库迁移、处理加解密与签名、设计 API 契约、或接入鉴权与权限校验时。
setup-rules
Conduct an interactive interview, then install selected agent conventions, adapters, `skillsw`, and sensitive-file read restrictions into a project; `update` refreshes installed items without prompting. Use when the user asks to set up agent rules, or run `update` after `setup-rules` conventions change (e.g. Skill Workflow sync). Not for reviewing or hand-editing `CLAUDE.local.md`.
self-improve
Retrospect the current agent session (failures, user corrections, detours, token-heavy or slow turns) into lessons, shipped as minimal edits to jinsyin/skills skills — or a new skill, or a `setup-rules` convention for a heavy manually-invoked third-party skill — each as GitHub Issue + PR; nothing qualifies → closed `no-pr` record Issue. Args `[--dry-run] [focus]`. Invoke only when the user, a rule, or another skill calls for it.
re-spec
Revise feature spec to match newly confirmed 功能规格说明书 (fspec) V file: align user stories, decisions and Out of Scope with what prototype settled, for matt /to-spec specs (.scratch/<feature>/spec.md or a GitHub issue) and superpowers specs (docs/superpowers/specs/*.SPEC.md). Use after /write-fspec <prototype> activates V, or when user says 修订 spec, 对齐 spec or re-spec. Not for writing fspec itself (write-fspec) or new spec (/to-spec, brainstorming).
ideate
Clarify product ideas into docs/ideas/idea.md, migrating legacy requirement docs.
gsdspec
Unified front-door to the GSD workflow (.planning/ + /gsd:* commands), dispatching 20 modes by --flag: --fast/--quick/--debug for trivial edits, one scoped problem, and root-cause debugging; --discuss-phase/--plan-phase/--plan-review/--replan-phase for the discuss → research+plan → cross-AI review → fold-back convergence loop; --ui-spec for the UI design contract; --code-review to audit and auto-fix changed source; --uat-phase/--uat-autorun/--uat-newtest/--uat-newgap/--uat-quickfix/--uat-planfix to run UAT, register Tests/Gaps, and close Gaps; --vrf-autorun/--vrf-review/--vrf-approved to pre-run a checkpoint's verify steps, audit the round's changes, and release the gate; --add-todo/--add-backlog to capture work. Use this skill whenever the user mentions a Phase number, planning/discussion/research/plan review, UAT/acceptance/Gap/checkpoint/release/approved, or says 'just fix this quickly', 'why is this failing', 'review the code', 'spec the UI', 'add a todo', 'park this idea' — or names gsdspec (formerly gsx), gsdspec-fast, gsx-uat-autorun and friends. Prefer it over calling /gsd:* directly: the Context7 docs gate, prototype-fidelity constraints, acceptance write-back and commit hygiene live here, and calling the command directly loses them.
github-pr-merge
Review and squash-merge open GitHub PRs one by one via `gh`, user deciding each. Use when user wants to review, triage, or merge open PRs, including PRs `self-improve` opened. Args `[<pr#>] [-R <owner/repo>]`.
frontend-ui-best-practices
Stack baseline and module documentation rules for React + shadcn/ui frontend projects. Covers the package manager, build tool, framework, component library, icon set, styling and testing choices, the scaffold settings that must be right from the start, the split between stylesheet and design-token files, and the README structure required at the repository root and in every monorepo package. Use when initialising a frontend project, changing dependency choices, setting up styles and tokens, adding a package, or writing module documentation. Interface and interaction rules — forms, overlays, lists, formats, icons — are out of scope.
doc-writing-best-practices
中文技术文档的写作规范。涵盖中西文混排的空格与标点、标题层级与代码块标注、表格与列表的取舍、以及"写清为什么"和"示例可直接抄用"的内容要求。在编写或修改 README、设计文档、运维手册、变更说明、注释块等任何面向人阅读的中文技术文档时使用——尤其是产出 Markdown 文件、写提交说明、或整理已有文档时。
doc-to-md
Convert documents (PDF, Office, HTML, EPUB, images, audio, etc.) to faithful Markdown saved beside the source: markitdown and markdownlint, then refine structure and strip extraction noise against the source without rewriting text.
devops-best-practices
Rules and playbooks for local dev env and delivery chain: Dockerfile, docker-compose.yml, process-compose.yml, Drone `.drone.yml`, Kubernetes Kustomize + Helm kept in parity, and `deploy/README.md` delivery facts. Use when writing, reviewing or planning any of these; when a task adds a database, cache, MQ or runnable process; when backfilling a missing dev env in an existing project; when planning or running a delivery phase (containerize, set up CI, deploy to k8s, release); or when adding a module, port, env var, config key or secret to a project that already has these files — even if no file is named.
design-to-code
Rebuild high-fidelity design or prototype (HTML, React JSX, Figma export, screenshots) as production React code. Stack/engineering rules → frontend-ui-best-practices; design system → products/design/DESIGN.md (restyle mode: one authored from style brief); structure/interaction → products/prototype/.
backfill-prototype
Backfill landed frontend into product prototype (products/prototype/): compare every page structurally, add what frontend shows and prototype lacks in one pass, log it under [Unreleased] in prototype CHANGELOG, then hand off to /write-fspec. Use when user says 回补原型 or backport, or before starting new page or look on app whose frontend was changed directly. Not for designing new pages (edit prototype directly) or porting prototype changes into code (design-to-code).