[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77SKKGWS687522P0FP237BV":3,"skill-same:01M77SKKGWS687522P0FP237BV":55},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":29,"commitSha":30,"skillDirectory":31,"forksCount":13,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M77SKKGWS687522P0FP237BV","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.","ConcertoNotes\u002Fcodex-plugins","ConcertoNotes","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F249301288?v=4","01M77NJ0BK2KN5YW0D8RHD99TB","01M77NJ0CCEDPATAY3JTXEWNK5",0,"MIT","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcommunity\u002Flvtd-skills\u002Fskills\u002Fcookiecutter\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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":14,"metadata":23,"description":7,"compatibility":28},{"tags":24,"version":25,"category":26,"displayName":27},"cookiecutter,templates,jinja,scaffolding","0.1.0","Developer Tooling","Cookiecutter","Codex, Claude Code, and other Agent Skills-compatible clients.","main","9ba3c9fadff1092395837bf1502e1b8a7f98b1e1","plugins\u002Fcommunity\u002Flvtd-skills\u002Fskills\u002Fcookiecutter","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins","https:\u002F\u002Fgithub.com\u002FConcertoNotes","2026-06-26 10:13:54",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add ConcertoNotes\u002Fcodex-plugins --skill cookiecutter",{"tool":41,"command":42},"bunx","bunx skills add ConcertoNotes\u002Fcodex-plugins --skill cookiecutter",{"tool":44,"command":45},"pnpm","pnpm dlx skills add ConcertoNotes\u002Fcodex-plugins --skill cookiecutter","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcommunity\u002Flvtd-skills\u002Fskills\u002Fcookiecutter\u002FSKILL.md",true,[49],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"assets\u002Fapp-icon.png","ASSET","资产文件",69657,"https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcommunity\u002Flvtd-skills\u002Fskills\u002Fcookiecutter\u002Fassets\u002Fapp-icon.png",[56,65,72,80,87,94],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":60,"licenseFileUrl":61,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":18},"01M77YB7WW36DS9AERTWP673E0","android-emulator-qa","Use when validating Android feature flows in an emulator with adb-driven launch, input, UI-tree inspection, screenshots, and logcat capture.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Ftest-android-apps\u002Fskills\u002Fandroid-emulator-qa\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Ftest-android-apps\u002Fskills\u002Fandroid-emulator-qa\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":18},"01M77Y7AA8N45G6NM0WJSS2W9C","supabase-postgres-best-practices","Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Fsupabase\u002Fskills\u002Fsupabase-postgres-best-practices\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":60,"licenseFileUrl":76,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M77Y2W5H5YGSW7MYWEJ8HYXD","sentry","Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Fsentry\u002Fskills\u002Fsentry\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Fsentry\u002Fskills\u002Fsentry\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M77Y06GV1DAME7PN9KBFHWRX","render-workflows","Sets up, develops, tests, and deploys Render Workflows. Covers first-time scaffolding (via CLI or manual), SDK installation (Python or TypeScript), task patterns (retries, subtasks, fan-out), local development, Dashboard deployment, and troubleshooting. Use when a user wants to set up Render Workflows for the first time, scaffold a workflow service, add or modify workflow tasks, test workflows locally, or deploy workflows to Render.","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Frender\u002Fskills\u002Frender-workflows\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":18},"01M77Y01A6RJA8VYT7CZ2TVETF","render-web-services","Configures Render web services—port binding, TLS, health checks, custom domains, auto-deploy, PR previews, persistent disks, and deploy lifecycle. Use when the user needs to set up a web service, fix health check failures, add a custom domain, configure zero-downtime deploys, or troubleshoot port binding issues.","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Frender\u002Fskills\u002Frender-web-services\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":18},"01M77XZW1AZ6B6NZTWWFVY72T3","render-static-sites","Deploys and configures static sites on Render's global CDN—build commands, publish paths, SPA routing, redirects, custom headers, and PR previews. Use when the user needs to deploy a static site, set up a React\u002FVue\u002FHugo\u002FGatsby frontend, configure SPA fallback routing, add redirect rules, customize response headers, or choose between a static site and a web service for their frontend. Trigger terms: static site, CDN, SPA, single-page app, React deploy, Vue deploy, Hugo, Gatsby, Docusaurus, Jekyll, staticPublishPath.","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Frender\u002Fskills\u002Frender-static-sites\u002FSKILL.md",[],[]]