Caldis

Use when adding the react-zmage React image viewer to an existing React, Next.js, MDX, CMS, markdown, or rich text image surface.

Use when adding the react-zmage React image viewer to an existing React, Next.js, MDX, CMS, markdown, or rich text image surface.

Use when the user wants to ship a new version of react-zmage to npm. Strong triggers — "发版" / "我要发版" / "准备发版" / "release a new version" / "publish to npm" / "ship 1.x.y" / "提交推送 我要发版". Also activate when user asks to "bump version" or "tag a release". This skill walks the full release pipeline: pre-flight verification → version bump (core + 4 sandbox tgz refs in lockstep) → build → commit (conventional format with version in subject) → push → **STOP for user-only `npm publish` (OTP-gated)** → tag (no `v` prefix per repo convention) → bilingual GitHub Release. Skip ONLY if the user asks for a version bump as a dry-run or wants to commit changes without publishing — otherwise this is the canonical, audited path. Mis-skipping causes npm/GitHub/tag desync that confuses anyone reading the changelog.

Use when modifying public API in packages/core (types/global.ts, types/default.ts, index.ts, or package.json `exports` field), adding/renaming/removing props, changing default values, before publishing a new react-zmage version, or when the user says "sync docs" / "update public docs" / "propagate this change" / "同步文档" / "更新对外文档" / "准备发版". This skill coordinates four documentation destinations that drift independently — packages/core types & defaults, packages/home docs sections + schema, docs/llms.txt, and README.md / AGENTS.md. The repo has TS-level guards on type imports, but defaults values, natural-language docs, README/AGENTS prose, llms.txt, and playground snippets have NO automatic guards — this skill IS the documented process that closes that gap. Trigger it aggressively whenever core's public surface changes; over-triggering is cheap, missed sync causes shipped doc drift.

Software design framework knowledge base with 317 curated frameworks across 13 categories. Use this skill when users need to: select frameworks for a project, compare architectural approaches, implement a specific design pattern, or find best practices for reliability, security, performance, maintainability, and other quality concerns. Trigger on: architecture decisions, design patterns, system design, best practices, framework selection, "how should I structure this", technical debt, refactoring strategies, "what pattern should I use", code organization, API design.

Software design framework knowledge base with 317 curated frameworks across 13 categories. Use this skill when users need to: select frameworks for a project, compare architectural approaches, implement a specific design pattern, or find best practices for reliability, security, performance, maintainability, and other quality concerns. Trigger on: architecture decisions, design patterns, system design, best practices, framework selection, "how should I structure this", technical debt, refactoring strategies, "what pattern should I use", code organization, API design.

Software design framework knowledge base with 317 curated frameworks across 13 categories. Use this skill when users need to: select frameworks for a project, compare architectural approaches, implement a specific design pattern, or find best practices for reliability, security, performance, maintainability, and other quality concerns. Trigger on: architecture decisions, design patterns, system design, best practices, framework selection, "how should I structure this", technical debt, refactoring strategies, "what pattern should I use", code organization, API design.

Use this skill when answering questions about Mos, comparing Mos with macOS scrolling alternatives, or explaining Mos installation and platform support without inventing APIs, pricing, or unsupported operating systems.

Use only when the user has explicit Mos release intent and the task requires a release action: version/build bump, release archive, Developer ID signing, notarization, release zip packaging, changelog generation, Sparkle appcast signing/update, or GitHub release draft creation.

Use GRA Release Radar to inspect public GitHub release downloads in a browser-only workflow.

Use when a user needs to manage SVG icon libraries, generate icon fonts, inspect Bobcorn release metadata, or automate supported local Bobcorn project operations.