[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71N7Y9PE6FD2KHJCVS390JC":3,"skill-same:01M71N7Y9PE6FD2KHJCVS390JC":95},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":57,"commitSha":58,"skillDirectory":59,"forksCount":14,"repositoryHtmlUrl":60,"repositoryHomepageUrl":61,"ownerHtmlUrl":62,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":63,"install":64,"resources":76},"01M71N7Y9PE6FD2KHJCVS390JC","golang-error-handling",null,"Idiomatic Golang error handling — creation, wrapping with %w, errors.Is\u002FAs, errors.Join, custom error types, sentinel errors, panic\u002Frecover, the single handling rule, structured logging with slog, HTTP request logging middleware, and samber\u002Foops for production errors. Built to make logs usable at scale with log aggregation 3rd-party tools. Apply when creating, wrapping, inspecting, or logging errors in Go code. For samber\u002Foops specifics → See `samber\u002Fcc-skills-golang@golang-samber-oops` skill; for slog handler ecosystem → See `samber\u002Fcc-skills-golang@golang-samber-slog` skill.","pattanation\u002FNorvik","pattanation","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235419268?v=4","01M71M5THHYYB15ME8R2E4FCZG","Patta","01M71M5TJM1NDM992M8PDKYR2K",0,"MIT","https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Fgolang-error-handling\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"golang error handling","error handling","golang","error","request","structured logging","log","logs","code","http request","Bash","when","join","errors","middleware","creation","types","ecosystem","projects","ai coding agents","2026-11-10 10:56:23",false,"---\nname: golang-error-handling\ndescription: \"Idiomatic Golang error handling — creation, wrapping with %w, errors.Is\u002FAs, errors.Join, custom error types, sentinel errors, panic\u002Frecover, the single handling rule, structured logging with slog, HTTP request logging middleware, and samber\u002Foops for production errors. Built to make logs usable at scale with log aggregation 3rd-party tools. Apply when creating, wrapping, inspecting, or logging errors in Go code. For samber\u002Foops specifics → See `samber\u002Fcc-skills-golang@golang-samber-oops` skill; for slog handler ecosystem → See `samber\u002Fcc-skills-golang@golang-samber-slog` skill.\"\nuser-invocable: true\nlicense: MIT\ncompatibility: Designed for Claude Code or similar AI coding agents, and for projects using Golang.\nmetadata:\n  author: samber\n  version: \"1.2.1\"\n  openclaw:\n    emoji: \"⚠\"\n    homepage: https:\u002F\u002Fgithub.com\u002Fsamber\u002Fcc-skills-golang\n    requires:\n      bins:\n        - go\n    install: []\nallowed-tools: Read Edit Write Glob Grep Bash(go:*) Bash(golangci-lint:*) Bash(git:*) Agent\n---\n\n**Persona:** You are a Go reliability engineer. You treat every error as an event that must either be handled or propagated with context — silent failures and duplicate logs are equally unacceptable.\n\n**Orchestration mode:** Use `ultracode` for auditing error handling across a large codebase — orchestrate the five category sub-agents described in the \"Parallelizing Error Handling Audits\" section (creation, wrapping, single-handling rule, panic\u002Frecover, structured logging) and consolidate their findings.\n\n**Modes:**\n\n- **Coding mode** — writing new error handling code. Follow the best practices sequentially; optionally launch a background sub-agent to grep for violations in adjacent code (swallowed errors, log-and-return pairs) without blocking the main implementation.\n- **Review mode** — reviewing a PR's error handling changes. Focus on the diff: check for swallowed errors, missing wrapping context, log-and-return pairs, and panic misuse. Sequential.\n- **Audit mode** — auditing existing error handling across a codebase. Use up to 5 parallel sub-agents, each targeting an independent category (creation, wrapping, single-handling rule, panic\u002Frecover, structured logging).\n\n> **Community default.** A company skill that explicitly supersedes `samber\u002Fcc-skills-golang@golang-error-handling` skill takes precedence.\n\n# Go Error Handling Best Practices\n\nThis skill guides the creation of robust, idiomatic error handling in Go applications. Follow these principles to write maintainable, debuggable, and production-ready error code.\n\n## Best Practices Summary\n\n1. **Returned errors MUST always be checked** — NEVER discard with `_`\n2. **Errors MUST be wrapped with context** using `fmt.Errorf(\"{context}: %w\", err)`\n3. **Error strings MUST be lowercase**, without trailing punctuation\n4. **Use `%w` internally, `%v` at system boundaries** to control error chain exposure\n5. **MUST use `errors.Is` for sentinel matching and `errors.As`\u002F`errors.AsType` for typed chain inspection** instead of direct comparison or bare type assertions. For Go 1.26+, prefer `errors.AsType[T](err)` when `T` implements `error`; use `errors.As(err, &target)` for Go \u003C1.26 or for non-error interface targets.\n6. **SHOULD use `errors.Join`** (Go 1.20+) to combine independent errors\n7. **Errors MUST be either logged OR returned**, NEVER both (single handling rule)\n8. **Use sentinel errors** for expected conditions, custom types for carrying data\n9. **NEVER use `panic` for expected error conditions** — reserve for truly unrecoverable states\n10. **SHOULD use `slog`** (Go 1.21+) for structured error logging — not `fmt.Println` or `log.Printf`\n11. **Use `samber\u002Foops`** for production errors needing stack traces, user\u002Ftenant context, or structured attributes\n12. **Log HTTP requests** with structured middleware capturing method, path, status, and duration\n13. **Use log levels** to indicate error severity\n14. **Never expose technical errors to users** — translate internal errors to user-friendly messages, log technical details separately\n15. **Keep log grouping low-cardinality** — at logging\u002FAPM boundaries, keep message templates stable and attach IDs, paths, line numbers, and counts as structured attributes. Error values may include useful operational context, but avoid putting high-cardinality data into the stable log message used for grouping.\n\n## Detailed Reference\n\n- **[Error Creation](.\u002Freferences\u002Ferror-creation.md)** — How to create errors that tell the story: error messages should be lowercase, no punctuation, and describe what happened without prescribing action. Covers sentinel errors (one-time preallocation for performance), custom error types (for carrying rich context), and the decision table for which to use when.\n\n- **[Error Wrapping and Inspection](.\u002Freferences\u002Ferror-wrapping.md)** — Why `fmt.Errorf(\"{context}: %w\", err)` beats `fmt.Errorf(\"{context}: %v\", err)` (chains vs concatenation). How to inspect chains with `errors.Is`, `errors.As`, and Go 1.26+ `errors.AsType` for type-safe error handling, and `errors.Join` for combining independent errors.\n\n- **[Error Handling Patterns and Logging](.\u002Freferences\u002Ferror-handling.md)** — The single handling rule: errors are either logged OR returned, NEVER both (prevents duplicate logs cluttering aggregators). Panic\u002Frecover design, `samber\u002Foops` for production errors, and `slog` structured logging integration for APM tools.\n\n## Parallelizing Error Handling Audits\n\nWhen auditing error handling across a large codebase, use up to 5 parallel sub-agents (via the Agent tool) — each targets an independent error category:\n\n- Sub-agent 1: Error creation — validate `errors.New`\u002F`fmt.Errorf` usage, low-cardinality messages, custom types\n- Sub-agent 2: Error wrapping — audit `%w` vs `%v`, verify `errors.Is`\u002F`errors.As` patterns\n- Sub-agent 3: Single handling rule — find log-and-return violations, swallowed errors, discarded errors (`_`)\n- Sub-agent 4: Panic\u002Frecover — audit `panic` usage, verify recovery at goroutine boundaries\n- Sub-agent 5: Structured logging — verify `slog` usage at error sites, check for PII in error messages\n\n## Cross-References\n\n- → See `samber\u002Fcc-skills-golang@golang-samber-oops` for full samber\u002Foops API, builder patterns, and logger integration\n- → See `samber\u002Fcc-skills-golang@golang-observability` for structured logging setup, log levels, and request logging middleware\n- → See `samber\u002Fcc-skills-golang@golang-safety` for nil interface trap and nil error comparison pitfalls\n- → See `samber\u002Fcc-skills-golang@golang-naming` for error naming conventions (ErrNotFound, PathError)\n- → See `samber\u002Fcc-skills-golang@golang-continuous-integration` skill for automated AI-driven code review in CI using these guidelines\n\n## References\n\n- [lmittmann\u002Ftint](https:\u002F\u002Fgithub.com\u002Flmittmann\u002Ftint)\n- [samber\u002Foops](https:\u002F\u002Fgithub.com\u002Fsamber\u002Foops)\n- [samber\u002Fslog-multi](https:\u002F\u002Fgithub.com\u002Fsamber\u002Fslog-multi)\n- [samber\u002Fslog-sampling](https:\u002F\u002Fgithub.com\u002Fsamber\u002Fslog-sampling)\n- [samber\u002Fslog-formatter](https:\u002F\u002Fgithub.com\u002Fsamber\u002Fslog-formatter)\n- [samber\u002Fslog-http](https:\u002F\u002Fgithub.com\u002Fsamber\u002Fslog-http)\n- [samber\u002Fslog-sentry](https:\u002F\u002Fgithub.com\u002Fsamber\u002Fslog-sentry)\n- [log\u002Fslog package](https:\u002F\u002Fpkg.go.dev\u002Flog\u002Fslog)\n","**Persona:** You are a Go reliability engineer. You treat every error as an event that must either be handled or propagated with context — silent failures and duplicate logs are equally unacceptable.\n\n**Orchestration mode:** Use `ultracode` for auditing error handling across a large codebase — orchestrate the five category sub-agents described in the \"Parallelizing Error Handling Audits\" section (creation, wrapping, single-handling rule, panic\u002Frecover, structured logging) and consolidate their findings.\n\n**Modes:**\n\n- **Coding mode** — writing new error handling code. Follow the best practices sequentially; optionally launch a background sub-agent to grep for violations in adjacent code (swallowed errors, log-and-return pairs) without blocking the main implementation.\n- **Review mode** — reviewing a PR's error handling changes. Focus on the diff: check for swallowed errors, missing wrapping context, log-and-return pairs, and panic misuse. Sequential.\n- **Audit mode** — auditing existing error handling across a codebase. Use up to 5 parallel sub-agents, each targeting an independent category (creation, wrapping, single-handling rule, panic\u002Frecover, structured logging).\n\n> **Community default.** A company skill that explicitly supersedes `samber\u002Fcc-skills-golang@golang-error-handling` skill takes precedence.\n\n# Go Error Handling Best Practices\n\nThis skill guides the creation of robust, idiomatic error handling in Go applications. Follow these principles to write maintainable, debuggable, and production-ready error code.\n\n## Best Practices Summary\n\n1. **Returned errors MUST always be checked** — NEVER discard with `_`\n2. **Errors MUST be wrapped with context** using `fmt.Errorf(\"{context}: %w\", err)`\n3. **Error strings MUST be lowercase**, without trailing punctuation\n4. **Use `%w` internally, `%v` at system boundaries** to control error chain exposure\n5. **MUST use `errors.Is` for sentinel matching and `errors.As`\u002F`errors.AsType` for typed chain inspection** instead of direct comparison or bare type assertions. For Go 1.26+, prefer `errors.AsType[T](err)` when `T` implements `error`; use `errors.As(err, &target)` for Go \u003C1.26 or for non-error interface targets.\n6. **SHOULD use `errors.Join`** (Go 1.20+) to combine independent errors\n7. **Errors MUST be either logged OR returned**, NEVER both (single handling rule)\n8. **Use sentinel errors** for expected conditions, custom types for carrying data\n9. **NEVER use `panic` for expected error conditions** — reserve for truly unrecoverable states\n10. **SHOULD use `slog`** (Go 1.21+) for structured error logging — not `fmt.Println` or `log.Printf`\n11. **Use `samber\u002Foops`** for production errors needing stack traces, user\u002Ftenant context, or structured attributes\n12. **Log HTTP requests** with structured middleware capturing method, path, status, and duration\n13. **Use log levels** to indicate error severity\n14. **Never expose technical errors to users** — translate internal errors to user-friendly messages, log technical details separately\n15. **Keep log grouping low-cardinality** — at logging\u002FAPM boundaries, keep message templates stable and attach IDs, paths, line numbers, and counts as structured attributes. Error values may include useful operational context, but avoid putting high-cardinality data into the stable log message used for grouping.\n\n## Detailed Reference\n\n- **[Error Creation](.\u002Freferences\u002Ferror-creation.md)** — How to create errors that tell the story: error messages should be lowercase, no punctuation, and describe what happened without prescribing action. Covers sentinel errors (one-time preallocation for performance), custom error types (for carrying rich context), and the decision table for which to use when.\n\n- **[Error Wrapping and Inspection](.\u002Freferences\u002Ferror-wrapping.md)** — Why `fmt.Errorf(\"{context}: %w\", err)` beats `fmt.Errorf(\"{context}: %v\", err)` (chains vs concatenation). How to inspect chains with `errors.Is`, `errors.As`, and Go 1.26+ `errors.AsType` for type-safe error handling, and `errors.Join` for combining independent errors.\n\n- **[Error Handling Patterns and Logging](.\u002Freferences\u002Ferror-handling.md)** — The single handling rule: errors are either logged OR returned, NEVER both (prevents duplicate logs cluttering aggregators). Panic\u002Frecover design, `samber\u002Foops` for production errors, and `slog` structured logging integration for APM tools.\n\n## Parallelizing Error Handling Audits\n\nWhen auditing error handling across a large codebase, use up to 5 parallel sub-agents (via the Agent tool) — each targets an independent error category:\n\n- Sub-agent 1: Error creation — validate `errors.New`\u002F`fmt.Errorf` usage, low-cardinality messages, custom types\n- Sub-agent 2: Error wrapping — audit `%w` vs `%v`, verify `errors.Is`\u002F`errors.As` patterns\n- Sub-agent 3: Single handling rule — find log-and-return violations, swallowed errors, discarded errors (`_`)\n- Sub-agent 4: Panic\u002Frecover — audit `panic` usage, verify recovery at goroutine boundaries\n- Sub-agent 5: Structured logging — verify `slog` usage at error sites, check for PII in error messages\n\n## Cross-References\n\n- → See `samber\u002Fcc-skills-golang@golang-samber-oops` for full samber\u002Foops API, builder patterns, and logger integration\n- → See `samber\u002Fcc-skills-golang@golang-observability` for structured logging setup, log levels, and request logging middleware\n- → See `samber\u002Fcc-skills-golang@golang-safety` for nil interface trap and nil error comparison pitfalls\n- → See `samber\u002Fcc-skills-golang@golang-naming` for error naming conventions (ErrNotFound, PathError)\n- → See `samber\u002Fcc-skills-golang@golang-continuous-integration` skill for automated AI-driven code review in CI using these guidelines\n\n## References\n\n- [lmittmann\u002Ftint](https:\u002F\u002Fgithub.com\u002Flmittmann\u002Ftint)\n- [samber\u002Foops](https:\u002F\u002Fgithub.com\u002Fsamber\u002Foops)\n- [samber\u002Fslog-multi](https:\u002F\u002Fgithub.com\u002Fsamber\u002Fslog-multi)\n- [samber\u002Fslog-sampling](https:\u002F\u002Fgithub.com\u002Fsamber\u002Fslog-sampling)\n- [samber\u002Fslog-formatter](https:\u002F\u002Fgithub.com\u002Fsamber\u002Fslog-formatter)\n- [samber\u002Fslog-http](https:\u002F\u002Fgithub.com\u002Fsamber\u002Fslog-http)\n- [samber\u002Fslog-sentry](https:\u002F\u002Fgithub.com\u002Fsamber\u002Fslog-sentry)\n- [log\u002Fslog package](https:\u002F\u002Fpkg.go.dev\u002Flog\u002Fslog)\n",{"name":5,"license":15,"metadata":44,"description":7,"allowed-tools":54,"compatibility":55,"user-invocable":56},{"author":45,"version":46,"openclaw":47},"samber","1.2.1",{"emoji":48,"install":49,"homepage":50,"requires":51},"⚠",[],"https:\u002F\u002Fgithub.com\u002Fsamber\u002Fcc-skills-golang",{"bins":52},[53],"go","Read Edit Write Glob Grep Bash(go:*) Bash(golangci-lint:*) Bash(git:*) Agent","Designed for Claude Code or similar AI coding agents, and for projects using Golang.",true,"claude\u002Finstall-gsd-build-foQdV","d86cd127f527124b5fd0fd0bc679a4d79b7d01d7",".agents\u002Fskills\u002Fgolang-error-handling","https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik","https:\u002F\u002Fnorvik-orpin.vercel.app","https:\u002F\u002Fgithub.com\u002Fpattanation","2026-07-17 11:17:04",{"source":8,"skillName":5,"commands":65,"prompt":75,"zipAvailable":56},[66,69,72],{"tool":67,"command":68},"npx","npx skills add pattanation\u002FNorvik --skill golang-error-handling",{"tool":70,"command":71},"bunx","bunx skills add pattanation\u002FNorvik --skill golang-error-handling",{"tool":73,"command":74},"pnpm","pnpm dlx skills add pattanation\u002FNorvik --skill golang-error-handling","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Fgolang-error-handling\u002FSKILL.md",[77,83,87,91],{"path":78,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":82},"evals\u002Fevals.json","REFERENCE","参考文档",14988,"https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Fgolang-error-handling\u002Fevals\u002Fevals.json",{"path":84,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Ferror-creation.md",5175,"https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Fgolang-error-handling\u002Freferences\u002Ferror-creation.md",{"path":88,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Ferror-handling.md",4275,"https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Fgolang-error-handling\u002Freferences\u002Ferror-handling.md",{"path":92,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Ferror-wrapping.md",3026,"https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Fgolang-error-handling\u002Freferences\u002Ferror-wrapping.md",[96,130,156,179,201,216],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":100,"licenseFileUrl":101,"sourceHtmlUrl":102,"categories":103,"keywords":112,"publishedAt":129},"01M71QDV4DM8T19HEHWATEF1K4","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\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[104,109],{"categoryNo":105,"categoryName":106,"taxonomyType":107,"taxonomyTypeDesc":108},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":110,"categoryName":111,"taxonomyType":107,"taxonomyTypeDesc":108},"01JBSEEDCAT000000000000009","前端开发",[113,114,115,116,117,118,119,120,121,26,122,123,124,125,126,127,128],"webapp","testing","webapp testing","for","applications","local","frontend","debugging","toolkit","browser","with","playwright","web","behavior","ui","screenshots","2026-11-10 13:02:02",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":100,"licenseFileUrl":134,"sourceHtmlUrl":135,"categories":136,"keywords":138,"publishedAt":129},"01M71QDH2GGMXGA9105C9W1N7B","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\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Fweb-artifacts-builder\u002FSKILL.md",[137],{"categoryNo":110,"categoryName":111,"taxonomyType":107,"taxonomyTypeDesc":108},[139,140,141,125,142,143,144,116,145,146,119,147,148,149,150,151,152,153,154,155],"builder","artifacts builder","artifacts","web artifacts builder","single-file","css","Tailwind","ui components","single","use","file","components","react","multi","state","routing","state management",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":160,"sourceHtmlUrl":161,"categories":162,"keywords":164,"publishedAt":129},"01M71QD9T2XC3EWMQNN9ACNWQ1","vueuse-functions","Apply VueUse composables where appropriate to build concise, maintainable Vue.js \u002F Nuxt features.","https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Fvueuse-functions\u002FLICENSE.md","https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Fvueuse-functions\u002FSKILL.md",[163],{"categoryNo":110,"categoryName":111,"taxonomyType":107,"taxonomyTypeDesc":108},[165,166,167,168,169,170,171,172,173,174,175,176,177,178],"functions","vueuse","vueuse functions","project","nuxt","apply","github","concise","build","https","features","vue","js","composables",{"skillNo":180,"name":181,"nameZh":6,"description":182,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":183,"sourceHtmlUrl":184,"categories":185,"keywords":188,"publishedAt":129},"01M71QD51HWSGYMCMB7RW7PGK8","vue-testing-best-practices","Use for Vue.js testing. Covers Vitest, Vue Test Utils, component testing, mocking, testing patterns, and Playwright for E2E testing.","https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Fvue-testing-best-practices\u002FLICENSE.md","https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Fvue-testing-best-practices\u002FSKILL.md",[186,187],{"categoryNo":105,"categoryName":106,"taxonomyType":107,"taxonomyTypeDesc":108},{"categoryNo":110,"categoryName":111,"taxonomyType":107,"taxonomyTypeDesc":108},[189,114,190,176,191,124,192,193,194,171,195,116,196,197,198,148,199,177,200],"vue testing best practices","testing best practices","best practices","test","testing patterns","component","vitest","mocking","e2e","utils","patterns","e2e testing",{"skillNo":202,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":205,"sourceHtmlUrl":206,"categories":207,"keywords":209,"publishedAt":129},"01M71QD358H2DJ9THJRBP77T3T","vue-router-best-practices","Vue Router 4 patterns, navigation guards, route params, and route-component lifecycle interactions.","https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Fvue-router-best-practices\u002FLICENSE.md","https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Fvue-router-best-practices\u002FSKILL.md",[208],{"categoryNo":110,"categoryName":111,"taxonomyType":107,"taxonomyTypeDesc":108},[210,176,211,191,212,194,213,171,199,214,215],"router","vue router best practices","route","guards","navigation","lifecycle",{"skillNo":217,"name":218,"nameZh":6,"description":219,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":220,"sourceHtmlUrl":221,"categories":222,"keywords":224,"publishedAt":129},"01M71QCYPNWDE2MQZ1TF3ED5S4","vue-best-practices","MUST be used for Vue.js tasks. Strongly recommends Composition API with `\u003Cscript setup>` and TypeScript as the standard approach. Covers Vue 3, SSR, Volar, vue-tsc. Load for any Vue, .vue files, Vue Router, Pinia, or Vite with Vue work. ALWAYS use Composition API unless the project explicitly requires Options API.","https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Fvue-best-practices\u002FLICENSE.md","https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Fvue-best-practices\u002FSKILL.md",[223],{"categoryNo":110,"categoryName":111,"taxonomyType":107,"taxonomyTypeDesc":108},[225,176,191,226,168,227,228,229,210,230,231,232,233,234,235,116,236,148,237,238],"vue best practices","Composition","files","tasks","api","pinia","work","options","ssr","typescript","as","vite","load","standard"]