[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FDNQNBTPCTCEW1CC8SAKMT":3,"skill-same:01M7FDNQNBTPCTCEW1CC8SAKMT":47},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7FDNQNBTPCTCEW1CC8SAKMT","tailwindcss-development",null,"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.","Dommmin\u002Fsh-site","Dommmin","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F93583747?v=4","01M7CDE9G4BYYW0GJCBBYG5N7T","Dominik","01M7FDFT9DG7ZC37NZX6BXMZ5H",0,"MIT","https:\u002F\u002Fgithub.com\u002FDommmin\u002Fsh-site\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Ftailwindcss-development\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: tailwindcss-development\ndescription: \"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.\"\nlicense: MIT\nmetadata:\n  author: laravel\n---\n\n# Tailwind CSS Development\n\n## Documentation\n\nUse `search-docs` for detailed Tailwind CSS v4 patterns and documentation.\n\n## Basic Usage\n\n- Use Tailwind CSS classes to style HTML. Check and follow existing Tailwind conventions in the project before introducing new patterns.\n- Offer to extract repeated patterns into components that match the project's conventions (e.g., Blade, JSX, Vue).\n- Consider class placement, order, priority, and defaults. Remove redundant classes, add classes to parent or child elements carefully to reduce repetition, and group elements logically.\n\n## Tailwind CSS v4 Specifics\n\n- Always use Tailwind CSS v4 and avoid deprecated utilities.\n- `corePlugins` is not supported in Tailwind v4.\n\n### CSS-First Configuration\n\nIn Tailwind v4, configuration is CSS-first using the `@theme` directive — no separate `tailwind.config.js` file is needed:\n\n\u003C!-- CSS-First Config -->\n```css\n@theme {\n  --color-brand: oklch(0.72 0.11 178);\n}\n```\n\n### Import Syntax\n\nIn Tailwind v4, import Tailwind with a regular CSS `@import` statement instead of the `@tailwind` directives used in v3:\n\n\u003C!-- v4 Import Syntax -->\n```diff\n- @tailwind base;\n- @tailwind components;\n- @tailwind utilities;\n+ @import \"tailwindcss\";\n```\n\n### Replaced Utilities\n\nTailwind v4 removed deprecated utilities. Use the replacements shown below. For opacity, drop the `*-opacity-*` class and append the value as a modifier on the existing color: `bg-blue-500 bg-opacity-50` becomes `bg-blue-500\u002F50`, `text-white text-opacity-75` becomes `text-white\u002F75`.\n\n| Deprecated | Replacement |\n|------------|-------------|\n| bg-opacity-* | bg-{color}\u002F* |\n| text-opacity-* | text-{color}\u002F* |\n| border-opacity-* | border-{color}\u002F* |\n| divide-opacity-* | divide-{color}\u002F* |\n| ring-opacity-* | ring-{color}\u002F* |\n| placeholder-opacity-* | placeholder-{color}\u002F* |\n| flex-shrink-* | shrink-* |\n| flex-grow-* | grow-* |\n| overflow-ellipsis | text-ellipsis |\n| decoration-slice | box-decoration-slice |\n| decoration-clone | box-decoration-clone |\n\n## Spacing\n\nUse `gap` utilities instead of margins for spacing between siblings:\n\n\u003C!-- Gap Utilities -->\n```html\n\u003Cdiv class=\"flex gap-8\">\n    \u003Cdiv>Item 1\u003C\u002Fdiv>\n    \u003Cdiv>Item 2\u003C\u002Fdiv>\n\u003C\u002Fdiv>\n```\n\n## Dark Mode\n\nIf existing pages and components support dark mode, new pages and components must support it the same way, typically using the `dark:` variant:\n\n\u003C!-- Dark Mode -->\n```html\n\u003Cdiv class=\"bg-white dark:bg-gray-900 text-gray-900 dark:text-white\">\n    Content adapts to color scheme\n\u003C\u002Fdiv>\n```\n\n## Common Pitfalls\n\n- Using deprecated v3 utilities (bg-opacity-*, flex-shrink-*, etc.)\n- Using `@tailwind` directives instead of `@import \"tailwindcss\"`\n- Trying to use `tailwind.config.js` instead of CSS `@theme` directive\n- Using margins for spacing between siblings instead of gap utilities\n- Forgetting to add dark mode variants when the project uses dark mode\n","# Tailwind CSS Development\n\n## Documentation\n\nUse `search-docs` for detailed Tailwind CSS v4 patterns and documentation.\n\n## Basic Usage\n\n- Use Tailwind CSS classes to style HTML. Check and follow existing Tailwind conventions in the project before introducing new patterns.\n- Offer to extract repeated patterns into components that match the project's conventions (e.g., Blade, JSX, Vue).\n- Consider class placement, order, priority, and defaults. Remove redundant classes, add classes to parent or child elements carefully to reduce repetition, and group elements logically.\n\n## Tailwind CSS v4 Specifics\n\n- Always use Tailwind CSS v4 and avoid deprecated utilities.\n- `corePlugins` is not supported in Tailwind v4.\n\n### CSS-First Configuration\n\nIn Tailwind v4, configuration is CSS-first using the `@theme` directive — no separate `tailwind.config.js` file is needed:\n\n\u003C!-- CSS-First Config -->\n```css\n@theme {\n  --color-brand: oklch(0.72 0.11 178);\n}\n```\n\n### Import Syntax\n\nIn Tailwind v4, import Tailwind with a regular CSS `@import` statement instead of the `@tailwind` directives used in v3:\n\n\u003C!-- v4 Import Syntax -->\n```diff\n- @tailwind base;\n- @tailwind components;\n- @tailwind utilities;\n+ @import \"tailwindcss\";\n```\n\n### Replaced Utilities\n\nTailwind v4 removed deprecated utilities. Use the replacements shown below. For opacity, drop the `*-opacity-*` class and append the value as a modifier on the existing color: `bg-blue-500 bg-opacity-50` becomes `bg-blue-500\u002F50`, `text-white text-opacity-75` becomes `text-white\u002F75`.\n\n| Deprecated | Replacement |\n|------------|-------------|\n| bg-opacity-* | bg-{color}\u002F* |\n| text-opacity-* | text-{color}\u002F* |\n| border-opacity-* | border-{color}\u002F* |\n| divide-opacity-* | divide-{color}\u002F* |\n| ring-opacity-* | ring-{color}\u002F* |\n| placeholder-opacity-* | placeholder-{color}\u002F* |\n| flex-shrink-* | shrink-* |\n| flex-grow-* | grow-* |\n| overflow-ellipsis | text-ellipsis |\n| decoration-slice | box-decoration-slice |\n| decoration-clone | box-decoration-clone |\n\n## Spacing\n\nUse `gap` utilities instead of margins for spacing between siblings:\n\n\u003C!-- Gap Utilities -->\n```html\n\u003Cdiv class=\"flex gap-8\">\n    \u003Cdiv>Item 1\u003C\u002Fdiv>\n    \u003Cdiv>Item 2\u003C\u002Fdiv>\n\u003C\u002Fdiv>\n```\n\n## Dark Mode\n\nIf existing pages and components support dark mode, new pages and components must support it the same way, typically using the `dark:` variant:\n\n\u003C!-- Dark Mode -->\n```html\n\u003Cdiv class=\"bg-white dark:bg-gray-900 text-gray-900 dark:text-white\">\n    Content adapts to color scheme\n\u003C\u002Fdiv>\n```\n\n## Common Pitfalls\n\n- Using deprecated v3 utilities (bg-opacity-*, flex-shrink-*, etc.)\n- Using `@tailwind` directives instead of `@import \"tailwindcss\"`\n- Trying to use `tailwind.config.js` instead of CSS `@theme` directive\n- Using margins for spacing between siblings instead of gap utilities\n- Forgetting to add dark mode variants when the project uses dark mode\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25},"laravel","main","1bd2039ce81806502a07c06da654de0f24a52105",".cursor\u002Fskills\u002Ftailwindcss-development","https:\u002F\u002Fgithub.com\u002FDommmin\u002Fsh-site","https:\u002F\u002Fgithub.com\u002FDommmin","https:\u002F\u002Fdominik-dev.pl\u002F","2026-10-23 18:01:22",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add Dommmin\u002Fsh-site --skill tailwindcss-development",{"tool":39,"command":40},"bunx","bunx skills add Dommmin\u002Fsh-site --skill tailwindcss-development",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Dommmin\u002Fsh-site --skill tailwindcss-development","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FDommmin\u002Fsh-site\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Ftailwindcss-development\u002FSKILL.md",true,[],[48,55,62,67,74,81],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7FDT0M31R8NN2FS655W5W6X","wayfinder-development","Use this skill for Laravel Wayfinder which auto-generates typed functions for Laravel controllers and routes. ALWAYS use this skill when frontend code needs to call backend routes or controller actions. Trigger when: connecting any React\u002FVue\u002FSvelte\u002FInertia frontend to Laravel controllers, routes, building end-to-end features with both frontend and backend, wiring up forms or links to backend endpoints, fixing route-related TypeScript errors, importing from @\u002Factions or @\u002Froutes, or running wayfinder:generate. Use Wayfinder route functions instead of hardcoded URLs. Covers: wayfinder() vite plugin, .url()\u002F.get()\u002F.post()\u002F.form(), query params, route model binding, tree-shaking. Do not use for backend-only task","https:\u002F\u002Fgithub.com\u002FDommmin\u002Fsh-site\u002Fblob\u002Fmain\u002F.kiro\u002Fskills\u002Fwayfinder-development\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7FDSWRP761BD3J1N86CSAY8","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\u002FDommmin\u002Fsh-site\u002Fblob\u002Fmain\u002F.kiro\u002Fskills\u002Ftesting-best-practices\u002FSKILL.md",[],[],{"skillNo":63,"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":64,"categories":65,"keywords":66,"publishedAt":19},"01M7FDSNHCZHX00Q6XM0Y3FV9B","https:\u002F\u002Fgithub.com\u002FDommmin\u002Fsh-site\u002Fblob\u002Fmain\u002F.kiro\u002Fskills\u002Ftailwindcss-development\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7FDSEMS0MY5HJ25VHFZQHBT","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\u002FDommmin\u002Fsh-site\u002Fblob\u002Fmain\u002F.kiro\u002Fskills\u002Flaravel-best-practices\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7FDS543B1WRJH4VM3TRCSRT","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. 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\u002FDommmin\u002Fsh-site\u002Fblob\u002Fmain\u002F.kiro\u002Fskills\u002Finfer-conventions\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7FDRZP6FMVKKT0YR9H4JXK6","inertia-react-development","Develops Inertia.js v3 React client-side applications. Activates when creating React pages, forms, or navigation; using \u003CLink>, \u003CForm>, useForm, useHttp, setLayoutProps, or router; working with deferred props, prefetching, optimistic updates, instant visits, or polling; or when user mentions React with Inertia, React pages, React forms, or React navigation.","https:\u002F\u002Fgithub.com\u002FDommmin\u002Fsh-site\u002Fblob\u002Fmain\u002F.kiro\u002Fskills\u002Finertia-react-development\u002FSKILL.md",[],[]]