- name
Design, build, or review a one-time in-app guide in Cherry Studio — a spotlight coachmark on a moved entry point, a changed default, or a capability users would not find, or a dialog that introduces n
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add CherryHQ/cherry-studio --skill product-guide -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add CherryHQ/cherry-studio --skill product-guide -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add CherryHQ/cherry-studio --skill product-guide -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add CherryHQ/cherry-studio --skill product-guide -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/CherryHQ/cherry-studio/tree/HEAD/.agents/skills/product-guideFrom the publisher
A guide tells users, once, where something is or what changed. It must look like part of Cherry Studio, show real data, never disturb the UI it points at, and never come back after it is dismissed.
Reference implementation: the Cherry Cloud plan activation guide from #24425. Its files exist on main once that PR merges; until then read them on the PR branch. Before that merge, main has an older, toast-only useCherryCloudSubscriptionReminder.ts that is not the reference. The design reference repeats the essential structure so this skill works without them.
src/renderer/windows/main/subscription/CherryCloudPlanActivationDialog.tsx: the decision dialog and its abstract illustration.src/renderer/components/cherryCloud/CherryCloudModelGuide.tsx: the anchored spotlight guide.src/renderer/windows/main/hooks/useCherryCloudSubscriptionReminder.ts: detection, edition rules, and data derivation.Match its size, type, spacing, and color unless a human asks otherwise. Exact values are in design-reference.md.
Add a guide only when at least one is true:
Do not add one for a new feature that sits where users already look, for copy tweaks, or for anything a toast or an inline empty state already explains. One change gets at most one guide.
Choose the audience. A guide about changed or moved behavior is for upgraded users only: fresh installs never saw the old UI. A guide about newly unlocked content follows the event that unlocked it.
Decide eligibility from the user's own state, not from a missing seen flag: renderer persist cache is empty on both a fresh install and an upgrade. Mark the guide due at the moment that changes the user's experience, and show it only while that due record exists. When that moment is in the renderer (an unlocking event, a renderer-side check of the user's stored setting), write the due record there. When only the main process knows (a data or preference migration), main cannot write renderer persist cache. If the migrated state still tells upgraded users apart from fresh installs, read that. If it does not (for example, both end up with the same preference value), the guide needs a marker written by the migration; that is a new channel, so stop and ask a human before adding it.
If the moved control is driven by a user-customizable default (a preference such as pinned toolbar items), changing the default does not affect existing users. That needs a migration and a product decision about whose settings to rewrite; raise it with a human before designing the guide.
cherry-electron-dev). Name the exact component and element the guide points at. Never place a guide from memory or from an older design.data-* attribute.For any guide with visible UI, produce light and dark preview screenshots (an HTML mock or a dev-instance capture) and get explicit human agreement before implementing. Iterate on the preview, not on shipped code. Save the screenshots under .context/.
pointer-events-none, so a click on the target also runs the target's own action, and an outside click also reaches whatever is underneath. Both are intended.text-xs (12px) and titles are text-sm font-semibold (14px). Never use 10/11/13px or text-base and larger inside a guide. When a card feels too large, reduce width and padding, not the type scale.top for targets near the bottom, such as the composer), align its edge with the cutout (alignOffset equal to minus the cutout padding for align="start"), and set the cutout radius to the target's radius plus the padding, or rounded-full for a round button.w-76 (304px) wide; height follows content (a text-only card has no preview strip and is shorter). Dialogs are 340px wide. Checkbox and button labels fit on one line; descriptions take at most two lines in English.emphasis button. primary appears only as a thin selection indicator. No gradients, colored tags, or ad-hoc dark: overrides.Skip this step if the guide shows no models, plans, quotas, or dates; still check both editions for layout differences near the target.
GET /api/v1/public/plans on the edition's Cherry Cloud origin) or the signed-in account response; never invent sample content. Seed dev-profile test data from those real values.expires_at; its date is the subscription_month quota window's period_end.ui.<feature>.*) and update it on every dismissal path.
ui.cherry_cloud.model_guide.seen flag, set it on dismissal, and check it before showing. Otherwise the next launch re-derives the guide and it returns.attemptedModelIdRef), never by handler identity, or the guide re-fires the action and loops with "Maximum update depth exceeded".useMandatoryGateOpen) or other dialog is open.Add keys to src/renderer/i18n/locales/en-us.json, run pnpm i18n:sync, translate every locale, and run pnpm i18n:check. Format dates with Intl.DateTimeFormat(i18n.language, …).
Write contract tests, not behavior pins:
Run them with explicit paths (pnpm test:renderer <files>).
Follow cherry-electron-dev: one dev instance at a time, a dedicated CS_DEV_USER_DATA_SUFFIX profile, and CDP for driving the app.
// TEMP-VERIFY. It must never be committed.ui.theme_mode).grep -rn "TEMP-VERIFY" src returns nothing.pnpm i18n:check on the changed files.© 2026 Skills Rack.
---name: product-guidedescription: Design, build, or review a one-time in-app guide in Cherry Studio — a spotlight coachmark on a moved entry…---# .agents/skills/product-guide/SKILL.mdOverview
Design, build, or review a one-time in-app guide in Cherry Studio — a spotlight coachmark on a moved entry point, a changed default, or a capability users would not find, or a dialog that introduces newly unlocked content. Use when a change moves UI, changes a default users rely on, or ships something hard to discover, and whenever a guide's design, data, behavior, or Electron verification is in question.
FAQ
Download .agents/skills/product-guide/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/CherryHQ/cherry-studio.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.