[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6M9263AWTCE8M8HTDSGDAJZ":3,"skill-same:01M6M9263AWTCE8M8HTDSGDAJZ":84},{"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":23,"publishedAt":45,"linkOnly":46,"markdownContent":47,"markdownBody":48,"frontMatter":49,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":55,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":58,"updatedAt":59,"install":60,"resources":73},"01M6M9263AWTCE8M8HTDSGDAJZ","dev-spec",null,"Compatibility alias for dev-grill-docs spec-only mode. Use for explicit dev-spec requests, old dev-spec workflows, or spec-only output without CONTEXT.md \u002F ADR updates. Ordinary requirement alignment belongs to dev-grill-docs. Preserves the feature artifact and acceptance contract, including when installed standalone.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1559,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJason-chen-coder\u002Fdev-skills\u002Fskills\u002Fdev-spec\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44],"dev","dev spec","spec","artifact","when","for","updates","mode","standalone","requests","output","feature","alias","contract","grill","alignment","only","use","adr","acceptance","workflows","2026-11-10 10:12:30",false,"---\nname: dev-spec\ndescription: 'Compatibility alias for dev-grill-docs spec-only mode. Use for explicit dev-spec requests, old dev-spec workflows, or spec-only output without CONTEXT.md \u002F ADR updates. Ordinary requirement alignment belongs to dev-grill-docs. Preserves the feature artifact and acceptance contract, including when installed standalone.'\n---\n\n# Dev Spec\n\nTreat `dev-spec` as `dev-grill-docs --spec-only`, forwarding `--quick` or `--deep`. Read [references\u002Fdev-baseline.md](references\u002Fdev-baseline.md).\n\nWhen `dev-grill-docs` is available in the installed skill catalog, load it and apply its spec-only mode. Do not assume a sibling directory exists. When it is unavailable, use the compact compatibility contract below; no other skill is required to produce the artifact.\n\n## Standalone compatibility contract\n\n- Read the user's request and relevant existing docs, code, terminology, and tests before asking questions.\n- Ask only about material unresolved behavior, scope, or acceptance. Preserve prior decisions; a clear request needs no mandatory interview. Record consequential evidence-backed assumptions and keep high-impact unresolved decisions explicit.\n- Produce `.claude\u002Fartifacts\u002Fdesigns\u002F\u003Cfeature>.md` in the user's project unless the user specifies another path or chat-only output. Reuse an identifiable existing slug; otherwise choose a descriptive one without a routine confirmation turn.\n- Include `Background`, `In scope`, `Out of scope`, `Solution`, and observable `Acceptance criteria` with stable `AC-1` identifiers. Include `Assumptions`, `Edge cases & risks`, `Open questions`, and core entities where relevant. The solution is a behavior sketch, not an implementation task list.\n- Record source and update date. Preserve status vocabulary: `DRAFT` for proposed or unaligned intent, `ALIGNED` for materially resolved requirements supported by user direction or an accepted source, `STUCK` for concrete blocking questions, and `IMPLEMENTED` only when actual implementation evidence supports it. Changed requirements invalidate implementation status for the affected scope.\n- A `STUCK` contract identifies the blocking decision, affected scope, and needed evidence or owner. Do not advance dependent implementation or planning by treating file existence as readiness.\n- Report the artifact and unresolved issues. Respect intake-only or analysis-only scope. If broader implementation is already authorized, continue through the available workflow when requirements are sufficient.\n\n## Boundaries\n\nThis alias writes no `CONTEXT.md` or `docs\u002Fadr\u002F` unless the user explicitly adds those outputs. It does not implement code or diagnose bugs. Analysis-only and no-file instructions take precedence over the default artifact path. See [examples.md](examples.md) for compatibility cases.\n\n## SDD Contract\n\nPreserve `In scope`, `Out of scope`, `Assumptions`, `Open questions`, and stable `Acceptance criteria` for downstream planning, implementation, verification, and review. Existing calls to `dev-spec` keep the same artifact path and lifecycle vocabulary as `dev-grill-docs --spec-only`.\n\n## Multi-Agent Note\n\nMain-agent-first. If delegation is available and authorized, explorers may gather bounded facts and independent reviewers may evaluate a substantial contract; one agent owns questions and writes. In the source repository, `docs\u002Fmulti-agent-policy.md` provides optional guidance, not a dependency for standalone use.\n","# Dev Spec\n\nTreat `dev-spec` as `dev-grill-docs --spec-only`, forwarding `--quick` or `--deep`. Read [references\u002Fdev-baseline.md](references\u002Fdev-baseline.md).\n\nWhen `dev-grill-docs` is available in the installed skill catalog, load it and apply its spec-only mode. Do not assume a sibling directory exists. When it is unavailable, use the compact compatibility contract below; no other skill is required to produce the artifact.\n\n## Standalone compatibility contract\n\n- Read the user's request and relevant existing docs, code, terminology, and tests before asking questions.\n- Ask only about material unresolved behavior, scope, or acceptance. Preserve prior decisions; a clear request needs no mandatory interview. Record consequential evidence-backed assumptions and keep high-impact unresolved decisions explicit.\n- Produce `.claude\u002Fartifacts\u002Fdesigns\u002F\u003Cfeature>.md` in the user's project unless the user specifies another path or chat-only output. Reuse an identifiable existing slug; otherwise choose a descriptive one without a routine confirmation turn.\n- Include `Background`, `In scope`, `Out of scope`, `Solution`, and observable `Acceptance criteria` with stable `AC-1` identifiers. Include `Assumptions`, `Edge cases & risks`, `Open questions`, and core entities where relevant. The solution is a behavior sketch, not an implementation task list.\n- Record source and update date. Preserve status vocabulary: `DRAFT` for proposed or unaligned intent, `ALIGNED` for materially resolved requirements supported by user direction or an accepted source, `STUCK` for concrete blocking questions, and `IMPLEMENTED` only when actual implementation evidence supports it. Changed requirements invalidate implementation status for the affected scope.\n- A `STUCK` contract identifies the blocking decision, affected scope, and needed evidence or owner. Do not advance dependent implementation or planning by treating file existence as readiness.\n- Report the artifact and unresolved issues. Respect intake-only or analysis-only scope. If broader implementation is already authorized, continue through the available workflow when requirements are sufficient.\n\n## Boundaries\n\nThis alias writes no `CONTEXT.md` or `docs\u002Fadr\u002F` unless the user explicitly adds those outputs. It does not implement code or diagnose bugs. Analysis-only and no-file instructions take precedence over the default artifact path. See [examples.md](examples.md) for compatibility cases.\n\n## SDD Contract\n\nPreserve `In scope`, `Out of scope`, `Assumptions`, `Open questions`, and stable `Acceptance criteria` for downstream planning, implementation, verification, and review. Existing calls to `dev-spec` keep the same artifact path and lifecycle vocabulary as `dev-grill-docs --spec-only`.\n\n## Multi-Agent Note\n\nMain-agent-first. If delegation is available and authorized, explorers may gather bounded facts and independent reviewers may evaluate a substantial contract; one agent owns questions and writes. In the source repository, `docs\u002Fmulti-agent-policy.md` provides optional guidance, not a dependency for standalone use.\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FJason-chen-coder\u002Fdev-skills\u002Fskills\u002Fdev-spec",474,"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-11 14:40:14",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill dev-spec",{"tool":66,"command":67},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill dev-spec",{"tool":69,"command":70},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill dev-spec","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJason-chen-coder\u002Fdev-skills\u002Fskills\u002Fdev-spec\u002FSKILL.md",true,[74,80],{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"examples.md","REFERENCE","参考文档",1473,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJason-chen-coder\u002Fdev-skills\u002Fskills\u002Fdev-spec\u002Fexamples.md",{"path":81,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fdev-baseline.md",3571,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJason-chen-coder\u002Fdev-skills\u002Fskills\u002Fdev-spec\u002Freferences\u002Fdev-baseline.md",[85,93,100,107,133,158],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":92},"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.","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":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":92},"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":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":92},"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":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":45},"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",[],[114,115,116,117,118,119,120,121,122,123,124,28,125,126,127,128,129,130,131,132],"search","deja search","never","error","ready","memory","re","decide","fix","design","debugging","you","done","reviewer","io","change","cli","merge","past",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":45},"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",[],[140,141,142,128,143,144,145,146,147,148,149,150,151,152,119,153,154,155,156,157],"deja reflect","reflect","review","with","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":175,"publishedAt":45},"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",[164,169,172],{"categoryNo":165,"categoryName":166,"taxonomyType":167,"taxonomyTypeDesc":168},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",{"categoryNo":170,"categoryName":171,"taxonomyType":167,"taxonomyTypeDesc":168},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":173,"categoryName":174,"taxonomyType":167,"taxonomyTypeDesc":168},"01JBSEEDCAT000000000000010","后端与接口",[160,176,177,178,32,179,180,154,181,120,182,183,184,185,28,186,187,188,189,190],"URL","Video","short-form","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api","publish"]