[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DH4B0TX5XSCYZNA0R4WCW9":3,"skill-same:01M7DH4B0TX5XSCYZNA0R4WCW9":63},{"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":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":48,"install":49,"resources":62},"01M7DH4B0TX5XSCYZNA0R4WCW9","ckw-design",null,"Frontend design entry point: direction, design system, visual philosophy. Use whenever building or touching the look of any web UI (components, pages, dashboards, React\u002FVue\u002FHTML-CSS) or when the user says \"make this look better\", \"fix the spacing\u002Flayout\", or mentions styling, color, type, or polish.","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\u002Fckw-design\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ckw-design\ndescription: \"Frontend design entry point: direction, design system, visual philosophy. Use whenever building or touching the look of any web UI (components, pages, dashboards, React\u002FVue\u002FHTML-CSS) or when the user says \\\"make this look better\\\", \\\"fix the spacing\u002Flayout\\\", or mentions styling, color, type, or polish.\"\nrisk: safe\nsource: community\nsource_type: community\nsource_repo: connerkward\u002Fckw-design-skill\ndate_added: \"2026-06-16\"\nauthor: Conner K Ward\nlicense: MIT\ntags:\n  - design\n  - frontend\n  - ui\n  - css\n  - typography\n  - responsive\ntools:\n  - claude-code\n  - antigravity\n  - cursor\n  - gemini-cli\n  - codex-cli\n---\n## When to Use\n\nUse whenever building or styling web UIs — components, pages, dashboards, landing pages, React\u002FVue\u002FHTML-CSS layouts — or whenever the user asks to make something \"look better\u002Fnicer\", fix spacing\u002Flayout, or mentions styling, color, typography, fonts, responsive design, polish, or aesthetics, even without the word \"design\".\n\n_Source: [connerkward\u002Fckw-design-skill](https:\u002F\u002Fgithub.com\u002Fconnerkward\u002Fckw-design-skill) (MIT)._\n\n# Design (entry)\n\nUse this skill when the user asks to build or style web UIs: components, pages, dashboards, landing pages, React\u002FVue\u002FHTML-CSS layouts, or any frontend interface. Goal: distinctive, production-grade output that avoids generic AI aesthetics.\n\n**Before reporting any design \"done\": render it and have a *separate* judge critique the image** (not the code, not self-grading) — see design-spatial §1. Blind generation can't see its own collisions; this applies to all design output, not just spatial work.\n\n> **MANDATORY HORIZONTAL-OVERFLOW GATE — runs before ANY web UI is \"done\".**\n> Measure `document.documentElement.scrollWidth - document.documentElement.clientWidth`\n> at a **narrow width (~390px and ~1024px), this turn**, and confirm it's `0`. This\n> bug is invisible at desktop width and re-appears every time a row (header, nav,\n> toolbar) gains an item, so it ships repeatedly. Default to `flex-wrap:wrap` on\n> header\u002Ftoolbar rows + `body{overflow-x:clip}`, and **re-measure after adding any\n> element to a horizontal row.** Full procedure + recurrence cases: design-spatial §4.\n> If you haven't measured narrow, you are not done — don't claim it.\n\n## Sub-skills (load when relevant)\n\n- **design-thinking** — Load for every design task. Defines purpose, tone, domain, color world, review bar, and cross-domain lens (cinema, architecture, marketing, UX, automotive, industrial design). See [design-thinking\u002FSKILL.md](https:\u002F\u002Fgithub.com\u002Fconnerkward\u002Fckw-design-skill\u002Fblob\u002Fmain\u002Fdesign-thinking\u002FSKILL.md).\n- **design-system** — Load when implementing: tokens, typography, motion, color semantics, backgrounds. Use when building components, pages, or design systems. See [design-system\u002FSKILL.md](https:\u002F\u002Fgithub.com\u002Fconnerkward\u002Fckw-design-skill\u002Fblob\u002Fmain\u002Fdesign-system\u002FSKILL.md).\n- **design-spatial** — Load when composing layout: explicit grid + 8-point spacing constraints, visual-weight\u002Fbalance\u002Falignment, and a render-then-critique vision loop. The fix for \"spatial understanding is off\" — generated layout that's centered mush, misaligned, or breaks at some widths. See [design-spatial\u002FSKILL.md](https:\u002F\u002Fgithub.com\u002Fconnerkward\u002Fckw-design-skill\u002Fblob\u002Fmain\u002Fdeterministic-design\u002Fdesign-spatial\u002FSKILL.md).\n- **design-ux** — Load when auditing USABILITY (not just looks): a UI that \"feels off\"\u002F\"sucks to use\", is hard to learn, needs an instruction wall, or any interactive tool\u002Feditor\u002Fapp before shipping. Scores the rendered UI against Nielsen's 10 + interaction heuristics via a SEPARATE fresh-eyes judge → prioritized fix list. Usability ≠ aesthetics. See [design-ux\u002FSKILL.md](https:\u002F\u002Fgithub.com\u002Fconnerkward\u002Fckw-design-skill\u002Fblob\u002Fmain\u002Fdeterministic-design\u002Fdesign-ux\u002FSKILL.md).\n- **design-philosophy** — Load for high-concept work, campaigns, or when the user asks for a visual philosophy, manifesto, or unmistakable art-like aesthetic. See [design-philosophy\u002FSKILL.md](https:\u002F\u002Fgithub.com\u002Fconnerkward\u002Fckw-design-skill\u002Fblob\u002Fmain\u002Fdesign-philosophy\u002FSKILL.md).\n\n## Visual assets — generate or source\n\nWhen design-thinking identifies a need for visual assets (logos, icons, hero images, textures, backgrounds):\n\n1. **Generate** → use an image-generation model or API for synthetic\u002Fbranded assets.\n2. **Source a real\u002Farchival one** → free stock or archival image search, often cheaper and more authentic than generating.\n3. Use design-thinking output (tone, domain, color world) to craft prompts \u002F queries.\n4. Evaluate against the design philosophy, refine, integrate into the build.\n\n## LLM-assisted work — always annotate model + cost\n\nWhen design work involves running an LLM (generative assets, VLM analysis, layout critique, prompt generation, etc.):\n\n- **Before running:** state which model will be used and the estimated cost (e.g., \"gpt-4o-mini · ~$0.005\u002Fimage\" or \"FLUX v1 · ~$0.006 per gen\").\n- **After results:** annotate the output with the model used, actual cost if different from estimate, and any key params (seed, prompt, settings). Cost goes *visible to the user* (in the message, contact sheet header, or asset caption), not buried in logs.\n- **Why:** the user is deciding whether the cost-to-quality trade-off is worth it. Unlabeled or hidden costs hide the most important lever. This rule mirrors `media-attribution-rule` for generative assets and extends it to any LLM operation in the design workflow.\n\n**Examples:**\n- \"Running gpt-4o-mini layout critique on 8 designs · est. ~$0.04 total\" (before).\n- Contact sheet header: \"FLUX v1 · $0.48 total (6 gen × $0.08)\" (after).\n- Asset caption: \"hero_banner_flux-dev_seed3891.jpg\" (seeds enable reproducibility).\n- Uncertainty slider result: \"VLM triage on 46,978 images · gpt-4o-mini · ~$9.40\" (before); \"✓ Completed: 12,447 images classified · gpt-4o-mini · $7.62\" (after).\n\n## Algorithm \u002F model explainers — show the equation, annotate the terms\n\nWhenever a UI surfaces an algorithm or model to the user (an \"ⓘ how this works\"\npanel, a model breakdown, a methods note), **include the actual equation, typeset,\nwith its key terms annotated** — don't settle for prose. A scorer described only in\nwords (\"ranks by how much of the picked color is present\") is unfalsifiable hand-\nwaving; the formula `score = Σ fracᵢ · max(0, 1 − ΔEᵢ\u002Fτ)` with each term labelled\ntells the user *exactly* what the knob does and builds trust that there's real math\nunder the hood.\n\n**How to apply:**\n- Render one clean, central equation per algorithm — the \"sexy\" core, not every\n  detail. Use proper notation: σ for sigmoid, Σ for sums, ‖·‖ for norms,\n  superscripts, ΔE, ∇²; a monospace\u002Fserif-math block set off from the prose.\n- **Annotate every symbol** immediately below: what `e_x`, `w`, `τ`, `Q` each are,\n  in one line each. An unlabelled equation is decoration; a labelled one is a spec.\n- Keep it dependency-light — styled HTML\u002FUnicode math is fine and works offline; only\n  reach for KaTeX\u002FMathJax if the expressions genuinely need it.\n- State the **decision rule** alongside the score (e.g. \"personal if P ≥ 0.55\").\n- This composes with the model+cost annotation above: the equation says *what* it\n  computes, the model\u002Fcost line says *what ran it and for how much*.\n\n**Example (a logistic head):**\n> P(personal │ x) = σ(**w**·**e**ₓ + b),  σ(z) = 1 \u002F (1 + e⁻ᶻ)\n> • **e**ₓ — the image's 768-d embedding · **w**, b — weights learned from your labels\n> · decision: personal if P ≥ 0.55, reference if P ≤ 0.40.\n\n## Select-all always has a deselect — no dead-end selections\n\nAny **\"Select all\"** affordance MUST be paired with a way to **clear the selection** —\npreferably the *same button*, label-flipped when everything is already selected\n(\"Select all\" ⇄ \"Deselect all\"). A select-all with no inverse is a trap: the user\nover-selects (or hits it by reflex), then has to un-click items one by one, or reload\nthe page, to get back. The cost is silent — it only bites *after* they've committed to\nthe wrong set.\n\n**How to apply:**\n- **Toggle the same button** (simplest, fewest controls): when all visible items are\n  selected, the button reads \"Deselect all\" and clears; otherwise \"Select all\". One\n  control, no dead end.\n- Or a **separate Clear\u002FDeselect** shown whenever the selection is non-empty.\n- The deselect must reach the **same scope** the select-all did (all *shown*, all\n  *filtered*, all *on this page*) — don't let \"Select all\" grab 500 but \"Clear\" only\n  drop the 50 on screen.\n- This generalizes: any reversible bulk toggle (select, expand-all, mute-all,\n  check-all) needs its inverse one tap away. Symmetry of action — see\n  restraint-rule (don't strand the user mid-task).\n\n## Limitations\n\n- This skill improves visual direction and review discipline, but it does not replace rendering the actual UI and checking it in target browsers or devices.\n- Some recommendations assume access to screenshots, browser automation, or vision review; when those are unavailable, treat the guidance as a design checklist rather than proof.\n- Brand, legal, accessibility, and localization constraints from the product owner override the taste rules here.\n","## When to Use\n\nUse whenever building or styling web UIs — components, pages, dashboards, landing pages, React\u002FVue\u002FHTML-CSS layouts — or whenever the user asks to make something \"look better\u002Fnicer\", fix spacing\u002Flayout, or mentions styling, color, typography, fonts, responsive design, polish, or aesthetics, even without the word \"design\".\n\n_Source: [connerkward\u002Fckw-design-skill](https:\u002F\u002Fgithub.com\u002Fconnerkward\u002Fckw-design-skill) (MIT)._\n\n# Design (entry)\n\nUse this skill when the user asks to build or style web UIs: components, pages, dashboards, landing pages, React\u002FVue\u002FHTML-CSS layouts, or any frontend interface. Goal: distinctive, production-grade output that avoids generic AI aesthetics.\n\n**Before reporting any design \"done\": render it and have a *separate* judge critique the image** (not the code, not self-grading) — see design-spatial §1. Blind generation can't see its own collisions; this applies to all design output, not just spatial work.\n\n> **MANDATORY HORIZONTAL-OVERFLOW GATE — runs before ANY web UI is \"done\".**\n> Measure `document.documentElement.scrollWidth - document.documentElement.clientWidth`\n> at a **narrow width (~390px and ~1024px), this turn**, and confirm it's `0`. This\n> bug is invisible at desktop width and re-appears every time a row (header, nav,\n> toolbar) gains an item, so it ships repeatedly. Default to `flex-wrap:wrap` on\n> header\u002Ftoolbar rows + `body{overflow-x:clip}`, and **re-measure after adding any\n> element to a horizontal row.** Full procedure + recurrence cases: design-spatial §4.\n> If you haven't measured narrow, you are not done — don't claim it.\n\n## Sub-skills (load when relevant)\n\n- **design-thinking** — Load for every design task. Defines purpose, tone, domain, color world, review bar, and cross-domain lens (cinema, architecture, marketing, UX, automotive, industrial design). See [design-thinking\u002FSKILL.md](https:\u002F\u002Fgithub.com\u002Fconnerkward\u002Fckw-design-skill\u002Fblob\u002Fmain\u002Fdesign-thinking\u002FSKILL.md).\n- **design-system** — Load when implementing: tokens, typography, motion, color semantics, backgrounds. Use when building components, pages, or design systems. See [design-system\u002FSKILL.md](https:\u002F\u002Fgithub.com\u002Fconnerkward\u002Fckw-design-skill\u002Fblob\u002Fmain\u002Fdesign-system\u002FSKILL.md).\n- **design-spatial** — Load when composing layout: explicit grid + 8-point spacing constraints, visual-weight\u002Fbalance\u002Falignment, and a render-then-critique vision loop. The fix for \"spatial understanding is off\" — generated layout that's centered mush, misaligned, or breaks at some widths. See [design-spatial\u002FSKILL.md](https:\u002F\u002Fgithub.com\u002Fconnerkward\u002Fckw-design-skill\u002Fblob\u002Fmain\u002Fdeterministic-design\u002Fdesign-spatial\u002FSKILL.md).\n- **design-ux** — Load when auditing USABILITY (not just looks): a UI that \"feels off\"\u002F\"sucks to use\", is hard to learn, needs an instruction wall, or any interactive tool\u002Feditor\u002Fapp before shipping. Scores the rendered UI against Nielsen's 10 + interaction heuristics via a SEPARATE fresh-eyes judge → prioritized fix list. Usability ≠ aesthetics. See [design-ux\u002FSKILL.md](https:\u002F\u002Fgithub.com\u002Fconnerkward\u002Fckw-design-skill\u002Fblob\u002Fmain\u002Fdeterministic-design\u002Fdesign-ux\u002FSKILL.md).\n- **design-philosophy** — Load for high-concept work, campaigns, or when the user asks for a visual philosophy, manifesto, or unmistakable art-like aesthetic. See [design-philosophy\u002FSKILL.md](https:\u002F\u002Fgithub.com\u002Fconnerkward\u002Fckw-design-skill\u002Fblob\u002Fmain\u002Fdesign-philosophy\u002FSKILL.md).\n\n## Visual assets — generate or source\n\nWhen design-thinking identifies a need for visual assets (logos, icons, hero images, textures, backgrounds):\n\n1. **Generate** → use an image-generation model or API for synthetic\u002Fbranded assets.\n2. **Source a real\u002Farchival one** → free stock or archival image search, often cheaper and more authentic than generating.\n3. Use design-thinking output (tone, domain, color world) to craft prompts \u002F queries.\n4. Evaluate against the design philosophy, refine, integrate into the build.\n\n## LLM-assisted work — always annotate model + cost\n\nWhen design work involves running an LLM (generative assets, VLM analysis, layout critique, prompt generation, etc.):\n\n- **Before running:** state which model will be used and the estimated cost (e.g., \"gpt-4o-mini · ~$0.005\u002Fimage\" or \"FLUX v1 · ~$0.006 per gen\").\n- **After results:** annotate the output with the model used, actual cost if different from estimate, and any key params (seed, prompt, settings). Cost goes *visible to the user* (in the message, contact sheet header, or asset caption), not buried in logs.\n- **Why:** the user is deciding whether the cost-to-quality trade-off is worth it. Unlabeled or hidden costs hide the most important lever. This rule mirrors `media-attribution-rule` for generative assets and extends it to any LLM operation in the design workflow.\n\n**Examples:**\n- \"Running gpt-4o-mini layout critique on 8 designs · est. ~$0.04 total\" (before).\n- Contact sheet header: \"FLUX v1 · $0.48 total (6 gen × $0.08)\" (after).\n- Asset caption: \"hero_banner_flux-dev_seed3891.jpg\" (seeds enable reproducibility).\n- Uncertainty slider result: \"VLM triage on 46,978 images · gpt-4o-mini · ~$9.40\" (before); \"✓ Completed: 12,447 images classified · gpt-4o-mini · $7.62\" (after).\n\n## Algorithm \u002F model explainers — show the equation, annotate the terms\n\nWhenever a UI surfaces an algorithm or model to the user (an \"ⓘ how this works\"\npanel, a model breakdown, a methods note), **include the actual equation, typeset,\nwith its key terms annotated** — don't settle for prose. A scorer described only in\nwords (\"ranks by how much of the picked color is present\") is unfalsifiable hand-\nwaving; the formula `score = Σ fracᵢ · max(0, 1 − ΔEᵢ\u002Fτ)` with each term labelled\ntells the user *exactly* what the knob does and builds trust that there's real math\nunder the hood.\n\n**How to apply:**\n- Render one clean, central equation per algorithm — the \"sexy\" core, not every\n  detail. Use proper notation: σ for sigmoid, Σ for sums, ‖·‖ for norms,\n  superscripts, ΔE, ∇²; a monospace\u002Fserif-math block set off from the prose.\n- **Annotate every symbol** immediately below: what `e_x`, `w`, `τ`, `Q` each are,\n  in one line each. An unlabelled equation is decoration; a labelled one is a spec.\n- Keep it dependency-light — styled HTML\u002FUnicode math is fine and works offline; only\n  reach for KaTeX\u002FMathJax if the expressions genuinely need it.\n- State the **decision rule** alongside the score (e.g. \"personal if P ≥ 0.55\").\n- This composes with the model+cost annotation above: the equation says *what* it\n  computes, the model\u002Fcost line says *what ran it and for how much*.\n\n**Example (a logistic head):**\n> P(personal │ x) = σ(**w**·**e**ₓ + b),  σ(z) = 1 \u002F (1 + e⁻ᶻ)\n> • **e**ₓ — the image's 768-d embedding · **w**, b — weights learned from your labels\n> · decision: personal if P ≥ 0.55, reference if P ≤ 0.40.\n\n## Select-all always has a deselect — no dead-end selections\n\nAny **\"Select all\"** affordance MUST be paired with a way to **clear the selection** —\npreferably the *same button*, label-flipped when everything is already selected\n(\"Select all\" ⇄ \"Deselect all\"). A select-all with no inverse is a trap: the user\nover-selects (or hits it by reflex), then has to un-click items one by one, or reload\nthe page, to get back. The cost is silent — it only bites *after* they've committed to\nthe wrong set.\n\n**How to apply:**\n- **Toggle the same button** (simplest, fewest controls): when all visible items are\n  selected, the button reads \"Deselect all\" and clears; otherwise \"Select all\". One\n  control, no dead end.\n- Or a **separate Clear\u002FDeselect** shown whenever the selection is non-empty.\n- The deselect must reach the **same scope** the select-all did (all *shown*, all\n  *filtered*, all *on this page*) — don't let \"Select all\" grab 500 but \"Clear\" only\n  drop the 50 on screen.\n- This generalizes: any reversible bulk toggle (select, expand-all, mute-all,\n  check-all) needs its inverse one tap away. Symmetry of action — see\n  restraint-rule (don't strand the user mid-task).\n\n## Limitations\n\n- This skill improves visual direction and review discipline, but it does not replace rendering the actual UI and checking it in target browsers or devices.\n- Some recommendations assume access to screenshots, browser automation, or vision review; when those are unavailable, treat the guidance as a design checklist rather than proof.\n- Brand, legal, accessibility, and localization constraints from the product owner override the taste rules here.\n",{"name":5,"risk":24,"tags":25,"tools":32,"author":38,"source":39,"license":15,"date_added":40,"description":7,"source_repo":41,"source_type":39},"safe",[26,27,28,29,30,31],"design","frontend","ui","css","typography","responsive",[33,34,35,36,37],"claude-code","antigravity","cursor","gemini-cli","codex-cli","Conner K Ward","community","2026-06-16","connerkward\u002Fckw-design-skill","main","b1e4ffadb4f933bbbcaa03a83f8b9929171ac28b",".agents\u002Fskills\u002Fckw-design",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":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill ckw-design",{"tool":55,"command":56},"bunx","bunx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill ckw-design",{"tool":58,"command":59},"pnpm","pnpm dlx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill ckw-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fckw-design\u002FSKILL.md",true,[],[64,71,78,85,92,99],{"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},"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":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"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":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"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":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"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":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"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":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"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",[],[]]