[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78DPRJYTPWDWREG7RRQDY3G":3,"skill-same:01M78DPRJYTPWDWREG7RRQDY3G":49},{"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":28,"commitSha":29,"skillDirectory":30,"forksCount":14,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M78DPRJYTPWDWREG7RRQDY3G","web-design-master",null,"Professional web design standard (\"AI Professional Web Design Master Prompt\") covering page\u002Fsection\u002Flayout design, visual hierarchy, color systems, typography scales, 8-point grid spacing, responsive breakpoints, accessibility, and design QA review. Use when designing or building any page, section, or layout so it looks deliberately designed by a professional product team rather than a generic AI template.","P-Core-System\u002Fpcore-orchestra","P-Core-System","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F316099351?v=4","01M78DJ0920WA62RQ0Q00B81HQ","P Core System","01M78DJ09XWRZS3VDK927QW72Z",0,"MIT","https:\u002F\u002Fgithub.com\u002FP-Core-System\u002Fpcore-orchestra\u002Fblob\u002Fmain\u002Fbundle\u002Fopencode\u002Fskills\u002Fweb-design-master\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: web-design-master\ndescription: Professional web design standard (\"AI Professional Web Design Master Prompt\") covering page\u002Fsection\u002Flayout design, visual hierarchy, color systems, typography scales, 8-point grid spacing, responsive breakpoints, accessibility, and design QA review. Use when designing or building any page, section, or layout so it looks deliberately designed by a professional product team rather than a generic AI template.\nargument-hint: \"[page, section, or component]\"\nlicense: MIT\nmetadata:\n  author: claudekit\n  version: \"1.0.0\"\n---\n\n# Web Design Master Skill\n\nProfessional web design standard that produces sites looking deliberately designed by a\nprofessional team — not a generic AI template. Encodes the full \"AI Professional Web\nDesign Master Prompt\" as actionable guidance for design and build work.\n\n## Role\n\nPrincipal Product Designer, Senior UX\u002FUI Designer, Design Systems Engineer, Senior\nFrontend Engineer.\n\n**Goal:** a site that looks deliberately designed by a professional team, not a generic\nAI template. Prioritize: visual hierarchy, usability, accessibility, consistency,\nresponsive, performance, clean modern aesthetics, strong information architecture,\nproduction-ready.\n\n## When to Use This Skill\n\nUse when:\n- Designing or building a page, section, or layout (hero, features, pricing, CTA, etc.)\n- Establishing a color system, typography scale, spacing tokens, or component specs\n- Making the UI responsive across breakpoints (375 \u002F 768 \u002F 1024 \u002F 1440px)\n- Reviewing an existing design for visual hierarchy, contrast, alignment, or consistency\n- Doing a design QA pass before calling a UI \"done\"\n\n## 1. Visual Hierarchy\n\n- **F-pattern** for content-heavy pages (text\u002Freading); **Z-pattern** for landing\u002Fmarketing pages.\n- **CTA hierarchy:** Primary (strong accent, action label) → Secondary (outline\u002Fghost\u002Fneutral) → Tertiary (text link\u002Fsubtle).\n- **Never make multiple CTAs compete** — exactly one primary per screen\u002Fsection.\n\nExample:\n```\n[Primary   ]> Save changes\n[Secondary ]> Cancel\n[Tertiary  ]> Learn more\n```\n\n## 2. Color 60\u002F30\u002F10\n\n- **60% dominant neutral background**, **30% secondary** (cards\u002Fnav\u002Fsections), **10% accent** (primary CTA\u002Flinks\u002Fstatus\u002Fbadges\u002Fselected\u002Fhover\u002Ffocus).\n- **WCAG AA ≥ 4.5:1** for normal text; ≥ 3:1 for large text.\n- Avoid excess gradients and competing accents.\n\n## 3. 8-Point Grid\n\nUse spacing from the 8-point scale: `8, 16, 24, 32, 40, 48, 64, 80, 96, 120px`.\n- Card internal padding ~24px; card gap 24–32px; sections 80–120px.\n- Avoid off-scale values like 13, 19, 27, 37px.\n\n## 4. Whitespace\n\n- Generous negative space. Sections ~80–120px on desktop; reduce on mobile.\n- Whitespace supports hierarchy — tighter grouping for related content, more for separation.\n\n## 5. Typography\n\nModern sans-serif fonts: Inter, Plus Jakarta Sans, Geist, IBM Plex Sans.\n**Perfect Fourth 1.333 scale:**\n- body 16, h3 ~21, h2 ~28, h1 ~37, hero ~49.\n- Body 16px, line-height 1.5–1.6, max width ~65ch.\n- Headings line-height 1.1–1.2.\n\n## 6. Responsive\n\nMobile-first. Desktop 12-col grid, max width 1200–1440px. Tablet adapts. Mobile 1-col,\nstacked CTAs, touch targets ≥ 44×44px. **Never just shrink desktop** — re-layout.\n\n## 7. Components\n\nConsistent buttons\u002Finputs\u002Fcards\u002Fbadges\u002Fnav\u002Fmodal\u002Fdropdown\u002Ftabs\u002Falerts\u002Fforms\u002Ftables\u002Ftooltips\nwith consistent spacing, type, radius, color, and states. Avoid divergent variants — one\nsource of truth, not five nearly-identical buttons.\n\n## 8. Border Radius\n\nSmall token system — no random 3+7+11+17+23px:\n- inputs\u002Fbuttons **8px**\n- cards **16px**\n- large containers **20–24px**\n\n## 9. Shadows\n\nSubtle layered elevation — low opacity, large blur, small offset. Avoid heavy black\nshadows, old 3D, neumorphism, strong outlines.\n\n## 10. Micro-interactions\n\nFast, subtle, purposeful, accessible. Hover\u002Ffocus\u002Fcard\u002Fnav transitions, loading,\nskeleton, feedback, accordion. **Respect `prefers-reduced-motion`.**\n\n## 11. Content Hierarchy\n\nEach section answers a question:\n- hero: what \u002F who \u002F why \u002F next\n- features: problem\n- social proof: trust\n- pricing: cost \u002F what you receive\n- CTA: next step\n\nNever emit template-only filler sections.\n\n## 12. Visual Direction\n\nClean \u002F modern \u002F premium \u002F professional \u002F calm \u002F intentional \u002F trustworthy. Avoid excess\ngradients and colors, glassmorphism, unnecessary illustrations, random shapes, overly\nrounded cards, decorative elements, and the generic AI look.\n\n## 13. Accessibility\n\n- Color contrast, keyboard navigation, visible focus\n- Semantic HTML, heading hierarchy, form labels\n- Descriptive buttons, alt text, touch targets ≥ 44px\n- **Never use color alone** to convey meaning\n\n## 14. UX Quality Check\n\n- **Visual** — hierarchy, whitespace, color, typography, alignment\n- **UX** — new-user understanding, primary CTA obvious, secondary subordinate, nav, mobile\n- **A11y** — contrast, keyboard, focus, touch\n- **Responsive** — 375\u002F768\u002F1024\u002F1440px; no overflow, broken grid, overlap, tiny buttons, unreadable type, or broken images\n\n## 15. Implementation\n\n- Reusable components, design tokens, no duplicated styles, predictable layout logic\n- Semantic HTML, organized responsive rules, consistent spacing, optimized images\n- Minimal JS, accessible\n- **If Tailwind:** design-token approach — not random utilities\n\n## 16. Final Standard\n\nAsk: *\"Does this look like a deliberate product design system or an AI template?\"*\nIf generic, improve hierarchy \u002F typography \u002F spacing \u002F alignment \u002F color restraint \u002F\ncomponent consistency \u002F responsive \u002F content. **Add more design system, not decoration.**\n\n## Output\n\n- Information architecture, page\u002Fsection structure, design system\n- Color tokens, typography scale, spacing tokens, component specs\n- Responsive, accessibility, production-ready frontend\n\n## Best Practices\n\n1. **One primary CTA per screen** — never let multiple CTAs compete\n2. **8-point spacing everywhere** — never drift to odd pixel values\n3. **Token over utility** — colors, radii, shadows, spacing come from tokens\n4. **Accessibility first** — contrast, keyboard, focus, semantic HTML from the start\n5. **Reusable components** — shared spacing\u002Ftype\u002Fradius\u002Fcolor\u002Fstates, few variants\n6. **Design restraint** — fewer colors + gradients, not more decoration\n7. **Mobile-first responsive** — re-layout, don't shrink\n8. **QA on final render** — check hierarchy, contrast, alignment, all breakpoints\n\n## Complements\n\nPair with `ui-ux-pro-max` (product\u002Fpage reasoning), `design-system` (tokens\u002Fcomponents),\nand `ui-styling` (Tailwind\u002Fshadcn theming). Reference template:\n`templates\u002Farchitectures\u002F28-web-design-master.md`.","# Web Design Master Skill\n\nProfessional web design standard that produces sites looking deliberately designed by a\nprofessional team — not a generic AI template. Encodes the full \"AI Professional Web\nDesign Master Prompt\" as actionable guidance for design and build work.\n\n## Role\n\nPrincipal Product Designer, Senior UX\u002FUI Designer, Design Systems Engineer, Senior\nFrontend Engineer.\n\n**Goal:** a site that looks deliberately designed by a professional team, not a generic\nAI template. Prioritize: visual hierarchy, usability, accessibility, consistency,\nresponsive, performance, clean modern aesthetics, strong information architecture,\nproduction-ready.\n\n## When to Use This Skill\n\nUse when:\n- Designing or building a page, section, or layout (hero, features, pricing, CTA, etc.)\n- Establishing a color system, typography scale, spacing tokens, or component specs\n- Making the UI responsive across breakpoints (375 \u002F 768 \u002F 1024 \u002F 1440px)\n- Reviewing an existing design for visual hierarchy, contrast, alignment, or consistency\n- Doing a design QA pass before calling a UI \"done\"\n\n## 1. Visual Hierarchy\n\n- **F-pattern** for content-heavy pages (text\u002Freading); **Z-pattern** for landing\u002Fmarketing pages.\n- **CTA hierarchy:** Primary (strong accent, action label) → Secondary (outline\u002Fghost\u002Fneutral) → Tertiary (text link\u002Fsubtle).\n- **Never make multiple CTAs compete** — exactly one primary per screen\u002Fsection.\n\nExample:\n```\n[Primary   ]> Save changes\n[Secondary ]> Cancel\n[Tertiary  ]> Learn more\n```\n\n## 2. Color 60\u002F30\u002F10\n\n- **60% dominant neutral background**, **30% secondary** (cards\u002Fnav\u002Fsections), **10% accent** (primary CTA\u002Flinks\u002Fstatus\u002Fbadges\u002Fselected\u002Fhover\u002Ffocus).\n- **WCAG AA ≥ 4.5:1** for normal text; ≥ 3:1 for large text.\n- Avoid excess gradients and competing accents.\n\n## 3. 8-Point Grid\n\nUse spacing from the 8-point scale: `8, 16, 24, 32, 40, 48, 64, 80, 96, 120px`.\n- Card internal padding ~24px; card gap 24–32px; sections 80–120px.\n- Avoid off-scale values like 13, 19, 27, 37px.\n\n## 4. Whitespace\n\n- Generous negative space. Sections ~80–120px on desktop; reduce on mobile.\n- Whitespace supports hierarchy — tighter grouping for related content, more for separation.\n\n## 5. Typography\n\nModern sans-serif fonts: Inter, Plus Jakarta Sans, Geist, IBM Plex Sans.\n**Perfect Fourth 1.333 scale:**\n- body 16, h3 ~21, h2 ~28, h1 ~37, hero ~49.\n- Body 16px, line-height 1.5–1.6, max width ~65ch.\n- Headings line-height 1.1–1.2.\n\n## 6. Responsive\n\nMobile-first. Desktop 12-col grid, max width 1200–1440px. Tablet adapts. Mobile 1-col,\nstacked CTAs, touch targets ≥ 44×44px. **Never just shrink desktop** — re-layout.\n\n## 7. Components\n\nConsistent buttons\u002Finputs\u002Fcards\u002Fbadges\u002Fnav\u002Fmodal\u002Fdropdown\u002Ftabs\u002Falerts\u002Fforms\u002Ftables\u002Ftooltips\nwith consistent spacing, type, radius, color, and states. Avoid divergent variants — one\nsource of truth, not five nearly-identical buttons.\n\n## 8. Border Radius\n\nSmall token system — no random 3+7+11+17+23px:\n- inputs\u002Fbuttons **8px**\n- cards **16px**\n- large containers **20–24px**\n\n## 9. Shadows\n\nSubtle layered elevation — low opacity, large blur, small offset. Avoid heavy black\nshadows, old 3D, neumorphism, strong outlines.\n\n## 10. Micro-interactions\n\nFast, subtle, purposeful, accessible. Hover\u002Ffocus\u002Fcard\u002Fnav transitions, loading,\nskeleton, feedback, accordion. **Respect `prefers-reduced-motion`.**\n\n## 11. Content Hierarchy\n\nEach section answers a question:\n- hero: what \u002F who \u002F why \u002F next\n- features: problem\n- social proof: trust\n- pricing: cost \u002F what you receive\n- CTA: next step\n\nNever emit template-only filler sections.\n\n## 12. Visual Direction\n\nClean \u002F modern \u002F premium \u002F professional \u002F calm \u002F intentional \u002F trustworthy. Avoid excess\ngradients and colors, glassmorphism, unnecessary illustrations, random shapes, overly\nrounded cards, decorative elements, and the generic AI look.\n\n## 13. Accessibility\n\n- Color contrast, keyboard navigation, visible focus\n- Semantic HTML, heading hierarchy, form labels\n- Descriptive buttons, alt text, touch targets ≥ 44px\n- **Never use color alone** to convey meaning\n\n## 14. UX Quality Check\n\n- **Visual** — hierarchy, whitespace, color, typography, alignment\n- **UX** — new-user understanding, primary CTA obvious, secondary subordinate, nav, mobile\n- **A11y** — contrast, keyboard, focus, touch\n- **Responsive** — 375\u002F768\u002F1024\u002F1440px; no overflow, broken grid, overlap, tiny buttons, unreadable type, or broken images\n\n## 15. Implementation\n\n- Reusable components, design tokens, no duplicated styles, predictable layout logic\n- Semantic HTML, organized responsive rules, consistent spacing, optimized images\n- Minimal JS, accessible\n- **If Tailwind:** design-token approach — not random utilities\n\n## 16. Final Standard\n\nAsk: *\"Does this look like a deliberate product design system or an AI template?\"*\nIf generic, improve hierarchy \u002F typography \u002F spacing \u002F alignment \u002F color restraint \u002F\ncomponent consistency \u002F responsive \u002F content. **Add more design system, not decoration.**\n\n## Output\n\n- Information architecture, page\u002Fsection structure, design system\n- Color tokens, typography scale, spacing tokens, component specs\n- Responsive, accessibility, production-ready frontend\n\n## Best Practices\n\n1. **One primary CTA per screen** — never let multiple CTAs compete\n2. **8-point spacing everywhere** — never drift to odd pixel values\n3. **Token over utility** — colors, radii, shadows, spacing come from tokens\n4. **Accessibility first** — contrast, keyboard, focus, semantic HTML from the start\n5. **Reusable components** — shared spacing\u002Ftype\u002Fradius\u002Fcolor\u002Fstates, few variants\n6. **Design restraint** — fewer colors + gradients, not more decoration\n7. **Mobile-first responsive** — re-layout, don't shrink\n8. **QA on final render** — check hierarchy, contrast, alignment, all breakpoints\n\n## Complements\n\nPair with `ui-ux-pro-max` (product\u002Fpage reasoning), `design-system` (tokens\u002Fcomponents),\nand `ui-styling` (Tailwind\u002Fshadcn theming). Reference template:\n`templates\u002Farchitectures\u002F28-web-design-master.md`.",{"name":5,"license":15,"metadata":24,"description":7,"argument-hint":27},{"author":25,"version":26},"claudekit","1.0.0","[page, section, or component]","main","5a348537f6ee031f76c168e397c0d023f35ef333","bundle\u002Fopencode\u002Fskills\u002Fweb-design-master","https:\u002F\u002Fgithub.com\u002FP-Core-System\u002Fpcore-orchestra","https:\u002F\u002Fgithub.com\u002FP-Core-System","P Core System — the P-Core family: trading, AI brain, assistant, orchestration, and web AI server.","2026-11-13 11:33:11",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add P-Core-System\u002Fpcore-orchestra --skill web-design-master",{"tool":41,"command":42},"bunx","bunx skills add P-Core-System\u002Fpcore-orchestra --skill web-design-master",{"tool":44,"command":45},"pnpm","pnpm dlx skills add P-Core-System\u002Fpcore-orchestra --skill web-design-master","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FP-Core-System\u002Fpcore-orchestra\u002Fblob\u002Fmain\u002Fbundle\u002Fopencode\u002Fskills\u002Fweb-design-master\u002FSKILL.md",true,[],[50,57,64,71,76,83],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M78DYATRNCN2NFKA4YRBG0T9","wrangler","Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002FP-Core-System\u002Fpcore-orchestra\u002Fblob\u002Fmain\u002Fbundle\u002Fskills\u002Fwrangler\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M78DY6XPJ7B09HWH01PGQTJZ","workers-best-practices","Reviews and authors Cloudflare Workers code against production best practices. Load when writing new Workers, reviewing Worker code, configuring wrangler.jsonc, or checking for common Workers anti-patterns (streaming, floating promises, global state, secrets, bindings, observability). Biases towards retrieval from Cloudflare docs over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002FP-Core-System\u002Fpcore-orchestra\u002Fblob\u002Fmain\u002Fbundle\u002Fskills\u002Fworkers-best-practices\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M78DY267V5PK9KD65ENG451F","web-perf","Analyzes web performance using Chrome DevTools MCP. Measures Core Web Vitals (LCP, INP, CLS) and supplementary metrics (FCP, TBT, Speed Index), identifies render-blocking resources, network dependency chains, layout shifts, caching issues, and accessibility gaps. Use when asked to audit, profile, debug, or optimize page load performance, Lighthouse scores, or site speed. Biases towards retrieval from current documentation over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002FP-Core-System\u002Fpcore-orchestra\u002Fblob\u002Fmain\u002Fbundle\u002Fskills\u002Fweb-perf\u002FSKILL.md",[],[],{"skillNo":72,"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":73,"categories":74,"keywords":75,"publishedAt":19},"01M78DXXT4TWE2K8M0E9V417J9","https:\u002F\u002Fgithub.com\u002FP-Core-System\u002Fpcore-orchestra\u002Fblob\u002Fmain\u002Fbundle\u002Fskills\u002Fweb-design-master\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},"01M78DXTPQ1XARW18D46JFY5AP","verification-before-completion","Require command evidence before claiming done. Use proactively before VERIFY_PASS, ORCHESTRA_COMPLETE, or \"all fixed\" statements. Run tests, lint, health, or git checks — never trust claims without output.","https:\u002F\u002Fgithub.com\u002FP-Core-System\u002Fpcore-orchestra\u002Fblob\u002Fmain\u002Fbundle\u002Fskills\u002Fverification-before-completion\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":87,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M78DXKFTZ00TJRWK84FNHGVH","ui-ux-pro-max","UI\u002FUX design intelligence for web and mobile. Searchable local database with 84 styles, 192 color palettes, 74 font pairings, 192 product types, 98 UX guidelines, 104 icon entries, 16 GSAP motion presets, and 25 chart types across 22 stacks (React, Next.js, Vue, Nuxt, Svelte, Astro, SwiftUI, React Native, Flutter, Tailwind, shadcn\u002Fui, Jetpack Compose, Angular, Laravel, JavaFX, WPF, WinUI, Avalonia, Uno Platform, UWP, Three.js, and HTML\u002FCSS). Use when designing, building, or reviewing UI: pages, components, color schemes, typography, layout, accessibility, animation, or data visualization.","https:\u002F\u002Fgithub.com\u002FP-Core-System\u002Fpcore-orchestra\u002Fblob\u002Fmain\u002Fbundle\u002Fskills\u002Fui-ux-pro-max\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FP-Core-System\u002Fpcore-orchestra\u002Fblob\u002Fmain\u002Fbundle\u002Fskills\u002Fui-ux-pro-max\u002FSKILL.md",[],[]]