[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CQJR0QH9GYGS87178TETB6":3,"skill-same:01M6CQJR0QH9GYGS87178TETB6":112},{"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":31,"publishedAt":58,"linkOnly":59,"markdownContent":60,"markdownBody":61,"frontMatter":62,"refName":75,"commitSha":76,"skillDirectory":77,"forksCount":14,"repositoryHtmlUrl":78,"repositoryHomepageUrl":79,"ownerHtmlUrl":80,"ownerBlogUrl":81,"ownerDescription":82,"updatedAt":83,"install":84,"resources":97},"01M6CQJR0QH9GYGS87178TETB6","design-md",null,"Author\u002Fvalidate\u002Fexport Google's DESIGN.md token spec files.","Trollz1004\u002FANTIGRAVITY","Trollz1004","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F132442315?v=4","01M6CQ4Z97ERZA2CXR388F6NZ1","Joshua Coleman","01M6CQ4ZCYE67QPNWBBV8H9DBE",0,"MIT","https:\u002F\u002Fgithub.com\u002FTrollz1004\u002FANTIGRAVITY\u002Fblob\u002Fmain\u002Fhermes\u002Fdesign-ui\u002Fdesign-md\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57],"design md","design","Tailwind","author","dtcg","tokens","token","files","design-system","export","hermes agent","hermes","system","WCAG","excalidraw","ui","diagram","windows","architecture","validate","accessibility","web","linux","spec","macos","google","2026-11-10 10:12:30",false,"---\nname: design-md\ndescription: Author\u002Fvalidate\u002Fexport Google's DESIGN.md token spec files.\nversion: 1.1.0\nauthor: Hermes Agent\nlicense: MIT\nplatforms: [linux, macos, windows]\nmetadata:\n  hermes:\n    tags: [design, design-system, tokens, ui, accessibility, wcag, tailwind, dtcg, google]\n    related_skills: [popular-web-designs, claude-design, excalidraw, architecture-diagram]\n---\n\n# DESIGN.md Skill\n\nDESIGN.md is Google's open spec (Apache-2.0, `google-labs-code\u002Fdesign.md`) for\ndescribing a visual identity to coding agents. One file combines:\n\n- **YAML front matter** — machine-readable design tokens (normative values)\n- **Markdown body** — human-readable rationale, organized into canonical sections\n\nTokens give exact values. Prose tells agents *why* those values exist and how to\napply them. The CLI (`npx @google\u002Fdesign.md`) lints structure + WCAG contrast,\ndiffs versions for regressions, and exports to Tailwind or W3C DTCG JSON.\n\n## When to use this skill\n\n- User asks for a DESIGN.md file, design tokens, or a design system spec\n- User wants consistent UI\u002Fbrand across multiple projects or tools\n- User pastes an existing DESIGN.md and asks to lint, diff, export, or extend it\n- User asks to port a style guide into a format agents can consume\n- User wants contrast \u002F WCAG accessibility validation on their color palette\n\nFor purely visual inspiration or layout examples, use `popular-web-designs`\ninstead. For *process and taste* when designing a one-off HTML artifact\nfrom scratch (prototype, deck, landing page, component lab), use\n`claude-design`. This skill is for the *formal spec file* itself.\n\n## File anatomy\n\n```md\n---\nversion: alpha\nname: Heritage\ndescription: Architectural minimalism meets journalistic gravitas.\ncolors:\n  primary: \"#1A1C1E\"\n  secondary: \"#6C7278\"\n  tertiary: \"#B8422E\"\n  neutral: \"#F7F5F2\"\ntypography:\n  h1:\n    fontFamily: Public Sans\n    fontSize: 3rem\n    fontWeight: 700\n    lineHeight: 1.1\n    letterSpacing: \"-0.02em\"\n  body-md:\n    fontFamily: Public Sans\n    fontSize: 1rem\nrounded:\n  sm: 4px\n  md: 8px\n  lg: 16px\nspacing:\n  sm: 8px\n  md: 16px\n  lg: 24px\ncomponents:\n  button-primary:\n    backgroundColor: \"{colors.tertiary}\"\n    textColor: \"#FFFFFF\"\n    rounded: \"{rounded.sm}\"\n    padding: 12px\n  button-primary-hover:\n    backgroundColor: \"{colors.primary}\"\n---\n\n## Overview\n\nArchitectural Minimalism meets Journalistic Gravitas...\n\n## Colors\n\n- **Primary (#1A1C1E):** Deep ink for headlines and core text.\n- **Tertiary (#B8422E):** \"Boston Clay\" — the sole driver for interaction.\n\n## Typography\n\nPublic Sans for everything except small all-caps labels...\n\n## Components\n\n`button-primary` is the only high-emphasis action on a page...\n```\n\n## Token types\n\n| Type | Format | Example |\n|------|--------|---------|\n| Color | any CSS color (hex, `rgb()`, `oklch()`, named) | `\"#1A1C1E\"`, `\"oklch(62% 0.18 250)\"` |\n| Dimension | number + unit (`px`, `em`, `rem`) | `48px`, `-0.02em` |\n| Token reference | `{path.to.token}` | `{colors.primary}` |\n| Typography | object with `fontFamily`, `fontSize`, `fontWeight`, `lineHeight`, `letterSpacing`, `fontFeature`, `fontVariation` | see above |\n\nComponent property whitelist: `backgroundColor`, `textColor`, `typography`,\n`rounded`, `padding`, `size`, `height`, `width`. Variants (hover, active,\npressed) are **separate component entries** with related key names\n(`button-primary-hover`), not nested.\n\n## Canonical section order\n\nSections are optional, but present ones should appear in this order. The\nlinter flags out-of-order sections (`section-order`, warning) and duplicate\nheadings — consumers per the spec reject duplicates, so fix both before\nreturning the file.\n\n1. Overview (alias: Brand & Style)\n2. Colors\n3. Typography\n4. Layout (alias: Layout & Spacing)\n5. Elevation & Depth (alias: Elevation)\n6. Shapes\n7. Components\n8. Do's and Don'ts\n\nUnknown sections are preserved, not errored. Unknown token names are accepted\nif the value type is valid. Unknown component properties produce a warning.\n\n## Workflow: authoring a new DESIGN.md\n\n1. **Ask the user** (or infer) the brand tone, accent color, and typography\n   direction. If they provided a site, image, or vibe, translate it to the\n   token shape above.\n2. **Write `DESIGN.md`** in their project root using `write_file`. Always\n   include `name:` and `colors:`; other sections optional but encouraged.\n3. **Use token references** (`{colors.primary}`) in the `components:` section\n   instead of re-typing hex values. Keeps the palette single-source.\n4. **Lint it** (see below). Fix any broken references or WCAG failures\n   before returning.\n5. **If the user has an existing project**, also write Tailwind or DTCG\n   exports next to the file (`tailwind.theme.json`, `tokens.json`).\n\n## Workflow: lint \u002F diff \u002F export\n\nThe CLI is `@google\u002Fdesign.md` (Node). Use `npx` — no global install needed.\n\n```bash\n# Validate structure + token references + WCAG contrast\nnpx -y @google\u002Fdesign.md lint DESIGN.md\n\n# Compare two versions, fail on regression (exit 1 = regression)\nnpx -y @google\u002Fdesign.md diff DESIGN.md DESIGN-v2.md\n\n# Export to Tailwind v3 theme JSON (`tailwind` is a back-compat alias)\nnpx -y @google\u002Fdesign.md export --format json-tailwind DESIGN.md > tailwind.theme.json\n\n# Export to a Tailwind v4 CSS @theme block (--color-*, --text-*, --radius-*, ...)\nnpx -y @google\u002Fdesign.md export --format css-tailwind DESIGN.md > theme.css\n\n# Export to W3C DTCG (Design Tokens Format Module) JSON\nnpx -y @google\u002Fdesign.md export --format dtcg DESIGN.md > tokens.json\n\n# Print the spec itself — useful when injecting into an agent prompt\nnpx -y @google\u002Fdesign.md spec --rules-only --format json\n```\n\nAll commands accept `-` for stdin. `lint` returns exit 1 on errors (warnings\nalone exit 0). `export` exits 0 on a successful export regardless of lint\nfindings in the source — run `lint` separately to gate on those. Output is\nJSON by default; parse it if you need to report findings structurally.\n\nOn Windows, the `design.md` bin name can collide with the `.md` file\nassociation (silent no-op or the file opens in an editor). Use the dot-free\nalias: `npx -y -p @google\u002Fdesign.md designmd lint DESIGN.md`.\n\n### Lint rule reference (the 9 rules, as of CLI 0.3.0)\n\n- `broken-ref` (error) — `{colors.missing}` points at a non-existent token\n- `contrast-ratio` (warning) — component `textColor` vs `backgroundColor`\n  below WCAG AA (4.5:1)\n- `missing-primary` (warning) — colors defined but no `primary` token\n- `missing-typography` (warning) — colors defined but no typography tokens\n- `orphaned-tokens` (warning) — color tokens never referenced by a component\n- `section-order` (warning) — sections out of the canonical order\n- `unknown-key` (warning) — top-level YAML key that looks like a typo of a\n  schema key (`colours:` → `colors:`); custom extension keys stay silent\n- `token-summary`, `missing-sections` (info) — counts and absent optional\n  sections\n\nWhen the user cares about accessibility, call this out explicitly in your\nsummary — WCAG findings are the most load-bearing reason to use the CLI.\n\n## Pitfalls\n\n- **Don't nest component variants.** `button-primary.hover` is wrong;\n  `button-primary-hover` as a sibling key is right.\n- **Hex colors must be quoted strings.** YAML will otherwise choke on `#` or\n  truncate values like `#1A1C1E` oddly.\n- **Negative dimensions need quotes too.** `letterSpacing: -0.02em` parses as\n  a YAML flow — write `letterSpacing: \"-0.02em\"`.\n- **Section order matters even though the linter only warns.** If the user\n  gives you prose in a random order, reorder it to match the canonical list\n  before saving — spec-compliant consumers expect it.\n- **Typography sub-property typos are silently dropped.** As of CLI 0.3.0 a\n  typo like `fontwight:` produces no finding and the value vanishes from\n  exports — double-check sub-property names against the schema\n  (`fontFamily`, `fontSize`, `fontWeight`, `lineHeight`, `letterSpacing`,\n  `fontFeature`, `fontVariation`).\n- **`version: alpha` is the current spec version** (as of Jul 2026, CLI\n  0.3.0). The spec is marked alpha — watch for breaking changes.\n- **Token references resolve by dotted path.** `{colors.primary}` works;\n  `{primary}` does not.\n\n## Spec source of truth\n\n- Repo: https:\u002F\u002Fgithub.com\u002Fgoogle-labs-code\u002Fdesign.md (Apache-2.0)\n- CLI: `@google\u002Fdesign.md` on npm\n- License of generated DESIGN.md files: whatever the user's project uses;\n  the spec itself is Apache-2.0.\n","# DESIGN.md Skill\n\nDESIGN.md is Google's open spec (Apache-2.0, `google-labs-code\u002Fdesign.md`) for\ndescribing a visual identity to coding agents. One file combines:\n\n- **YAML front matter** — machine-readable design tokens (normative values)\n- **Markdown body** — human-readable rationale, organized into canonical sections\n\nTokens give exact values. Prose tells agents *why* those values exist and how to\napply them. The CLI (`npx @google\u002Fdesign.md`) lints structure + WCAG contrast,\ndiffs versions for regressions, and exports to Tailwind or W3C DTCG JSON.\n\n## When to use this skill\n\n- User asks for a DESIGN.md file, design tokens, or a design system spec\n- User wants consistent UI\u002Fbrand across multiple projects or tools\n- User pastes an existing DESIGN.md and asks to lint, diff, export, or extend it\n- User asks to port a style guide into a format agents can consume\n- User wants contrast \u002F WCAG accessibility validation on their color palette\n\nFor purely visual inspiration or layout examples, use `popular-web-designs`\ninstead. For *process and taste* when designing a one-off HTML artifact\nfrom scratch (prototype, deck, landing page, component lab), use\n`claude-design`. This skill is for the *formal spec file* itself.\n\n## File anatomy\n\n```md\n---\nversion: alpha\nname: Heritage\ndescription: Architectural minimalism meets journalistic gravitas.\ncolors:\n  primary: \"#1A1C1E\"\n  secondary: \"#6C7278\"\n  tertiary: \"#B8422E\"\n  neutral: \"#F7F5F2\"\ntypography:\n  h1:\n    fontFamily: Public Sans\n    fontSize: 3rem\n    fontWeight: 700\n    lineHeight: 1.1\n    letterSpacing: \"-0.02em\"\n  body-md:\n    fontFamily: Public Sans\n    fontSize: 1rem\nrounded:\n  sm: 4px\n  md: 8px\n  lg: 16px\nspacing:\n  sm: 8px\n  md: 16px\n  lg: 24px\ncomponents:\n  button-primary:\n    backgroundColor: \"{colors.tertiary}\"\n    textColor: \"#FFFFFF\"\n    rounded: \"{rounded.sm}\"\n    padding: 12px\n  button-primary-hover:\n    backgroundColor: \"{colors.primary}\"\n---\n\n## Overview\n\nArchitectural Minimalism meets Journalistic Gravitas...\n\n## Colors\n\n- **Primary (#1A1C1E):** Deep ink for headlines and core text.\n- **Tertiary (#B8422E):** \"Boston Clay\" — the sole driver for interaction.\n\n## Typography\n\nPublic Sans for everything except small all-caps labels...\n\n## Components\n\n`button-primary` is the only high-emphasis action on a page...\n```\n\n## Token types\n\n| Type | Format | Example |\n|------|--------|---------|\n| Color | any CSS color (hex, `rgb()`, `oklch()`, named) | `\"#1A1C1E\"`, `\"oklch(62% 0.18 250)\"` |\n| Dimension | number + unit (`px`, `em`, `rem`) | `48px`, `-0.02em` |\n| Token reference | `{path.to.token}` | `{colors.primary}` |\n| Typography | object with `fontFamily`, `fontSize`, `fontWeight`, `lineHeight`, `letterSpacing`, `fontFeature`, `fontVariation` | see above |\n\nComponent property whitelist: `backgroundColor`, `textColor`, `typography`,\n`rounded`, `padding`, `size`, `height`, `width`. Variants (hover, active,\npressed) are **separate component entries** with related key names\n(`button-primary-hover`), not nested.\n\n## Canonical section order\n\nSections are optional, but present ones should appear in this order. The\nlinter flags out-of-order sections (`section-order`, warning) and duplicate\nheadings — consumers per the spec reject duplicates, so fix both before\nreturning the file.\n\n1. Overview (alias: Brand & Style)\n2. Colors\n3. Typography\n4. Layout (alias: Layout & Spacing)\n5. Elevation & Depth (alias: Elevation)\n6. Shapes\n7. Components\n8. Do's and Don'ts\n\nUnknown sections are preserved, not errored. Unknown token names are accepted\nif the value type is valid. Unknown component properties produce a warning.\n\n## Workflow: authoring a new DESIGN.md\n\n1. **Ask the user** (or infer) the brand tone, accent color, and typography\n   direction. If they provided a site, image, or vibe, translate it to the\n   token shape above.\n2. **Write `DESIGN.md`** in their project root using `write_file`. Always\n   include `name:` and `colors:`; other sections optional but encouraged.\n3. **Use token references** (`{colors.primary}`) in the `components:` section\n   instead of re-typing hex values. Keeps the palette single-source.\n4. **Lint it** (see below). Fix any broken references or WCAG failures\n   before returning.\n5. **If the user has an existing project**, also write Tailwind or DTCG\n   exports next to the file (`tailwind.theme.json`, `tokens.json`).\n\n## Workflow: lint \u002F diff \u002F export\n\nThe CLI is `@google\u002Fdesign.md` (Node). Use `npx` — no global install needed.\n\n```bash\n# Validate structure + token references + WCAG contrast\nnpx -y @google\u002Fdesign.md lint DESIGN.md\n\n# Compare two versions, fail on regression (exit 1 = regression)\nnpx -y @google\u002Fdesign.md diff DESIGN.md DESIGN-v2.md\n\n# Export to Tailwind v3 theme JSON (`tailwind` is a back-compat alias)\nnpx -y @google\u002Fdesign.md export --format json-tailwind DESIGN.md > tailwind.theme.json\n\n# Export to a Tailwind v4 CSS @theme block (--color-*, --text-*, --radius-*, ...)\nnpx -y @google\u002Fdesign.md export --format css-tailwind DESIGN.md > theme.css\n\n# Export to W3C DTCG (Design Tokens Format Module) JSON\nnpx -y @google\u002Fdesign.md export --format dtcg DESIGN.md > tokens.json\n\n# Print the spec itself — useful when injecting into an agent prompt\nnpx -y @google\u002Fdesign.md spec --rules-only --format json\n```\n\nAll commands accept `-` for stdin. `lint` returns exit 1 on errors (warnings\nalone exit 0). `export` exits 0 on a successful export regardless of lint\nfindings in the source — run `lint` separately to gate on those. Output is\nJSON by default; parse it if you need to report findings structurally.\n\nOn Windows, the `design.md` bin name can collide with the `.md` file\nassociation (silent no-op or the file opens in an editor). Use the dot-free\nalias: `npx -y -p @google\u002Fdesign.md designmd lint DESIGN.md`.\n\n### Lint rule reference (the 9 rules, as of CLI 0.3.0)\n\n- `broken-ref` (error) — `{colors.missing}` points at a non-existent token\n- `contrast-ratio` (warning) — component `textColor` vs `backgroundColor`\n  below WCAG AA (4.5:1)\n- `missing-primary` (warning) — colors defined but no `primary` token\n- `missing-typography` (warning) — colors defined but no typography tokens\n- `orphaned-tokens` (warning) — color tokens never referenced by a component\n- `section-order` (warning) — sections out of the canonical order\n- `unknown-key` (warning) — top-level YAML key that looks like a typo of a\n  schema key (`colours:` → `colors:`); custom extension keys stay silent\n- `token-summary`, `missing-sections` (info) — counts and absent optional\n  sections\n\nWhen the user cares about accessibility, call this out explicitly in your\nsummary — WCAG findings are the most load-bearing reason to use the CLI.\n\n## Pitfalls\n\n- **Don't nest component variants.** `button-primary.hover` is wrong;\n  `button-primary-hover` as a sibling key is right.\n- **Hex colors must be quoted strings.** YAML will otherwise choke on `#` or\n  truncate values like `#1A1C1E` oddly.\n- **Negative dimensions need quotes too.** `letterSpacing: -0.02em` parses as\n  a YAML flow — write `letterSpacing: \"-0.02em\"`.\n- **Section order matters even though the linter only warns.** If the user\n  gives you prose in a random order, reorder it to match the canonical list\n  before saving — spec-compliant consumers expect it.\n- **Typography sub-property typos are silently dropped.** As of CLI 0.3.0 a\n  typo like `fontwight:` produces no finding and the value vanishes from\n  exports — double-check sub-property names against the schema\n  (`fontFamily`, `fontSize`, `fontWeight`, `lineHeight`, `letterSpacing`,\n  `fontFeature`, `fontVariation`).\n- **`version: alpha` is the current spec version** (as of Jul 2026, CLI\n  0.3.0). The spec is marked alpha — watch for breaking changes.\n- **Token references resolve by dotted path.** `{colors.primary}` works;\n  `{primary}` does not.\n\n## Spec source of truth\n\n- Repo: https:\u002F\u002Fgithub.com\u002Fgoogle-labs-code\u002Fdesign.md (Apache-2.0)\n- CLI: `@google\u002Fdesign.md` on npm\n- License of generated DESIGN.md files: whatever the user's project uses;\n  the spec itself is Apache-2.0.\n",{"name":5,"author":63,"license":15,"version":64,"metadata":65,"platforms":74,"description":7},"Hermes Agent","1.1.0",{"hermes":66},{"tags":67,"related_skills":70},[33,40,37,47,52,68,69,36,57],"wcag","tailwind",[71,72,46,73],"popular-web-designs","claude-design","architecture-diagram",[54,56,49],"main","6deb42cc8c67a99d7613cb5802f8bbe01a0f3d12","hermes\u002Fdesign-ui\u002Fdesign-md","https:\u002F\u002Fgithub.com\u002FTrollz1004\u002FANTIGRAVITY","https:\u002F\u002Fwww.ai-solutions.store","https:\u002F\u002Fgithub.com\u002FTrollz1004","https:\u002F\u002Fyouandinotai.com","Founder building YouAndINotAI, OnlineRecycle, and AIDoesItAll through Trash Or Treasure Online Recycler LLC.","2026-11-11 18:41:12",{"source":8,"skillName":5,"commands":85,"prompt":95,"zipAvailable":96},[86,89,92],{"tool":87,"command":88},"npx","npx skills add Trollz1004\u002FANTIGRAVITY --skill design-md",{"tool":90,"command":91},"bunx","bunx skills add Trollz1004\u002FANTIGRAVITY --skill design-md",{"tool":93,"command":94},"pnpm","pnpm dlx skills add Trollz1004\u002FANTIGRAVITY --skill design-md","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTrollz1004\u002FANTIGRAVITY\u002Fblob\u002Fmain\u002Fhermes\u002Fdesign-ui\u002Fdesign-md\u002FSKILL.md",true,[98,104,108],{"path":99,"resourceType":100,"resourceTypeDesc":101,"sizeBytes":102,"sourceHtmlUrl":103},"SOURCE.md","REFERENCE","参考文档",186,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fprediction-markets\u002Fotto-ai-prediction-markets\u002FSOURCE.md",{"path":105,"resourceType":100,"resourceTypeDesc":101,"sizeBytes":106,"sourceHtmlUrl":107},"templates\u002Fstarter.md",2566,"https:\u002F\u002Fgithub.com\u002FTrollz1004\u002FANTIGRAVITY\u002Fblob\u002Fmain\u002Fhermes\u002Fdesign-ui\u002Fdesign-md\u002Ftemplates\u002Fstarter.md",{"path":109,"resourceType":100,"resourceTypeDesc":101,"sizeBytes":110,"sourceHtmlUrl":111},"TRUST.auto.yaml",2217,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fprediction-markets\u002Fotto-ai-prediction-markets\u002FTRUST.auto.yaml",[113,141,172,196,221,247],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":117,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":58},"01M6M5BT49KEBHJM9D0P5NM8ED","security-audit","Security guidance and vulnerability review for codebases, APIs, services, CLI tools, libraries, and daemons. Use for security questions, focused reviews, vulnerability research, security audits, or pen tests. Run the complete workflow only for explicit codebase audit or pen-test requests, full\u002Fcomprehensive\u002Fend-to-end reviews, or requested report artifacts.","https:\u002F\u002Fgithub.com\u002FTrollz1004\u002FANTIGRAVITY\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsecurity-audit\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTrollz1004\u002FANTIGRAVITY\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsecurity-audit\u002FSKILL.md",[],[121,122,123,124,125,126,127,128,129,130,131,132,133,134,135,136,137,138,139,140],"security audit","audit","security","reviews","end","only","workflow","vulnerability","review","libraries","cli","run","Tools","full","for","complete","security guidance","codebase audit","tests","use",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":145,"licenseFileUrl":146,"sourceHtmlUrl":147,"categories":148,"keywords":154,"publishedAt":58},"01M6M5B16Q534MKFHKBHRZ2773","impeccable","Use when the user wants to design, redesign, shape, critique, audit, polish, simplify, harden, animate, or otherwise improve a frontend interface: websites, landing pages, dashboards, product UI, components, forms, settings, onboarding, empty states, and native iOS or Android screens. Handles UX review, hierarchy, layout, typography, color, motion, UX copy, accessibility, responsive behavior, edge cases, and capturing or documenting design systems (DESIGN.md, tokens). Also for making bland UI bolder, loud UI quieter, or ambitious visual effects. Not for backend-only or non-UI tasks.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FTrollz1004\u002FANTIGRAVITY\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimpeccable\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTrollz1004\u002FANTIGRAVITY\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimpeccable\u002FSKILL.md",[149,152,153],{"categoryNo":150,"categoryName":151,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},[143,155,156,157,158,159,33,160,126,161,162,163,164,165,129,166,167,168,169,170,171],"ux copy","states","quieter","frontend","improve","interface","design systems","effects","simplify","tasks","components","hierarchy","critique","native","product","layout","when",{"skillNo":173,"name":174,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":176,"sourceHtmlUrl":177,"categories":178,"keywords":181,"publishedAt":58},"01M6M5AHHV2NPZYVMW48HP7A6H","hallmark","Design skill for websites and new pages that look designed, not generated. Use when the user asks to build or design something new, or names Hallmark. Never use it on an existing design unless the user names Hallmark, as in `\u002Fhallmark redesign \u003Cpath>`.","https:\u002F\u002Fgithub.com\u002FTrollz1004\u002FANTIGRAVITY\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fhallmark\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTrollz1004\u002FANTIGRAVITY\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fhallmark\u002FSKILL.md",[179,180],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[174,182,183,135,184,185,33,186,140,187,188,189,122,190,191,192,193,194,195,171],"as","never","true","pages","generated","Existing","prompt","build","redesign","look","it","user","path","new",{"skillNo":197,"name":198,"nameZh":6,"description":199,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":145,"licenseFileUrl":200,"sourceHtmlUrl":201,"categories":202,"keywords":207,"publishedAt":58},"01M6CQDXJ785JCD5PMKYD239ZZ","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002FTrollz1004\u002FANTIGRAVITY\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FTrollz1004\u002FANTIGRAVITY\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[203,206],{"categoryNo":204,"categoryName":205,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":150,"categoryName":151,"taxonomyType":21,"taxonomyTypeDesc":22},[208,209,210,211,158,212,213,214,215,216,53,217,47,218,135,219,220],"webapp","testing","webapp testing","applications","debugging","toolkit","logs","browser","playwright","behavior","screenshots","local","with",{"skillNo":222,"name":223,"nameZh":6,"description":224,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":225,"sourceHtmlUrl":226,"categories":227,"keywords":228,"publishedAt":58},"01M6CQ5HBDE9Q5WJZXQ7G72MYD","appinsights-instrumentation","Guidance for instrumenting webapps with Azure Application Insights. Provides telemetry patterns, SDK setup, and configuration references. USE FOR: how to instrument app, App Insights SDK, telemetry patterns, what is App Insights, Application Insights guidance, instrumentation examples, APM best practices. DO NOT USE FOR: adding App Insights to my app (use azure-prepare), add telemetry to my project (use azure-prepare), add monitoring (use azure-prepare). This skill provides guidance—azure-prepare orchestrates component changes.","https:\u002F\u002Fgithub.com\u002FTrollz1004\u002FANTIGRAVITY\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fappinsights-instrumentation\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FTrollz1004\u002FANTIGRAVITY\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fappinsights-instrumentation\u002FSKILL.md",[],[229,230,231,232,233,140,234,235,236,237,238,239,240,241,242,243,244,245,246,135],"appinsights instrumentation","instrumentation","do","azure","telemetry","monitoring","references","component","how","patterns","apm","sdk setup","app","project","insights","how to","my","add",{"skillNo":248,"name":249,"nameZh":6,"description":250,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":251,"categories":252,"keywords":266,"publishedAt":58},"01M6CQNQ5FNDP6K32RKXQ9X157","youtube-automation","YouTube automation: upload, SEO, thumbnails, scheduling, analytics.","https:\u002F\u002Fgithub.com\u002FTrollz1004\u002FANTIGRAVITY\u002Fblob\u002Fmain\u002Fops\u002Fskills\u002Fyoutube-automation\u002FSKILL.md",[253,256,259,260,263],{"categoryNo":254,"categoryName":255,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":257,"categoryName":258,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000019","营销推广",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":261,"categoryName":262,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000033","数据分析师",{"categoryNo":264,"categoryName":265,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000035","市场营销",[267,268,269,49,270,54,271,272,43,273,42,274,56,275],"automation","youtube","youtube automation","seo","scheduling","thumbnails","analytics","content","upload"]