[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F2DCSGKVG59FFMDBHY8TH6":3,"skill-same:01M7F2DCSGKVG59FFMDBHY8TH6":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7F2DCSGKVG59FFMDBHY8TH6","dsh-client-ui-ux",null,"Design and review DeepSeek Harness client UI changes — visual token discipline, reuse-before-adding, feedback surfaces (toast vs in-place notice vs empty state), overlay and menu safety, platform window adaptation, loading states, and error copy placement. Use when adding or changing product-user-visible GUI behavior in packages\u002Fclient, or when reviewing such a PR.","OJamals\u002Ffi","OJamals","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F190230429?v=4","01M7F28NRDVKV848GX2433PSBH","A. Omar Aljamal, MD","01M7F28NS029WSHBC32Z79PD0F",3,"MIT","https:\u002F\u002Fgithub.com\u002FOJamals\u002Ffi\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdsh-client-ui-ux\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: dsh-client-ui-ux\ndescription: Design and review DeepSeek Harness client UI changes — visual token discipline, reuse-before-adding, feedback surfaces (toast vs in-place notice vs empty state), overlay and menu safety, platform window adaptation, loading states, and error copy placement. Use when adding or changing product-user-visible GUI behavior in packages\u002Fclient, or when reviewing such a PR.\n---\n\n# DeepSeek Harness Client UI\u002FUX\n\nThis skill is guidance, not a complete checklist. It covers judgment calls that lint, typecheck, and the i18n gate cannot make: where feedback appears, what gets reused, and how surfaces behave at window edges and across platforms. Copy quality itself follows [dsh-prose-standard](..\u002Fdsh-prose-standard\u002FSKILL.md); locale ownership follows the [locale-owned copy decision](..\u002F..\u002Fnotes\u002Fimplemented\u002Farchitecture\u002F2026-08-23-locale-owned-client-ui-copy.md); styling ownership and token rules live in [docs\u002Fweb-styling.md](..\u002F..\u002F..\u002Fdocs\u002Fweb-styling.md) and the [ui-primitives component catalog](..\u002F..\u002F..\u002Fpackages\u002Fclient\u002Fui-primitives\u002FREADME.md#component-catalog) — this skill adds judgment on top of those rules, not a second copy of them.\n\n## Visual foundation\n\n- **Use existing tokens for color, radius, and spacing.** Before introducing a literal value, search the target page and its nearest established sibling (the Plugins page is the usual reference for full-page surfaces) for the token or value already in use, and adopt it. The same applies to whole treatments — toasts, menus, in-message artifact previews, sidebar tab layout, colors, clearance rules, page padding: reuse the established component or rule wherever one exists instead of inventing a parallel one.\n- **Verify every color in both light and dark mode.** An ink\u002Fbackground pair must stay readable under both themes before it ships. Dimmed tones are the standing counter-example: they suit decorative surfaces, but on text they routinely fall below readability in one theme — never put a dimmed color on text without checking both.\n- **Font weight tops out at 500 in feature CSS you add or change.** Do not use 600+ for emphasis; differentiate with size or ink instead. The markdown typography tokens owned by ui-theme are the standing exception.\n- **Pick font sizes from the theme typography variables when an existing role matches, otherwise from the page's existing scale.** Parallel content shares one size; never invent a size for a single element, and keep the number of distinct sizes on a page small (13px is the established row\u002Fdetail size). When the page itself has no precedent, borrow the size and spacing ratios of the most similar existing page or element.\n- **Icons, text, and neighbouring elements stay proportionate and aligned.** Every element lines up with its siblings along a deliberate axis (baseline, vertical center, or shared edge), and an icon's size stays in proportion to the text beside it; never ship an element that aligns to nothing or visibly outweighs its neighbours.\n\n## Reuse before adding\n\n- **Extend an existing component, container, or interaction before creating a new one.** A new capability that fits an existing surface (an extra menu item, a new prop on an existing primitive) beats a parallel element stacked beside it.\n- **Icons come from the existing icon library.** Pick the semantically closest existing icon; a new glyph requires designer approval before it lands — when reviewing a PR that adds one, suggest requesting a designer review.\n- **Right-sidebar content registers a slot in the existing sidebar**, never a separate sidebar. Every sidebar tab declares a tab icon matching its meaning.\n- **Icon-only actions whose meaning is not obvious get a Tooltip.** Informational content the pointer must rest on or select uses HoverCard instead. Prefer these shared primitives over ad-hoc title attributes.\n\n## Feedback surfaces\n\nChoose the surface by the lifetime of the message relative to the surface that produced it:\n\n- **Transient operation outcomes use the app-wide Toast primitive**, not in-place notices, and the toast's state and rendering live in a host that outlives the reporting surface (a `shell.overlay` entry, as RowActionToast does) — a toast rendered by the panel itself unmounts with that panel. A deletion can close the panel or tab that requested it; only a toast held outside that surface survives the close. Report success and failure; do not report still-pending states.\n- **A failed operation keeps the data visible.** A failed deletion keeps its row; the toast announces the failure. Never blank content to show an error for a transient operation.\n- **In-place notices are for states tied to the surface itself**: a query failure with its Retry action, field validation on the form that owns the field. A populated panel keeps a compact notice beside its retained content; only an empty panel centers a full error state.\n- **Error copy is plain language, and short.** No internal jargon or technical nouns unless an error code must be exposed for debugging. Prefer one clear sentence; anything explainable in two sentences must not grow into paragraphs. A Chinese notice of at most two sentences omits the trailing 句号（。）. The notice must not break the existing layout — reserve its space or overlay it; never shift neighbouring elements.\n\n## Loading states\n\n- Lists use their skeleton; every other page-level load centers a bare spinner. Never place a spinner in a corner of the page.\n- One loading treatment per page\u002Fcomponent — concurrent regions must not each flash their own style.\n- No loading text unless the context needs it (narrow sidebars almost never do).\n\n## Overlays and menus\n\nEvery menu, popover, and tooltip must be verified for all three before merge:\n\n- **Dismissable**: outside click (and Escape where focusable) closes it.\n- **Viewport-fitting**: it slides or flips to stay inside the window with an edge margin, and flips only into a side that actually fits (no oscillation when neither side fits).\n- **Unclipped**: it escapes `overflow` ancestors and containing blocks (portal to body where needed) and is never covered by neighbouring elements.\n\nScrollbars stay inside their container: use the shared scrollbar styles rather than component-specific selectors, and verify the bar neither overflows the container nor gets clipped by its rounded corners or edges — keep a small inset instead of letting it sit flush against the container edge.\n\n## Platform window adaptation\n\n- Any new header element or full page must account for macOS and Windows window chrome. On macOS the titlebar clearance is `--dsh-frame-top-clearance`, consumed by Menu, Modal, and overlay primitives as their top safe margin — **never change the global variable to fix one page**. Add a scoped `[data-platform='darwin']` override on the page's own inset instead, and assert the override in the page's stylesheet spec.\n- State the intended total offset (clearance + page inset) when reviewing, so two pages aligning to \"the same top spacing\" agree on the sum, not just one addend.\n\n## Spacing review\n\n- Review every changed region for gaps: nothing sits flush against its neighbour without an intentional gap, and adjacent icons and elements keep the region's established spacing.\n- Prefer symmetry for parallel elements; an unexplained one-off gap or offset usually signals a missed shared value.\n\n## Design review escalation\n\n- A PR with extensive UI changes, or any clearly user-perceivable change to UI or interaction, must get a designer or product review. When no approver holds that role, suggest requesting one from the design\u002Fproduct reviewers (roster as of 2026-09: yx zhang, yifffan, zhangziya, gaokaige; update this list here when membership changes).\n","# DeepSeek Harness Client UI\u002FUX\n\nThis skill is guidance, not a complete checklist. It covers judgment calls that lint, typecheck, and the i18n gate cannot make: where feedback appears, what gets reused, and how surfaces behave at window edges and across platforms. Copy quality itself follows [dsh-prose-standard](..\u002Fdsh-prose-standard\u002FSKILL.md); locale ownership follows the [locale-owned copy decision](..\u002F..\u002Fnotes\u002Fimplemented\u002Farchitecture\u002F2026-08-23-locale-owned-client-ui-copy.md); styling ownership and token rules live in [docs\u002Fweb-styling.md](..\u002F..\u002F..\u002Fdocs\u002Fweb-styling.md) and the [ui-primitives component catalog](..\u002F..\u002F..\u002Fpackages\u002Fclient\u002Fui-primitives\u002FREADME.md#component-catalog) — this skill adds judgment on top of those rules, not a second copy of them.\n\n## Visual foundation\n\n- **Use existing tokens for color, radius, and spacing.** Before introducing a literal value, search the target page and its nearest established sibling (the Plugins page is the usual reference for full-page surfaces) for the token or value already in use, and adopt it. The same applies to whole treatments — toasts, menus, in-message artifact previews, sidebar tab layout, colors, clearance rules, page padding: reuse the established component or rule wherever one exists instead of inventing a parallel one.\n- **Verify every color in both light and dark mode.** An ink\u002Fbackground pair must stay readable under both themes before it ships. Dimmed tones are the standing counter-example: they suit decorative surfaces, but on text they routinely fall below readability in one theme — never put a dimmed color on text without checking both.\n- **Font weight tops out at 500 in feature CSS you add or change.** Do not use 600+ for emphasis; differentiate with size or ink instead. The markdown typography tokens owned by ui-theme are the standing exception.\n- **Pick font sizes from the theme typography variables when an existing role matches, otherwise from the page's existing scale.** Parallel content shares one size; never invent a size for a single element, and keep the number of distinct sizes on a page small (13px is the established row\u002Fdetail size). When the page itself has no precedent, borrow the size and spacing ratios of the most similar existing page or element.\n- **Icons, text, and neighbouring elements stay proportionate and aligned.** Every element lines up with its siblings along a deliberate axis (baseline, vertical center, or shared edge), and an icon's size stays in proportion to the text beside it; never ship an element that aligns to nothing or visibly outweighs its neighbours.\n\n## Reuse before adding\n\n- **Extend an existing component, container, or interaction before creating a new one.** A new capability that fits an existing surface (an extra menu item, a new prop on an existing primitive) beats a parallel element stacked beside it.\n- **Icons come from the existing icon library.** Pick the semantically closest existing icon; a new glyph requires designer approval before it lands — when reviewing a PR that adds one, suggest requesting a designer review.\n- **Right-sidebar content registers a slot in the existing sidebar**, never a separate sidebar. Every sidebar tab declares a tab icon matching its meaning.\n- **Icon-only actions whose meaning is not obvious get a Tooltip.** Informational content the pointer must rest on or select uses HoverCard instead. Prefer these shared primitives over ad-hoc title attributes.\n\n## Feedback surfaces\n\nChoose the surface by the lifetime of the message relative to the surface that produced it:\n\n- **Transient operation outcomes use the app-wide Toast primitive**, not in-place notices, and the toast's state and rendering live in a host that outlives the reporting surface (a `shell.overlay` entry, as RowActionToast does) — a toast rendered by the panel itself unmounts with that panel. A deletion can close the panel or tab that requested it; only a toast held outside that surface survives the close. Report success and failure; do not report still-pending states.\n- **A failed operation keeps the data visible.** A failed deletion keeps its row; the toast announces the failure. Never blank content to show an error for a transient operation.\n- **In-place notices are for states tied to the surface itself**: a query failure with its Retry action, field validation on the form that owns the field. A populated panel keeps a compact notice beside its retained content; only an empty panel centers a full error state.\n- **Error copy is plain language, and short.** No internal jargon or technical nouns unless an error code must be exposed for debugging. Prefer one clear sentence; anything explainable in two sentences must not grow into paragraphs. A Chinese notice of at most two sentences omits the trailing 句号（。）. The notice must not break the existing layout — reserve its space or overlay it; never shift neighbouring elements.\n\n## Loading states\n\n- Lists use their skeleton; every other page-level load centers a bare spinner. Never place a spinner in a corner of the page.\n- One loading treatment per page\u002Fcomponent — concurrent regions must not each flash their own style.\n- No loading text unless the context needs it (narrow sidebars almost never do).\n\n## Overlays and menus\n\nEvery menu, popover, and tooltip must be verified for all three before merge:\n\n- **Dismissable**: outside click (and Escape where focusable) closes it.\n- **Viewport-fitting**: it slides or flips to stay inside the window with an edge margin, and flips only into a side that actually fits (no oscillation when neither side fits).\n- **Unclipped**: it escapes `overflow` ancestors and containing blocks (portal to body where needed) and is never covered by neighbouring elements.\n\nScrollbars stay inside their container: use the shared scrollbar styles rather than component-specific selectors, and verify the bar neither overflows the container nor gets clipped by its rounded corners or edges — keep a small inset instead of letting it sit flush against the container edge.\n\n## Platform window adaptation\n\n- Any new header element or full page must account for macOS and Windows window chrome. On macOS the titlebar clearance is `--dsh-frame-top-clearance`, consumed by Menu, Modal, and overlay primitives as their top safe margin — **never change the global variable to fix one page**. Add a scoped `[data-platform='darwin']` override on the page's own inset instead, and assert the override in the page's stylesheet spec.\n- State the intended total offset (clearance + page inset) when reviewing, so two pages aligning to \"the same top spacing\" agree on the sum, not just one addend.\n\n## Spacing review\n\n- Review every changed region for gaps: nothing sits flush against its neighbour without an intentional gap, and adjacent icons and elements keep the region's established spacing.\n- Prefer symmetry for parallel elements; an unexplained one-off gap or offset usually signals a missed shared value.\n\n## Design review escalation\n\n- A PR with extensive UI changes, or any clearly user-perceivable change to UI or interaction, must get a designer or product review. When no approver holds that role, suggest requesting one from the design\u002Fproduct reviewers (roster as of 2026-09: yx zhang, yifffan, zhangziya, gaokaige; update this list here when membership changes).\n",{"name":5,"description":7},"main","da5a0c7ce142dc4c02297a9c40f7f9483d70c0cd",".agents\u002Fskills\u002Fdsh-client-ui-ux",1,"https:\u002F\u002Fgithub.com\u002FOJamals\u002Ffi","https:\u002F\u002Fgithub.com\u002FOJamals","https:\u002F\u002Faljamal.work","Internist & hospitalist. Clinical AI that has to earn its answers: evaluation, safety and clinical NLP.","2026-11-15 06:18:36",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add OJamals\u002Ffi --skill dsh-client-ui-ux",{"tool":39,"command":40},"bunx","bunx skills add OJamals\u002Ffi --skill dsh-client-ui-ux",{"tool":42,"command":43},"pnpm","pnpm dlx skills add OJamals\u002Ffi --skill dsh-client-ui-ux","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FOJamals\u002Ffi\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdsh-client-ui-ux\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7F2H65DRC9H6YBX2X9AY3W7","user-only-skill","Prove model-disabled skills stay outside the model catalog.","https:\u002F\u002Fgithub.com\u002FOJamals\u002Ffi\u002Fblob\u002Fmain\u002Fsnapshots\u002Fsession\u002Fskill-load\u002Fworkspace\u002F.dsh\u002Fskills\u002Fuser-only-skill\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7F2GSX6RCFK12GS7GSY3B6Q","snapshot-skill","Exercise project skill discovery and loading in snapshot tests.","https:\u002F\u002Fgithub.com\u002FOJamals\u002Ffi\u002Fblob\u002Fmain\u002Fsnapshots\u002Fsession\u002Fskill-load\u002Fworkspace\u002F.dsh\u002Fskills\u002Fsnapshot-skill\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7F2G84RNW56KS4VCGPV7NGX","model-only-skill","Prove user-disabled skills remain available to the model.","https:\u002F\u002Fgithub.com\u002FOJamals\u002Ffi\u002Fblob\u002Fmain\u002Fsnapshots\u002Fsession\u002Fskill-load\u002Fworkspace\u002F.dsh\u002Fskills\u002Fmodel-only-skill\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7F2G3QBJB748G8C6M3BWA1P","office-xlsx","Read, create, and modify Excel workbooks (.xlsx), including data, formulas, formatting, and pandas analysis. Use for Excel inputs or deliverables. Load before running Office commands. Data and formula tasks skip visual inspection; inspect only for formatting or layout needs. Use only bundled LibreOffice unless the user explicitly opts out; without that opt-out, do not search for another LibreOffice executable.","https:\u002F\u002Fgithub.com\u002FOJamals\u002Ffi\u002Fblob\u002Fmain\u002Fpackages\u002Fskill\u002Fskill-office\u002Fassets\u002Foffice-xlsx\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7F2FZTBV428N1FJDJSSEHTA","office-pptx","Create, read, edit, and check PowerPoint presentations (.pptx), including slide text, tables, images, and charts. Use when a PPTX file is an input or requested deliverable. Load this skill before running Office commands. Use only bundled LibreOffice unless the user explicitly opts out; without that opt-out, do not search for another LibreOffice executable.","https:\u002F\u002Fgithub.com\u002FOJamals\u002Ffi\u002Fblob\u002Fmain\u002Fpackages\u002Fskill\u002Fskill-office\u002Fassets\u002Foffice-pptx\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7F2FW8DGQ1RF3QASTXGZSNK","office-docx","Create, read, edit, and check Word documents (.docx), including reports, letters, and formatted tables. Use when a DOCX file is an input or requested deliverable. Load this skill before running Office commands. Use only bundled LibreOffice unless the user explicitly opts out; without that opt-out, do not search for another LibreOffice executable.","https:\u002F\u002Fgithub.com\u002FOJamals\u002Ffi\u002Fblob\u002Fmain\u002Fpackages\u002Fskill\u002Fskill-office\u002Fassets\u002Foffice-docx\u002FSKILL.md",[],[]]