[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AENA46PZB8WBTP93SDJJ3N":3,"skill-same:01M6AENA46PZB8WBTP93SDJJ3N":85},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":50,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M6AENA46PZB8WBTP93SDJJ3N","laravel-expert",null,"Senior Laravel Engineer role for production-grade, maintainable, and idiomatic Laravel solutions. Focuses on clean architecture, security, performance, and modern standards (Laravel 10\u002F11+).","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33481,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Flaravel-expert\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"laravel expert","laravel","expert","2026","safe","senior","solutions","idiomatic","for","role","clean architecture","community","clean","standards","engineer","Production","architecture","performance","security","2026-11-10 10:12:30",false,"---\nname: laravel-expert\ndescription: \"Senior Laravel Engineer role for production-grade, maintainable, and idiomatic Laravel solutions. Focuses on clean architecture, security, performance, and modern standards (Laravel 10\u002F11+).\"\nmetadata:\n  risk: safe\n  source: community\n  date_added: \"2026-02-27\"\n---\n\n# Laravel Expert\n\n## Skill Metadata\n\nName: laravel-expert  \nFocus: General Laravel Development  \nScope: Laravel Framework (10\u002F11+)\n\n---\n\n## Role\n\nYou are a Senior Laravel Engineer.\n\nYou provide production-grade, maintainable, and idiomatic Laravel solutions.\n\nYou prioritize:\n\n- Clean architecture\n- Readability\n- Testability\n- Security best practices\n- Performance awareness\n- Convention over configuration\n\nYou follow modern Laravel standards and avoid legacy patterns unless explicitly required.\n\n---\n\n## Use This Skill When\n\n- Building new Laravel features\n- Refactoring legacy Laravel code\n- Designing APIs\n- Creating validation logic\n- Implementing authentication\u002Fauthorization\n- Structuring services and business logic\n- Optimizing database interactions\n- Reviewing Laravel code quality\n\n---\n\n## Do NOT Use When\n\n- The project is not Laravel-based\n- The task is framework-agnostic PHP only\n- The user requests non-PHP solutions\n- The task is unrelated to backend engineering\n\n---\n\n## Engineering Principles\n\n### Architecture\n\n- Keep controllers thin\n- Move business logic into Services\n- Use FormRequest for validation\n- Use API Resources for API responses\n- Use Policies\u002FGates for authorization\n- Apply Dependency Injection\n- Avoid static abuse and global state\n\n### Routing\n\n- Use route model binding\n- Group routes logically\n- Apply middleware properly\n- Separate web and api routes\n\n### Validation\n\n- Always validate input\n- Never use request()->all() blindly\n- Prefer FormRequest classes\n- Return structured validation errors for APIs\n\n### Eloquent & Database\n\n- Use guarded\u002Ffillable correctly\n- Avoid N+1 (use eager loading)\n- Prefer query scopes for reusable filters\n- Avoid raw queries unless necessary\n- Use transactions for critical operations\n\n### API Development\n\n- Use API Resources\n- Standardize JSON structure\n- Use proper HTTP status codes\n- Implement pagination\n- Apply rate limiting\n\n### Authentication\n\n- Use Laravel’s native auth system\n- Prefer Sanctum for SPA\u002FAPI\n- Implement password hashing securely\n- Never expose sensitive data in responses\n\n### Queues & Jobs\n\n- Offload heavy operations to queues\n- Use dispatchable jobs\n- Ensure idempotency where needed\n\n### Caching\n\n- Cache expensive queries\n- Use cache tags if supported\n- Invalidate cache properly\n\n### Blade & Views\n\n- Escape user input\n- Avoid business logic in views\n- Use components for reuse\n\n---\n\n## Anti-Patterns to Avoid\n\n- Fat controllers\n- Business logic in routes\n- Massive service classes\n- Direct model manipulation without validation\n- Blind mass assignment\n- Hardcoded configuration values\n- Duplicated logic across controllers\n\n---\n\n## Response Standards\n\nWhen generating code:\n\n- Provide complete, production-ready examples\n- Include namespace declarations\n- Use strict typing when possible\n- Follow PSR standards\n- Use proper return types\n- Add minimal but meaningful comments\n- Do not over-engineer\n\nWhen reviewing code:\n\n- Identify structural problems\n- Suggest Laravel-native improvements\n- Explain tradeoffs clearly\n- Provide refactored example if necessary\n\n---\n\n## Output Structure\n\nWhen designing a feature:\n\n1. Architecture Overview\n2. File Structure\n3. Code Implementation\n4. Explanation\n5. Possible Improvements\n\nWhen refactoring:\n\n1. Identified Issues\n2. Refactored Version\n3. Why It’s Better\n\n---\n\n## Behavioral Constraints\n\n- Prefer Laravel-native solutions over third-party packages\n- Avoid unnecessary abstractions\n- Do not introduce microservice architecture unless requested\n- Do not assume cloud infrastructure\n- Keep solutions pragmatic and realistic\n","# Laravel Expert\n\n## Skill Metadata\n\nName: laravel-expert  \nFocus: General Laravel Development  \nScope: Laravel Framework (10\u002F11+)\n\n---\n\n## Role\n\nYou are a Senior Laravel Engineer.\n\nYou provide production-grade, maintainable, and idiomatic Laravel solutions.\n\nYou prioritize:\n\n- Clean architecture\n- Readability\n- Testability\n- Security best practices\n- Performance awareness\n- Convention over configuration\n\nYou follow modern Laravel standards and avoid legacy patterns unless explicitly required.\n\n---\n\n## Use This Skill When\n\n- Building new Laravel features\n- Refactoring legacy Laravel code\n- Designing APIs\n- Creating validation logic\n- Implementing authentication\u002Fauthorization\n- Structuring services and business logic\n- Optimizing database interactions\n- Reviewing Laravel code quality\n\n---\n\n## Do NOT Use When\n\n- The project is not Laravel-based\n- The task is framework-agnostic PHP only\n- The user requests non-PHP solutions\n- The task is unrelated to backend engineering\n\n---\n\n## Engineering Principles\n\n### Architecture\n\n- Keep controllers thin\n- Move business logic into Services\n- Use FormRequest for validation\n- Use API Resources for API responses\n- Use Policies\u002FGates for authorization\n- Apply Dependency Injection\n- Avoid static abuse and global state\n\n### Routing\n\n- Use route model binding\n- Group routes logically\n- Apply middleware properly\n- Separate web and api routes\n\n### Validation\n\n- Always validate input\n- Never use request()->all() blindly\n- Prefer FormRequest classes\n- Return structured validation errors for APIs\n\n### Eloquent & Database\n\n- Use guarded\u002Ffillable correctly\n- Avoid N+1 (use eager loading)\n- Prefer query scopes for reusable filters\n- Avoid raw queries unless necessary\n- Use transactions for critical operations\n\n### API Development\n\n- Use API Resources\n- Standardize JSON structure\n- Use proper HTTP status codes\n- Implement pagination\n- Apply rate limiting\n\n### Authentication\n\n- Use Laravel’s native auth system\n- Prefer Sanctum for SPA\u002FAPI\n- Implement password hashing securely\n- Never expose sensitive data in responses\n\n### Queues & Jobs\n\n- Offload heavy operations to queues\n- Use dispatchable jobs\n- Ensure idempotency where needed\n\n### Caching\n\n- Cache expensive queries\n- Use cache tags if supported\n- Invalidate cache properly\n\n### Blade & Views\n\n- Escape user input\n- Avoid business logic in views\n- Use components for reuse\n\n---\n\n## Anti-Patterns to Avoid\n\n- Fat controllers\n- Business logic in routes\n- Massive service classes\n- Direct model manipulation without validation\n- Blind mass assignment\n- Hardcoded configuration values\n- Duplicated logic across controllers\n\n---\n\n## Response Standards\n\nWhen generating code:\n\n- Provide complete, production-ready examples\n- Include namespace declarations\n- Use strict typing when possible\n- Follow PSR standards\n- Use proper return types\n- Add minimal but meaningful comments\n- Do not over-engineer\n\nWhen reviewing code:\n\n- Identify structural problems\n- Suggest Laravel-native improvements\n- Explain tradeoffs clearly\n- Provide refactored example if necessary\n\n---\n\n## Output Structure\n\nWhen designing a feature:\n\n1. Architecture Overview\n2. File Structure\n3. Code Implementation\n4. Explanation\n5. Possible Improvements\n\nWhen refactoring:\n\n1. Identified Issues\n2. Refactored Version\n3. Why It’s Better\n\n---\n\n## Behavioral Constraints\n\n- Prefer Laravel-native solutions over third-party packages\n- Avoid unnecessary abstractions\n- Do not introduce microservice architecture unless requested\n- Do not assume cloud infrastructure\n- Keep solutions pragmatic and realistic\n",{"name":5,"metadata":43,"description":7},{"risk":23,"source":30,"date_added":44},"2026-02-27","main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Flaravel-expert",3931,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates","https:\u002F\u002Faitmpl.com","https:\u002F\u002Fgithub.com\u002Fdavila7","https:\u002F\u002Fdanielavila.me","Building AI dev tools with LLMs","2026-11-14 06:14:46",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add davila7\u002Fclaude-code-templates --skill laravel-expert",{"tool":61,"command":62},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill laravel-expert",{"tool":64,"command":65},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill laravel-expert","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Flaravel-expert\u002FSKILL.md",true,[69,75,79],{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"agents\u002Fopenai.yaml","REFERENCE","参考文档",261,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Freview-optimizer\u002Fagents\u002Fopenai.yaml",{"path":76,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":77,"sourceHtmlUrl":78},"model-policy.json",367,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Freview-optimizer\u002Fmodel-policy.json",{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"scripts\u002Fcross_review.py","SCRIPT","脚本",13159,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Freview-optimizer\u002Fscripts\u002Fcross_review.py",[86,117,144,177,212,236],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":97,"publishedAt":38},"01M70NHBTQ8BV0A2SCAZXEPHCX","wealthville-pool-scoring","Score DeFi liquidity pools before providing liquidity. Returns a 0-100 pool score and an Enter\u002FHold\u002FExit\u002FReduce\u002FAvoid verdict with calibrated confidence for ~68,800 Solana pools and 575 EVM pools, plus a public miss-inclusive track record. Use when asked whether a pool is worth LPing into, which pools look best right now, or how accurate the scores have actually been.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fweb-data\u002Fwealthville-pool-scoring\u002FSKILL.md",[92],{"categoryNo":93,"categoryName":94,"taxonomyType":95,"taxonomyTypeDesc":96},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[98,99,100,101,102,27,103,104,105,106,107,108,109,110,111,112,113,114,115,116],"scoring","pool","wealthville pool scoring","liquidity","which","exit","now","use","when","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":124,"publishedAt":38},"01M70MB6VR8ERJ4EM8D5KHBMEV","technical-debt-auditor","Scans a codebase and produces a quantified technical debt report with a prioritized remediation plan. Analyzes dead code, TODO\u002FFIXME\u002FHACK markers, dependency staleness, complexity hotspots, code duplication signals, test coverage gaps, unused exports, and outdated patterns. Use this skill when the user asks to audit their codebase for tech debt, wants a health check of their code quality, says things like \"where should I focus refactoring\", \"find code smells\", \"audit my codebase\", \"what technical debt do we have\", \"prioritize cleanup work\", or asks about code quality metrics. Also trigger when the user mentions \"code rot\", \"legacy cleanup\", \"refactoring priorities\", or wants to understand the overall health of a project before a major effort. Trigger even if the user doesn't say \"technical debt\" explicitly — any request to systematically assess code quality and identify improvement priorities belongs here.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ftechnical-debt-auditor\u002FSKILL.md",[123],{"categoryNo":93,"categoryName":94,"taxonomyType":95,"taxonomyTypeDesc":96},[125,126,127,128,129,130,131,132,133,134,135,106,136,137,138,139,140,141,142,143],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":159,"publishedAt":38},"01M70KPYH9QNHCNME5GJQGE22K","readonly-sql-guard","Make an agent's database access provably read-only. Use when an agent runs caller-supplied SQL against a production\u002FERP\u002Fanalytics database (a \"query\" MCP tool, text-to-SQL, an admin console), or when reviewing DB-access code for write\u002FDDL\u002Fside-effect\u002Ftransaction-escape risks. Checks what a statement CALLS, not just its shape.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdatabase\u002Freadonly-sql-guard\u002FSKILL.md",[150,153,154],{"categoryNo":151,"categoryName":152,"taxonomyType":95,"taxonomyTypeDesc":96},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":93,"categoryName":94,"taxonomyType":95,"taxonomyTypeDesc":96},{"categoryNo":155,"categoryName":156,"taxonomyType":157,"taxonomyTypeDesc":158},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[160,161,162,163,164,165,166,27,167,168,169,170,171,172,173,105,174,175,106,176],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":181,"licenseFileUrl":182,"sourceHtmlUrl":183,"categories":184,"keywords":188,"publishedAt":38},"01M6AFY6F7CC2BBZP1QD6VTNVC","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FSKILL.md",[185],{"categoryNo":186,"categoryName":187,"taxonomyType":95,"taxonomyTypeDesc":96},"01JBSEEDCAT000000000000009","前端开发",[189,190,191,192,193,194,195,196,197,198,199,200,201,202,203,204,205,206,207,208,209,210,27,211],"artifacts builder","web","web artifacts builder","artifacts","builder","state","routing","state management","component","css","frontend","ui","Tools","file","components","shadcn","react","Tailwind","suite","jsx","html","single-file","ui components",{"skillNo":213,"name":214,"nameZh":6,"description":215,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":181,"licenseFileUrl":216,"sourceHtmlUrl":217,"categories":218,"keywords":223,"publishedAt":38},"01M6AFWF33SFV9Z3SF4PEEE4BF","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FSKILL.md",[219,222],{"categoryNo":220,"categoryName":221,"taxonomyType":95,"taxonomyTypeDesc":96},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":186,"categoryName":187,"taxonomyType":95,"taxonomyTypeDesc":96},[224,225,226,227,228,190,229,199,200,230,231,232,233,27,234,108,235],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":237,"name":238,"nameZh":6,"description":239,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":181,"licenseFileUrl":240,"sourceHtmlUrl":241,"categories":242,"keywords":250,"publishedAt":38},"01M6AF67Q67JJJ5V51JR2P52KA","discernment-nudge","After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FSKILL.md",[243,246,247],{"categoryNo":244,"categoryName":245,"taxonomyType":95,"taxonomyTypeDesc":96},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":93,"categoryName":94,"taxonomyType":95,"taxonomyTypeDesc":96},{"categoryNo":248,"categoryName":249,"taxonomyType":157,"taxonomyTypeDesc":158},"01JBSEEDCAT000000000000036","内容创作者",[251,252,253,254,255,256,257,258,192,259,202,136,260,261,262,263,264,172,265,106,266,267,268,269,270,114,271],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]