[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DRFS97125JS4GYENNZ1N58":3,"skill-same:01M7DRFS97125JS4GYENNZ1N58":51},{"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":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":36,"install":37,"resources":50},"01M7DRFS97125JS4GYENNZ1N58","ui-score",null,"Score a UI file's design quality 0-100 against StyleSeed's design language — per-category breakdown, the worst offenders, and a prioritized fix list. A quantified version of \u002Fss-review.","Hazek-dc\u002FPresensiGuru_FaceNet_EMAR","Hazek-dc","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F75208960?v=4","01M7DEQV5B4YGS86A81DYH81DR","Hazek","01M7DEQV5XP4TM0C6NTHXCXCHR",1,"MIT","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fui-score\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ui-score\ndescription: Score a UI file's design quality 0-100 against StyleSeed's design language — per-category breakdown, the worst offenders, and a prioritized fix list. A quantified version of \u002Fss-review.\nrisk: unknown\nsource: https:\u002F\u002Fgithub.com\u002Fbitjaru\u002Fstyleseed\u002Ftree\u002Fmain\u002Fengine\u002F.claude\u002Fskills\u002Fss-score\nsource_repo: bitjaru\u002Fstyleseed\nsource_type: community\ndate_added: 2026-07-01\nlicense: MIT\nlicense_source: https:\u002F\u002Fgithub.com\u002Fbitjaru\u002Fstyleseed\u002Fblob\u002Fmain\u002FLICENSE\n---\n\n# Design Score\n## When to Use\n\nUse this skill when you need score a UI file's design quality 0-100 against StyleSeed's design language — per-category breakdown, the worst offenders, and a prioritized fix list. A quantified version of \u002Fss-review.\n\n\n`\u002Fss-review` tells you *what's wrong*. `\u002Fss-score` tells you *how good it is\noverall* and *what to fix first* — a single number plus a category breakdown, so\nyou can track UI quality like you track test coverage.\n\n## When NOT to use\n\n- For a quick pass\u002Ffail before committing → use `\u002Fss-lint`\n- For a full prose audit with fixes → use `\u002Fss-review`\n- For non-UI files (logic, config) — scoring is meaningless\n\n## What to score\n\nScore the file (or each file in a directory) on **six weighted categories** that\nmap to the design language. Total = 100.\n\n| Category | Weight | Reads from |\n|---|---|---|\n| **Color discipline** | 18 | DESIGN-LANGUAGE §1, §18, §72 + VISUAL-CRAFT §C4 |\n| **Hierarchy & typography** | 18 | §2, §3, §4, §16 + Font Size table + VISUAL-CRAFT §C2 |\n| **Layout & rhythm** | 14 | §13, §14, §15, §61 + VISUAL-CRAFT §C1 |\n| **Cards & elevation** | 12 | §7, §8, §12, §1 + VISUAL-CRAFT §C3 |\n| **States & a11y** | 18 | §11, §70, §71, §72 + VISUAL-CRAFT §C3 |\n| **Motion & interaction** | 8 | §24, §59 + `engine\u002Fmotion` |\n| **Coherence** | 12 | VISUAL-CRAFT §C0 (one choice per axis) |\n\n## How to score each category\n\nFor each category, start at full marks and **subtract** for violations you find by\nreading the code. Be specific and evidence-based — cite the line.\n\n**Color discipline (20)** — deduct for: any `#000`\u002F`text-black` (−4 each, cap −8);\nmore than one accent hue used decoratively (−5); **emoji used as UI icons** (multi-color,\nbreaks single accent) (−5); **a normal\u002FOK\u002F\"보통\" state shown in a status color** instead of\nneutral grey (−4); **status color on most\u002Fevery row** (no severity hierarchy) (−4);\n**decorative hues** (gold stars, rainbow category dots) instead of accent\u002Fgrey (−3);\nhardcoded hex where a semantic token exists (−2 each, cap −6); status conveyed by color\nalone (−4).\n\n**Hierarchy & typography (20)** — deduct for: number\u002Funit not ~2:1 (−4); font\nsizes off the Font Size table \u002F `text-[var(--…)]` for size (−5); everything the\nsame weight, no clear primary (−5); cramped or wrong line-height on body (−3).\n\n**Layout & rhythm (15)** — deduct for: content on bare background, not in cards\n(−6); `px-4`\u002F`px-8`\u002F`mx-4` instead of `px-6`\u002F`mx-6` (−3); same section type\nrepeated in a row (−4); no `space-y-6` rhythm (−3).\n\n**Cards & elevation (15)** — deduct for: 1px borders doing separation work that\ntone+shadow should (−4); shadows over ~8% opacity \u002F visibly heavy (−4); no\ncard\u002Fbackground tone separation (−5).\n\n**States & a11y (20)** — deduct for: missing empty\u002Floading\u002Ferror state on a data\nsurface (−5 each, cap −10); contrast below 4.5:1 body \u002F 3:1 large (−6); touch\ntarget \u003C 44px (−4); no visible focus \u002F `outline:none` (−5); icon-only control\nwithout `aria-label` (−3).\n\n**Motion & interaction (8)** — deduct for: random\u002Fad-hoc fades instead of a named\nseed\u002Fkeyword (−3); motion that delays content or blocks an action (−4); no\n`prefers-reduced-motion` handling on custom motion (−3); scroll-linked\u002Fparallax\n(forbidden, §59) (−5).\n\n**Coherence (12)** — the \"one choice per axis\" laws (VISUAL-CRAFT §C0). Deduct for\neach axis that is *mixed* rather than unified across the file: mixed radius\npersonalities, e.g. sharp panel + pill buttons (−5); two+ competing accent hues used\nfor emphasis (−4); mixed shadow languages \u002F light directions (−3); mixed icon\nfamilies, fill modes, or stroke weights (−3); same radius on a nested element instead\nof `inner = outer − padding` (−2); inconsistent control heights for buttons\u002Finputs\n(−2). This is the category that most predicts \"looks AI-generated\" — weight evidence\nof system-wide consistency, not per-component prettiness.\n\nClamp each category at 0. Sum to a total.\n\n## Output format\n\n```\n## Design Score: 70 \u002F 100   (src\u002Fapp\u002FDashboard.tsx)\n\n████████████████░░░░░░  C-\n\nColor discipline      13\u002F18   ▓▓▓░  #000 headings (l.12,40); orange+blue+green accents (l.28-34)\nHierarchy & typography 15\u002F18  ▓▓▓▓  number\u002Funit 1:1 on hero (l.18)\nLayout & rhythm        11\u002F14  ▓▓▓░  two identical KPI rows (l.22-31)\nCards & elevation       8\u002F12  ▓▓░░  1px borders doing separation (l.22)\nStates & a11y          11\u002F18  ▓▓░░  no empty\u002Floading state; focus ring missing (l.55)\nMotion & interaction    6\u002F8   ▓▓▓░  default fade, not a named seed\nCoherence               6\u002F12  ▓▓░░  sharp cards (l.22) + pill buttons (l.48); 3 accent hues (§C0)\n\n### Fix first (highest score gain)\n1. Add empty + loading states to the orders list       → +7 states (§71)\n2. Unify radius (pick soft 8-12px) + collapse to one accent → +9 coherence+color (§C0, §2)\n3. Drop the 1px borders, use tone + ≤8% shadow         → +4 cards  (§7)\n\nRe-score after: ~92 \u002F 100.\n```\n\nUse letter bands: 90+ A · 80-89 B · 70-79 C · 60-69 D · \u003C60 F.\n\n## Gate mode (use this as the Quality Gate before showing the user UI)\n\nThe Quality Gate (CLAUDE.md \u002F AGENTS.md) is `\u002Fss-score` run as a loop, not a one-off:\n\n1. Score the just-generated UI.\n2. If **\u003C 80**, apply the \"fix first\" list (use `\u002Fss-review` to make the edits), then **re-score**.\n3. Repeat up to ~3×, or until ≥ 80.\n4. Present the UI with the final score and a one-line \"fixed: …\".\n\nThe pass bar is a **floor, not a ceiling** — get to ≥ 80 and stop; don't chase 100. The point\nis that no first-draft, obviously-incoherent UI reaches the user. Especially never ship below\n80 with a rainbow status list, emoji icons, two accents, or missing states — those are the\nexact tells the gate exists to catch.\n\n## Rules\n\n- **Read the file** — score from real evidence (line numbers), never guess.\n- Order the \"fix first\" list by **score gain**, not by severity alone — the goal\n  is the fastest path to a better number.\n- For a directory, print a one-line score per file, then the lowest-scoring file's\n  full breakdown.\n- Don't auto-edit in plain scoring. `\u002Fss-score` measures; `\u002Fss-review` and `\u002Fss-motion` fix.\n  In **Gate mode** (above) you do fix-and-re-score until the floor is met.\n- As a *gate*, ≥ 80 is a floor before showing the user — but don't over-polish: chasing 95→100\n  to delay shipping is worse than shipping a clean 85.\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n","# Design Score\n## When to Use\n\nUse this skill when you need score a UI file's design quality 0-100 against StyleSeed's design language — per-category breakdown, the worst offenders, and a prioritized fix list. A quantified version of \u002Fss-review.\n\n\n`\u002Fss-review` tells you *what's wrong*. `\u002Fss-score` tells you *how good it is\noverall* and *what to fix first* — a single number plus a category breakdown, so\nyou can track UI quality like you track test coverage.\n\n## When NOT to use\n\n- For a quick pass\u002Ffail before committing → use `\u002Fss-lint`\n- For a full prose audit with fixes → use `\u002Fss-review`\n- For non-UI files (logic, config) — scoring is meaningless\n\n## What to score\n\nScore the file (or each file in a directory) on **six weighted categories** that\nmap to the design language. Total = 100.\n\n| Category | Weight | Reads from |\n|---|---|---|\n| **Color discipline** | 18 | DESIGN-LANGUAGE §1, §18, §72 + VISUAL-CRAFT §C4 |\n| **Hierarchy & typography** | 18 | §2, §3, §4, §16 + Font Size table + VISUAL-CRAFT §C2 |\n| **Layout & rhythm** | 14 | §13, §14, §15, §61 + VISUAL-CRAFT §C1 |\n| **Cards & elevation** | 12 | §7, §8, §12, §1 + VISUAL-CRAFT §C3 |\n| **States & a11y** | 18 | §11, §70, §71, §72 + VISUAL-CRAFT §C3 |\n| **Motion & interaction** | 8 | §24, §59 + `engine\u002Fmotion` |\n| **Coherence** | 12 | VISUAL-CRAFT §C0 (one choice per axis) |\n\n## How to score each category\n\nFor each category, start at full marks and **subtract** for violations you find by\nreading the code. Be specific and evidence-based — cite the line.\n\n**Color discipline (20)** — deduct for: any `#000`\u002F`text-black` (−4 each, cap −8);\nmore than one accent hue used decoratively (−5); **emoji used as UI icons** (multi-color,\nbreaks single accent) (−5); **a normal\u002FOK\u002F\"보통\" state shown in a status color** instead of\nneutral grey (−4); **status color on most\u002Fevery row** (no severity hierarchy) (−4);\n**decorative hues** (gold stars, rainbow category dots) instead of accent\u002Fgrey (−3);\nhardcoded hex where a semantic token exists (−2 each, cap −6); status conveyed by color\nalone (−4).\n\n**Hierarchy & typography (20)** — deduct for: number\u002Funit not ~2:1 (−4); font\nsizes off the Font Size table \u002F `text-[var(--…)]` for size (−5); everything the\nsame weight, no clear primary (−5); cramped or wrong line-height on body (−3).\n\n**Layout & rhythm (15)** — deduct for: content on bare background, not in cards\n(−6); `px-4`\u002F`px-8`\u002F`mx-4` instead of `px-6`\u002F`mx-6` (−3); same section type\nrepeated in a row (−4); no `space-y-6` rhythm (−3).\n\n**Cards & elevation (15)** — deduct for: 1px borders doing separation work that\ntone+shadow should (−4); shadows over ~8% opacity \u002F visibly heavy (−4); no\ncard\u002Fbackground tone separation (−5).\n\n**States & a11y (20)** — deduct for: missing empty\u002Floading\u002Ferror state on a data\nsurface (−5 each, cap −10); contrast below 4.5:1 body \u002F 3:1 large (−6); touch\ntarget \u003C 44px (−4); no visible focus \u002F `outline:none` (−5); icon-only control\nwithout `aria-label` (−3).\n\n**Motion & interaction (8)** — deduct for: random\u002Fad-hoc fades instead of a named\nseed\u002Fkeyword (−3); motion that delays content or blocks an action (−4); no\n`prefers-reduced-motion` handling on custom motion (−3); scroll-linked\u002Fparallax\n(forbidden, §59) (−5).\n\n**Coherence (12)** — the \"one choice per axis\" laws (VISUAL-CRAFT §C0). Deduct for\neach axis that is *mixed* rather than unified across the file: mixed radius\npersonalities, e.g. sharp panel + pill buttons (−5); two+ competing accent hues used\nfor emphasis (−4); mixed shadow languages \u002F light directions (−3); mixed icon\nfamilies, fill modes, or stroke weights (−3); same radius on a nested element instead\nof `inner = outer − padding` (−2); inconsistent control heights for buttons\u002Finputs\n(−2). This is the category that most predicts \"looks AI-generated\" — weight evidence\nof system-wide consistency, not per-component prettiness.\n\nClamp each category at 0. Sum to a total.\n\n## Output format\n\n```\n## Design Score: 70 \u002F 100   (src\u002Fapp\u002FDashboard.tsx)\n\n████████████████░░░░░░  C-\n\nColor discipline      13\u002F18   ▓▓▓░  #000 headings (l.12,40); orange+blue+green accents (l.28-34)\nHierarchy & typography 15\u002F18  ▓▓▓▓  number\u002Funit 1:1 on hero (l.18)\nLayout & rhythm        11\u002F14  ▓▓▓░  two identical KPI rows (l.22-31)\nCards & elevation       8\u002F12  ▓▓░░  1px borders doing separation (l.22)\nStates & a11y          11\u002F18  ▓▓░░  no empty\u002Floading state; focus ring missing (l.55)\nMotion & interaction    6\u002F8   ▓▓▓░  default fade, not a named seed\nCoherence               6\u002F12  ▓▓░░  sharp cards (l.22) + pill buttons (l.48); 3 accent hues (§C0)\n\n### Fix first (highest score gain)\n1. Add empty + loading states to the orders list       → +7 states (§71)\n2. Unify radius (pick soft 8-12px) + collapse to one accent → +9 coherence+color (§C0, §2)\n3. Drop the 1px borders, use tone + ≤8% shadow         → +4 cards  (§7)\n\nRe-score after: ~92 \u002F 100.\n```\n\nUse letter bands: 90+ A · 80-89 B · 70-79 C · 60-69 D · \u003C60 F.\n\n## Gate mode (use this as the Quality Gate before showing the user UI)\n\nThe Quality Gate (CLAUDE.md \u002F AGENTS.md) is `\u002Fss-score` run as a loop, not a one-off:\n\n1. Score the just-generated UI.\n2. If **\u003C 80**, apply the \"fix first\" list (use `\u002Fss-review` to make the edits), then **re-score**.\n3. Repeat up to ~3×, or until ≥ 80.\n4. Present the UI with the final score and a one-line \"fixed: …\".\n\nThe pass bar is a **floor, not a ceiling** — get to ≥ 80 and stop; don't chase 100. The point\nis that no first-draft, obviously-incoherent UI reaches the user. Especially never ship below\n80 with a rainbow status list, emoji icons, two accents, or missing states — those are the\nexact tells the gate exists to catch.\n\n## Rules\n\n- **Read the file** — score from real evidence (line numbers), never guess.\n- Order the \"fix first\" list by **score gain**, not by severity alone — the goal\n  is the fastest path to a better number.\n- For a directory, print a one-line score per file, then the lowest-scoring file's\n  full breakdown.\n- Don't auto-edit in plain scoring. `\u002Fss-score` measures; `\u002Fss-review` and `\u002Fss-motion` fix.\n  In **Gate mode** (above) you do fix-and-re-score until the floor is met.\n- As a *gate*, ≥ 80 is a floor before showing the user — but don't over-polish: chasing 95→100\n  to delay shipping is worse than shipping a clean 85.\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n",{"name":5,"risk":24,"source":25,"license":15,"date_added":26,"description":7,"source_repo":27,"source_type":28,"license_source":29},"unknown","https:\u002F\u002Fgithub.com\u002Fbitjaru\u002Fstyleseed\u002Ftree\u002Fmain\u002Fengine\u002F.claude\u002Fskills\u002Fss-score",1782864000000,"bitjaru\u002Fstyleseed","community","https:\u002F\u002Fgithub.com\u002Fbitjaru\u002Fstyleseed\u002Fblob\u002Fmain\u002FLICENSE","main","b1e4ffadb4f933bbbcaa03a83f8b9929171ac28b",".agents\u002Fskills\u002Fui-score",0,"https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR","https:\u002F\u002Fgithub.com\u002FHazek-dc","2026-10-22 08:36:44",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill ui-score",{"tool":43,"command":44},"bunx","bunx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill ui-score",{"tool":46,"command":47},"pnpm","pnpm dlx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill ui-score","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fui-score\u002FSKILL.md",true,[],[52,59,66,73,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7DS6GGYRZAYD33PFPS8Z2T3","testing-best-practices","Laravel test design and review. Use when selecting coverage, naming or structuring tests, choosing assertions or test data, isolating dependencies, testing HTTP or security boundaries, improving suite performance, or reviewing test value. Use framework guidance or search-docs for Pest and PHPUnit syntax.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Ftesting-best-practices\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"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},"01M7DS6BC3AW7HTPRHE2TTVKWM","tailwindcss-development","Always invoke when the user's message includes 'tailwind' in any form. Also invoke for: building responsive grid layouts (multi-column card grids, product grids), flex\u002Fgrid page structures (dashboards with sidebars, fixed topbars, mobile-toggle navs), styling UI components (cards, tables, navbars, pricing sections, forms, inputs, badges), adding dark mode variants, fixing spacing or typography, and Tailwind v3\u002Fv4 work. The core use case: writing or fixing Tailwind utility classes in HTML templates (Blade, JSX, Vue). Skip for backend PHP logic, database queries, API routes, JavaScript with no HTML\u002FCSS component, CSS file audits, build tool configuration, and vanilla CSS.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Ftailwindcss-development\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7DS66GE6B11MYJDVC74HXM4","laravel-best-practices","Apply this skill whenever writing, reviewing, or refactoring Laravel PHP code. This includes creating or modifying controllers, models, migrations, form requests, policies, jobs, scheduled commands, service classes, and Eloquent queries. Triggers for N+1 and query performance issues, caching strategies, authorization and security patterns, validation, error handling, queue and job configuration, route definitions, and architectural decisions. Also use for Laravel code reviews and refactoring existing Laravel code to follow best practices. Covers any task involving Laravel backend PHP code patterns.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Flaravel-best-practices\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7DS5ZW717DMS6P1E90AQCKV","infer-conventions","Use this skill to analyze how a Laravel application is actually written and record its conventions as shared rules. Trigger when the user wants to detect, infer, document, or standardize project conventions or coding style, set up or grow `.ai\u002Frules`, resolve mixed or conflicting patterns (e.g. \"are we using Form Requests or inline validation?\"), or onboard agents and teammates to \"how we do things here\". Covers: a systematic sweep of ~49 Laravel convention dimensions (validation, models, architecture, testing, frontend, database, console), open-ended house-pattern discovery, conflict reporting, and recording rules scoped to the right paths via the Boost `record-rule` MCP tool. Only run this skill when the user explicitly asks for it; never start a sweep as part of another task. Do not use for one-off code review, enforcing formatting a linter already handles, or editing `.ai\u002Frules` files by hand.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Finfer-conventions\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7DS5W12RGCVJTFQJ1N0GB8E","inertia-react-development","Develops Inertia.js v2 React client-side applications. Activates when creating React pages, forms, or navigation; using \u003CLink>, \u003CForm>, useForm, or router; working with deferred props, prefetching, or polling; or when user mentions React with Inertia, React pages, React forms, or React navigation.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Finertia-react-development\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7DS5PVDPMPCWSK2RXPDC9BB","deploying-to-cloud","Deploys and manages Laravel applications on Laravel Cloud using the `cloud` CLI. Use when the user wants to deploy an app, ship to Cloud, create or manage applications, environments, databases, caches, object storage, queues, domains, instances, background processes, secrets, compute, scheduled tasks, or Laravel Cloud infrastructure; or check billing, usage, or spend. Triggers on deployment, shipping, Cloud management, environment setup, database provisioning, billing or usage queries, the `cloud` CLI, and Laravel Cloud deployment troubleshooting.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Fdeploying-to-cloud\u002FSKILL.md",[],[]]