[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DQD0AB377SWJV80NG3MN81":3,"skill-same:01M7DQD0AB377SWJV80NG3MN81":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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":35,"repositoryHtmlUrl":36,"repositoryHomepageUrl":6,"ownerHtmlUrl":37,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":38,"install":39,"resources":51},"01M7DQD0AB377SWJV80NG3MN81","seo-schema",null,"Detect, validate, and generate Schema.org structured data. JSON-LD format preferred. Use when user says \"schema\", \"structured data\", \"rich results\", \"JSON-LD\", or \"markup\".","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\u002Fseo-schema\u002Fseo-schema\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fseo-schema\u002Fseo-schema\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: seo-schema\ndescription: >\n  Detect, validate, and generate Schema.org structured data. JSON-LD format\n  preferred. Use when user says \"schema\", \"structured data\", \"rich results\",\n  \"JSON-LD\", or \"markup\".\nuser-invocable: true\nargument-hint: \"[url]\"\nlicense: MIT\nmetadata:\n  author: AgriciDaniel\n  version: \"2.2.5\"\n  category: seo\n---\n\n# Schema Markup Analysis & Generation\n\n## Detection\n\n1. Scan page source for JSON-LD `\u003Cscript type=\"application\u002Fld+json\">`\n2. Check for Microdata (`itemscope`, `itemprop`)\n3. Check for RDFa (`typeof`, `property`)\n4. Always recommend JSON-LD as primary format (Google's stated preference)\n\n## Validation\n\n- Check required properties per schema type\n- Validate against Google's supported rich result types\n- Test for common errors:\n  - Missing @context\n  - Invalid @type\n  - Wrong data types\n  - Placeholder text\n  - Relative URLs (should be absolute)\n  - Invalid date formats\n- Flag deprecated types (see below)\n\n## Schema Type Status (as of June 2026)\n\nRead `..\u002Fseo\u002Freferences\u002Fschema-types.md` for the full list. Key rules:\n\n### ACTIVE (recommend freely):\nOrganization, LocalBusiness, SoftwareApplication, WebApplication, Product (with Certification markup as of April 2025), ProductGroup, Offer, Service, Article, BlogPosting, NewsArticle, Review, AggregateRating, BreadcrumbList, WebSite, WebPage, Person, ProfilePage, ContactPage, VideoObject, ImageObject, Event, JobPosting, Course, DiscussionForumPosting\n\n### VIDEO & SPECIALIZED (recommend freely):\nBroadcastEvent, Clip, SeekToAction, SoftwareSourceCode\n\nSee `schema\u002Ftemplates.json` for ready-to-use JSON-LD templates for these types.\n\n> **JSON-LD and JavaScript rendering:** Per Google's December 2025 JS SEO guidance, structured data injected via JavaScript may face delayed processing. For time-sensitive markup (especially Product, Offer), include JSON-LD in the initial server-rendered HTML.\n\n### NO RICH RESULTS, KEEP IF USEFUL:\n- **FAQPage**: Google retired FAQ rich results for ALL sites on May 7, 2026 (supersedes the Aug 2023 gov\u002Fhealth restriction). No Google SERP rich-result benefit; flag existing FAQPage at Info (not Critical) rather than removal. For genuine user Q&A pages, use **QAPage**.\n\n### DEPRECATED (never recommend):\n- **HowTo**: Rich results removed September 2023\n- **SpecialAnnouncement**: Deprecated July 31, 2025\n- **CourseInfo, EstimatedSalary, LearningVideo**: Retired June 2025\n- **ClaimReview**: Retired from rich results June 2025\n- **VehicleListing**: Retired from rich results June 2025\n- **Practice Problem**: Deprecation notice 2025-11-05; Search Console \u002F Rich Results Test support removed 2026-01-06\n- **Book Actions**: Deprecated\u002Fremoved from Google rich results; do not recommend it for SERP features.\n- Search Console \u002F Rich Results Test \u002F appearance-filter support for CourseInfo, EstimatedSalary, LearningVideo, SpecialAnnouncement, VehicleListing was removed 2025-09-09; Practice Problem support was removed 2026-01-06.\n\n### Supported for Dataset Search only:\n- **Dataset**: Not discontinued; consumed by Google Dataset Search, with no Google Search rich-result surface. Don't advise removal as if it were killed.\n\n### Still supported (do not flag):\n- QAPage (expanded comment-thread properties 2026-03-24), DiscussionForumPosting, Education Q&A (Quiz \u002F `eduQuestionType=Flashcard`). For e-commerce, **hasAdultConsideration** (added 2026-05-20; value `https:\u002F\u002Fschema.org\u002FSexualContentConsideration`) is required for adult products. `Product.category` accepts `Text`, `CategoryCode`, or arrays mixing both.\n\n## Generation\n\nWhen generating schema for a page:\n1. Identify page type from content analysis\n2. Select appropriate schema type(s)\n3. Generate valid JSON-LD with all required + recommended properties\n4. Include only truthful, verifiable data. Use placeholders clearly marked for user to fill\n5. Validate output before presenting\n6. For review markup, reject fake reviews and undisclosed incentivized reviews.\n   An incentive must be clearly and prominently disclosed on the page.\n\n## Common Schema Templates\n\n### Organization\n```json\n{\n  \"@context\": \"https:\u002F\u002Fschema.org\",\n  \"@type\": \"Organization\",\n  \"name\": \"[Company Name]\",\n  \"url\": \"[Website URL]\",\n  \"logo\": \"[Logo URL]\",\n  \"contactPoint\": {\n    \"@type\": \"ContactPoint\",\n    \"telephone\": \"[Phone]\",\n    \"contactType\": \"customer service\"\n  },\n  \"sameAs\": [\n    \"[Facebook URL]\",\n    \"[LinkedIn URL]\",\n    \"[Twitter URL]\"\n  ]\n}\n```\n\n### LocalBusiness\n```json\n{\n  \"@context\": \"https:\u002F\u002Fschema.org\",\n  \"@type\": \"LocalBusiness\",\n  \"name\": \"[Business Name]\",\n  \"address\": {\n    \"@type\": \"PostalAddress\",\n    \"streetAddress\": \"[Street]\",\n    \"addressLocality\": \"[City]\",\n    \"addressRegion\": \"[State]\",\n    \"postalCode\": \"[ZIP]\",\n    \"addressCountry\": \"US\"\n  },\n  \"telephone\": \"[Phone]\",\n  \"openingHours\": \"Mo-Fr 09:00-17:00\",\n  \"geo\": {\n    \"@type\": \"GeoCoordinates\",\n    \"latitude\": \"[Lat]\",\n    \"longitude\": \"[Long]\"\n  }\n}\n```\n\n### Article\u002FBlogPosting\n```json\n{\n  \"@context\": \"https:\u002F\u002Fschema.org\",\n  \"@type\": \"Article\",\n  \"headline\": \"[Title]\",\n  \"author\": {\n    \"@type\": \"Person\",\n    \"name\": \"[Author Name]\"\n  },\n  \"datePublished\": \"[YYYY-MM-DD]\",\n  \"dateModified\": \"[YYYY-MM-DD]\",\n  \"image\": \"[Image URL]\",\n  \"publisher\": {\n    \"@type\": \"Organization\",\n    \"name\": \"[Publisher]\",\n    \"logo\": {\n      \"@type\": \"ImageObject\",\n      \"url\": \"[Logo URL]\"\n    }\n  }\n}\n```\n\n## Output\n\n- `SCHEMA-REPORT.md`: detection and validation results\n- `generated-schema.json`: ready-to-use JSON-LD snippets\n\n### Validation Results\n| Schema | Type | Status | Issues |\n|--------|------|--------|--------|\n| ... | ... | ✅\u002F⚠️\u002F❌ | ... |\n\n### Recommendations\n- Missing schema opportunities\n- Validation fixes needed\n- Generated code for implementation\n\n## Error Handling\n\n| Scenario | Action |\n|----------|--------|\n| URL unreachable | Report connection error with status code. Suggest verifying URL and checking if the page requires authentication. |\n| No schema markup found | Report that no JSON-LD, Microdata, or RDFa was detected. Recommend appropriate schema types based on page content analysis. |\n| Invalid JSON-LD syntax | Parse and report specific syntax errors (missing brackets, trailing commas, unquoted keys). Provide corrected JSON-LD output. |\n| Deprecated schema type detected | Flag the deprecated type with its retirement date. Recommend the current replacement type or advise removal if no replacement exists. |\n","# Schema Markup Analysis & Generation\n\n## Detection\n\n1. Scan page source for JSON-LD `\u003Cscript type=\"application\u002Fld+json\">`\n2. Check for Microdata (`itemscope`, `itemprop`)\n3. Check for RDFa (`typeof`, `property`)\n4. Always recommend JSON-LD as primary format (Google's stated preference)\n\n## Validation\n\n- Check required properties per schema type\n- Validate against Google's supported rich result types\n- Test for common errors:\n  - Missing @context\n  - Invalid @type\n  - Wrong data types\n  - Placeholder text\n  - Relative URLs (should be absolute)\n  - Invalid date formats\n- Flag deprecated types (see below)\n\n## Schema Type Status (as of June 2026)\n\nRead `..\u002Fseo\u002Freferences\u002Fschema-types.md` for the full list. Key rules:\n\n### ACTIVE (recommend freely):\nOrganization, LocalBusiness, SoftwareApplication, WebApplication, Product (with Certification markup as of April 2025), ProductGroup, Offer, Service, Article, BlogPosting, NewsArticle, Review, AggregateRating, BreadcrumbList, WebSite, WebPage, Person, ProfilePage, ContactPage, VideoObject, ImageObject, Event, JobPosting, Course, DiscussionForumPosting\n\n### VIDEO & SPECIALIZED (recommend freely):\nBroadcastEvent, Clip, SeekToAction, SoftwareSourceCode\n\nSee `schema\u002Ftemplates.json` for ready-to-use JSON-LD templates for these types.\n\n> **JSON-LD and JavaScript rendering:** Per Google's December 2025 JS SEO guidance, structured data injected via JavaScript may face delayed processing. For time-sensitive markup (especially Product, Offer), include JSON-LD in the initial server-rendered HTML.\n\n### NO RICH RESULTS, KEEP IF USEFUL:\n- **FAQPage**: Google retired FAQ rich results for ALL sites on May 7, 2026 (supersedes the Aug 2023 gov\u002Fhealth restriction). No Google SERP rich-result benefit; flag existing FAQPage at Info (not Critical) rather than removal. For genuine user Q&A pages, use **QAPage**.\n\n### DEPRECATED (never recommend):\n- **HowTo**: Rich results removed September 2023\n- **SpecialAnnouncement**: Deprecated July 31, 2025\n- **CourseInfo, EstimatedSalary, LearningVideo**: Retired June 2025\n- **ClaimReview**: Retired from rich results June 2025\n- **VehicleListing**: Retired from rich results June 2025\n- **Practice Problem**: Deprecation notice 2025-11-05; Search Console \u002F Rich Results Test support removed 2026-01-06\n- **Book Actions**: Deprecated\u002Fremoved from Google rich results; do not recommend it for SERP features.\n- Search Console \u002F Rich Results Test \u002F appearance-filter support for CourseInfo, EstimatedSalary, LearningVideo, SpecialAnnouncement, VehicleListing was removed 2025-09-09; Practice Problem support was removed 2026-01-06.\n\n### Supported for Dataset Search only:\n- **Dataset**: Not discontinued; consumed by Google Dataset Search, with no Google Search rich-result surface. Don't advise removal as if it were killed.\n\n### Still supported (do not flag):\n- QAPage (expanded comment-thread properties 2026-03-24), DiscussionForumPosting, Education Q&A (Quiz \u002F `eduQuestionType=Flashcard`). For e-commerce, **hasAdultConsideration** (added 2026-05-20; value `https:\u002F\u002Fschema.org\u002FSexualContentConsideration`) is required for adult products. `Product.category` accepts `Text`, `CategoryCode`, or arrays mixing both.\n\n## Generation\n\nWhen generating schema for a page:\n1. Identify page type from content analysis\n2. Select appropriate schema type(s)\n3. Generate valid JSON-LD with all required + recommended properties\n4. Include only truthful, verifiable data. Use placeholders clearly marked for user to fill\n5. Validate output before presenting\n6. For review markup, reject fake reviews and undisclosed incentivized reviews.\n   An incentive must be clearly and prominently disclosed on the page.\n\n## Common Schema Templates\n\n### Organization\n```json\n{\n  \"@context\": \"https:\u002F\u002Fschema.org\",\n  \"@type\": \"Organization\",\n  \"name\": \"[Company Name]\",\n  \"url\": \"[Website URL]\",\n  \"logo\": \"[Logo URL]\",\n  \"contactPoint\": {\n    \"@type\": \"ContactPoint\",\n    \"telephone\": \"[Phone]\",\n    \"contactType\": \"customer service\"\n  },\n  \"sameAs\": [\n    \"[Facebook URL]\",\n    \"[LinkedIn URL]\",\n    \"[Twitter URL]\"\n  ]\n}\n```\n\n### LocalBusiness\n```json\n{\n  \"@context\": \"https:\u002F\u002Fschema.org\",\n  \"@type\": \"LocalBusiness\",\n  \"name\": \"[Business Name]\",\n  \"address\": {\n    \"@type\": \"PostalAddress\",\n    \"streetAddress\": \"[Street]\",\n    \"addressLocality\": \"[City]\",\n    \"addressRegion\": \"[State]\",\n    \"postalCode\": \"[ZIP]\",\n    \"addressCountry\": \"US\"\n  },\n  \"telephone\": \"[Phone]\",\n  \"openingHours\": \"Mo-Fr 09:00-17:00\",\n  \"geo\": {\n    \"@type\": \"GeoCoordinates\",\n    \"latitude\": \"[Lat]\",\n    \"longitude\": \"[Long]\"\n  }\n}\n```\n\n### Article\u002FBlogPosting\n```json\n{\n  \"@context\": \"https:\u002F\u002Fschema.org\",\n  \"@type\": \"Article\",\n  \"headline\": \"[Title]\",\n  \"author\": {\n    \"@type\": \"Person\",\n    \"name\": \"[Author Name]\"\n  },\n  \"datePublished\": \"[YYYY-MM-DD]\",\n  \"dateModified\": \"[YYYY-MM-DD]\",\n  \"image\": \"[Image URL]\",\n  \"publisher\": {\n    \"@type\": \"Organization\",\n    \"name\": \"[Publisher]\",\n    \"logo\": {\n      \"@type\": \"ImageObject\",\n      \"url\": \"[Logo URL]\"\n    }\n  }\n}\n```\n\n## Output\n\n- `SCHEMA-REPORT.md`: detection and validation results\n- `generated-schema.json`: ready-to-use JSON-LD snippets\n\n### Validation Results\n| Schema | Type | Status | Issues |\n|--------|------|--------|--------|\n| ... | ... | ✅\u002F⚠️\u002F❌ | ... |\n\n### Recommendations\n- Missing schema opportunities\n- Validation fixes needed\n- Generated code for implementation\n\n## Error Handling\n\n| Scenario | Action |\n|----------|--------|\n| URL unreachable | Report connection error with status code. Suggest verifying URL and checking if the page requires authentication. |\n| No schema markup found | Report that no JSON-LD, Microdata, or RDFa was detected. Recommend appropriate schema types based on page content analysis. |\n| Invalid JSON-LD syntax | Parse and report specific syntax errors (missing brackets, trailing commas, unquoted keys). Provide corrected JSON-LD output. |\n| Deprecated schema type detected | Flag the deprecated type with its retirement date. Recommend the current replacement type or advise removal if no replacement exists. |\n",{"name":5,"license":15,"metadata":25,"description":29,"argument-hint":30,"user-invocable":31},{"author":26,"version":27,"category":28},"AgriciDaniel","2.2.5","seo","Detect, validate, and generate Schema.org structured data. JSON-LD format preferred. Use when user says \"schema\", \"structured data\", \"rich results\", \"JSON-LD\", or \"markup\".\n","[url]",true,"main","b1e4ffadb4f933bbbcaa03a83f8b9929171ac28b",".agents\u002Fskills\u002Fseo-schema\u002Fseo-schema",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":40,"prompt":50,"zipAvailable":31},[41,44,47],{"tool":42,"command":43},"npx","npx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill seo-schema",{"tool":45,"command":46},"bunx","bunx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill seo-schema",{"tool":48,"command":49},"pnpm","pnpm dlx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill seo-schema","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fseo-schema\u002Fseo-schema\u002FSKILL.md",[52,57],{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":16},"LICENSE.txt","LICENSE","许可证",143,{"path":58,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fdeprecated-types-2024-2026.md","REFERENCE","参考文档",5061,"https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fseo-schema\u002Fseo-schema\u002Freferences\u002Fdeprecated-types-2024-2026.md",[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":20},"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":20},"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":20},"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":20},"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":20},"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":20},"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",[],[]]