[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AECJSE37E00WWGX2CTM4E2":3,"skill-same:01M6AECJSE37E00WWGX2CTM4E2":128},{"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":26,"publishedAt":53,"linkOnly":54,"markdownContent":55,"markdownBody":56,"frontMatter":57,"refName":58,"commitSha":59,"skillDirectory":60,"forksCount":61,"repositoryHtmlUrl":62,"repositoryHomepageUrl":63,"ownerHtmlUrl":64,"ownerBlogUrl":65,"ownerDescription":66,"updatedAt":67,"install":68,"resources":81},"01M6AECJSE37E00WWGX2CTM4E2","backend-dev-guidelines",null,"Comprehensive backend development guide for Node.js\u002FExpress\u002FTypeScript microservices. Use when creating routes, controllers, services, repositories, middleware, or working with Express APIs, Prisma database access, Sentry error tracking, Zod validation, unifiedConfig, dependency injection, or async patterns. Covers layered architecture (routes → controllers → services → repositories), BaseController pattern, error handling, performance monitoring, testing strategies, and migration from legacy patterns.","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\u002Fbackend-dev-guidelines\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52],"guidelines","backend dev","dev","backend","backend dev guidelines","services","repositories","for","prisma","express","strategies","use","guide","zod","injection","testing","monitoring","microservices","database","sentry","validation","error handling","development","architecture","performance","typescript","2026-11-10 10:12:30",false,"---\nname: backend-dev-guidelines\ndescription: Comprehensive backend development guide for Node.js\u002FExpress\u002FTypeScript microservices. Use when creating routes, controllers, services, repositories, middleware, or working with Express APIs, Prisma database access, Sentry error tracking, Zod validation, unifiedConfig, dependency injection, or async patterns. Covers layered architecture (routes → controllers → services → repositories), BaseController pattern, error handling, performance monitoring, testing strategies, and migration from legacy patterns.\n---\n\n# Backend Development Guidelines\n\n## Purpose\n\nEstablish consistency and best practices across backend microservices (blog-api, auth-service, notifications-service) using modern Node.js\u002FExpress\u002FTypeScript patterns.\n\n## When to Use This Skill\n\nAutomatically activates when working on:\n- Creating or modifying routes, endpoints, APIs\n- Building controllers, services, repositories\n- Implementing middleware (auth, validation, error handling)\n- Database operations with Prisma\n- Error tracking with Sentry\n- Input validation with Zod\n- Configuration management\n- Backend testing and refactoring\n\n---\n\n## Quick Start\n\n### New Backend Feature Checklist\n\n- [ ] **Route**: Clean definition, delegate to controller\n- [ ] **Controller**: Extend BaseController\n- [ ] **Service**: Business logic with DI\n- [ ] **Repository**: Database access (if complex)\n- [ ] **Validation**: Zod schema\n- [ ] **Sentry**: Error tracking\n- [ ] **Tests**: Unit + integration tests\n- [ ] **Config**: Use unifiedConfig\n\n### New Microservice Checklist\n\n- [ ] Directory structure (see [architecture-overview.md](architecture-overview.md))\n- [ ] instrument.ts for Sentry\n- [ ] unifiedConfig setup\n- [ ] BaseController class\n- [ ] Middleware stack\n- [ ] Error boundary\n- [ ] Testing framework\n\n---\n\n## Architecture Overview\n\n### Layered Architecture\n\n```\nHTTP Request\n    ↓\nRoutes (routing only)\n    ↓\nControllers (request handling)\n    ↓\nServices (business logic)\n    ↓\nRepositories (data access)\n    ↓\nDatabase (Prisma)\n```\n\n**Key Principle:** Each layer has ONE responsibility.\n\nSee [architecture-overview.md](architecture-overview.md) for complete details.\n\n---\n\n## Directory Structure\n\n```\nservice\u002Fsrc\u002F\n├── config\u002F              # UnifiedConfig\n├── controllers\u002F         # Request handlers\n├── services\u002F            # Business logic\n├── repositories\u002F        # Data access\n├── routes\u002F              # Route definitions\n├── middleware\u002F          # Express middleware\n├── types\u002F               # TypeScript types\n├── validators\u002F          # Zod schemas\n├── utils\u002F               # Utilities\n├── tests\u002F               # Tests\n├── instrument.ts        # Sentry (FIRST IMPORT)\n├── app.ts               # Express setup\n└── server.ts            # HTTP server\n```\n\n**Naming Conventions:**\n- Controllers: `PascalCase` - `UserController.ts`\n- Services: `camelCase` - `userService.ts`\n- Routes: `camelCase + Routes` - `userRoutes.ts`\n- Repositories: `PascalCase + Repository` - `UserRepository.ts`\n\n---\n\n## Core Principles (7 Key Rules)\n\n### 1. Routes Only Route, Controllers Control\n\n```typescript\n\u002F\u002F ❌ NEVER: Business logic in routes\nrouter.post('\u002Fsubmit', async (req, res) => {\n    \u002F\u002F 200 lines of logic\n});\n\n\u002F\u002F ✅ ALWAYS: Delegate to controller\nrouter.post('\u002Fsubmit', (req, res) => controller.submit(req, res));\n```\n\n### 2. All Controllers Extend BaseController\n\n```typescript\nexport class UserController extends BaseController {\n    async getUser(req: Request, res: Response): Promise\u003Cvoid> {\n        try {\n            const user = await this.userService.findById(req.params.id);\n            this.handleSuccess(res, user);\n        } catch (error) {\n            this.handleError(error, res, 'getUser');\n        }\n    }\n}\n```\n\n### 3. All Errors to Sentry\n\n```typescript\ntry {\n    await operation();\n} catch (error) {\n    Sentry.captureException(error);\n    throw error;\n}\n```\n\n### 4. Use unifiedConfig, NEVER process.env\n\n```typescript\n\u002F\u002F ❌ NEVER\nconst timeout = process.env.TIMEOUT_MS;\n\n\u002F\u002F ✅ ALWAYS\nimport { config } from '.\u002Fconfig\u002FunifiedConfig';\nconst timeout = config.timeouts.default;\n```\n\n### 5. Validate All Input with Zod\n\n```typescript\nconst schema = z.object({ email: z.string().email() });\nconst validated = schema.parse(req.body);\n```\n\n### 6. Use Repository Pattern for Data Access\n\n```typescript\n\u002F\u002F Service → Repository → Database\nconst users = await userRepository.findActive();\n```\n\n### 7. Comprehensive Testing Required\n\n```typescript\ndescribe('UserService', () => {\n    it('should create user', async () => {\n        expect(user).toBeDefined();\n    });\n});\n```\n\n---\n\n## Common Imports\n\n```typescript\n\u002F\u002F Express\nimport express, { Request, Response, NextFunction, Router } from 'express';\n\n\u002F\u002F Validation\nimport { z } from 'zod';\n\n\u002F\u002F Database\nimport { PrismaClient } from '@prisma\u002Fclient';\nimport type { Prisma } from '@prisma\u002Fclient';\n\n\u002F\u002F Sentry\nimport * as Sentry from '@sentry\u002Fnode';\n\n\u002F\u002F Config\nimport { config } from '.\u002Fconfig\u002FunifiedConfig';\n\n\u002F\u002F Middleware\nimport { SSOMiddlewareClient } from '.\u002Fmiddleware\u002FSSOMiddleware';\nimport { asyncErrorWrapper } from '.\u002Fmiddleware\u002FerrorBoundary';\n```\n\n---\n\n## Quick Reference\n\n### HTTP Status Codes\n\n| Code | Use Case |\n|------|----------|\n| 200 | Success |\n| 201 | Created |\n| 400 | Bad Request |\n| 401 | Unauthorized |\n| 403 | Forbidden |\n| 404 | Not Found |\n| 500 | Server Error |\n\n### Service Templates\n\n**Blog API** (✅ Mature) - Use as template for REST APIs\n**Auth Service** (✅ Mature) - Use as template for authentication patterns\n\n---\n\n## Anti-Patterns to Avoid\n\n❌ Business logic in routes\n❌ Direct process.env usage\n❌ Missing error handling\n❌ No input validation\n❌ Direct Prisma everywhere\n❌ console.log instead of Sentry\n\n---\n\n## Navigation Guide\n\n| Need to... | Read this |\n|------------|-----------|\n| Understand architecture | [architecture-overview.md](architecture-overview.md) |\n| Create routes\u002Fcontrollers | [routing-and-controllers.md](routing-and-controllers.md) |\n| Organize business logic | [services-and-repositories.md](services-and-repositories.md) |\n| Validate input | [validation-patterns.md](validation-patterns.md) |\n| Add error tracking | [sentry-and-monitoring.md](sentry-and-monitoring.md) |\n| Create middleware | [middleware-guide.md](middleware-guide.md) |\n| Database access | [database-patterns.md](database-patterns.md) |\n| Manage config | [configuration.md](configuration.md) |\n| Handle async\u002Ferrors | [async-and-errors.md](async-and-errors.md) |\n| Write tests | [testing-guide.md](testing-guide.md) |\n| See examples | [complete-examples.md](complete-examples.md) |\n\n---\n\n## Resource Files\n\n### [architecture-overview.md](architecture-overview.md)\nLayered architecture, request lifecycle, separation of concerns\n\n### [routing-and-controllers.md](routing-and-controllers.md)\nRoute definitions, BaseController, error handling, examples\n\n### [services-and-repositories.md](services-and-repositories.md)\nService patterns, DI, repository pattern, caching\n\n### [validation-patterns.md](validation-patterns.md)\nZod schemas, validation, DTO pattern\n\n### [sentry-and-monitoring.md](sentry-and-monitoring.md)\nSentry init, error capture, performance monitoring\n\n### [middleware-guide.md](middleware-guide.md)\nAuth, audit, error boundaries, AsyncLocalStorage\n\n### [database-patterns.md](database-patterns.md)\nPrismaService, repositories, transactions, optimization\n\n### [configuration.md](configuration.md)\nUnifiedConfig, environment configs, secrets\n\n### [async-and-errors.md](async-and-errors.md)\nAsync patterns, custom errors, asyncErrorWrapper\n\n### [testing-guide.md](testing-guide.md)\nUnit\u002Fintegration tests, mocking, coverage\n\n### [complete-examples.md](complete-examples.md)\nFull examples, refactoring guide\n\n---\n\n## Related Skills\n\n- **database-verification** - Verify column names and schema consistency\n- **error-tracking** - Sentry integration patterns\n- **skill-developer** - Meta-skill for creating and managing skills\n\n---\n\n**Skill Status**: COMPLETE ✅\n**Line Count**: \u003C 500 ✅\n**Progressive Disclosure**: 11 resource files ✅\n","# Backend Development Guidelines\n\n## Purpose\n\nEstablish consistency and best practices across backend microservices (blog-api, auth-service, notifications-service) using modern Node.js\u002FExpress\u002FTypeScript patterns.\n\n## When to Use This Skill\n\nAutomatically activates when working on:\n- Creating or modifying routes, endpoints, APIs\n- Building controllers, services, repositories\n- Implementing middleware (auth, validation, error handling)\n- Database operations with Prisma\n- Error tracking with Sentry\n- Input validation with Zod\n- Configuration management\n- Backend testing and refactoring\n\n---\n\n## Quick Start\n\n### New Backend Feature Checklist\n\n- [ ] **Route**: Clean definition, delegate to controller\n- [ ] **Controller**: Extend BaseController\n- [ ] **Service**: Business logic with DI\n- [ ] **Repository**: Database access (if complex)\n- [ ] **Validation**: Zod schema\n- [ ] **Sentry**: Error tracking\n- [ ] **Tests**: Unit + integration tests\n- [ ] **Config**: Use unifiedConfig\n\n### New Microservice Checklist\n\n- [ ] Directory structure (see [architecture-overview.md](architecture-overview.md))\n- [ ] instrument.ts for Sentry\n- [ ] unifiedConfig setup\n- [ ] BaseController class\n- [ ] Middleware stack\n- [ ] Error boundary\n- [ ] Testing framework\n\n---\n\n## Architecture Overview\n\n### Layered Architecture\n\n```\nHTTP Request\n    ↓\nRoutes (routing only)\n    ↓\nControllers (request handling)\n    ↓\nServices (business logic)\n    ↓\nRepositories (data access)\n    ↓\nDatabase (Prisma)\n```\n\n**Key Principle:** Each layer has ONE responsibility.\n\nSee [architecture-overview.md](architecture-overview.md) for complete details.\n\n---\n\n## Directory Structure\n\n```\nservice\u002Fsrc\u002F\n├── config\u002F              # UnifiedConfig\n├── controllers\u002F         # Request handlers\n├── services\u002F            # Business logic\n├── repositories\u002F        # Data access\n├── routes\u002F              # Route definitions\n├── middleware\u002F          # Express middleware\n├── types\u002F               # TypeScript types\n├── validators\u002F          # Zod schemas\n├── utils\u002F               # Utilities\n├── tests\u002F               # Tests\n├── instrument.ts        # Sentry (FIRST IMPORT)\n├── app.ts               # Express setup\n└── server.ts            # HTTP server\n```\n\n**Naming Conventions:**\n- Controllers: `PascalCase` - `UserController.ts`\n- Services: `camelCase` - `userService.ts`\n- Routes: `camelCase + Routes` - `userRoutes.ts`\n- Repositories: `PascalCase + Repository` - `UserRepository.ts`\n\n---\n\n## Core Principles (7 Key Rules)\n\n### 1. Routes Only Route, Controllers Control\n\n```typescript\n\u002F\u002F ❌ NEVER: Business logic in routes\nrouter.post('\u002Fsubmit', async (req, res) => {\n    \u002F\u002F 200 lines of logic\n});\n\n\u002F\u002F ✅ ALWAYS: Delegate to controller\nrouter.post('\u002Fsubmit', (req, res) => controller.submit(req, res));\n```\n\n### 2. All Controllers Extend BaseController\n\n```typescript\nexport class UserController extends BaseController {\n    async getUser(req: Request, res: Response): Promise\u003Cvoid> {\n        try {\n            const user = await this.userService.findById(req.params.id);\n            this.handleSuccess(res, user);\n        } catch (error) {\n            this.handleError(error, res, 'getUser');\n        }\n    }\n}\n```\n\n### 3. All Errors to Sentry\n\n```typescript\ntry {\n    await operation();\n} catch (error) {\n    Sentry.captureException(error);\n    throw error;\n}\n```\n\n### 4. Use unifiedConfig, NEVER process.env\n\n```typescript\n\u002F\u002F ❌ NEVER\nconst timeout = process.env.TIMEOUT_MS;\n\n\u002F\u002F ✅ ALWAYS\nimport { config } from '.\u002Fconfig\u002FunifiedConfig';\nconst timeout = config.timeouts.default;\n```\n\n### 5. Validate All Input with Zod\n\n```typescript\nconst schema = z.object({ email: z.string().email() });\nconst validated = schema.parse(req.body);\n```\n\n### 6. Use Repository Pattern for Data Access\n\n```typescript\n\u002F\u002F Service → Repository → Database\nconst users = await userRepository.findActive();\n```\n\n### 7. Comprehensive Testing Required\n\n```typescript\ndescribe('UserService', () => {\n    it('should create user', async () => {\n        expect(user).toBeDefined();\n    });\n});\n```\n\n---\n\n## Common Imports\n\n```typescript\n\u002F\u002F Express\nimport express, { Request, Response, NextFunction, Router } from 'express';\n\n\u002F\u002F Validation\nimport { z } from 'zod';\n\n\u002F\u002F Database\nimport { PrismaClient } from '@prisma\u002Fclient';\nimport type { Prisma } from '@prisma\u002Fclient';\n\n\u002F\u002F Sentry\nimport * as Sentry from '@sentry\u002Fnode';\n\n\u002F\u002F Config\nimport { config } from '.\u002Fconfig\u002FunifiedConfig';\n\n\u002F\u002F Middleware\nimport { SSOMiddlewareClient } from '.\u002Fmiddleware\u002FSSOMiddleware';\nimport { asyncErrorWrapper } from '.\u002Fmiddleware\u002FerrorBoundary';\n```\n\n---\n\n## Quick Reference\n\n### HTTP Status Codes\n\n| Code | Use Case |\n|------|----------|\n| 200 | Success |\n| 201 | Created |\n| 400 | Bad Request |\n| 401 | Unauthorized |\n| 403 | Forbidden |\n| 404 | Not Found |\n| 500 | Server Error |\n\n### Service Templates\n\n**Blog API** (✅ Mature) - Use as template for REST APIs\n**Auth Service** (✅ Mature) - Use as template for authentication patterns\n\n---\n\n## Anti-Patterns to Avoid\n\n❌ Business logic in routes\n❌ Direct process.env usage\n❌ Missing error handling\n❌ No input validation\n❌ Direct Prisma everywhere\n❌ console.log instead of Sentry\n\n---\n\n## Navigation Guide\n\n| Need to... | Read this |\n|------------|-----------|\n| Understand architecture | [architecture-overview.md](architecture-overview.md) |\n| Create routes\u002Fcontrollers | [routing-and-controllers.md](routing-and-controllers.md) |\n| Organize business logic | [services-and-repositories.md](services-and-repositories.md) |\n| Validate input | [validation-patterns.md](validation-patterns.md) |\n| Add error tracking | [sentry-and-monitoring.md](sentry-and-monitoring.md) |\n| Create middleware | [middleware-guide.md](middleware-guide.md) |\n| Database access | [database-patterns.md](database-patterns.md) |\n| Manage config | [configuration.md](configuration.md) |\n| Handle async\u002Ferrors | [async-and-errors.md](async-and-errors.md) |\n| Write tests | [testing-guide.md](testing-guide.md) |\n| See examples | [complete-examples.md](complete-examples.md) |\n\n---\n\n## Resource Files\n\n### [architecture-overview.md](architecture-overview.md)\nLayered architecture, request lifecycle, separation of concerns\n\n### [routing-and-controllers.md](routing-and-controllers.md)\nRoute definitions, BaseController, error handling, examples\n\n### [services-and-repositories.md](services-and-repositories.md)\nService patterns, DI, repository pattern, caching\n\n### [validation-patterns.md](validation-patterns.md)\nZod schemas, validation, DTO pattern\n\n### [sentry-and-monitoring.md](sentry-and-monitoring.md)\nSentry init, error capture, performance monitoring\n\n### [middleware-guide.md](middleware-guide.md)\nAuth, audit, error boundaries, AsyncLocalStorage\n\n### [database-patterns.md](database-patterns.md)\nPrismaService, repositories, transactions, optimization\n\n### [configuration.md](configuration.md)\nUnifiedConfig, environment configs, secrets\n\n### [async-and-errors.md](async-and-errors.md)\nAsync patterns, custom errors, asyncErrorWrapper\n\n### [testing-guide.md](testing-guide.md)\nUnit\u002Fintegration tests, mocking, coverage\n\n### [complete-examples.md](complete-examples.md)\nFull examples, refactoring guide\n\n---\n\n## Related Skills\n\n- **database-verification** - Verify column names and schema consistency\n- **error-tracking** - Sentry integration patterns\n- **skill-developer** - Meta-skill for creating and managing skills\n\n---\n\n**Skill Status**: COMPLETE ✅\n**Line Count**: \u003C 500 ✅\n**Progressive Disclosure**: 11 resource files ✅\n",{"name":5,"description":7},"main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fbackend-dev-guidelines",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":69,"prompt":79,"zipAvailable":80},[70,73,76],{"tool":71,"command":72},"npx","npx skills add davila7\u002Fclaude-code-templates --skill backend-dev-guidelines",{"tool":74,"command":75},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill backend-dev-guidelines",{"tool":77,"command":78},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill backend-dev-guidelines","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fbackend-dev-guidelines\u002FSKILL.md",true,[82,88,92,96,100,104,108,112,116,120,124],{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"resources\u002Farchitecture-overview.md","REFERENCE","参考文档",12866,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fbackend-dev-guidelines\u002Fresources\u002Farchitecture-overview.md",{"path":89,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":90,"sourceHtmlUrl":91},"resources\u002Fasync-and-errors.md",6862,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fbackend-dev-guidelines\u002Fresources\u002Fasync-and-errors.md",{"path":93,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":94,"sourceHtmlUrl":95},"resources\u002Fcomplete-examples.md",16478,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fbackend-dev-guidelines\u002Fresources\u002Fcomplete-examples.md",{"path":97,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":98,"sourceHtmlUrl":99},"resources\u002Fconfiguration.md",5816,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fbackend-dev-guidelines\u002Fresources\u002Fconfiguration.md",{"path":101,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":102,"sourceHtmlUrl":103},"resources\u002Fdatabase-patterns.md",4937,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fbackend-dev-guidelines\u002Fresources\u002Fdatabase-patterns.md",{"path":105,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":106,"sourceHtmlUrl":107},"resources\u002Fmiddleware-guide.md",5169,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fbackend-dev-guidelines\u002Fresources\u002Fmiddleware-guide.md",{"path":109,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":110,"sourceHtmlUrl":111},"resources\u002Frouting-and-controllers.md",19930,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fbackend-dev-guidelines\u002Fresources\u002Frouting-and-controllers.md",{"path":113,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":114,"sourceHtmlUrl":115},"resources\u002Fsentry-and-monitoring.md",7753,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fbackend-dev-guidelines\u002Fresources\u002Fsentry-and-monitoring.md",{"path":117,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":118,"sourceHtmlUrl":119},"resources\u002Fservices-and-repositories.md",22299,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fbackend-dev-guidelines\u002Fresources\u002Fservices-and-repositories.md",{"path":121,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":122,"sourceHtmlUrl":123},"resources\u002Ftesting-guide.md",5420,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fbackend-dev-guidelines\u002Fresources\u002Ftesting-guide.md",{"path":125,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":126,"sourceHtmlUrl":127},"resources\u002Fvalidation-patterns.md",18038,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fbackend-dev-guidelines\u002Fresources\u002Fvalidation-patterns.md",[129,157,184,214,249,270],{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":138,"publishedAt":53},"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",[135],{"categoryNo":136,"categoryName":137,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[139,140,141,142,143,34,144,145,38,146,147,148,149,150,151,152,153,154,155,156],"scoring","pool","wealthville pool scoring","liquidity","which","exit","now","when","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":164,"publishedAt":53},"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",[163],{"categoryNo":136,"categoryName":137,"taxonomyType":21,"taxonomyTypeDesc":22},[165,166,167,168,169,170,171,172,173,174,175,146,176,177,178,179,180,181,182,183],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":185,"name":186,"nameZh":6,"description":187,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":188,"categories":189,"keywords":197,"publishedAt":53},"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",[190,191,192],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":136,"categoryName":137,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":193,"categoryName":194,"taxonomyType":195,"taxonomyTypeDesc":196},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[198,199,200,201,202,203,204,34,205,206,207,208,209,210,211,38,212,45,146,213],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","query",{"skillNo":215,"name":216,"nameZh":6,"description":217,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":218,"licenseFileUrl":219,"sourceHtmlUrl":220,"categories":221,"keywords":225,"publishedAt":53},"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",[222],{"categoryNo":223,"categoryName":224,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[226,227,228,229,230,231,232,233,234,235,236,237,238,239,240,241,242,243,244,245,246,247,34,248],"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":250,"name":251,"nameZh":6,"description":252,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":218,"licenseFileUrl":253,"sourceHtmlUrl":254,"categories":255,"keywords":258,"publishedAt":53},"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",[256,257],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":223,"categoryName":224,"taxonomyType":21,"taxonomyTypeDesc":22},[259,42,260,261,262,227,263,236,237,264,265,266,267,34,268,148,269],"webapp testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":271,"name":272,"nameZh":6,"description":273,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":218,"licenseFileUrl":274,"sourceHtmlUrl":275,"categories":276,"keywords":284,"publishedAt":53},"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",[277,280,281],{"categoryNo":278,"categoryName":279,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":136,"categoryName":137,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":282,"categoryName":283,"taxonomyType":195,"taxonomyTypeDesc":196},"01JBSEEDCAT000000000000036","内容创作者",[285,286,287,288,289,290,291,292,229,293,239,176,294,295,296,297,298,210,299,146,300,301,302,303,304,154,305],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]