[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DRGD23ATN2VKAEQY1JB732":3,"skill-same:01M7DRGD23ATN2VKAEQY1JB732":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},"01M7DRGD23ATN2VKAEQY1JB732","ui-update",null,"Update StyleSeed engine in your project — analyzes what's outdated and updates safely","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-update\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ui-update\ndescription: Update StyleSeed engine in your project — analyzes what's outdated and updates safely\nrisk: unknown\nsource: https:\u002F\u002Fgithub.com\u002Fbitjaru\u002Fstyleseed\u002Ftree\u002Fmain\u002Fengine\u002F.claude\u002Fskills\u002Fss-update\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# StyleSeed Update Assistant\n## When to Use\n\nUse this skill when you need update StyleSeed engine in your project — analyzes what's outdated and updates safely.\n\n\n## When NOT to use\n\n- For first-time setup → use `\u002Fss-setup`\n- For just one new component or skin — copy that file manually\n- For projects that have heavily diverged from upstream — manual diff review first\n- For updating user code\u002Fcomponents — this updates engine files only, not your custom UI\n\nAutomatically detect and update StyleSeed files in the current project.\n\n## Reassure the user first\n\nUpdating is **safe and reversible**. Updates are additive — new rules,\ncomponents, skins, and skills get added; your `theme.css`, your components, and\nyour app code are never overwritten, and design rules only ever get added (never\nchanged in a breaking way). A big version jump looks like a lot changed, but\nit's almost all additions. **Do NOT warn the user that the build will break**\nunless you actually find a changed component\u002Fimport API. Tell them: commit first,\ncopy the new rules + skills, run a build, and `git reset --hard` if anything is\noff — they can't permanently break their project.\n\n## Instructions\n\n### Step 1: Detect Current Setup\n\nScan the project to find where StyleSeed files are:\n\n```bash\n# Find DESIGN-LANGUAGE.md\nfind . -name \"DESIGN-LANGUAGE.md\" -not -path \"*\u002Fnode_modules\u002F*\"\n\n# Find CLAUDE.md\nfind . -name \"CLAUDE.md\" -not -path \"*\u002Fnode_modules\u002F*\"\n\n# Find skills (ss-* is current; ui-*\u002Fux-* are legacy names to migrate from)\nfind . -path \"*\u002F.claude\u002Fskills\u002Fss-*\" -o -path \"*\u002F.claude\u002Fskills\u002Fui-*\" -o -path \"*\u002F.claude\u002Fskills\u002Fux-*\" | head -20\n\n# Find theme.css\nfind . -name \"theme.css\" -not -path \"*\u002Fnode_modules\u002F*\"\n\n# Find .cursorrules\nfind . -name \".cursorrules\"\n```\n\nReport what was found and where.\n\n### Step 2: Check StyleSeed Version\n\n**Fast check first** — compare the local version to the published one without cloning:\n```bash\n# local marker (may be absent on older installs)\ncat engine\u002FVERSION 2>\u002Fdev\u002Fnull || cat VERSION 2>\u002Fdev\u002Fnull || echo \"unknown\"\n# latest published version + what's new\ncurl -s https:\u002F\u002Fstyleseed-demo.vercel.app\u002Fversion.json\n```\nIf the local version already matches `version.json`'s `version`, tell the user they're\nup to date and stop. Otherwise report `whatsNew` and continue.\n\nThen clone\u002Fpull to actually diff the files:\n```bash\nif [ -d \"\u002Ftmp\u002Fstyleseed\" ]; then\n  cd \u002Ftmp\u002Fstyleseed && git pull\nelse\n  git clone https:\u002F\u002Fgithub.com\u002Fbitjaru\u002Fstyleseed.git \u002Ftmp\u002Fstyleseed\nfi\n```\n\nCompare:\n- `engine\u002FVERSION` (or `version.json`) vs the local copy — the source of truth\n- DESIGN-LANGUAGE.md rule count + Table of Contents\n- Skills present in `.claude\u002Fskills\u002F` vs upstream (don't hardcode a count — list the diff)\n- Whether `CLAUDE.md`, `AGENTS.md`, and `.cursorrules` exist (ship all three)\n- New engine docs (VISUAL-CRAFT.md, APP-PLAYBOOKS.md, PAGE-TYPES.md)\n\n### Step 3: Report & Ask\n\nShow the user what needs updating:\n\n```\nStyleSeed Update Report:\n\nCurrent state:\n- DESIGN-LANGUAGE.md: [location] — [old\u002Fcurrent version indicator]\n- Skills: [count] found (latest: 12)\n- Golden Rules: [yes\u002Fno]\n- .cursorrules: [yes\u002Fno]\n\nRecommended updates:\n1. ✅ [safe] Update skills (X → 12)\n2. ✅ [safe] Add .cursorrules\n3. ⚠️ [review] Update DESIGN-LANGUAGE.md ([old line count] → [new line count])\n4. ⚠️ [merge] Add Golden Rules to CLAUDE.md (won't overwrite existing content)\n\nShall I proceed? (I'll ask before each ⚠️ item)\n```\n\n### Step 4: Execute Updates\n\nFor each update, in order:\n\n**Always safe (do without asking):**\n- Copy skills: `cp -r \u002Ftmp\u002Fstyleseed\u002Fengine\u002F.claude\u002Fskills\u002F .claude\u002Fskills\u002F`\n- Copy .cursorrules (if not exists): `cp \u002Ftmp\u002Fstyleseed\u002Fengine\u002F.cursorrules .cursorrules`\n\n**Ask before doing:**\n\nFor DESIGN-LANGUAGE.md:\n- Show diff summary: how many new rules, what sections added\n- Ask: \"Update DESIGN-LANGUAGE.md? (Y\u002FN)\"\n- If yes: copy to the detected location\n\nFor CLAUDE.md (Golden Rules):\n- Check if Golden Rules section already exists\n- If not: ask \"Add Golden Rules section to your CLAUDE.md? This adds 10 lines at the top. Your existing content stays untouched.\"\n- If yes: insert Golden Rules after the first heading\n\n**Never touch:**\n- theme.css — say \"Your theme.css (skin) is untouched.\"\n- components\u002F — say \"Your components are untouched. Run `\u002Fss-lint` to check compliance.\"\n\n### Step 5: Summary\n\n```\nUpdate complete!\n\n✅ Skills: 12 (added X new)\n✅ .cursorrules: added\n✅ DESIGN-LANGUAGE.md: updated to latest\n✅ Golden Rules: added to CLAUDE.md\n\nNot touched:\n- theme.css (your skin)\n- components\u002F (your code)\n\nNext: run \u002Fss-lint on your pages to check for rule violations.\n```\n\n## Important\n\n- NEVER overwrite theme.css\n- NEVER overwrite a project-specific CLAUDE.md — only MERGE the Golden Rules section\n- NEVER overwrite components without explicit user approval\n- Always show what will change before changing it\n- If unsure, ask the user\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","# StyleSeed Update Assistant\n## When to Use\n\nUse this skill when you need update StyleSeed engine in your project — analyzes what's outdated and updates safely.\n\n\n## When NOT to use\n\n- For first-time setup → use `\u002Fss-setup`\n- For just one new component or skin — copy that file manually\n- For projects that have heavily diverged from upstream — manual diff review first\n- For updating user code\u002Fcomponents — this updates engine files only, not your custom UI\n\nAutomatically detect and update StyleSeed files in the current project.\n\n## Reassure the user first\n\nUpdating is **safe and reversible**. Updates are additive — new rules,\ncomponents, skins, and skills get added; your `theme.css`, your components, and\nyour app code are never overwritten, and design rules only ever get added (never\nchanged in a breaking way). A big version jump looks like a lot changed, but\nit's almost all additions. **Do NOT warn the user that the build will break**\nunless you actually find a changed component\u002Fimport API. Tell them: commit first,\ncopy the new rules + skills, run a build, and `git reset --hard` if anything is\noff — they can't permanently break their project.\n\n## Instructions\n\n### Step 1: Detect Current Setup\n\nScan the project to find where StyleSeed files are:\n\n```bash\n# Find DESIGN-LANGUAGE.md\nfind . -name \"DESIGN-LANGUAGE.md\" -not -path \"*\u002Fnode_modules\u002F*\"\n\n# Find CLAUDE.md\nfind . -name \"CLAUDE.md\" -not -path \"*\u002Fnode_modules\u002F*\"\n\n# Find skills (ss-* is current; ui-*\u002Fux-* are legacy names to migrate from)\nfind . -path \"*\u002F.claude\u002Fskills\u002Fss-*\" -o -path \"*\u002F.claude\u002Fskills\u002Fui-*\" -o -path \"*\u002F.claude\u002Fskills\u002Fux-*\" | head -20\n\n# Find theme.css\nfind . -name \"theme.css\" -not -path \"*\u002Fnode_modules\u002F*\"\n\n# Find .cursorrules\nfind . -name \".cursorrules\"\n```\n\nReport what was found and where.\n\n### Step 2: Check StyleSeed Version\n\n**Fast check first** — compare the local version to the published one without cloning:\n```bash\n# local marker (may be absent on older installs)\ncat engine\u002FVERSION 2>\u002Fdev\u002Fnull || cat VERSION 2>\u002Fdev\u002Fnull || echo \"unknown\"\n# latest published version + what's new\ncurl -s https:\u002F\u002Fstyleseed-demo.vercel.app\u002Fversion.json\n```\nIf the local version already matches `version.json`'s `version`, tell the user they're\nup to date and stop. Otherwise report `whatsNew` and continue.\n\nThen clone\u002Fpull to actually diff the files:\n```bash\nif [ -d \"\u002Ftmp\u002Fstyleseed\" ]; then\n  cd \u002Ftmp\u002Fstyleseed && git pull\nelse\n  git clone https:\u002F\u002Fgithub.com\u002Fbitjaru\u002Fstyleseed.git \u002Ftmp\u002Fstyleseed\nfi\n```\n\nCompare:\n- `engine\u002FVERSION` (or `version.json`) vs the local copy — the source of truth\n- DESIGN-LANGUAGE.md rule count + Table of Contents\n- Skills present in `.claude\u002Fskills\u002F` vs upstream (don't hardcode a count — list the diff)\n- Whether `CLAUDE.md`, `AGENTS.md`, and `.cursorrules` exist (ship all three)\n- New engine docs (VISUAL-CRAFT.md, APP-PLAYBOOKS.md, PAGE-TYPES.md)\n\n### Step 3: Report & Ask\n\nShow the user what needs updating:\n\n```\nStyleSeed Update Report:\n\nCurrent state:\n- DESIGN-LANGUAGE.md: [location] — [old\u002Fcurrent version indicator]\n- Skills: [count] found (latest: 12)\n- Golden Rules: [yes\u002Fno]\n- .cursorrules: [yes\u002Fno]\n\nRecommended updates:\n1. ✅ [safe] Update skills (X → 12)\n2. ✅ [safe] Add .cursorrules\n3. ⚠️ [review] Update DESIGN-LANGUAGE.md ([old line count] → [new line count])\n4. ⚠️ [merge] Add Golden Rules to CLAUDE.md (won't overwrite existing content)\n\nShall I proceed? (I'll ask before each ⚠️ item)\n```\n\n### Step 4: Execute Updates\n\nFor each update, in order:\n\n**Always safe (do without asking):**\n- Copy skills: `cp -r \u002Ftmp\u002Fstyleseed\u002Fengine\u002F.claude\u002Fskills\u002F .claude\u002Fskills\u002F`\n- Copy .cursorrules (if not exists): `cp \u002Ftmp\u002Fstyleseed\u002Fengine\u002F.cursorrules .cursorrules`\n\n**Ask before doing:**\n\nFor DESIGN-LANGUAGE.md:\n- Show diff summary: how many new rules, what sections added\n- Ask: \"Update DESIGN-LANGUAGE.md? (Y\u002FN)\"\n- If yes: copy to the detected location\n\nFor CLAUDE.md (Golden Rules):\n- Check if Golden Rules section already exists\n- If not: ask \"Add Golden Rules section to your CLAUDE.md? This adds 10 lines at the top. Your existing content stays untouched.\"\n- If yes: insert Golden Rules after the first heading\n\n**Never touch:**\n- theme.css — say \"Your theme.css (skin) is untouched.\"\n- components\u002F — say \"Your components are untouched. Run `\u002Fss-lint` to check compliance.\"\n\n### Step 5: Summary\n\n```\nUpdate complete!\n\n✅ Skills: 12 (added X new)\n✅ .cursorrules: added\n✅ DESIGN-LANGUAGE.md: updated to latest\n✅ Golden Rules: added to CLAUDE.md\n\nNot touched:\n- theme.css (your skin)\n- components\u002F (your code)\n\nNext: run \u002Fss-lint on your pages to check for rule violations.\n```\n\n## Important\n\n- NEVER overwrite theme.css\n- NEVER overwrite a project-specific CLAUDE.md — only MERGE the Golden Rules section\n- NEVER overwrite components without explicit user approval\n- Always show what will change before changing it\n- If unsure, ask the user\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-update",1782864000000,"bitjaru\u002Fstyleseed","community","https:\u002F\u002Fgithub.com\u002Fbitjaru\u002Fstyleseed\u002Fblob\u002Fmain\u002FLICENSE","main","b1e4ffadb4f933bbbcaa03a83f8b9929171ac28b",".agents\u002Fskills\u002Fui-update",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-update",{"tool":43,"command":44},"bunx","bunx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill ui-update",{"tool":46,"command":47},"pnpm","pnpm dlx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill ui-update","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fui-update\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",[],[]]