[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75D2XE2EN74ZQMMRQCV1TEZ":3,"skill-same:01M75D2XE2EN74ZQMMRQCV1TEZ":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M75D2XE2EN74ZQMMRQCV1TEZ","design",null,"Canonical repo-local DESIGN.md workflow for product, UI\u002FUX, and frontend decision source of truth","agisota\u002Fold-one","agisota","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F121413592?v=4","01M75B4BRNT67EC1NDRT8QZEP2","01M75B4BS7QR9VP580MSCPTS3X",3,"MIT","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fdesign\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: design\ndescription: Canonical repo-local DESIGN.md workflow for product, UI\u002FUX, and frontend decision source of truth\n---\n\n# Design Skill\n\nUse `$design` when product, UI\u002FUX, frontend, or design-system decisions need a durable source of truth in the repository. This skill discovers existing design context, interviews for missing product\u002Fdesign information, and creates or refreshes repo-local `DESIGN.md` so future UI\u002FUX\u002Ffrontend work is grounded instead of improvised.\n\n## Purpose\n\nMake repo-local `DESIGN.md` source of truth and canonical design contract for the current repository:\n\n`existing repo evidence -> missing-context interview -> create\u002Frefresh DESIGN.md -> use DESIGN.md for UI\u002FUX\u002Ffrontend decisions`.\n\nThe output is not a pixel-matching loop and not a one-off visual critique. It is the maintained design brief\u002Fchecklist that implementation, review, and future visual work should cite.\n\n## Use when\n\n- The user asks for design direction, UX guidance, frontend planning, or design-system alignment.\n- A repo needs a design brief before UI\u002Ffrontend implementation begins.\n- Existing UI\u002Fcomponents\u002Fassets\u002Fscreenshots need to be summarized into a reusable design source of truth.\n- UI\u002FUX\u002Ffrontend decisions are ambiguous and should be resolved through product context, constraints, and documented principles.\n- A feature needs `DESIGN.md` created or refreshed before `$ralph`, a designer lane, or implementation work proceeds.\n\n## Do not use when\n\n- The user provides or requests a visual reference\u002Fimage\u002Flive URL and wants measured implementation until screenshots match. Use `$visual-ralph` for that visual-reference implementation loop.\n- The task is pure backend\u002FAPI\u002Finfrastructure work with no user-facing design consequence.\n- The user only asks to compare screenshots or score visual fidelity. Use `$visual-ralph` and its built-in visual verdict flow.\n\n## Relationship to `$visual-ralph`\n\n`$design` owns the durable repo design source of truth: product goals, users, IA, visual language, components, accessibility, constraints, and open questions in `DESIGN.md`.\n\n`$visual-ralph` owns implementation against an approved generated\u002Fstatic\u002Flive-URL visual reference, with screenshot capture, Visual Ralph verdict scoring, and pixel-diff evidence. `$visual-ralph` may read `DESIGN.md`, and it may leave design-system artifacts behind, but it does not replace the `DESIGN.md` discovery\u002Finterview\u002Frefresh workflow.\n\nIf both are needed, run `$design` first to establish the design contract, then run `$visual-ralph` only after the visual reference\u002Fbaseline is approved.\n\n## Workflow\n\n### 1. Discover local design evidence\n\nInspect the repository before writing guidance. Look for:\n\n- `DESIGN.md`, `docs\u002Fdesign*`, `docs\u002Fux*`, `docs\u002Ffrontend*`, `README.md`, product specs, PRDs, and issue notes.\n- Existing UI source: routes, pages, layouts, components, stories, examples, demos, theme files, CSS variables, Tailwind\u002Ftheme config, tokens, icons, and assets.\n- Screenshots, mockups, brand files, logos, Figma\u002Fexport notes, Storybook snapshots, Playwright screenshots, visual-regression baselines, or `.omx\u002Fartifacts\u002Fvisual-ralph\u002F*` references.\n- Accessibility, responsive, i18n, content, and platform constraints already encoded in code or docs.\n\nRecord evidence with file paths. Distinguish observed facts from design inferences.\n\n### 2. Interview only for missing context\n\nAsk concise questions only when repo evidence cannot answer design-critical context. Prefer one focused round that closes the biggest gaps, such as:\n\n- target users\u002Fpersonas and jobs to be done,\n- product\u002Fbusiness goals and non-goals,\n- brand personality or forbidden aesthetics,\n- primary flows and information architecture,\n- accessibility level, device\u002Fbrowser support, and implementation constraints,\n- existing design assets or references the repo does not contain.\n\nIf the user wants autonomous progress or cannot answer, create `DESIGN.md` with explicit assumptions and open questions instead of blocking.\n\n### 3. Create or refresh `DESIGN.md`\n\nUse the structure below. Preserve useful existing content, remove contradictions, and mark unknowns as open questions. Keep it actionable for implementers and reviewers.\n\n#### Required `DESIGN.md` structure\u002Fchecklist\n\n```markdown\n# Design\n\n## Source of truth\n- Status: Draft | Active | Needs refresh\n- Last refreshed: YYYY-MM-DD\n- Primary product surfaces:\n- Evidence reviewed:\n\n## Brand\n- Personality:\n- Trust signals:\n- Avoid:\n\n## Product goals\n- Goals:\n- Non-goals:\n- Success signals:\n\n## Personas and jobs\n- Primary personas:\n- User jobs:\n- Key contexts of use:\n\n## Information architecture\n- Primary navigation:\n- Core routes\u002Fscreens:\n- Content hierarchy:\n\n## Design principles\n- Principle 1:\n- Principle 2:\n- Tradeoffs:\n\n## Visual language\n- Color:\n- Typography:\n- Spacing\u002Flayout rhythm:\n- Shape\u002Fradius\u002Felevation:\n- Motion:\n- Imagery\u002Ficonography:\n\n## Components\n- Existing components to reuse:\n- New\u002Fchanged components:\n- Variants and states:\n- Token\u002Fcomponent ownership:\n\n## Accessibility\n- Target standard:\n- Keyboard\u002Ffocus behavior:\n- Contrast\u002Freadability:\n- Screen-reader semantics:\n- Reduced motion and sensory considerations:\n\n## Responsive behavior\n- Supported breakpoints\u002Fdevices:\n- Layout adaptations:\n- Touch\u002Fhover differences:\n\n## Interaction states\n- Loading:\n- Empty:\n- Error:\n- Success:\n- Disabled:\n- Offline\u002Fslow network, if applicable:\n\n## Content voice\n- Tone:\n- Terminology:\n- Microcopy rules:\n\n## Implementation constraints\n- Framework\u002Fstyling system:\n- Design-token constraints:\n- Performance constraints:\n- Compatibility constraints:\n- Test\u002Fscreenshot expectations:\n\n## Open questions\n- [ ] Question \u002F owner \u002F impact\n```\n\n### 4. Use `DESIGN.md` as the decision contract\n\nFor UI\u002FUX\u002Ffrontend work after the refresh:\n\n- Cite the relevant `DESIGN.md` sections before making design choices.\n- Prefer existing components, tokens, and documented constraints.\n- If implementation reveals a design contradiction, update `DESIGN.md` or add an open question before proceeding.\n- Do not introduce a new design-system layer when existing repo-native patterns can be extended.\n\n### 5. Handoff to implementation or Visual Ralph when appropriate\n\n- For normal frontend implementation, hand off with the relevant `DESIGN.md` sections, repo evidence, and acceptance criteria.\n- For visual-reference\u002Fimage\u002Flive-URL matching, hand off to `$visual-ralph` with the approved reference\u002Fbaseline and note that `DESIGN.md` is supporting context, not the visual verdict target.\n\n## Completion checklist\n\nDo not declare the design workflow complete until:\n\n- Existing design docs\u002Fassets\u002Fcomponents\u002Fscreenshots have been inspected or explicitly noted as absent.\n- Missing product\u002Fdesign context has been answered, assumed, or listed in `DESIGN.md` open questions.\n- `DESIGN.md` exists at the repo root and contains all required checklist sections.\n- UI\u002FUX\u002Ffrontend recommendations cite `DESIGN.md` rather than relying on unstated preferences.\n- Any `$visual-ralph` handoff is clearly separated as visual implementation matching, not DESIGN.md governance.\n\nTask: {{ARGUMENTS}}\n","# Design Skill\n\nUse `$design` when product, UI\u002FUX, frontend, or design-system decisions need a durable source of truth in the repository. This skill discovers existing design context, interviews for missing product\u002Fdesign information, and creates or refreshes repo-local `DESIGN.md` so future UI\u002FUX\u002Ffrontend work is grounded instead of improvised.\n\n## Purpose\n\nMake repo-local `DESIGN.md` source of truth and canonical design contract for the current repository:\n\n`existing repo evidence -> missing-context interview -> create\u002Frefresh DESIGN.md -> use DESIGN.md for UI\u002FUX\u002Ffrontend decisions`.\n\nThe output is not a pixel-matching loop and not a one-off visual critique. It is the maintained design brief\u002Fchecklist that implementation, review, and future visual work should cite.\n\n## Use when\n\n- The user asks for design direction, UX guidance, frontend planning, or design-system alignment.\n- A repo needs a design brief before UI\u002Ffrontend implementation begins.\n- Existing UI\u002Fcomponents\u002Fassets\u002Fscreenshots need to be summarized into a reusable design source of truth.\n- UI\u002FUX\u002Ffrontend decisions are ambiguous and should be resolved through product context, constraints, and documented principles.\n- A feature needs `DESIGN.md` created or refreshed before `$ralph`, a designer lane, or implementation work proceeds.\n\n## Do not use when\n\n- The user provides or requests a visual reference\u002Fimage\u002Flive URL and wants measured implementation until screenshots match. Use `$visual-ralph` for that visual-reference implementation loop.\n- The task is pure backend\u002FAPI\u002Finfrastructure work with no user-facing design consequence.\n- The user only asks to compare screenshots or score visual fidelity. Use `$visual-ralph` and its built-in visual verdict flow.\n\n## Relationship to `$visual-ralph`\n\n`$design` owns the durable repo design source of truth: product goals, users, IA, visual language, components, accessibility, constraints, and open questions in `DESIGN.md`.\n\n`$visual-ralph` owns implementation against an approved generated\u002Fstatic\u002Flive-URL visual reference, with screenshot capture, Visual Ralph verdict scoring, and pixel-diff evidence. `$visual-ralph` may read `DESIGN.md`, and it may leave design-system artifacts behind, but it does not replace the `DESIGN.md` discovery\u002Finterview\u002Frefresh workflow.\n\nIf both are needed, run `$design` first to establish the design contract, then run `$visual-ralph` only after the visual reference\u002Fbaseline is approved.\n\n## Workflow\n\n### 1. Discover local design evidence\n\nInspect the repository before writing guidance. Look for:\n\n- `DESIGN.md`, `docs\u002Fdesign*`, `docs\u002Fux*`, `docs\u002Ffrontend*`, `README.md`, product specs, PRDs, and issue notes.\n- Existing UI source: routes, pages, layouts, components, stories, examples, demos, theme files, CSS variables, Tailwind\u002Ftheme config, tokens, icons, and assets.\n- Screenshots, mockups, brand files, logos, Figma\u002Fexport notes, Storybook snapshots, Playwright screenshots, visual-regression baselines, or `.omx\u002Fartifacts\u002Fvisual-ralph\u002F*` references.\n- Accessibility, responsive, i18n, content, and platform constraints already encoded in code or docs.\n\nRecord evidence with file paths. Distinguish observed facts from design inferences.\n\n### 2. Interview only for missing context\n\nAsk concise questions only when repo evidence cannot answer design-critical context. Prefer one focused round that closes the biggest gaps, such as:\n\n- target users\u002Fpersonas and jobs to be done,\n- product\u002Fbusiness goals and non-goals,\n- brand personality or forbidden aesthetics,\n- primary flows and information architecture,\n- accessibility level, device\u002Fbrowser support, and implementation constraints,\n- existing design assets or references the repo does not contain.\n\nIf the user wants autonomous progress or cannot answer, create `DESIGN.md` with explicit assumptions and open questions instead of blocking.\n\n### 3. Create or refresh `DESIGN.md`\n\nUse the structure below. Preserve useful existing content, remove contradictions, and mark unknowns as open questions. Keep it actionable for implementers and reviewers.\n\n#### Required `DESIGN.md` structure\u002Fchecklist\n\n```markdown\n# Design\n\n## Source of truth\n- Status: Draft | Active | Needs refresh\n- Last refreshed: YYYY-MM-DD\n- Primary product surfaces:\n- Evidence reviewed:\n\n## Brand\n- Personality:\n- Trust signals:\n- Avoid:\n\n## Product goals\n- Goals:\n- Non-goals:\n- Success signals:\n\n## Personas and jobs\n- Primary personas:\n- User jobs:\n- Key contexts of use:\n\n## Information architecture\n- Primary navigation:\n- Core routes\u002Fscreens:\n- Content hierarchy:\n\n## Design principles\n- Principle 1:\n- Principle 2:\n- Tradeoffs:\n\n## Visual language\n- Color:\n- Typography:\n- Spacing\u002Flayout rhythm:\n- Shape\u002Fradius\u002Felevation:\n- Motion:\n- Imagery\u002Ficonography:\n\n## Components\n- Existing components to reuse:\n- New\u002Fchanged components:\n- Variants and states:\n- Token\u002Fcomponent ownership:\n\n## Accessibility\n- Target standard:\n- Keyboard\u002Ffocus behavior:\n- Contrast\u002Freadability:\n- Screen-reader semantics:\n- Reduced motion and sensory considerations:\n\n## Responsive behavior\n- Supported breakpoints\u002Fdevices:\n- Layout adaptations:\n- Touch\u002Fhover differences:\n\n## Interaction states\n- Loading:\n- Empty:\n- Error:\n- Success:\n- Disabled:\n- Offline\u002Fslow network, if applicable:\n\n## Content voice\n- Tone:\n- Terminology:\n- Microcopy rules:\n\n## Implementation constraints\n- Framework\u002Fstyling system:\n- Design-token constraints:\n- Performance constraints:\n- Compatibility constraints:\n- Test\u002Fscreenshot expectations:\n\n## Open questions\n- [ ] Question \u002F owner \u002F impact\n```\n\n### 4. Use `DESIGN.md` as the decision contract\n\nFor UI\u002FUX\u002Ffrontend work after the refresh:\n\n- Cite the relevant `DESIGN.md` sections before making design choices.\n- Prefer existing components, tokens, and documented constraints.\n- If implementation reveals a design contradiction, update `DESIGN.md` or add an open question before proceeding.\n- Do not introduce a new design-system layer when existing repo-native patterns can be extended.\n\n### 5. Handoff to implementation or Visual Ralph when appropriate\n\n- For normal frontend implementation, hand off with the relevant `DESIGN.md` sections, repo evidence, and acceptance criteria.\n- For visual-reference\u002Fimage\u002Flive-URL matching, hand off to `$visual-ralph` with the approved reference\u002Fbaseline and note that `DESIGN.md` is supporting context, not the visual verdict target.\n\n## Completion checklist\n\nDo not declare the design workflow complete until:\n\n- Existing design docs\u002Fassets\u002Fcomponents\u002Fscreenshots have been inspected or explicitly noted as absent.\n- Missing product\u002Fdesign context has been answered, assumed, or listed in `DESIGN.md` open questions.\n- `DESIGN.md` exists at the repo root and contains all required checklist sections.\n- UI\u002FUX\u002Ffrontend recommendations cite `DESIGN.md` rather than relying on unstated preferences.\n- Any `$visual-ralph` handoff is clearly separated as visual implementation matching, not DESIGN.md governance.\n\nTask: {{ARGUMENTS}}\n",{"name":5,"description":7},"main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Fdesign",1,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one","https:\u002F\u002Fagisota.github.io\u002Fold-one\u002F","https:\u002F\u002Fgithub.com\u002Fagisota","pzd.world","2026-07-04 22:32:06",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add agisota\u002Fold-one --skill design",{"tool":38,"command":39},"bunx","bunx skills add agisota\u002Fold-one --skill design",{"tool":41,"command":42},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fdesign\u002FSKILL.md",true,[],[47,54,61,70,77,84],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":18},"01M75KRGZWQWE9JDBS6RX42NWV","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M75KRCZHKE0ZYAQFFYHS0YNP","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":65,"licenseFileUrl":66,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":18},"01M75KR94KYQ30DTE1P9WNDAE0","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M75KR3H13YJ9QHMD49818FA1","yara-rule-authoring","Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyara-rule-authoring\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M75KQMPY8A4Y8XTDD2DT0M9T","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M75KQHNZ0ANZNJGZY6M8MDAK","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]