[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72CDQY98HY0QGDX137XZD71":3,"skill-same:01M72CDQY98HY0QGDX137XZD71":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":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M72CDQY98HY0QGDX137XZD71","whats-new-entry",null,"Append a user-facing \"What's New\" entry to the Maude UI feed (apps\u002Fstudio\u002Fwhats-new.json) when closing out a feature. Use during \u002Fflow:done for any user-visible design \u002F dev-server change, or when the user asks to \"add a what's new entry\", \"announce this in the UI\", or \"update the changelog feed\". Writes a pending entry (version null — stamped at release); can attach spotlight tour steps for a new UI affordance.","1aGh\u002Fmaude","1aGh","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F17166964?v=4","01M72CAQDBB0YG724KFT7WEYRF","Michal Dovrtel","01M72CAQDXC32AWQRZYNJXXDC4",3,"MIT","https:\u002F\u002Fgithub.com\u002F1aGh\u002Fmaude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwhats-new-entry\u002FSKILL.md",[],[],"2026-11-10 18:39:20",false,"---\nname: whats-new-entry\ndescription: Append a user-facing \"What's New\" entry to the Maude UI feed (apps\u002Fstudio\u002Fwhats-new.json) when closing out a feature. Use during \u002Fflow:done for any user-visible design \u002F dev-server change, or when the user asks to \"add a what's new entry\", \"announce this in the UI\", or \"update the changelog feed\". Writes a pending entry (version null — stamped at release); can attach spotlight tour steps for a new UI affordance.\n---\n\n# whats-new-entry — append to the Maude UI \"What's New\" feed\n\nRepo-internal skill (Maude-specific; lives in `.claude\u002Fskills\u002F`, not shipped via the marketplace or npm). It owns the authoring + append logic that `\u002Fflow:done` delegates to via `integrations.whatsNew.skill` in `.ai\u002Fworkflows.config.json`. Keeps the **generic** flow plugin free of Maude paths (DDR-D).\n\n## What the feed is\n\n`apps\u002Fstudio\u002Fwhats-new.json` is the single source of truth (DDR-A) for the notices the Maude UI surfaces — the Home \"What's new\" line (`client\u002Fv2\u002Fsignin\u002FWhatsNewLine.jsx`), the first-run toast, Menu › Help › What's new (the project menu's Help row, which carries the unseen count), and the panel it opens (`GET \u002F_api\u002Fwhats-new`). It ships with the dev-server and describes **Maude's own product** updates. Schema: `apps\u002Fstudio\u002Fwhats-new.schema.json`. Background: `.ai\u002Fplans\u002Ffeature-in-app-whats-new-tour.md`.\n\n## When to run\n\nInvoked during `\u002Fflow:done` (step 4d) for a **user-visible** change to the design plugin \u002F dev-server \u002F Maude UI. Skip for internal refactors, infra, docs-only, or flow-plugin-only work — same judgment call as the changelog reminder. Also usable ad-hoc: \"announce X in the UI\".\n\n## How to author an entry\n\n1. **Decide if it's user-visible.** If not → tell the user, do nothing.\n\n2. **Draft the entry** from the plan + commit. Shape (validate against the schema):\n   - `id` — kebab slug, usually derived from the plan slug (e.g. `phase-23-canvas-images` → `canvas-images-link-unfurl`). Must be unique in the feed.\n   - `version` — **`null`** (pending). The release flow (`scripts\u002Fbump-version.sh` → `scripts\u002Fstamp-whats-new.mjs`) stamps it with the shipped version + date. Do NOT guess a version.\n   - `date` — `null` (stamped at release).\n   - `kind` — `feature` | `improvement` | `usage` | `fix`.\n   - `title` — short, benefit-first (≤ ~48 chars). No version numbers in the title.\n   - `summary` — 1–2 sentences, plain language, what the user can now do. No internal jargon (DDR refs, file paths, task numbers).\n   - `learnMore` — optional docs URL (omit if none).\n   - `surface` — `design-ui` for canvas-browser features.\n   - `tour` — **optional** spotlight steps, only if the feature added a visible UI affordance. Each: `{ target, title, body, placement?, optional? }`. The target is a `[data-testid=\"…\"]` or `[data-tour=\"…\"]` hook that exists in `client\u002Ftestids.json` (never a styling class; the toolbars are inside the canvas frame and cannot be spotlit); `optional: true` skips the step when the element is absent for a role or shell. `test\u002Ftour-targets.test.ts` pins every replayable target to a current hook, so add the hook to `testids.json` \u002F `TESTIDS.md` first. When a later redesign removes the chrome a tour points at, set the entry's `replayable: false` (the panel then offers no \"Take tour\"); never leave a dead target on a replayable entry.\n\n3. **Idempotency.** If an entry with the same `id` already exists, update it in place instead of appending a duplicate.\n\n4. **Append** to the top of `entries` (newest first) and write the file back with 2-space indent + trailing newline.\n\n5. **Validate.** `cd apps\u002Fstudio && bun test test\u002Fwhats-new.test.ts` (the loader + shape tests run against the committed feed) — must stay green. The feed must also satisfy `whats-new.schema.json`.\n\n6. **Mirror to the site** (only once Phase 2 of the plan has landed `gen:whatsnew`): `pnpm --filter @maude\u002Fsite gen:whatsnew` and stage the resulting `site\u002Flib\u002Fwhats-new.json`. If the script doesn't exist yet, skip silently.\n\n7. **Stage** `apps\u002Fstudio\u002Fwhats-new.json` (and the site feed if regenerated) so it rides in the feature commit.\n\n## Notes\n\n- No client rebuild is needed for a feed-only change — the client fetches the JSON at runtime. (A rebuild is only needed when you touch `client\u002Fwhats-new*.{jsx,js}` \u002F `app.jsx` \u002F CSS — and then rebuild **release**: `MAUDE_SKIP_RUNTIME_BUILD=1 bun run build.ts --release`, never a bare source boot, which self-heals to unminified dev bundles.)\n- Keep entries honest and curated — this is the user's first impression of a release. One entry per shipped feature, not per commit.\n","# whats-new-entry — append to the Maude UI \"What's New\" feed\n\nRepo-internal skill (Maude-specific; lives in `.claude\u002Fskills\u002F`, not shipped via the marketplace or npm). It owns the authoring + append logic that `\u002Fflow:done` delegates to via `integrations.whatsNew.skill` in `.ai\u002Fworkflows.config.json`. Keeps the **generic** flow plugin free of Maude paths (DDR-D).\n\n## What the feed is\n\n`apps\u002Fstudio\u002Fwhats-new.json` is the single source of truth (DDR-A) for the notices the Maude UI surfaces — the Home \"What's new\" line (`client\u002Fv2\u002Fsignin\u002FWhatsNewLine.jsx`), the first-run toast, Menu › Help › What's new (the project menu's Help row, which carries the unseen count), and the panel it opens (`GET \u002F_api\u002Fwhats-new`). It ships with the dev-server and describes **Maude's own product** updates. Schema: `apps\u002Fstudio\u002Fwhats-new.schema.json`. Background: `.ai\u002Fplans\u002Ffeature-in-app-whats-new-tour.md`.\n\n## When to run\n\nInvoked during `\u002Fflow:done` (step 4d) for a **user-visible** change to the design plugin \u002F dev-server \u002F Maude UI. Skip for internal refactors, infra, docs-only, or flow-plugin-only work — same judgment call as the changelog reminder. Also usable ad-hoc: \"announce X in the UI\".\n\n## How to author an entry\n\n1. **Decide if it's user-visible.** If not → tell the user, do nothing.\n\n2. **Draft the entry** from the plan + commit. Shape (validate against the schema):\n   - `id` — kebab slug, usually derived from the plan slug (e.g. `phase-23-canvas-images` → `canvas-images-link-unfurl`). Must be unique in the feed.\n   - `version` — **`null`** (pending). The release flow (`scripts\u002Fbump-version.sh` → `scripts\u002Fstamp-whats-new.mjs`) stamps it with the shipped version + date. Do NOT guess a version.\n   - `date` — `null` (stamped at release).\n   - `kind` — `feature` | `improvement` | `usage` | `fix`.\n   - `title` — short, benefit-first (≤ ~48 chars). No version numbers in the title.\n   - `summary` — 1–2 sentences, plain language, what the user can now do. No internal jargon (DDR refs, file paths, task numbers).\n   - `learnMore` — optional docs URL (omit if none).\n   - `surface` — `design-ui` for canvas-browser features.\n   - `tour` — **optional** spotlight steps, only if the feature added a visible UI affordance. Each: `{ target, title, body, placement?, optional? }`. The target is a `[data-testid=\"…\"]` or `[data-tour=\"…\"]` hook that exists in `client\u002Ftestids.json` (never a styling class; the toolbars are inside the canvas frame and cannot be spotlit); `optional: true` skips the step when the element is absent for a role or shell. `test\u002Ftour-targets.test.ts` pins every replayable target to a current hook, so add the hook to `testids.json` \u002F `TESTIDS.md` first. When a later redesign removes the chrome a tour points at, set the entry's `replayable: false` (the panel then offers no \"Take tour\"); never leave a dead target on a replayable entry.\n\n3. **Idempotency.** If an entry with the same `id` already exists, update it in place instead of appending a duplicate.\n\n4. **Append** to the top of `entries` (newest first) and write the file back with 2-space indent + trailing newline.\n\n5. **Validate.** `cd apps\u002Fstudio && bun test test\u002Fwhats-new.test.ts` (the loader + shape tests run against the committed feed) — must stay green. The feed must also satisfy `whats-new.schema.json`.\n\n6. **Mirror to the site** (only once Phase 2 of the plan has landed `gen:whatsnew`): `pnpm --filter @maude\u002Fsite gen:whatsnew` and stage the resulting `site\u002Flib\u002Fwhats-new.json`. If the script doesn't exist yet, skip silently.\n\n7. **Stage** `apps\u002Fstudio\u002Fwhats-new.json` (and the site feed if regenerated) so it rides in the feature commit.\n\n## Notes\n\n- No client rebuild is needed for a feed-only change — the client fetches the JSON at runtime. (A rebuild is only needed when you touch `client\u002Fwhats-new*.{jsx,js}` \u002F `app.jsx` \u002F CSS — and then rebuild **release**: `MAUDE_SKIP_RUNTIME_BUILD=1 bun run build.ts --release`, never a bare source boot, which self-heals to unminified dev bundles.)\n- Keep entries honest and curated — this is the user's first impression of a release. One entry per shipped feature, not per commit.\n",{"name":5,"description":7},"main","cfde9d2b169e4b418a5c5efb35297cc575dc764c",".claude\u002Fskills\u002Fwhats-new-entry",0,"https:\u002F\u002Fgithub.com\u002F1aGh\u002Fmaude","https:\u002F\u002Fmaude.sh","https:\u002F\u002Fgithub.com\u002F1aGh","www.iagh.cz","2026-11-13 20:38:15",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add 1aGh\u002Fmaude --skill whats-new-entry",{"tool":39,"command":40},"bunx","bunx skills add 1aGh\u002Fmaude --skill whats-new-entry",{"tool":42,"command":43},"pnpm","pnpm dlx skills add 1aGh\u002Fmaude --skill whats-new-entry","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F1aGh\u002Fmaude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwhats-new-entry\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},"01M72CJCVNC5JB3M36ES649CTY","workflow-state","Read and update workflow state when planning, executing, completing, pausing or resuming project work.","https:\u002F\u002Fgithub.com\u002F1aGh\u002Fmaude\u002Fblob\u002Fmain\u002Fplugins\u002Fflow\u002Fskills\u002Fworkflow-state\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},"01M72CJAJBZT2RHE97ND8EFTA3","ui-rules","UI hard-stop rules and audit method: WCAG 2.1 AA accessibility, responsive layout and motion.","https:\u002F\u002Fgithub.com\u002F1aGh\u002Fmaude\u002Fblob\u002Fmain\u002Fplugins\u002Fflow\u002Fskills\u002Fui-rules\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},"01M72CJ857314HCC8A99T4K0D2","testing-rules","Apply test quality rules during implementation and review: meaningful assertions, isolation and coverage.","https:\u002F\u002Fgithub.com\u002F1aGh\u002Fmaude\u002Fblob\u002Fmain\u002Fplugins\u002Fflow\u002Fskills\u002Ftesting-rules\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},"01M72CJ6N80HW2WRS8BV4QSS4V","security-rules","Apply application and AI security checks to code reviews, implementation and threat-driven validation.","https:\u002F\u002Fgithub.com\u002F1aGh\u002Fmaude\u002Fblob\u002Fmain\u002Fplugins\u002Fflow\u002Fskills\u002Fsecurity-rules\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},"01M72CJ4C41Q4E1WDTFMKYFX3Q","scenario","Author or run cross-platform UI scenarios with selectors, screenshots, platform coverage and result reports.","https:\u002F\u002Fgithub.com\u002F1aGh\u002Fmaude\u002Fblob\u002Fmain\u002Fplugins\u002Fflow\u002Fskills\u002Fscenario\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},"01M72CJ1QYX752BM7G12250YJR","question-protocol","Batch necessary questions from workflow participants, collect user answers and route them to the requester.","https:\u002F\u002Fgithub.com\u002F1aGh\u002Fmaude\u002Fblob\u002Fmain\u002Fplugins\u002Fflow\u002Fskills\u002Fquestion-protocol\u002FSKILL.md",[],[]]