[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77SHSYAWB99CF3XHFNEJNEW":3,"skill-same:01M77SHSYAWB99CF3XHFNEJNEW":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},"01M77SHSYAWB99CF3XHFNEJNEW","alpinejs-django",null,"Use when adding, changing, or debugging Alpine.js behavior in this Django SaaS Starter project, especially in Django templates that may also use HTMX partial updates.","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\u002Falpinejs-django\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: alpinejs-django\ndescription: Use when adding, changing, or debugging Alpine.js behavior in this Django SaaS Starter project, especially in Django templates that may also use HTMX partial updates.\nlicense: MIT\ncompatibility: Codex, Claude Code, and other Agent Skills-compatible clients.\nmetadata:\n  version: \"0.1.0\"\n  displayName: Alpine.js Django\n  category: Django\n  tags: alpinejs,django,frontend,htmx\n---\n\n# Alpine.js with Django\n\nUse this skill for local browser state in Django-rendered templates: dropdowns,\nmodals, tabs, disclosures, inline filters, disabled\u002Floading states, small\npreview interactions, and client-only toggles. Use Django views\u002Fforms\u002Fmodels as\nthe source of truth for durable state. Use HTMX when the server needs to return\nfresh HTML.\n\n## Project setup\n\n- Alpine is installed from npm and copied by `scripts\u002Fcopy-vendor-assets.mjs`\n  to `frontend\u002Fstatic\u002Fvendors\u002Fjs\u002Falpine.min.js`.\n- `base_app.html` and `base_landing.html` load HTMX first, Alpine second, and\n  `frontend\u002Fstatic\u002Fjs\u002Fapp.js` third.\n- The loaded Alpine file is the self-starting CDN build. Do not call\n  `Alpine.start()` from `frontend\u002Fsrc\u002Fjs\u002Fapp.js`.\n- Simple Alpine behavior should usually live inline in the Django template with\n  `x-data`.\n- If a reusable component or store is worth extracting, register it before\n  Alpine starts. With the current script order, `frontend\u002Fsrc\u002Fjs\u002Fapp.js` runs too\n  late for reliable `document.addEventListener(\"alpine:init\", ...)`\n  registration unless the script order is changed.\n- When reusable Alpine registration is needed, add a dedicated classic script\n  such as `frontend\u002Fsrc\u002Fjs\u002Falpine-components.js`, register components\u002Fstores\n  inside `document.addEventListener(\"alpine:init\", ...)`, and include the copied\n  `frontend\u002Fstatic\u002Fjs\u002Falpine-components.js` before `vendors\u002Fjs\u002Falpine.min.js` in\n  both base templates. Keep `app.js` after Alpine, keep the self-starting Alpine\n  build, and still do not call `Alpine.start()` manually.\n\n## Ownership rules\n\n- Django owns persistence, authorization, validation, redirects, and rendered\n  HTML.\n- HTMX owns server round trips and DOM swaps.\n- Alpine owns ephemeral state already present in the browser.\n- Plain modules in `frontend\u002Fsrc\u002Fjs\u002F` own shared DOM behavior that is not\n  naturally scoped to one Alpine component.\n- Do not duplicate the same behavior in Alpine and a plain JS module.\n\n## Template patterns\n\nUse a small `x-data` object near the markup it controls:\n\n```html\n\u003Cdiv\n  x-data=\"{ open: false }\"\n  @keydown.escape.window=\"open = false\"\n  @click.outside=\"open = false\"\n>\n  \u003Cbutton\n    type=\"button\"\n    :aria-expanded=\"open.toString()\"\n    @click.stop=\"open = !open\"\n  >\n    Menu\n  \u003C\u002Fbutton>\n\n  \u003Cdiv x-cloak x-show=\"open\" x-transition>\n    ...\n  \u003C\u002Fdiv>\n\u003C\u002Fdiv>\n```\n\nPrefer Alpine directives over manual DOM manipulation:\n\n- `x-show` for toggling visibility while keeping the element in the DOM.\n- `x-if` on a `\u003Ctemplate>` when the element should be created and destroyed.\n- `x-model` for client-only input state; Django form submission and validation\n  still happen on the server.\n- `:class`, `:disabled`, `:aria-expanded`, and `:hidden` for state-derived\n  attributes.\n- `$watch` for one named state transition; `x-effect` only when the dependency\n  set is simple and intentional.\n- `$dispatch` for browser events between Alpine components or from Alpine to\n  HTMX triggers.\n\nUse `x-cloak` for anything hidden by default. The base templates already include\nthe required `[x-cloak] { display: none !important; }` CSS.\n\n## Django data\n\nKeep Django interpolation out of complex JavaScript expressions when possible.\n\nFor simple values, prefer HTML attributes:\n\n```html\n\u003Cdiv\n  data-initial-label=\"{{ object.name }}\"\n  x-data=\"{ label: '' }\"\n  x-init=\"label = $el.dataset.initialLabel\"\n>\n  \u003Cspan x-text=\"label\">\u003C\u002Fspan>\n\u003C\u002Fdiv>\n```\n\nFor structured values, prefer Django's `json_script` and parse it in `x-init`:\n\n```html\n{{ rows|json_script:\"rows-data\" }}\n\n\u003Cdiv\n  x-data=\"{ rows: [] }\"\n  x-init=\"rows = JSON.parse(document.getElementById('rows-data').textContent)\"\n>\n  \u003Ctemplate x-for=\"row in rows\" :key=\"row.id\">\n    \u003Cspan x-text=\"row.name\">\u003C\u002Fspan>\n  \u003C\u002Ftemplate>\n\u003C\u002Fdiv>\n```\n\nAvoid `|safe` inside Alpine expressions. If the browser must display text, use\n`x-text`. Use `x-html` only for trusted, already-sanitized HTML; most HTML should\nbe rendered by Django or returned through HTMX.\n\n## Alpine and HTMX\n\nWhen HTMX swaps a fragment containing `x-data`, Alpine should initialize the new\ncomponent automatically. Do not restart Alpine after HTMX swaps.\n\nKeep persistent Alpine state outside HTMX targets that will be replaced:\n\n```html\n\u003Csection x-data=\"{ panelOpen: false }\">\n  \u003Cbutton type=\"button\" @click=\"panelOpen = !panelOpen\">Filters\u003C\u002Fbutton>\n\n  \u003Cdiv id=\"results\" hx-get=\"{% url 'search_results' %}\" hx-trigger=\"change from:#filters\">\n    ...\n  \u003C\u002Fdiv>\n\u003C\u002Fsection>\n```\n\nUse events as the boundary between HTMX responses and Alpine state. From Django,\nset an `HX-Trigger` or `HX-Trigger-After-Swap` response header, then listen from\nAlpine:\n\n```html\n\u003Cdiv x-data=\"{ open: true }\" @profile-saved.window=\"open = false\">\n  \u003Cform hx-post=\"{% url 'profile_update' %}\" hx-target=\"#profile-panel\" hx-swap=\"outerHTML\">\n    ...\n  \u003C\u002Fform>\n\u003C\u002Fdiv>\n```\n\nListen for HTMX lifecycle events in kebab case from Alpine, such as\n`@htmx:after-swap.window`, because HTML attributes are case-insensitive.\n\nIf Alpine dispatches an event that HTMX should react to, make the trigger\nexplicit:\n\n```html\n\u003Cbutton type=\"button\" x-data @click=\"$dispatch('refresh-results')\">\n  Refresh\n\u003C\u002Fbutton>\n\n\u003Cdiv hx-get=\"{% url 'results' %}\" hx-trigger=\"refresh-results from:body\">\n  ...\n\u003C\u002Fdiv>\n```\n\n## Accessibility\n\n- Keep real buttons as `\u003Cbutton type=\"button\">` unless submitting a form.\n- Bind ARIA state from Alpine state, especially `aria-expanded`,\n  `aria-controls`, `aria-selected`, and `aria-hidden`.\n- Support `@keydown.escape.window` for dismissible overlays.\n- Use `@click.outside` for popovers and menus, paired with a visible trigger.\n- Preserve focus behavior for modals, menus, and swapped HTMX content. If focus\n  trapping is needed, add a focused plain JS module or Alpine plugin deliberately\n  instead of hand-rolling a brittle trap in attributes.\n\n## Security and CSP\n\n- Treat all Alpine expressions as JavaScript running in the user's browser.\n- Do not put secrets, signed tokens, or privileged data into `x-data`,\n  `data-*`, `json_script`, or hidden inputs unless the user is allowed to see\n  them.\n- If strict Content Security Policy without `unsafe-eval` is required, switch\n  deliberately to Alpine's CSP build and retest Alpine expressions. The default\n  `alpinejs\u002Fdist\u002Fcdn.min.js` build is not the CSP build.\n- If Alpine code makes `fetch()` requests, include Django CSRF headers or use\n  existing HTMX\u002FDjango forms instead.\n\n## Validation\n\n- For template-only Alpine changes, run the Django template or view tests that\n  cover the page, plus `npm run lint` if JavaScript modules changed.\n- For HTMX interactions, test the full page and the partial response path.\n- For generated projects, run `npm run build` before relying on static output.\n- Manually verify stateful controls in light and dark mode when changing visible\n  UI behavior.\n","# Alpine.js with Django\n\nUse this skill for local browser state in Django-rendered templates: dropdowns,\nmodals, tabs, disclosures, inline filters, disabled\u002Floading states, small\npreview interactions, and client-only toggles. Use Django views\u002Fforms\u002Fmodels as\nthe source of truth for durable state. Use HTMX when the server needs to return\nfresh HTML.\n\n## Project setup\n\n- Alpine is installed from npm and copied by `scripts\u002Fcopy-vendor-assets.mjs`\n  to `frontend\u002Fstatic\u002Fvendors\u002Fjs\u002Falpine.min.js`.\n- `base_app.html` and `base_landing.html` load HTMX first, Alpine second, and\n  `frontend\u002Fstatic\u002Fjs\u002Fapp.js` third.\n- The loaded Alpine file is the self-starting CDN build. Do not call\n  `Alpine.start()` from `frontend\u002Fsrc\u002Fjs\u002Fapp.js`.\n- Simple Alpine behavior should usually live inline in the Django template with\n  `x-data`.\n- If a reusable component or store is worth extracting, register it before\n  Alpine starts. With the current script order, `frontend\u002Fsrc\u002Fjs\u002Fapp.js` runs too\n  late for reliable `document.addEventListener(\"alpine:init\", ...)`\n  registration unless the script order is changed.\n- When reusable Alpine registration is needed, add a dedicated classic script\n  such as `frontend\u002Fsrc\u002Fjs\u002Falpine-components.js`, register components\u002Fstores\n  inside `document.addEventListener(\"alpine:init\", ...)`, and include the copied\n  `frontend\u002Fstatic\u002Fjs\u002Falpine-components.js` before `vendors\u002Fjs\u002Falpine.min.js` in\n  both base templates. Keep `app.js` after Alpine, keep the self-starting Alpine\n  build, and still do not call `Alpine.start()` manually.\n\n## Ownership rules\n\n- Django owns persistence, authorization, validation, redirects, and rendered\n  HTML.\n- HTMX owns server round trips and DOM swaps.\n- Alpine owns ephemeral state already present in the browser.\n- Plain modules in `frontend\u002Fsrc\u002Fjs\u002F` own shared DOM behavior that is not\n  naturally scoped to one Alpine component.\n- Do not duplicate the same behavior in Alpine and a plain JS module.\n\n## Template patterns\n\nUse a small `x-data` object near the markup it controls:\n\n```html\n\u003Cdiv\n  x-data=\"{ open: false }\"\n  @keydown.escape.window=\"open = false\"\n  @click.outside=\"open = false\"\n>\n  \u003Cbutton\n    type=\"button\"\n    :aria-expanded=\"open.toString()\"\n    @click.stop=\"open = !open\"\n  >\n    Menu\n  \u003C\u002Fbutton>\n\n  \u003Cdiv x-cloak x-show=\"open\" x-transition>\n    ...\n  \u003C\u002Fdiv>\n\u003C\u002Fdiv>\n```\n\nPrefer Alpine directives over manual DOM manipulation:\n\n- `x-show` for toggling visibility while keeping the element in the DOM.\n- `x-if` on a `\u003Ctemplate>` when the element should be created and destroyed.\n- `x-model` for client-only input state; Django form submission and validation\n  still happen on the server.\n- `:class`, `:disabled`, `:aria-expanded`, and `:hidden` for state-derived\n  attributes.\n- `$watch` for one named state transition; `x-effect` only when the dependency\n  set is simple and intentional.\n- `$dispatch` for browser events between Alpine components or from Alpine to\n  HTMX triggers.\n\nUse `x-cloak` for anything hidden by default. The base templates already include\nthe required `[x-cloak] { display: none !important; }` CSS.\n\n## Django data\n\nKeep Django interpolation out of complex JavaScript expressions when possible.\n\nFor simple values, prefer HTML attributes:\n\n```html\n\u003Cdiv\n  data-initial-label=\"{{ object.name }}\"\n  x-data=\"{ label: '' }\"\n  x-init=\"label = $el.dataset.initialLabel\"\n>\n  \u003Cspan x-text=\"label\">\u003C\u002Fspan>\n\u003C\u002Fdiv>\n```\n\nFor structured values, prefer Django's `json_script` and parse it in `x-init`:\n\n```html\n{{ rows|json_script:\"rows-data\" }}\n\n\u003Cdiv\n  x-data=\"{ rows: [] }\"\n  x-init=\"rows = JSON.parse(document.getElementById('rows-data').textContent)\"\n>\n  \u003Ctemplate x-for=\"row in rows\" :key=\"row.id\">\n    \u003Cspan x-text=\"row.name\">\u003C\u002Fspan>\n  \u003C\u002Ftemplate>\n\u003C\u002Fdiv>\n```\n\nAvoid `|safe` inside Alpine expressions. If the browser must display text, use\n`x-text`. Use `x-html` only for trusted, already-sanitized HTML; most HTML should\nbe rendered by Django or returned through HTMX.\n\n## Alpine and HTMX\n\nWhen HTMX swaps a fragment containing `x-data`, Alpine should initialize the new\ncomponent automatically. Do not restart Alpine after HTMX swaps.\n\nKeep persistent Alpine state outside HTMX targets that will be replaced:\n\n```html\n\u003Csection x-data=\"{ panelOpen: false }\">\n  \u003Cbutton type=\"button\" @click=\"panelOpen = !panelOpen\">Filters\u003C\u002Fbutton>\n\n  \u003Cdiv id=\"results\" hx-get=\"{% url 'search_results' %}\" hx-trigger=\"change from:#filters\">\n    ...\n  \u003C\u002Fdiv>\n\u003C\u002Fsection>\n```\n\nUse events as the boundary between HTMX responses and Alpine state. From Django,\nset an `HX-Trigger` or `HX-Trigger-After-Swap` response header, then listen from\nAlpine:\n\n```html\n\u003Cdiv x-data=\"{ open: true }\" @profile-saved.window=\"open = false\">\n  \u003Cform hx-post=\"{% url 'profile_update' %}\" hx-target=\"#profile-panel\" hx-swap=\"outerHTML\">\n    ...\n  \u003C\u002Fform>\n\u003C\u002Fdiv>\n```\n\nListen for HTMX lifecycle events in kebab case from Alpine, such as\n`@htmx:after-swap.window`, because HTML attributes are case-insensitive.\n\nIf Alpine dispatches an event that HTMX should react to, make the trigger\nexplicit:\n\n```html\n\u003Cbutton type=\"button\" x-data @click=\"$dispatch('refresh-results')\">\n  Refresh\n\u003C\u002Fbutton>\n\n\u003Cdiv hx-get=\"{% url 'results' %}\" hx-trigger=\"refresh-results from:body\">\n  ...\n\u003C\u002Fdiv>\n```\n\n## Accessibility\n\n- Keep real buttons as `\u003Cbutton type=\"button\">` unless submitting a form.\n- Bind ARIA state from Alpine state, especially `aria-expanded`,\n  `aria-controls`, `aria-selected`, and `aria-hidden`.\n- Support `@keydown.escape.window` for dismissible overlays.\n- Use `@click.outside` for popovers and menus, paired with a visible trigger.\n- Preserve focus behavior for modals, menus, and swapped HTMX content. If focus\n  trapping is needed, add a focused plain JS module or Alpine plugin deliberately\n  instead of hand-rolling a brittle trap in attributes.\n\n## Security and CSP\n\n- Treat all Alpine expressions as JavaScript running in the user's browser.\n- Do not put secrets, signed tokens, or privileged data into `x-data`,\n  `data-*`, `json_script`, or hidden inputs unless the user is allowed to see\n  them.\n- If strict Content Security Policy without `unsafe-eval` is required, switch\n  deliberately to Alpine's CSP build and retest Alpine expressions. The default\n  `alpinejs\u002Fdist\u002Fcdn.min.js` build is not the CSP build.\n- If Alpine code makes `fetch()` requests, include Django CSRF headers or use\n  existing HTMX\u002FDjango forms instead.\n\n## Validation\n\n- For template-only Alpine changes, run the Django template or view tests that\n  cover the page, plus `npm run lint` if JavaScript modules changed.\n- For HTMX interactions, test the full page and the partial response path.\n- For generated projects, run `npm run build` before relying on static output.\n- Manually verify stateful controls in light and dark mode when changing visible\n  UI behavior.\n",{"name":5,"license":14,"metadata":23,"description":7,"compatibility":28},{"tags":24,"version":25,"category":26,"displayName":27},"alpinejs,django,frontend,htmx","0.1.0","Django","Alpine.js Django","Codex, Claude Code, and other Agent Skills-compatible clients.","main","9ba3c9fadff1092395837bf1502e1b8a7f98b1e1","plugins\u002Fcommunity\u002Flvtd-skills\u002Fskills\u002Falpinejs-django","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 alpinejs-django",{"tool":41,"command":42},"bunx","bunx skills add ConcertoNotes\u002Fcodex-plugins --skill alpinejs-django",{"tool":44,"command":45},"pnpm","pnpm dlx skills add ConcertoNotes\u002Fcodex-plugins --skill alpinejs-django","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcommunity\u002Flvtd-skills\u002Fskills\u002Falpinejs-django\u002FSKILL.md",true,[49],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"assets\u002Fapp-icon.png","ASSET","资产文件",38047,"https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcommunity\u002Flvtd-skills\u002Fskills\u002Falpinejs-django\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",[],[]]