[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MCCTF60H8PVRJPJRWEYTCK":3,"skill-same:01M6MCCTF60H8PVRJPJRWEYTCK":120},{"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":37,"publishedAt":59,"linkOnly":60,"markdownContent":61,"markdownBody":62,"frontMatter":63,"refName":70,"commitSha":71,"skillDirectory":72,"forksCount":73,"repositoryHtmlUrl":74,"repositoryHomepageUrl":75,"ownerHtmlUrl":76,"ownerBlogUrl":77,"ownerDescription":78,"updatedAt":79,"install":80,"resources":93},"01M6MCCTF60H8PVRJPJRWEYTCK","go-idiomatic-api-design",null,"Design and review stable, idiomatic Go package APIs covering naming, exported declarations, embedding, receivers, typed-nil interfaces, generics, functional options, method sets, errors, wire contracts, compatibility, and examples. Use when creating a reusable Go package, reviewing its public surface, evolving an exported API, or choosing concrete types, functions, methods, fields, interfaces, or type parameters.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fgo-idiomatic-api-design\u002FSKILL.md",[18,23,26,29,34],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":30,"categoryName":31,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":35,"categoryName":36,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000032","设计师",[38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57,58],"go","api design","go idiomatic api design","api","idiomatic","go idiomatic","design","options","when","exported","errors","api-design","functional","types","embedding","methods","compatibility","contracts","code","packages","review","2026-11-10 10:12:30",false,"---\nname: go-idiomatic-api-design\ndescription: Design and review stable, idiomatic Go package APIs covering naming, exported declarations, embedding, receivers, typed-nil interfaces, generics, functional options, method sets, errors, wire contracts, compatibility, and examples. Use when creating a reusable Go package, reviewing its public surface, evolving an exported API, or choosing concrete types, functions, methods, fields, interfaces, or type parameters.\nlicense: MIT\ncompatibility: Codex, Claude Code, and other Agent Skills-compatible clients.\nmetadata:\n  version: \"0.2.0\"\n  displayName: Go Idiomatic API Design\n  category: Go\n  tags: go,golang,api-design,packages,interfaces,compatibility\n---\n\n# Go Idiomatic API Design\n\nDesign from the caller's code inward. Prefer the smallest coherent public\nsurface that preserves invariants and can evolve without needless interfaces.\n\n## Core Workflow\n\n1. Identify callers, supported operations, and compatibility constraints.\n2. Sketch realistic call sites before choosing exported names or types.\n3. Keep packages cohesive and names clear without package-name stutter.\n4. Prefer concrete provider APIs; define narrow interfaces at consumers.\n5. Decide zero-value, mutation, copying, concurrency, and error contracts.\n6. Review embedding, receiver method sets, typed nils, generics, and option conflicts.\n7. Integrate standard interfaces only when their semantics truly match.\n8. Prove the public surface with external tests and executable examples.\n9. Review the change for accidental compatibility commitments.\n\n## Read Next\n\n| Task | Load |\n|---|---|\n| Design or evolve an API | `guidelines.md`, `workflows\u002Freview-public-api.md` |\n| Choose types, fields, methods, or interfaces | `references\u002Fapi-design\u002Frules.md` |\n| Understand compatibility and method sets | `references\u002Fapi-design\u002Fknowledge.md` |\n| Review concrete patterns | `references\u002Fapi-design\u002Fexamples.md` |\n\n## Guardrails\n\n- Do not export a field merely to avoid writing behavior.\n- Do not define a provider-wide interface as a mirror of its methods.\n- Do not accept an interface before a real consumer requires substitution.\n- Do not use a standard interface when its conventional semantics are surprising.\n- Do not claim conformance assertions prove behavior.\n- Do not embed a public type unless every promoted behavior is intentional.\n- Do not return a typed nil pointer through an interface success path.\n- Check the module's Go language version before giving version-sensitive advice.\n\n## Source Notes\n\nGuidance is transformed and paraphrased from Inanc Gumus, *Go by Example:\nProgrammer's Guide to Idiomatic and Testable Programs* (Manning, 2025),\nespecially Chapters 1, 2, 5, 9, and 10. Examples are original.\n\nEmbedding, receivers, generics, functional options, and typed-nil guidance also\nincorporates transformed material from Teiva Harsanyi, *100 Go Mistakes and\nHow to Avoid Them* (Manning, 2022), Chapters 2 and 6.\n\nBook: https:\u002F\u002Fwww.manning.com\u002Fbooks\u002Fgo-by-example\n\nCurrent language and documentation contracts should be verified against\nhttps:\u002F\u002Fgo.dev\u002Fref\u002Fspec, https:\u002F\u002Fgo.dev\u002Fdoc\u002Fcomment, and the module's pinned Go\nversion.\n","# Go Idiomatic API Design\n\nDesign from the caller's code inward. Prefer the smallest coherent public\nsurface that preserves invariants and can evolve without needless interfaces.\n\n## Core Workflow\n\n1. Identify callers, supported operations, and compatibility constraints.\n2. Sketch realistic call sites before choosing exported names or types.\n3. Keep packages cohesive and names clear without package-name stutter.\n4. Prefer concrete provider APIs; define narrow interfaces at consumers.\n5. Decide zero-value, mutation, copying, concurrency, and error contracts.\n6. Review embedding, receiver method sets, typed nils, generics, and option conflicts.\n7. Integrate standard interfaces only when their semantics truly match.\n8. Prove the public surface with external tests and executable examples.\n9. Review the change for accidental compatibility commitments.\n\n## Read Next\n\n| Task | Load |\n|---|---|\n| Design or evolve an API | `guidelines.md`, `workflows\u002Freview-public-api.md` |\n| Choose types, fields, methods, or interfaces | `references\u002Fapi-design\u002Frules.md` |\n| Understand compatibility and method sets | `references\u002Fapi-design\u002Fknowledge.md` |\n| Review concrete patterns | `references\u002Fapi-design\u002Fexamples.md` |\n\n## Guardrails\n\n- Do not export a field merely to avoid writing behavior.\n- Do not define a provider-wide interface as a mirror of its methods.\n- Do not accept an interface before a real consumer requires substitution.\n- Do not use a standard interface when its conventional semantics are surprising.\n- Do not claim conformance assertions prove behavior.\n- Do not embed a public type unless every promoted behavior is intentional.\n- Do not return a typed nil pointer through an interface success path.\n- Check the module's Go language version before giving version-sensitive advice.\n\n## Source Notes\n\nGuidance is transformed and paraphrased from Inanc Gumus, *Go by Example:\nProgrammer's Guide to Idiomatic and Testable Programs* (Manning, 2025),\nespecially Chapters 1, 2, 5, 9, and 10. Examples are original.\n\nEmbedding, receivers, generics, functional options, and typed-nil guidance also\nincorporates transformed material from Teiva Harsanyi, *100 Go Mistakes and\nHow to Avoid Them* (Manning, 2022), Chapters 2 and 6.\n\nBook: https:\u002F\u002Fwww.manning.com\u002Fbooks\u002Fgo-by-example\n\nCurrent language and documentation contracts should be verified against\nhttps:\u002F\u002Fgo.dev\u002Fref\u002Fspec, https:\u002F\u002Fgo.dev\u002Fdoc\u002Fcomment, and the module's pinned Go\nversion.\n",{"name":5,"license":15,"metadata":64,"description":7,"compatibility":69},{"tags":65,"version":66,"category":67,"displayName":68},"go,golang,api-design,packages,interfaces,compatibility","0.2.0","Go","Go Idiomatic API Design","Codex, Claude Code, and other Agent Skills-compatible clients.","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fgo-idiomatic-api-design",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":81,"prompt":91,"zipAvailable":92},[82,85,88],{"tool":83,"command":84},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill go-idiomatic-api-design",{"tool":86,"command":87},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill go-idiomatic-api-design",{"tool":89,"command":90},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill go-idiomatic-api-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fgo-idiomatic-api-design\u002FSKILL.md",true,[94,100,104,108,112,116],{"path":95,"resourceType":96,"resourceTypeDesc":97,"sizeBytes":98,"sourceHtmlUrl":99},"agents\u002Fopenai.yaml","REFERENCE","参考文档",234,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fgo-idiomatic-api-design\u002Fagents\u002Fopenai.yaml",{"path":101,"resourceType":96,"resourceTypeDesc":97,"sizeBytes":102,"sourceHtmlUrl":103},"guidelines.md",1851,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fgo-idiomatic-api-design\u002Fguidelines.md",{"path":105,"resourceType":96,"resourceTypeDesc":97,"sizeBytes":106,"sourceHtmlUrl":107},"references\u002Fapi-design\u002Fexamples.md",1546,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fgo-idiomatic-api-design\u002Freferences\u002Fapi-design\u002Fexamples.md",{"path":109,"resourceType":96,"resourceTypeDesc":97,"sizeBytes":110,"sourceHtmlUrl":111},"references\u002Fapi-design\u002Fknowledge.md",3896,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fgo-idiomatic-api-design\u002Freferences\u002Fapi-design\u002Fknowledge.md",{"path":113,"resourceType":96,"resourceTypeDesc":97,"sizeBytes":114,"sourceHtmlUrl":115},"references\u002Fapi-design\u002Frules.md",2707,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fgo-idiomatic-api-design\u002Freferences\u002Fapi-design\u002Frules.md",{"path":117,"resourceType":96,"resourceTypeDesc":97,"sizeBytes":118,"sourceHtmlUrl":119},"workflows\u002Freview-public-api.md",1588,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fgo-idiomatic-api-design\u002Fworkflows\u002Freview-public-api.md",[121,130,137,144,169,193],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":125,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":129},"01M746ZWACVKMZ1BJXJZHYJSSX","migrate-to-e2e","Moves an existing Playwright, Cypress, Selenium, Appium, Detox, Maestro, or TesterArmy suite to e2e one slice at a time, with the old suite running beside the new one until each ported test is proven. Keeps a MIGRATION.md progress file so any later session resumes where the last stopped. Optionally plants a defect to show both suites catch it. Use for \u002Fmigrate-to-e2e, \"migrate our tests to e2e\", \"port these Maestro flows\", \"move our TesterArmy tests\", or when a project has an e2e config and an older suite still running.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fmigrate-to-e2e\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"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":125,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":129},"01M746ZPTAX1Q0FBKAB1CYND7E","e2e","Writes, runs, and debugs end-to-end tests for web and mobile apps with e2e, the agentic test runner, which mixes agent.act goals with exact locator assertions on a Playwright browser or an iOS or Android device. Also drives a project's running app live over the e2e MCP server to look at a screen, check a UI change, take a screenshot or record a video, and try a locator; and runs bug bashes, parallel e2e explore runs with each bug proven by a repro test. Use when a project depends on e2e or has an e2e.config.ts, when asked for end-to-end, browser, mobile, or agentic UI tests, to check a change in the running app, to QA or bug bash an app or branch, or when an e2e run fails.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fe2e\u002FSKILL.md",[],[],{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":125,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":143,"publishedAt":129},"01M746ZJN784HVHMDP9MQGCSGG","create-verification-skill","Generate a project-local verify-\u003Capp> skill on top of e2e, so any coding agent can launch the app, check it is worth driving, exercise a feature the way a user does, keep evidence, and bug bash it. Writes the skill, a feature map with one explore charter per feature, and proves it once. Use for \u002Fcreate-verification-skill, \"make a verification skill for this repo\", or when a project has no scripted way to prove UI behavior.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fcreate-verification-skill\u002FSKILL.md",[],[],{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":125,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":150,"publishedAt":59},"01M716A6ETNB9B1SQ3GXZC75VR","deja-search","deja-vu memory — search the user's past AI coding sessions with the deja CLI. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before you call a change done or ready to merge, before you recommend a tool, library, design or reviewer, before re-debugging an error that may already be solved, when they say 'didn't we fix this before', 'what did we decide about X' or 'I already have that', and before telling them something on this machine does not exist.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-search\u002FSKILL.md",[],[151,152,153,154,155,156,157,158,159,44,160,46,161,162,163,164,165,166,167,168],"search","deja search","never","error","ready","memory","re","decide","fix","debugging","you","done","reviewer","io","change","cli","merge","past",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":125,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":175,"publishedAt":59},"01M716A3J2W5SENSE9VGMXB375","deja-reflect","End-of-session reflection and memory curation with deja-vu. Review what was decided, what commands broke and what repaired them, and record durable project rules or decisions with deja remember so the next session starts with them.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-reflect\u002FSKILL.md",[],[176,177,58,164,178,179,180,181,182,183,184,185,186,187,156,188,189,190,191,192],"deja reflect","reflect","with","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":194,"name":195,"nameZh":6,"description":196,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":125,"licenseFileUrl":6,"sourceHtmlUrl":197,"categories":198,"keywords":204,"publishedAt":59},"01M715T3RR4BAYSR57HPPTJ0PF","revid","Make, edit, export and post AI videos with Revid (revid.ai) through the Revid MCP server. Use whenever the user wants a short-form or long-form video made (from an idea, a script, a URL, an article, a PDF, a tweet, a product page, their own clips, or a song), wants to find what is going viral on TikTok, YouTube, Instagram or X before making something, wants to edit or re-export an existing Revid project, generate a standalone AI image or clip, make a series episode, or publish and schedule a finished video to connected social accounts. Covers setup (hosted MCP with OAuth, or an API key), the 36 tools, credits, polling and the rules for publishing. Routes to the more specific revid-* skills when one fits.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftmakersas\u002Frevid-skills\u002Fskills\u002Frevid\u002FSKILL.md",[199,202,203],{"categoryNo":200,"categoryName":201,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[195,205,206,207,208,209,210,189,211,157,212,213,214,215,46,216,217,218,41,219],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","publish"]