[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MBYDRYT4FDN59YAF1PTE1V":3,"skill-same:01M6MBYDRYT4FDN59YAF1PTE1V":90},{"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":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":60,"commitSha":61,"skillDirectory":62,"forksCount":63,"repositoryHtmlUrl":64,"repositoryHomepageUrl":65,"ownerHtmlUrl":66,"ownerBlogUrl":67,"ownerDescription":68,"updatedAt":69,"install":70,"resources":83},"01M6MBYDRYT4FDN59YAF1PTE1V","cookiecutter",null,"Use when adding, changing, testing, or debugging Cookiecutter templates, including cookiecutter.json variables, Jinja-rendered files, hooks, _copy_without_render, optional feature cleanup, and generated-project validation.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1571,"MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fcookiecutter\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[5,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"hooks","when","Variables","render","feature","project","scaffolding","files","developer tooling","tooling","testing","use","generated","json","developer","validation","code","cleanup","debugging","codex","2026-11-10 10:12:30",false,"---\nname: cookiecutter\ndescription: Use when adding, changing, testing, or debugging Cookiecutter templates, including cookiecutter.json variables, Jinja-rendered files, hooks, _copy_without_render, optional feature cleanup, and generated-project validation.\nlicense: MIT\ncompatibility: Codex, Claude Code, and other Agent Skills-compatible clients.\nmetadata:\n  version: \"0.1.0\"\n  displayName: Cookiecutter\n  category: Developer Tooling\n  tags: cookiecutter,templates,jinja,scaffolding\n---\n\n# Cookiecutter Template Work\n\nUse this skill before changing a repository that has `cookiecutter.json`,\n`hooks\u002F`, or a generated project directory such as\n`{{ cookiecutter.project_slug }}\u002F`.\n\n## First Pass\n\n1. Read the repo instructions, `README.md`, `cookiecutter.json`, existing tests,\n   and any hooks before editing.\n2. Identify the template root and the generated project root. Make changes in\n   the template files, not in one rendered sample.\n3. Search for the relevant Cookiecutter variables and feature flags with `rg`\n   before adding new ones.\n4. Check how the repo validates rendered projects. Prefer existing render tests\n   and smoke-check commands over inventing a separate validation path.\n\n## Template Boundaries\n\n- `cookiecutter.json` is the user-facing interface. Every new prompt, default,\n  derived value, private value, and choice should be deliberate and documented\n  where the repo documents options.\n- The generated project directory may itself contain Jinja in file names and\n  paths. Treat both file contents and paths as render surfaces.\n- Follow the repo's current variable style. If it already uses `y`\u002F`n` strings,\n  keep using that style for new feature flags. If it uses Cookiecutter boolean\n  values, keep those as real JSON booleans.\n- Optional features must be valid in both enabled and disabled states. Remove or\n  gate app files, imports, URL routes, settings, dependencies, docs, tests,\n  workflows, and migrations together.\n- Do not add maintainer-specific names, local paths, secrets, or one-agent\n  assumptions to generated output.\n\n## Jinja Rules\n\n- Keep rendered files valid in their target language: Python, JSON, TOML, YAML,\n  shell, Markdown, HTML, JavaScript, or CSS.\n- Watch for dangling commas after conditional blocks in JSON, TOML, Python data\n  structures, YAML lists, package manifests, and GitHub Actions.\n- Use whitespace control (`{%- ... -%}`) only when it improves rendered syntax\n  or formatting. Validate the rendered result, not only the template source.\n- Use safe serialization for strings inserted into code or data files. Prefer\n  the repo's existing JSON\u002FJinja filter pattern, such as `|tojson`, when it is\n  already used.\n- If generated output must preserve literal Jinja, template syntax, or agent\n  placeholders, either escape the braces, wrap the content in raw blocks, or add\n  the path to `_copy_without_render`.\n- `_copy_without_render` prevents rendering file contents, but paths are still\n  rendered. Include both directory and recursive glob entries when a whole tree\n  must be copied verbatim.\n\n## Hooks\n\n- Put Cookiecutter hooks in `hooks\u002F` as `pre_prompt`, `pre_gen_project`, or\n  `post_gen_project` scripts. Prefer Python for cross-platform templates unless\n  the repo is intentionally platform-specific.\n- `pre_gen_project` and `post_gen_project` run from the generated project root\n  and can use rendered Cookiecutter variables.\n- Make hooks deterministic, idempotent, and relative-path based. Avoid network\n  calls, secrets, interactive prompts, and machine-local paths.\n- A non-zero hook exit stops generation and Cookiecutter cleans the generated\n  directory. Fail early for invalid user input; be defensive for cleanup.\n- Use post-generation cleanup for whole optional files or directories. Use\n  inline Jinja for small syntax-aware changes inside files that must remain.\n\n## Testing\n\n- Add or update tests that render the template with explicit context values.\n  Cover each changed option both enabled and disabled when practical.\n- Include assertions for absence, not only presence: disabled optional features\n  should not leave imports, dependencies, routes, docs, workflows, migrations,\n  or placeholder text behind.\n- Exercise the real Cookiecutter CLI when changing generation behavior, hooks,\n  template selection, or command-line assumptions.\n- For runtime behavior changes, generate a project in a temp directory and run\n  that project's documented checks.\n- Inspect rendered files that are sensitive to syntax: JSON, TOML, YAML,\n  Python modules, shell scripts, and package manifests.\n\n## Common Failure Patterns\n\n- Jinja renders syntactically valid template source into invalid generated code.\n- A disabled option removes files but leaves settings, imports, URLs,\n  dependencies, docs, tests, migrations, or CI references.\n- Literal `{{ ... }}` placeholders intended for the generated project are\n  consumed by Cookiecutter.\n- Hooks assume the template repo as the working directory instead of the\n  generated project root.\n- Tests render one happy-path context but miss another supported option\n  combination.\n- Generated files include local paths, personal names, secrets, or assumptions\n  about a specific AI tool.\n\n## Definition of Done\n\n- Template changes are made at the template level.\n- Relevant enabled and disabled option combinations render successfully.\n- The generated output has no stale placeholders, syntax errors, orphan imports,\n  or hard-coded maintainer-specific values.\n- The repo's template test suite passes.\n- Docs and changelog entries are updated when users or generated-project\n  contributors need to know about the change.\n\n## References\n\n- Official documentation: https:\u002F\u002Fcookiecutter.readthedocs.io\u002Fen\u002Fstable\u002F\n- Upstream repository: https:\u002F\u002Fgithub.com\u002Fcookiecutter\u002Fcookiecutter\n","# Cookiecutter Template Work\n\nUse this skill before changing a repository that has `cookiecutter.json`,\n`hooks\u002F`, or a generated project directory such as\n`{{ cookiecutter.project_slug }}\u002F`.\n\n## First Pass\n\n1. Read the repo instructions, `README.md`, `cookiecutter.json`, existing tests,\n   and any hooks before editing.\n2. Identify the template root and the generated project root. Make changes in\n   the template files, not in one rendered sample.\n3. Search for the relevant Cookiecutter variables and feature flags with `rg`\n   before adding new ones.\n4. Check how the repo validates rendered projects. Prefer existing render tests\n   and smoke-check commands over inventing a separate validation path.\n\n## Template Boundaries\n\n- `cookiecutter.json` is the user-facing interface. Every new prompt, default,\n  derived value, private value, and choice should be deliberate and documented\n  where the repo documents options.\n- The generated project directory may itself contain Jinja in file names and\n  paths. Treat both file contents and paths as render surfaces.\n- Follow the repo's current variable style. If it already uses `y`\u002F`n` strings,\n  keep using that style for new feature flags. If it uses Cookiecutter boolean\n  values, keep those as real JSON booleans.\n- Optional features must be valid in both enabled and disabled states. Remove or\n  gate app files, imports, URL routes, settings, dependencies, docs, tests,\n  workflows, and migrations together.\n- Do not add maintainer-specific names, local paths, secrets, or one-agent\n  assumptions to generated output.\n\n## Jinja Rules\n\n- Keep rendered files valid in their target language: Python, JSON, TOML, YAML,\n  shell, Markdown, HTML, JavaScript, or CSS.\n- Watch for dangling commas after conditional blocks in JSON, TOML, Python data\n  structures, YAML lists, package manifests, and GitHub Actions.\n- Use whitespace control (`{%- ... -%}`) only when it improves rendered syntax\n  or formatting. Validate the rendered result, not only the template source.\n- Use safe serialization for strings inserted into code or data files. Prefer\n  the repo's existing JSON\u002FJinja filter pattern, such as `|tojson`, when it is\n  already used.\n- If generated output must preserve literal Jinja, template syntax, or agent\n  placeholders, either escape the braces, wrap the content in raw blocks, or add\n  the path to `_copy_without_render`.\n- `_copy_without_render` prevents rendering file contents, but paths are still\n  rendered. Include both directory and recursive glob entries when a whole tree\n  must be copied verbatim.\n\n## Hooks\n\n- Put Cookiecutter hooks in `hooks\u002F` as `pre_prompt`, `pre_gen_project`, or\n  `post_gen_project` scripts. Prefer Python for cross-platform templates unless\n  the repo is intentionally platform-specific.\n- `pre_gen_project` and `post_gen_project` run from the generated project root\n  and can use rendered Cookiecutter variables.\n- Make hooks deterministic, idempotent, and relative-path based. Avoid network\n  calls, secrets, interactive prompts, and machine-local paths.\n- A non-zero hook exit stops generation and Cookiecutter cleans the generated\n  directory. Fail early for invalid user input; be defensive for cleanup.\n- Use post-generation cleanup for whole optional files or directories. Use\n  inline Jinja for small syntax-aware changes inside files that must remain.\n\n## Testing\n\n- Add or update tests that render the template with explicit context values.\n  Cover each changed option both enabled and disabled when practical.\n- Include assertions for absence, not only presence: disabled optional features\n  should not leave imports, dependencies, routes, docs, workflows, migrations,\n  or placeholder text behind.\n- Exercise the real Cookiecutter CLI when changing generation behavior, hooks,\n  template selection, or command-line assumptions.\n- For runtime behavior changes, generate a project in a temp directory and run\n  that project's documented checks.\n- Inspect rendered files that are sensitive to syntax: JSON, TOML, YAML,\n  Python modules, shell scripts, and package manifests.\n\n## Common Failure Patterns\n\n- Jinja renders syntactically valid template source into invalid generated code.\n- A disabled option removes files but leaves settings, imports, URLs,\n  dependencies, docs, tests, migrations, or CI references.\n- Literal `{{ ... }}` placeholders intended for the generated project are\n  consumed by Cookiecutter.\n- Hooks assume the template repo as the working directory instead of the\n  generated project root.\n- Tests render one happy-path context but miss another supported option\n  combination.\n- Generated files include local paths, personal names, secrets, or assumptions\n  about a specific AI tool.\n\n## Definition of Done\n\n- Template changes are made at the template level.\n- Relevant enabled and disabled option combinations render successfully.\n- The generated output has no stale placeholders, syntax errors, orphan imports,\n  or hard-coded maintainer-specific values.\n- The repo's template test suite passes.\n- Docs and changelog entries are updated when users or generated-project\n  contributors need to know about the change.\n\n## References\n\n- Official documentation: https:\u002F\u002Fcookiecutter.readthedocs.io\u002Fen\u002Fstable\u002F\n- Upstream repository: https:\u002F\u002Fgithub.com\u002Fcookiecutter\u002Fcookiecutter\n",{"name":5,"license":15,"metadata":54,"description":7,"compatibility":59},{"tags":55,"version":56,"category":57,"displayName":58},"cookiecutter,templates,jinja,scaffolding","0.1.0","Developer Tooling","Cookiecutter","Codex, Claude Code, and other Agent Skills-compatible clients.","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fcookiecutter",490,"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 02:12:02",{"source":8,"skillName":5,"commands":71,"prompt":81,"zipAvailable":82},[72,75,78],{"tool":73,"command":74},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cookiecutter",{"tool":76,"command":77},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cookiecutter",{"tool":79,"command":80},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cookiecutter","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fcookiecutter\u002FSKILL.md",true,[84],{"path":85,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":88,"sourceHtmlUrl":89},"assets\u002Fapp-icon.png","ASSET","资产文件",69657,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fcookiecutter\u002Fassets\u002Fapp-icon.png",[91,100,107,114,139,163],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":95,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":99},"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":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":95,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":99},"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":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":95,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":99},"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":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":95,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":49},"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",[],[121,122,123,124,125,126,127,128,129,130,47,30,131,132,133,134,135,136,137,138],"search","deja search","never","error","ready","memory","re","decide","fix","design","you","done","reviewer","io","change","cli","merge","past",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":95,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":49},"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",[],[146,147,148,134,149,150,151,152,153,154,155,156,157,158,126,159,34,160,161,162],"deja reflect","reflect","review","with","record","github","next","https","node","Rules","decisions","brew","remember","project rules","session","end","reflection",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":95,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":178,"publishedAt":49},"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",[169,172,175],{"categoryNo":170,"categoryName":171,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":173,"categoryName":174,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":176,"categoryName":177,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[165,179,180,181,182,183,184,34,185,127,186,187,188,189,30,190,191,192,193,194],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api","publish"]