[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77KWRVEZ5F1V0PMTST8YCSD":3,"skill-same:01M77KWRVEZ5F1V0PMTST8YCSD":45},{"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":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M77KWRVEZ5F1V0PMTST8YCSD","ui-ux",null,"Desktop UI\u002FUX guidance for Watchdown's editor surface (Electron + CodeMirror): accessibility and keyboard support, contrast and dark mode, editor typography, animation and reduced-motion, color semantics for diff\u002Fauthorship\u002Fconflict, and status\u002Ffeedback. Plus project-specific guidance for the live presence and diff-attribution UI. Use when designing, building, or reviewing any editor UI — gutters, markers, author glyphs, highlights, the status bar, or conflict rendering.","mfozmen\u002Fwatchdown","mfozmen","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F39158545?v=4","01M77KW7QEKWC5G7RKQHX8QJ88","Mehmet Fahri Özmen","01M77KW7R61H9AP16VC3X67S4Y",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmfozmen\u002Fwatchdown\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fui-ux\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ui-ux\ndescription: >\n  Desktop UI\u002FUX guidance for Watchdown's editor surface (Electron + CodeMirror):\n  accessibility and keyboard support, contrast and dark mode, editor typography,\n  animation and reduced-motion, color semantics for diff\u002Fauthorship\u002Fconflict, and\n  status\u002Ffeedback. Plus project-specific guidance for the live presence and\n  diff-attribution UI. Use when designing, building, or reviewing any editor UI —\n  gutters, markers, author glyphs, highlights, the status bar, or conflict rendering.\n---\n\n# UI\u002FUX — Watchdown editor\n\nCurated, desktop-focused UX reference for the Watchdown markdown editor. Distilled\nfor an **Electron + CodeMirror desktop app** — not mobile. The defining UI is the\n**editor surface plus the live presence \u002F diff-attribution layer** (gutter markers,\nauthor icons, change highlights, status bar, inline conflict rendering).\n\n## When to use\n\n- Designing or building the editor UI, gutter, status bar, or any control.\n- Implementing the presence \u002F diff-attribution layer (changed-line markers, author\n  glyphs, highlight-on-external-change, \"Claude is editing…\" status).\n- Rendering the conflict state (inline markers, accept\u002Fkeep affordances).\n- Reviewing UI for accessibility, contrast, keyboard support, or visual consistency.\n\n## Skip\n\n- Pure core \u002F sync-engine logic (it has no UI — keep it that way).\n- Backend, filesystem, or build\u002FCI work.\n\nThis is desktop. Ignore mobile-only concerns (touch-target sizes, safe areas\u002Fnotch,\nhaptics, bottom nav, swipe gestures) unless a real touch surface is added later.\n\n## 1. Accessibility & keyboard (CRITICAL)\n\n- Keyboard-first: every action reachable without a mouse; Tab order matches visual order.\n- Preserve visible focus rings (2–4px) on all interactive controls — never remove them.\n- Respect editor\u002FOS keyboard shortcuts; don't shadow standard ones.\n- `aria-label` (or equivalent) on icon-only controls, including the author\u002Fpresence glyph.\n- Don't convey meaning by color alone — pair diff\u002Fauthorship\u002Fconflict color with an\n  icon, marker, or text so it survives color-blindness and high-contrast modes.\n- Provide a text\u002Ftooltip equivalent for every gutter marker and author icon\n  (e.g. \"Changed by Claude · 2s ago\").\n- Announce live changes politely (`aria-live=\"polite\"`) so external edits and status\n  changes reach screen readers without stealing focus.\n\n## 2. Contrast & dark mode (CRITICAL)\n\n- Body\u002Feditor text ≥ 4.5:1; secondary text ≥ 3:1. Diff and marker colors ≥ 3:1 vs background.\n- Design light and dark together; dark mode uses desaturated tonal variants, not\n  inverted colors. Verify contrast per theme — don't assume light values carry over.\n- Keep dividers, gutter markers, and interaction states visible in **both** themes.\n- Drive all colors from semantic tokens (e.g. `--diff-added`, `--author-external`,\n  `--conflict`), never raw hex in components.\n\n## 3. Editor typography\n\n- Monospace for the editor buffer; consistent line-height (~1.5) for readability.\n- Use `font-display: swap\u002Foptional` and reserve space to avoid layout shift on load.\n- Tabular figures for any aligned numeric UI (line numbers, timers).\n- Don't truncate where wrapping is possible; if truncating, offer the full text on hover.\n\n## 4. Animation & reduced-motion (MEDIUM)\n\n- Micro-interactions 150–300ms; the brief highlight on an externally-changed region\n  lands in this range — long enough to notice, short enough not to nag.\n- Animate `transform`\u002F`opacity` only; never `width`\u002F`height`\u002F`top`\u002F`left` (causes reflow\u002FCLS).\n- Honor `prefers-reduced-motion`: replace highlight fades\u002Fpulses with an instant,\n  static marker. Motion must be optional, never required to perceive a change.\n- Animation should express cause→effect (a change appeared here), not decorate.\n- Keep input\u002Ftyping latency under ~100ms; never block typing during an animation.\n\n## 5. Color semantics for diff \u002F authorship \u002F conflict\n\n- Distinct, tokenized, accessible roles: added vs removed vs externally-changed vs\n  conflicting. Each role = color **and** a non-color cue (gutter glyph, underline, icon).\n- Author attribution needs a stable per-author color + a labeled icon; the external\n  (e.g. Claude) author glyph is an SVG icon, **not an emoji** (emoji render\n  inconsistently and can't be themed via tokens).\n- Conflict regions must be unmistakable and legible in both themes; pair the color\n  with clear inline structure, not just a background tint.\n\n## 6. Feedback & status\n\n- The status bar is the primary feedback channel: reflect clean \u002F dirty \u002F conflict and\n  presence (\"Claude is editing…\" vs \"Claude idle\") promptly and unambiguously.\n- Show progress for anything over ~300ms; prefer a calm indicator over a blocking spinner.\n- Destructive or lossy actions (discarding unsaved edits, overwriting on conflict)\n  require confirmation and, where possible, undo.\n- Empty\u002Fidle states should explain, not show a blank surface.\n\n## 7. Layout & polish\n\n- One consistent icon set (stroke width, corner radius); SVG\u002Fvector only — no raster, no emoji.\n- Consistent spacing rhythm (4\u002F8px scale) and a defined z-index scale\n  (editor \u003C gutter overlays \u003C tooltips \u003C modals).\n- Press\u002Fhover\u002Factive\u002Fdisabled states visually distinct without shifting layout bounds.\n- One primary action per surface; secondary actions visually subordinate.\n\n## Pre-delivery checklist (desktop)\n\n- [ ] Fully keyboard operable; focus order logical; focus rings visible.\n- [ ] Text ≥ 4.5:1, markers\u002Fdiff ≥ 3:1 — verified in light **and** dark.\n- [ ] No color-only meaning — every diff\u002Fauthor\u002Fconflict cue has a non-color signal.\n- [ ] `prefers-reduced-motion` respected (highlights degrade to static markers).\n- [ ] Author\u002Fpresence glyphs are SVG icons with accessible labels and tooltips.\n- [ ] Status bar correctly reflects clean \u002F dirty \u002F conflict and presence.\n- [ ] No layout shift from change highlights or state transitions (transform\u002Fopacity only).\n- [ ] Colors come from semantic tokens, not inline hex.\n\n---\n\nAdapted (desktop-only subset) from\n[ui-ux-pro-max](https:\u002F\u002Fgithub.com\u002Fnextlevelbuilder\u002Fui-ux-pro-max-skill) by\nNext Level Builder, MIT License. The original is a mobile\u002FReact-Native design-system\ntool with a Python search CLI and a large data corpus; this is a trimmed, static,\ndesktop-editor-focused reference with no scripts or bundled data.\n","# UI\u002FUX — Watchdown editor\n\nCurated, desktop-focused UX reference for the Watchdown markdown editor. Distilled\nfor an **Electron + CodeMirror desktop app** — not mobile. The defining UI is the\n**editor surface plus the live presence \u002F diff-attribution layer** (gutter markers,\nauthor icons, change highlights, status bar, inline conflict rendering).\n\n## When to use\n\n- Designing or building the editor UI, gutter, status bar, or any control.\n- Implementing the presence \u002F diff-attribution layer (changed-line markers, author\n  glyphs, highlight-on-external-change, \"Claude is editing…\" status).\n- Rendering the conflict state (inline markers, accept\u002Fkeep affordances).\n- Reviewing UI for accessibility, contrast, keyboard support, or visual consistency.\n\n## Skip\n\n- Pure core \u002F sync-engine logic (it has no UI — keep it that way).\n- Backend, filesystem, or build\u002FCI work.\n\nThis is desktop. Ignore mobile-only concerns (touch-target sizes, safe areas\u002Fnotch,\nhaptics, bottom nav, swipe gestures) unless a real touch surface is added later.\n\n## 1. Accessibility & keyboard (CRITICAL)\n\n- Keyboard-first: every action reachable without a mouse; Tab order matches visual order.\n- Preserve visible focus rings (2–4px) on all interactive controls — never remove them.\n- Respect editor\u002FOS keyboard shortcuts; don't shadow standard ones.\n- `aria-label` (or equivalent) on icon-only controls, including the author\u002Fpresence glyph.\n- Don't convey meaning by color alone — pair diff\u002Fauthorship\u002Fconflict color with an\n  icon, marker, or text so it survives color-blindness and high-contrast modes.\n- Provide a text\u002Ftooltip equivalent for every gutter marker and author icon\n  (e.g. \"Changed by Claude · 2s ago\").\n- Announce live changes politely (`aria-live=\"polite\"`) so external edits and status\n  changes reach screen readers without stealing focus.\n\n## 2. Contrast & dark mode (CRITICAL)\n\n- Body\u002Feditor text ≥ 4.5:1; secondary text ≥ 3:1. Diff and marker colors ≥ 3:1 vs background.\n- Design light and dark together; dark mode uses desaturated tonal variants, not\n  inverted colors. Verify contrast per theme — don't assume light values carry over.\n- Keep dividers, gutter markers, and interaction states visible in **both** themes.\n- Drive all colors from semantic tokens (e.g. `--diff-added`, `--author-external`,\n  `--conflict`), never raw hex in components.\n\n## 3. Editor typography\n\n- Monospace for the editor buffer; consistent line-height (~1.5) for readability.\n- Use `font-display: swap\u002Foptional` and reserve space to avoid layout shift on load.\n- Tabular figures for any aligned numeric UI (line numbers, timers).\n- Don't truncate where wrapping is possible; if truncating, offer the full text on hover.\n\n## 4. Animation & reduced-motion (MEDIUM)\n\n- Micro-interactions 150–300ms; the brief highlight on an externally-changed region\n  lands in this range — long enough to notice, short enough not to nag.\n- Animate `transform`\u002F`opacity` only; never `width`\u002F`height`\u002F`top`\u002F`left` (causes reflow\u002FCLS).\n- Honor `prefers-reduced-motion`: replace highlight fades\u002Fpulses with an instant,\n  static marker. Motion must be optional, never required to perceive a change.\n- Animation should express cause→effect (a change appeared here), not decorate.\n- Keep input\u002Ftyping latency under ~100ms; never block typing during an animation.\n\n## 5. Color semantics for diff \u002F authorship \u002F conflict\n\n- Distinct, tokenized, accessible roles: added vs removed vs externally-changed vs\n  conflicting. Each role = color **and** a non-color cue (gutter glyph, underline, icon).\n- Author attribution needs a stable per-author color + a labeled icon; the external\n  (e.g. Claude) author glyph is an SVG icon, **not an emoji** (emoji render\n  inconsistently and can't be themed via tokens).\n- Conflict regions must be unmistakable and legible in both themes; pair the color\n  with clear inline structure, not just a background tint.\n\n## 6. Feedback & status\n\n- The status bar is the primary feedback channel: reflect clean \u002F dirty \u002F conflict and\n  presence (\"Claude is editing…\" vs \"Claude idle\") promptly and unambiguously.\n- Show progress for anything over ~300ms; prefer a calm indicator over a blocking spinner.\n- Destructive or lossy actions (discarding unsaved edits, overwriting on conflict)\n  require confirmation and, where possible, undo.\n- Empty\u002Fidle states should explain, not show a blank surface.\n\n## 7. Layout & polish\n\n- One consistent icon set (stroke width, corner radius); SVG\u002Fvector only — no raster, no emoji.\n- Consistent spacing rhythm (4\u002F8px scale) and a defined z-index scale\n  (editor \u003C gutter overlays \u003C tooltips \u003C modals).\n- Press\u002Fhover\u002Factive\u002Fdisabled states visually distinct without shifting layout bounds.\n- One primary action per surface; secondary actions visually subordinate.\n\n## Pre-delivery checklist (desktop)\n\n- [ ] Fully keyboard operable; focus order logical; focus rings visible.\n- [ ] Text ≥ 4.5:1, markers\u002Fdiff ≥ 3:1 — verified in light **and** dark.\n- [ ] No color-only meaning — every diff\u002Fauthor\u002Fconflict cue has a non-color signal.\n- [ ] `prefers-reduced-motion` respected (highlights degrade to static markers).\n- [ ] Author\u002Fpresence glyphs are SVG icons with accessible labels and tooltips.\n- [ ] Status bar correctly reflects clean \u002F dirty \u002F conflict and presence.\n- [ ] No layout shift from change highlights or state transitions (transform\u002Fopacity only).\n- [ ] Colors come from semantic tokens, not inline hex.\n\n---\n\nAdapted (desktop-only subset) from\n[ui-ux-pro-max](https:\u002F\u002Fgithub.com\u002Fnextlevelbuilder\u002Fui-ux-pro-max-skill) by\nNext Level Builder, MIT License. The original is a mobile\u002FReact-Native design-system\ntool with a Python search CLI and a large data corpus; this is a trimmed, static,\ndesktop-editor-focused reference with no scripts or bundled data.\n",{"name":5,"description":7},"main","babb6a5a383e6263c21aa7cb32be87a4cce61f66",".claude\u002Fskills\u002Fui-ux","https:\u002F\u002Fgithub.com\u002Fmfozmen\u002Fwatchdown","https:\u002F\u002Fgithub.com\u002Fmfozmen","https:\u002F\u002Fmehmetfahriozmen.dev\u002F","2026-11-12 20:07:19",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add mfozmen\u002Fwatchdown --skill ui-ux",{"tool":37,"command":38},"bunx","bunx skills add mfozmen\u002Fwatchdown --skill ui-ux",{"tool":40,"command":41},"pnpm","pnpm dlx skills add mfozmen\u002Fwatchdown --skill ui-ux","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmfozmen\u002Fwatchdown\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fui-ux\u002FSKILL.md",true,[],[46,53,60,66,72],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M77KWP7XNTE3SBNP8FZNJ5XJ","release-process","How Watchdown versions and ships releases via release-please — squash-merge rules, the release PR gate, tag\u002Finstaller build, and the RELEASE_PLEASE_PAT caveat. Use when merging PRs, cutting a release, or touching versioning.","https:\u002F\u002Fgithub.com\u002Fmfozmen\u002Fwatchdown\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frelease-process\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M77KWFN4YPSXC37FZBV0JJPM","demo-capture","How to capture the real running Watchdown window on Windows for screenshots and demo GIFs (README hero, release assets), and how to script a live-external-edit-sync GIF. Covers the capture method that actually works (PrintWindow + PW_RENDERFULLCONTENT + SetProcessDPIAware), why capturePage and plain screen-grabs fail, and the ImageMagick assembly recipe. Use whenever producing a screenshot\u002FGIF of the app, or when a capture comes out blank, half-cropped, frameless, or from the wrong desktop.","https:\u002F\u002Fgithub.com\u002Fmfozmen\u002Fwatchdown\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdemo-capture\u002FSKILL.md",[],[],{"skillNo":61,"name":5,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M77KWDZKS1ZPRMNXTDBZJFT4","Use when designing, building, or reviewing Watchdown's editor UI, including presence, attribution, status, and conflicts.","https:\u002F\u002Fgithub.com\u002Fmfozmen\u002Fwatchdown\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fui-ux\u002FSKILL.md",[],[],{"skillNo":67,"name":48,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M77KWBPRE0Y8KJ0H05N1FDD4","Use when merging Watchdown PRs, cutting a release, or changing versioning.","https:\u002F\u002Fgithub.com\u002Fmfozmen\u002Fwatchdown\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frelease-process\u002FSKILL.md",[],[],{"skillNo":73,"name":55,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M77KW9TN6N42Z46GFNB3PHXF","Use when capturing a screenshot or demo GIF of Watchdown on Windows, or troubleshooting a failed capture.","https:\u002F\u002Fgithub.com\u002Fmfozmen\u002Fwatchdown\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdemo-capture\u002FSKILL.md",[],[]]