[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DQQJ4Z98QACGF4QDFFW970":3,"skill-same:01M7DQQJ4Z98QACGF4QDFFW970":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},"01M7DQQJ4Z98QACGF4QDFFW970","source-driven-development",null,"Grounds every implementation decision in official documentation. Use when you want authoritative, source-cited code free from outdated patterns. Use when building with any framework or library where correctness matters.","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\u002Fsource-driven-development\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: source-driven-development\ndescription: Grounds every implementation decision in official documentation. Use when you want authoritative, source-cited code free from outdated patterns. Use when building with any framework or library where correctness matters.\nrisk: unknown\nsource: https:\u002F\u002Fgithub.com\u002Faddyosmani\u002Fagent-skills\u002Ftree\u002Fmain\u002Fskills\u002Fsource-driven-development\nsource_repo: addyosmani\u002Fagent-skills\nsource_type: community\ndate_added: 2026-07-01\nlicense: MIT\nlicense_source: https:\u002F\u002Fgithub.com\u002Faddyosmani\u002Fagent-skills\u002Fblob\u002Fmain\u002FLICENSE\n---\n\n# Source-Driven Development\n\n## Overview\n\nEvery framework-specific code decision must be backed by official documentation. Don't implement from memory — verify, cite, and let the user see your sources. Training data goes stale, APIs get deprecated, best practices evolve. This skill ensures the user gets code they can trust because every pattern traces back to an authoritative source they can check.\n\n## When to Use\n\n- The user wants code that follows current best practices for a given framework\n- Building boilerplate, starter code, or patterns that will be copied across a project\n- The user explicitly asks for documented, verified, or \"correct\" implementation\n- Implementing features where the framework's recommended approach matters (forms, routing, data fetching, state management, auth)\n- Reviewing or improving code that uses framework-specific patterns\n- Any time you are about to write framework-specific code from memory\n\n**When NOT to use:**\n\n- Correctness does not depend on a specific version (renaming variables, fixing typos, moving files)\n- Pure logic that works the same across all versions (loops, conditionals, data structures)\n- The user explicitly wants speed over verification (\"just do it quickly\")\n\n## The Process\n\n```\nDETECT ──→ FETCH ──→ IMPLEMENT ──→ CITE\n  │          │           │            │\n  ▼          ▼           ▼            ▼\n What       Get the    Follow the   Show your\n stack?     relevant   documented   sources\n            docs       patterns\n```\n\n### Step 1: Detect Stack and Versions\n\nRead the project's dependency file to identify exact versions:\n\n```\npackage.json    → Node\u002FReact\u002FVue\u002FAngular\u002FSvelte\ncomposer.json   → PHP\u002FSymfony\u002FLaravel\nrequirements.txt \u002F pyproject.toml → Python\u002FDjango\u002FFlask\ngo.mod          → Go\nCargo.toml      → Rust\nGemfile         → Ruby\u002FRails\n```\n\nState what you found explicitly:\n\n```\nSTACK DETECTED:\n- React 19.1.0 (from package.json)\n- Vite 6.2.0\n- Tailwind CSS 4.0.3\n→ Fetching official docs for the relevant patterns.\n```\n\nIf versions are missing or ambiguous, **ask the user**. Don't guess — the version determines which patterns are correct.\n\n### Step 2: Fetch Official Documentation\n\nFetch the specific documentation page for the feature you're implementing. Not the homepage, not the full docs — the relevant page.\n\n**Source hierarchy (in order of authority):**\n\n| Priority | Source | Example |\n|----------|--------|---------|\n| 1 | Official documentation | react.dev, docs.djangoproject.com, symfony.com\u002Fdoc |\n| 2 | Official blog \u002F changelog | react.dev\u002Fblog, nextjs.org\u002Fblog |\n| 3 | Web standards references | MDN, web.dev, html.spec.whatwg.org |\n| 4 | Browser\u002Fruntime compatibility | caniuse.com, node.green |\n\n**Not authoritative — never cite as primary sources:**\n\n- Stack Overflow answers\n- Blog posts or tutorials (even popular ones)\n- AI-generated documentation or summaries\n- Your own training data (that is the whole point — verify it)\n\n**Be precise with what you fetch:**\n\n```\nBAD:  Fetch the React homepage\nGOOD: Fetch react.dev\u002Freference\u002Freact\u002FuseActionState\n\nBAD:  Search \"django authentication best practices\"\nGOOD: Fetch docs.djangoproject.com\u002Fen\u002F6.0\u002Ftopics\u002Fauth\u002F\n```\n\nAfter fetching, extract the key patterns and note any deprecation warnings or migration guidance.\n\nWhen official sources conflict with each other (e.g. a migration guide contradicts the API reference), surface the discrepancy to the user and verify which pattern actually works against the detected version.\n\n### Step 3: Implement Following Documented Patterns\n\nWrite code that matches what the documentation shows:\n\n- Use the API signatures from the docs, not from memory\n- If the docs show a new way to do something, use the new way\n- If the docs deprecate a pattern, don't use the deprecated version\n- If the docs don't cover something, flag it as unverified\n\n**When docs conflict with existing project code:**\n\n```\nCONFLICT DETECTED:\nThe existing codebase uses useState for form loading state,\nbut React 19 docs recommend useActionState for this pattern.\n(Source: react.dev\u002Freference\u002Freact\u002FuseActionState)\n\nOptions:\nA) Use the modern pattern (useActionState) — consistent with current docs\nB) Match existing code (useState) — consistent with codebase\n→ Which approach do you prefer?\n```\n\nSurface the conflict. Don't silently pick one.\n\n### Step 4: Cite Your Sources\n\nEvery framework-specific pattern gets a citation. The user must be able to verify every decision.\n\n**In code comments:**\n\n```typescript\n\u002F\u002F React 19 form handling with useActionState\n\u002F\u002F Source: https:\u002F\u002Freact.dev\u002Freference\u002Freact\u002FuseActionState#usage\nconst [state, formAction, isPending] = useActionState(submitOrder, initialState);\n```\n\n**In conversation:**\n\n```\nI'm using useActionState instead of manual useState for the\nform submission state. React 19 replaced the manual\nisPending\u002FsetIsPending pattern with this hook.\n\nSource: https:\u002F\u002Freact.dev\u002Fblog\u002F2024\u002F12\u002F05\u002Freact-19#actions\n\"useTransition now supports async functions [...] to handle\npending states automatically\"\n```\n\n**Citation rules:**\n\n- Full URLs, not shortened\n- Prefer deep links with anchors where possible (e.g. `\u002FuseActionState#usage` over `\u002FuseActionState`) — anchors survive doc restructuring better than top-level pages\n- Quote the relevant passage when it supports a non-obvious decision\n- Include browser\u002Fruntime support data when recommending platform features\n- If you cannot find documentation for a pattern, say so explicitly:\n\n```\nUNVERIFIED: I could not find official documentation for this\npattern. This is based on training data and may be outdated.\nVerify before using in production.\n```\n\nHonesty about what you couldn't verify is more valuable than false confidence.\n\n## Common Rationalizations\n\n| Rationalization | Reality |\n|---|---|\n| \"I'm confident about this API\" | Confidence is not evidence. Training data contains outdated patterns that look correct but break against current versions. Verify. |\n| \"Fetching docs wastes tokens\" | Hallucinating an API wastes more. The user debugs for an hour, then discovers the function signature changed. One fetch prevents hours of rework. |\n| \"The docs won't have what I need\" | If the docs don't cover it, that's valuable information — the pattern may not be officially recommended. |\n| \"I'll just mention it might be outdated\" | A disclaimer doesn't help. Either verify and cite, or clearly flag it as unverified. Hedging is the worst option. |\n| \"This is a simple task, no need to check\" | Simple tasks with wrong patterns become templates. The user copies your deprecated form handler into ten components before discovering the modern approach exists. |\n\n## Red Flags\n\n- Writing framework-specific code without checking the docs for that version\n- Using \"I believe\" or \"I think\" about an API instead of citing the source\n- Implementing a pattern without knowing which version it applies to\n- Citing Stack Overflow or blog posts instead of official documentation\n- Using deprecated APIs because they appear in training data\n- Not reading `package.json` \u002F dependency files before implementing\n- Delivering code without source citations for framework-specific decisions\n- Fetching an entire docs site when only one page is relevant\n\n## Verification\n\nAfter implementing with source-driven development:\n\n- [ ] Framework and library versions were identified from the dependency file\n- [ ] Official documentation was fetched for framework-specific patterns\n- [ ] All sources are official documentation, not blog posts or training data\n- [ ] Code follows the patterns shown in the current version's documentation\n- [ ] Non-trivial decisions include source citations with full URLs\n- [ ] No deprecated APIs are used (checked against migration guides)\n- [ ] Conflicts between docs and existing code were surfaced to the user\n- [ ] Anything that could not be verified is explicitly flagged as unverified\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","# Source-Driven Development\n\n## Overview\n\nEvery framework-specific code decision must be backed by official documentation. Don't implement from memory — verify, cite, and let the user see your sources. Training data goes stale, APIs get deprecated, best practices evolve. This skill ensures the user gets code they can trust because every pattern traces back to an authoritative source they can check.\n\n## When to Use\n\n- The user wants code that follows current best practices for a given framework\n- Building boilerplate, starter code, or patterns that will be copied across a project\n- The user explicitly asks for documented, verified, or \"correct\" implementation\n- Implementing features where the framework's recommended approach matters (forms, routing, data fetching, state management, auth)\n- Reviewing or improving code that uses framework-specific patterns\n- Any time you are about to write framework-specific code from memory\n\n**When NOT to use:**\n\n- Correctness does not depend on a specific version (renaming variables, fixing typos, moving files)\n- Pure logic that works the same across all versions (loops, conditionals, data structures)\n- The user explicitly wants speed over verification (\"just do it quickly\")\n\n## The Process\n\n```\nDETECT ──→ FETCH ──→ IMPLEMENT ──→ CITE\n  │          │           │            │\n  ▼          ▼           ▼            ▼\n What       Get the    Follow the   Show your\n stack?     relevant   documented   sources\n            docs       patterns\n```\n\n### Step 1: Detect Stack and Versions\n\nRead the project's dependency file to identify exact versions:\n\n```\npackage.json    → Node\u002FReact\u002FVue\u002FAngular\u002FSvelte\ncomposer.json   → PHP\u002FSymfony\u002FLaravel\nrequirements.txt \u002F pyproject.toml → Python\u002FDjango\u002FFlask\ngo.mod          → Go\nCargo.toml      → Rust\nGemfile         → Ruby\u002FRails\n```\n\nState what you found explicitly:\n\n```\nSTACK DETECTED:\n- React 19.1.0 (from package.json)\n- Vite 6.2.0\n- Tailwind CSS 4.0.3\n→ Fetching official docs for the relevant patterns.\n```\n\nIf versions are missing or ambiguous, **ask the user**. Don't guess — the version determines which patterns are correct.\n\n### Step 2: Fetch Official Documentation\n\nFetch the specific documentation page for the feature you're implementing. Not the homepage, not the full docs — the relevant page.\n\n**Source hierarchy (in order of authority):**\n\n| Priority | Source | Example |\n|----------|--------|---------|\n| 1 | Official documentation | react.dev, docs.djangoproject.com, symfony.com\u002Fdoc |\n| 2 | Official blog \u002F changelog | react.dev\u002Fblog, nextjs.org\u002Fblog |\n| 3 | Web standards references | MDN, web.dev, html.spec.whatwg.org |\n| 4 | Browser\u002Fruntime compatibility | caniuse.com, node.green |\n\n**Not authoritative — never cite as primary sources:**\n\n- Stack Overflow answers\n- Blog posts or tutorials (even popular ones)\n- AI-generated documentation or summaries\n- Your own training data (that is the whole point — verify it)\n\n**Be precise with what you fetch:**\n\n```\nBAD:  Fetch the React homepage\nGOOD: Fetch react.dev\u002Freference\u002Freact\u002FuseActionState\n\nBAD:  Search \"django authentication best practices\"\nGOOD: Fetch docs.djangoproject.com\u002Fen\u002F6.0\u002Ftopics\u002Fauth\u002F\n```\n\nAfter fetching, extract the key patterns and note any deprecation warnings or migration guidance.\n\nWhen official sources conflict with each other (e.g. a migration guide contradicts the API reference), surface the discrepancy to the user and verify which pattern actually works against the detected version.\n\n### Step 3: Implement Following Documented Patterns\n\nWrite code that matches what the documentation shows:\n\n- Use the API signatures from the docs, not from memory\n- If the docs show a new way to do something, use the new way\n- If the docs deprecate a pattern, don't use the deprecated version\n- If the docs don't cover something, flag it as unverified\n\n**When docs conflict with existing project code:**\n\n```\nCONFLICT DETECTED:\nThe existing codebase uses useState for form loading state,\nbut React 19 docs recommend useActionState for this pattern.\n(Source: react.dev\u002Freference\u002Freact\u002FuseActionState)\n\nOptions:\nA) Use the modern pattern (useActionState) — consistent with current docs\nB) Match existing code (useState) — consistent with codebase\n→ Which approach do you prefer?\n```\n\nSurface the conflict. Don't silently pick one.\n\n### Step 4: Cite Your Sources\n\nEvery framework-specific pattern gets a citation. The user must be able to verify every decision.\n\n**In code comments:**\n\n```typescript\n\u002F\u002F React 19 form handling with useActionState\n\u002F\u002F Source: https:\u002F\u002Freact.dev\u002Freference\u002Freact\u002FuseActionState#usage\nconst [state, formAction, isPending] = useActionState(submitOrder, initialState);\n```\n\n**In conversation:**\n\n```\nI'm using useActionState instead of manual useState for the\nform submission state. React 19 replaced the manual\nisPending\u002FsetIsPending pattern with this hook.\n\nSource: https:\u002F\u002Freact.dev\u002Fblog\u002F2024\u002F12\u002F05\u002Freact-19#actions\n\"useTransition now supports async functions [...] to handle\npending states automatically\"\n```\n\n**Citation rules:**\n\n- Full URLs, not shortened\n- Prefer deep links with anchors where possible (e.g. `\u002FuseActionState#usage` over `\u002FuseActionState`) — anchors survive doc restructuring better than top-level pages\n- Quote the relevant passage when it supports a non-obvious decision\n- Include browser\u002Fruntime support data when recommending platform features\n- If you cannot find documentation for a pattern, say so explicitly:\n\n```\nUNVERIFIED: I could not find official documentation for this\npattern. This is based on training data and may be outdated.\nVerify before using in production.\n```\n\nHonesty about what you couldn't verify is more valuable than false confidence.\n\n## Common Rationalizations\n\n| Rationalization | Reality |\n|---|---|\n| \"I'm confident about this API\" | Confidence is not evidence. Training data contains outdated patterns that look correct but break against current versions. Verify. |\n| \"Fetching docs wastes tokens\" | Hallucinating an API wastes more. The user debugs for an hour, then discovers the function signature changed. One fetch prevents hours of rework. |\n| \"The docs won't have what I need\" | If the docs don't cover it, that's valuable information — the pattern may not be officially recommended. |\n| \"I'll just mention it might be outdated\" | A disclaimer doesn't help. Either verify and cite, or clearly flag it as unverified. Hedging is the worst option. |\n| \"This is a simple task, no need to check\" | Simple tasks with wrong patterns become templates. The user copies your deprecated form handler into ten components before discovering the modern approach exists. |\n\n## Red Flags\n\n- Writing framework-specific code without checking the docs for that version\n- Using \"I believe\" or \"I think\" about an API instead of citing the source\n- Implementing a pattern without knowing which version it applies to\n- Citing Stack Overflow or blog posts instead of official documentation\n- Using deprecated APIs because they appear in training data\n- Not reading `package.json` \u002F dependency files before implementing\n- Delivering code without source citations for framework-specific decisions\n- Fetching an entire docs site when only one page is relevant\n\n## Verification\n\nAfter implementing with source-driven development:\n\n- [ ] Framework and library versions were identified from the dependency file\n- [ ] Official documentation was fetched for framework-specific patterns\n- [ ] All sources are official documentation, not blog posts or training data\n- [ ] Code follows the patterns shown in the current version's documentation\n- [ ] Non-trivial decisions include source citations with full URLs\n- [ ] No deprecated APIs are used (checked against migration guides)\n- [ ] Conflicts between docs and existing code were surfaced to the user\n- [ ] Anything that could not be verified is explicitly flagged as unverified\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\u002Faddyosmani\u002Fagent-skills\u002Ftree\u002Fmain\u002Fskills\u002Fsource-driven-development",1782864000000,"addyosmani\u002Fagent-skills","community","https:\u002F\u002Fgithub.com\u002Faddyosmani\u002Fagent-skills\u002Fblob\u002Fmain\u002FLICENSE","main","b1e4ffadb4f933bbbcaa03a83f8b9929171ac28b",".agents\u002Fskills\u002Fsource-driven-development",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 source-driven-development",{"tool":43,"command":44},"bunx","bunx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill source-driven-development",{"tool":46,"command":47},"pnpm","pnpm dlx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill source-driven-development","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsource-driven-development\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",[],[]]