[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C77ZR2TZ4T4FS047K6VB7S":3,"skill-same:01M7C77ZR2TZ4T4FS047K6VB7S":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7C77ZR2TZ4T4FS047K6VB7S","grug-review",null,"Review changed code for proven bugs and harmful complection. Use for a diff, pull request, or changed files. Every finding needs a concrete failure or a concrete simpler version.","stepankuzmin\u002Fsvenska-app","stepankuzmin","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F533564?v=4","01M7ADH01MGRSMC0YNW589Q6CE","Stepan Kuzmin","01M7C74QGFNTQ4J5AA0QJVZ102",0,"MIT","https:\u002F\u002Fgithub.com\u002Fstepankuzmin\u002Fsvenska-app\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgrug-review\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: grug-review\ndescription: Review changed code for proven bugs and harmful complection. Use for a diff, pull request, or changed files. Every finding needs a concrete failure or a concrete simpler version.\n---\n\n# Grug review\n\nGrug does not invent findings. If grug cannot prove it, grug drops it.\n\n## Read the change\n\nRead the user request, plan, or specification when available, and state the\nchange's intent in one sentence. If you cannot, ask. Check its required\nbehavior, constraints, preserved behavior, and non-goals. Review changed lines\nand directly affected final code, including old code the change should have\ndeleted.\n\nAsk why odd code exists. Skip generated files, lockfiles, vendored code, and\nformatter or linter issues.\n\n## Prove correctness\n\nPost only when you can name the input or state, reachable path, and observable\nwrong result. Unauthorized access or data exposure is a wrong result.\n\nBefore posting, check whether the same function or caller already handles the\ncase and whether an apparently unused item is used by the type system.\n\n## Prove complection\n\nPost only when you can write simpler final code and say what it gives up.\n\nLook for dual authority, policy spread across callers, effects mixed into\ndecisions, or lifecycle state that changes no allowed events.\n\nLook for indirection that hides no work: a name for a value used once, a\nfactory the type already describes, a layer that only renames what it wraps, or\na file with one caller. Every read pays for the jump between files.\n\nThree real callers or a trust boundary may justify an abstraction. They do not\nprove it. A deep module hides hard work behind a small interface. Keep one\nauthority for each decision.\n\nTreat every new comment or explanatory docstring as a complection finding.\nReplace it with clear names or structure. Keep only legal headers, public API\ncontracts, issue or RFC links, and behavior forced by a dependency we cannot\nchange. A comment explaining our own surprising code means the code should\nchange. A comment saying \"do not remove\" or \"important\" is a claim: check it\nwith the grug-explore or why skill, and when it holds, propose a type, test, or lint that\nenforces it instead.\n\nA new lint or type suppression that silences a correctness rule is a\ncorrectness finding.\n\n## Report\n\nPost at most five findings, most important first.\n\n- A correctness finding names the file, line, failure, and fix.\n- A complection finding names the file, line, simpler version, and tradeoff.\n\nOutput findings only. If none pass, write exactly: `No issues found.`\n\nFinish after the findings. When the user wants fixes, suggest grug-implement.\nSuggest grug-design only when the review exposes an unresolved design choice.\n","# Grug review\n\nGrug does not invent findings. If grug cannot prove it, grug drops it.\n\n## Read the change\n\nRead the user request, plan, or specification when available, and state the\nchange's intent in one sentence. If you cannot, ask. Check its required\nbehavior, constraints, preserved behavior, and non-goals. Review changed lines\nand directly affected final code, including old code the change should have\ndeleted.\n\nAsk why odd code exists. Skip generated files, lockfiles, vendored code, and\nformatter or linter issues.\n\n## Prove correctness\n\nPost only when you can name the input or state, reachable path, and observable\nwrong result. Unauthorized access or data exposure is a wrong result.\n\nBefore posting, check whether the same function or caller already handles the\ncase and whether an apparently unused item is used by the type system.\n\n## Prove complection\n\nPost only when you can write simpler final code and say what it gives up.\n\nLook for dual authority, policy spread across callers, effects mixed into\ndecisions, or lifecycle state that changes no allowed events.\n\nLook for indirection that hides no work: a name for a value used once, a\nfactory the type already describes, a layer that only renames what it wraps, or\na file with one caller. Every read pays for the jump between files.\n\nThree real callers or a trust boundary may justify an abstraction. They do not\nprove it. A deep module hides hard work behind a small interface. Keep one\nauthority for each decision.\n\nTreat every new comment or explanatory docstring as a complection finding.\nReplace it with clear names or structure. Keep only legal headers, public API\ncontracts, issue or RFC links, and behavior forced by a dependency we cannot\nchange. A comment explaining our own surprising code means the code should\nchange. A comment saying \"do not remove\" or \"important\" is a claim: check it\nwith the grug-explore or why skill, and when it holds, propose a type, test, or lint that\nenforces it instead.\n\nA new lint or type suppression that silences a correctness rule is a\ncorrectness finding.\n\n## Report\n\nPost at most five findings, most important first.\n\n- A correctness finding names the file, line, failure, and fix.\n- A complection finding names the file, line, simpler version, and tradeoff.\n\nOutput findings only. If none pass, write exactly: `No issues found.`\n\nFinish after the findings. When the user wants fixes, suggest grug-implement.\nSuggest grug-design only when the review exposes an unresolved design choice.\n",{"name":5,"description":7},"main","982185840176c21a4953df3e87e85c484a6369d0",".agents\u002Fskills\u002Fgrug-review","https:\u002F\u002Fgithub.com\u002Fstepankuzmin\u002Fsvenska-app","https:\u002F\u002Fsvenska-app.stepan-kuzmin.workers.dev\u002F","https:\u002F\u002Fgithub.com\u002Fstepankuzmin","https:\u002F\u002Fstepankuzmin.com\u002F","Software Engineer at @Mapbox","2026-11-14 23:14:58",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add stepankuzmin\u002Fsvenska-app --skill grug-review",{"tool":39,"command":40},"bunx","bunx skills add stepankuzmin\u002Fsvenska-app --skill grug-review",{"tool":42,"command":43},"pnpm","pnpm dlx skills add stepankuzmin\u002Fsvenska-app --skill grug-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fstepankuzmin\u002Fsvenska-app\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgrug-review\u002FSKILL.md",true,[],[48,54,61,68,75,82],{"skillNo":49,"name":50,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7C7CWDP33VRCNNQ2X0Z2WVY","code-review","https:\u002F\u002Fgithub.com\u002Fstepankuzmin\u002Fsvenska-app\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcode-review\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7C7CSQ125KWMD152RVMEVR2","wrangler","Run or troubleshoot Wrangler CLI commands in projects that have a wrangler.jsonc, wrangler.json, or wrangler.toml file, including local development, Previews, deployment, and resource management. For new projects and projects without a Wrangler configuration file, use the cf CLI instead.","https:\u002F\u002Fgithub.com\u002Fstepankuzmin\u002Fsvenska-app\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwrangler\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7C7CQHGNS5KATKXFWBX1QVM","workers-best-practices","Cloudflare Workers best practices for production applications. Use when writing, reviewing, or configuring Workers.","https:\u002F\u002Fgithub.com\u002Fstepankuzmin\u002Fsvenska-app\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fworkers-best-practices\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7C7CG0Q35G35NFECMVW0YSX","why","Use when the user asks to investigate why code is built the way it is: 'why does X work this way', 'why we picked Y', design rationale, regressions, or postmortems. Not for explaining a single error or a quick question. Queries each available evidence source (git and PRs, issues, docs, team chat) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.","https:\u002F\u002Fgithub.com\u002Fstepankuzmin\u002Fsvenska-app\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7C7CAXBW5SPGDN6VB0VF03P","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002Fstepankuzmin\u002Fsvenska-app\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fvercel-react-best-practices\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7C7C7SBTJEA71CZ2ZTG62C1","vendor-skill","Adapt an external skill into this marketplace, or review upstream changes to one already adapted. Use when asked to vendor, import, adapt, mirror, or update a skill from skills.sh, `npx skills add`, or any external GitHub skills repo, especially to work around Claude Code Web only allowing one marketplace per GitHub repo name.","https:\u002F\u002Fgithub.com\u002Fstepankuzmin\u002Fsvenska-app\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fvendor-skill\u002FSKILL.md",[],[]]