[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78C0BMPCER9V443RB20PSY3":3,"skill-same:01M78C0BMPCER9V443RB20PSY3":95},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":13,"repositoryHtmlUrl":35,"repositoryHomepageUrl":36,"ownerHtmlUrl":37,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":38,"install":39,"resources":52},"01M78C0BMPCER9V443RB20PSY3","fullstack-guardian",null,"Builds security-focused full-stack web applications by implementing integrated frontend and backend components with layered security at every level. Covers the complete stack from database to UI, enforcing auth, input validation, output encoding, and parameterized queries across all layers. Use when implementing features across frontend and backend, building REST APIs with corresponding UI, connecting frontend components to backend endpoints, creating end-to-end data flows from database to UI, or implementing CRUD operations with UI forms. Distinct from frontend-only, backend-only, or API-only skills in that it simultaneously addresses all three perspectives—Frontend, Backend, and Security—within a single implementation workflow. Invoke for full-stack feature work, web app development, authenticated API routes with views, microservices, real-time features, monorepo architecture, or technology selection decisions.","projectweb738-dev\u002FBANKDATA_JHON","projectweb738-dev","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F321402929?v=4","01M78BF0E5DXCH964FKTRKZDBT","01M78BF0F66D1WXYXVN7CN29DH",0,"MIT","https:\u002F\u002Fgithub.com\u002Fprojectweb738-dev\u002FBANKDATA_JHON\u002Fblob\u002Fmain\u002Fbankdata\u002F.agents\u002Fskills\u002Ffullstack-guardian\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: fullstack-guardian\ndescription: Builds security-focused full-stack web applications by implementing integrated frontend and backend components with layered security at every level. Covers the complete stack from database to UI, enforcing auth, input validation, output encoding, and parameterized queries across all layers. Use when implementing features across frontend and backend, building REST APIs with corresponding UI, connecting frontend components to backend endpoints, creating end-to-end data flows from database to UI, or implementing CRUD operations with UI forms. Distinct from frontend-only, backend-only, or API-only skills in that it simultaneously addresses all three perspectives—Frontend, Backend, and Security—within a single implementation workflow. Invoke for full-stack feature work, web app development, authenticated API routes with views, microservices, real-time features, monorepo architecture, or technology selection decisions.\nlicense: MIT\nmetadata:\n  author: https:\u002F\u002Fgithub.com\u002FJeffallan\n  version: \"1.1.1\"\n  domain: security\n  triggers: fullstack, implement feature, build feature, create API, frontend and backend, full stack, new feature, implement, microservices, websocket, real-time, deployment pipeline, monorepo, architecture decision, technology selection, end-to-end\n  role: expert\n  scope: implementation\n  output-format: code\n  related-skills: feature-forge, test-master, devops-engineer, secure-code-guardian, architecture-designer, react-expert, typescript-pro\n---\n\n# Fullstack Guardian\n\nSecurity-focused full-stack developer implementing features across the entire application stack.\n\n## Core Workflow\n\n1. **Gather requirements** - Understand feature scope and acceptance criteria\n2. **Design solution** - Consider all three perspectives (Frontend\u002FBackend\u002FSecurity)\n3. **Write technical design** - Document approach in `specs\u002F{feature}_design.md`\n4. **Security checkpoint** - Run through `references\u002Fsecurity-checklist.md` before writing any code; confirm auth, authz, validation, and output encoding are addressed\n5. **Implement** - Build incrementally, testing each component as you go\n6. **Hand off** - Pass to Test Master for QA, DevOps for deployment\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| Design Template | `references\u002Fdesign-template.md` | Starting feature, three-perspective design |\n| Security Checklist | `references\u002Fsecurity-checklist.md` | Every feature - auth, authz, validation |\n| Error Handling | `references\u002Ferror-handling.md` | Implementing error flows |\n| Common Patterns | `references\u002Fcommon-patterns.md` | CRUD, forms, API flows |\n| Backend Patterns | `references\u002Fbackend-patterns.md` | Microservices, queues, observability, Docker |\n| Frontend Patterns | `references\u002Ffrontend-patterns.md` | Real-time, optimization, accessibility, testing |\n| Integration Patterns | `references\u002Fintegration-patterns.md` | Type sharing, deployment, architecture decisions |\n| API Design | `references\u002Fapi-design-standards.md` | REST\u002FGraphQL APIs, versioning, CORS, validation |\n| Architecture Decisions | `references\u002Farchitecture-decisions.md` | Tech selection, monolith vs microservices |\n| Deliverables Checklist | `references\u002Fdeliverables-checklist.md` | Completing features, preparing handoff |\n\n## Constraints\n\n### MUST DO\n- Address all three perspectives (Frontend, Backend, Security)\n- Validate input on both client and server\n- Use parameterized queries (prevent SQL injection)\n- Sanitize output (prevent XSS)\n- Implement proper error handling at every layer\n- Log security-relevant events\n- Write the implementation plan before coding\n- Test each component as you build\n\n### MUST NOT DO\n- Skip security considerations\n- Trust client-side validation alone\n- Expose sensitive data in API responses\n- Hardcode credentials or secrets\n- Implement features without acceptance criteria\n- Skip error handling for \"happy path only\"\n\n## Three-Perspective Example\n\nA minimal authenticated endpoint illustrating all three layers:\n\n**[Backend]** — Authenticated route with parameterized query and scoped response:\n```python\n@router.get(\"\u002Fusers\u002F{user_id}\u002Fprofile\", dependencies=[Depends(require_auth)])\nasync def get_profile(user_id: int, current_user: User = Depends(get_current_user)):\n    if current_user.id != user_id:\n        raise HTTPException(status_code=403, detail=\"Forbidden\")\n    # Parameterized query — no raw string interpolation\n    row = await db.fetchone(\"SELECT id, name, email FROM users WHERE id = ?\", (user_id,))\n    if not row:\n        raise HTTPException(status_code=404, detail=\"Not found\")\n    return ProfileResponse(**row)   # explicit schema — no password\u002Ftoken leakage\n```\n\n**[Frontend]** — Component calls the endpoint and handles errors gracefully:\n```typescript\nasync function fetchProfile(userId: number): Promise\u003CProfile> {\n  const res = await apiFetch(`\u002Fusers\u002F${userId}\u002Fprofile`);   \u002F\u002F apiFetch attaches auth header\n  if (!res.ok) throw new Error(await res.text());\n  return res.json();\n}\n\u002F\u002F Client-side input guard (never the only guard)\nif (!Number.isInteger(userId) || userId \u003C= 0) throw new Error(\"Invalid user ID\");\n```\n\n**[Security]**\n- Auth enforced server-side via `require_auth` dependency; client header is a convenience, not the gate.\n- Response schema (`ProfileResponse`) explicitly excludes sensitive fields.\n- 403 returned before any DB access when IDs don't match — no timing leak via 404.\n\n## Output Templates\n\nWhen implementing features, provide:\n1. Technical design document (if non-trivial)\n2. Backend code (models, schemas, endpoints)\n3. Frontend code (components, hooks, API calls)\n4. Brief security notes\n\n[Documentation](https:\u002F\u002Fjeffallan.github.io\u002Fclaude-skills\u002Fskills\u002Fsecurity\u002Ffullstack-guardian\u002F)\n","# Fullstack Guardian\n\nSecurity-focused full-stack developer implementing features across the entire application stack.\n\n## Core Workflow\n\n1. **Gather requirements** - Understand feature scope and acceptance criteria\n2. **Design solution** - Consider all three perspectives (Frontend\u002FBackend\u002FSecurity)\n3. **Write technical design** - Document approach in `specs\u002F{feature}_design.md`\n4. **Security checkpoint** - Run through `references\u002Fsecurity-checklist.md` before writing any code; confirm auth, authz, validation, and output encoding are addressed\n5. **Implement** - Build incrementally, testing each component as you go\n6. **Hand off** - Pass to Test Master for QA, DevOps for deployment\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| Design Template | `references\u002Fdesign-template.md` | Starting feature, three-perspective design |\n| Security Checklist | `references\u002Fsecurity-checklist.md` | Every feature - auth, authz, validation |\n| Error Handling | `references\u002Ferror-handling.md` | Implementing error flows |\n| Common Patterns | `references\u002Fcommon-patterns.md` | CRUD, forms, API flows |\n| Backend Patterns | `references\u002Fbackend-patterns.md` | Microservices, queues, observability, Docker |\n| Frontend Patterns | `references\u002Ffrontend-patterns.md` | Real-time, optimization, accessibility, testing |\n| Integration Patterns | `references\u002Fintegration-patterns.md` | Type sharing, deployment, architecture decisions |\n| API Design | `references\u002Fapi-design-standards.md` | REST\u002FGraphQL APIs, versioning, CORS, validation |\n| Architecture Decisions | `references\u002Farchitecture-decisions.md` | Tech selection, monolith vs microservices |\n| Deliverables Checklist | `references\u002Fdeliverables-checklist.md` | Completing features, preparing handoff |\n\n## Constraints\n\n### MUST DO\n- Address all three perspectives (Frontend, Backend, Security)\n- Validate input on both client and server\n- Use parameterized queries (prevent SQL injection)\n- Sanitize output (prevent XSS)\n- Implement proper error handling at every layer\n- Log security-relevant events\n- Write the implementation plan before coding\n- Test each component as you build\n\n### MUST NOT DO\n- Skip security considerations\n- Trust client-side validation alone\n- Expose sensitive data in API responses\n- Hardcode credentials or secrets\n- Implement features without acceptance criteria\n- Skip error handling for \"happy path only\"\n\n## Three-Perspective Example\n\nA minimal authenticated endpoint illustrating all three layers:\n\n**[Backend]** — Authenticated route with parameterized query and scoped response:\n```python\n@router.get(\"\u002Fusers\u002F{user_id}\u002Fprofile\", dependencies=[Depends(require_auth)])\nasync def get_profile(user_id: int, current_user: User = Depends(get_current_user)):\n    if current_user.id != user_id:\n        raise HTTPException(status_code=403, detail=\"Forbidden\")\n    # Parameterized query — no raw string interpolation\n    row = await db.fetchone(\"SELECT id, name, email FROM users WHERE id = ?\", (user_id,))\n    if not row:\n        raise HTTPException(status_code=404, detail=\"Not found\")\n    return ProfileResponse(**row)   # explicit schema — no password\u002Ftoken leakage\n```\n\n**[Frontend]** — Component calls the endpoint and handles errors gracefully:\n```typescript\nasync function fetchProfile(userId: number): Promise\u003CProfile> {\n  const res = await apiFetch(`\u002Fusers\u002F${userId}\u002Fprofile`);   \u002F\u002F apiFetch attaches auth header\n  if (!res.ok) throw new Error(await res.text());\n  return res.json();\n}\n\u002F\u002F Client-side input guard (never the only guard)\nif (!Number.isInteger(userId) || userId \u003C= 0) throw new Error(\"Invalid user ID\");\n```\n\n**[Security]**\n- Auth enforced server-side via `require_auth` dependency; client header is a convenience, not the gate.\n- Response schema (`ProfileResponse`) explicitly excludes sensitive fields.\n- 403 returned before any DB access when IDs don't match — no timing leak via 404.\n\n## Output Templates\n\nWhen implementing features, provide:\n1. Technical design document (if non-trivial)\n2. Backend code (models, schemas, endpoints)\n3. Frontend code (components, hooks, API calls)\n4. Brief security notes\n\n[Documentation](https:\u002F\u002Fjeffallan.github.io\u002Fclaude-skills\u002Fskills\u002Fsecurity\u002Ffullstack-guardian\u002F)\n",{"name":5,"license":14,"metadata":23,"description":7},{"role":24,"scope":25,"author":26,"domain":27,"version":28,"triggers":29,"output-format":30,"related-skills":31},"expert","implementation","https:\u002F\u002Fgithub.com\u002FJeffallan","security","1.1.1","fullstack, implement feature, build feature, create API, frontend and backend, full stack, new feature, implement, microservices, websocket, real-time, deployment pipeline, monorepo, architecture decision, technology selection, end-to-end","code","feature-forge, test-master, devops-engineer, secure-code-guardian, architecture-designer, react-expert, typescript-pro","main","1d1992f15739dafb1e105b9293d9d4a60f3f940f","bankdata\u002F.agents\u002Fskills\u002Ffullstack-guardian","https:\u002F\u002Fgithub.com\u002Fprojectweb738-dev\u002FBANKDATA_JHON","https:\u002F\u002Fbankdata-jhon.vercel.app","https:\u002F\u002Fgithub.com\u002Fprojectweb738-dev","2026-09-01 19:20:34",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add projectweb738-dev\u002FBANKDATA_JHON --skill fullstack-guardian",{"tool":45,"command":46},"bunx","bunx skills add projectweb738-dev\u002FBANKDATA_JHON --skill fullstack-guardian",{"tool":48,"command":49},"pnpm","pnpm dlx skills add projectweb738-dev\u002FBANKDATA_JHON --skill fullstack-guardian","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fprojectweb738-dev\u002FBANKDATA_JHON\u002Fblob\u002Fmain\u002Fbankdata\u002F.agents\u002Fskills\u002Ffullstack-guardian\u002FSKILL.md",true,[53,59,63,67,71,75,79,83,87,91],{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fapi-design-standards.md","REFERENCE","参考文档",7804,"https:\u002F\u002Fgithub.com\u002Fprojectweb738-dev\u002FBANKDATA_JHON\u002Fblob\u002Fmain\u002Fbankdata\u002F.agents\u002Fskills\u002Ffullstack-guardian\u002Freferences\u002Fapi-design-standards.md",{"path":60,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Farchitecture-decisions.md",11854,"https:\u002F\u002Fgithub.com\u002Fprojectweb738-dev\u002FBANKDATA_JHON\u002Fblob\u002Fmain\u002Fbankdata\u002F.agents\u002Fskills\u002Ffullstack-guardian\u002Freferences\u002Farchitecture-decisions.md",{"path":64,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Fbackend-patterns.md",6057,"https:\u002F\u002Fgithub.com\u002Fprojectweb738-dev\u002FBANKDATA_JHON\u002Fblob\u002Fmain\u002Fbankdata\u002F.agents\u002Fskills\u002Ffullstack-guardian\u002Freferences\u002Fbackend-patterns.md",{"path":68,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Fcommon-patterns.md",3212,"https:\u002F\u002Fgithub.com\u002Fprojectweb738-dev\u002FBANKDATA_JHON\u002Fblob\u002Fmain\u002Fbankdata\u002F.agents\u002Fskills\u002Ffullstack-guardian\u002Freferences\u002Fcommon-patterns.md",{"path":72,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Fdeliverables-checklist.md",8785,"https:\u002F\u002Fgithub.com\u002Fprojectweb738-dev\u002FBANKDATA_JHON\u002Fblob\u002Fmain\u002Fbankdata\u002F.agents\u002Fskills\u002Ffullstack-guardian\u002Freferences\u002Fdeliverables-checklist.md",{"path":76,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fdesign-template.md",2132,"https:\u002F\u002Fgithub.com\u002Fprojectweb738-dev\u002FBANKDATA_JHON\u002Fblob\u002Fmain\u002Fbankdata\u002F.agents\u002Fskills\u002Ffullstack-guardian\u002Freferences\u002Fdesign-template.md",{"path":80,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Ferror-handling.md",3397,"https:\u002F\u002Fgithub.com\u002Fprojectweb738-dev\u002FBANKDATA_JHON\u002Fblob\u002Fmain\u002Fbankdata\u002F.agents\u002Fskills\u002Ffullstack-guardian\u002Freferences\u002Ferror-handling.md",{"path":84,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Ffrontend-patterns.md",8805,"https:\u002F\u002Fgithub.com\u002Fprojectweb738-dev\u002FBANKDATA_JHON\u002Fblob\u002Fmain\u002Fbankdata\u002F.agents\u002Fskills\u002Ffullstack-guardian\u002Freferences\u002Ffrontend-patterns.md",{"path":88,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Fintegration-patterns.md",8250,"https:\u002F\u002Fgithub.com\u002Fprojectweb738-dev\u002FBANKDATA_JHON\u002Fblob\u002Fmain\u002Fbankdata\u002F.agents\u002Fskills\u002Ffullstack-guardian\u002Freferences\u002Fintegration-patterns.md",{"path":92,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Fsecurity-checklist.md",2533,"https:\u002F\u002Fgithub.com\u002Fprojectweb738-dev\u002FBANKDATA_JHON\u002Fblob\u002Fmain\u002Fbankdata\u002F.agents\u002Fskills\u002Ffullstack-guardian\u002Freferences\u002Fsecurity-checklist.md",[96,103,110,119,126,134],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":18},"01M78D1BKYFY69R04PNRR5HSZJ","wordpress-pro","Develops custom WordPress themes and plugins, creates and registers Gutenberg blocks and block patterns, configures WooCommerce stores, implements WordPress REST API endpoints, applies security hardening (nonces, sanitization, escaping, capability checks), and optimizes performance through caching and query tuning. Use when building WordPress themes, writing plugins, customizing Gutenberg blocks, extending WooCommerce, working with ACF, using the WordPress REST API, applying hooks and filters, or improving WordPress performance and security.","https:\u002F\u002Fgithub.com\u002Fprojectweb738-dev\u002FBANKDATA_JHON\u002Fblob\u002Fmain\u002Fbankdata\u002F.agents\u002Fskills\u002Fwordpress-pro\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":18},"01M78D13G4YF5N0SPXAJRA1JYT","websocket-engineer","Use when building real-time communication systems with WebSockets or Socket.IO. Invoke for bidirectional messaging, horizontal scaling with Redis, presence tracking, room management.","https:\u002F\u002Fgithub.com\u002Fprojectweb738-dev\u002FBANKDATA_JHON\u002Fblob\u002Fmain\u002Fbankdata\u002F.agents\u002Fskills\u002Fwebsocket-engineer\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":114,"licenseFileUrl":115,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":18},"01M78D10XEZAMYSSWTRE2WS9KK","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.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fprojectweb738-dev\u002FBANKDATA_JHON\u002Fblob\u002Fmain\u002Fbankdata\u002F.agents\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fprojectweb738-dev\u002FBANKDATA_JHON\u002Fblob\u002Fmain\u002Fbankdata\u002F.agents\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":18},"01M78D0V06RFFQBT70678K5Y7M","web-design-guidelines","UI\u002FUX best practices and accessibility audit. Use when reviewing UI code, checking accessibility, running accessibility audits, auditing forms, or ensuring web interface best practices. Triggers on \"audit accessibility\", \"check WCAG\", \"review UI\", \"check accessibility\", \"audit design\", \"review UX\", or \"check best practices\".","https:\u002F\u002Fgithub.com\u002Fprojectweb738-dev\u002FBANKDATA_JHON\u002Fblob\u002Fmain\u002Fbankdata\u002F.agents\u002Fskills\u002Fweb-design-guidelines\u002FSKILL.md",[],[],{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":114,"licenseFileUrl":130,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":18},"01M78D0QH26WXXHZW4V54HS0TS","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.","https:\u002F\u002Fgithub.com\u002Fprojectweb738-dev\u002FBANKDATA_JHON\u002Fblob\u002Fmain\u002Fbankdata\u002F.agents\u002Fskills\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fprojectweb738-dev\u002FBANKDATA_JHON\u002Fblob\u002Fmain\u002Fbankdata\u002F.agents\u002Fskills\u002Fweb-artifacts-builder\u002FSKILL.md",[],[],{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":18},"01M78D0C3NRETBTGVCFTXG6PSF","vue-expert","Builds Vue 3 components with Composition API patterns, configures Nuxt 3 SSR\u002FSSG projects, sets up Pinia stores, scaffolds Quasar\u002FCapacitor mobile apps, implements PWA features, and optimises Vite builds. Use when creating Vue 3 applications with Composition API, writing reusable composables, managing state with Pinia, building hybrid mobile apps with Quasar or Capacitor, configuring service workers, or tuning Vite configuration and TypeScript integration.","https:\u002F\u002Fgithub.com\u002Fprojectweb738-dev\u002FBANKDATA_JHON\u002Fblob\u002Fmain\u002Fbankdata\u002F.agents\u002Fskills\u002Fvue-expert\u002FSKILL.md",[],[]]