[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C38QNHGT7XMXH78MRGFD2Q":3,"skill-same:01M7C38QNHGT7XMXH78MRGFD2Q":126},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M7C38QNHGT7XMXH78MRGFD2Q","theme-cms-business",null,"This skill should be used for service, company, clinic, education, and other non-store Laravel CMS themes with editable content, shared layout, assets, routes, pagination, and SEO QA.","Truc350\u002FWebHomeStay","Truc350","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F176447042?v=4","01M7C2S7D6AAK15J66E3NDXSXK","Huỳnh Thị Thanh Trúc","01M7C2S7DTPMN5ZM8876HF8KF8",0,"MIT","https:\u002F\u002Fgithub.com\u002FTruc350\u002FWebHomeStay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftheme-cms-business\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: theme-cms-business\ndescription: \"This skill should be used for service, company, clinic, education, and other non-store Laravel CMS themes with editable content, shared layout, assets, routes, pagination, and SEO QA.\"\nlicense: MIT\nmetadata:\n  version: \"5.1.0\"\n---\n\n# CMS Business Theme Builder\n\nCreate a complete installable business\u002Fservice theme for the configured Laravel CMS root. Treat `themes\\default` as the structural reference and a current industry theme as the quality example. Keep content, assets, widget settings, routes, and admin editing coherent. For a product catalog, ordering, cart, checkout, price, stock, or shop brief, activate `theme-cms-ecommerce` together with this foundation; do not use this skill alone to turn a service homepage into a storefront.\n\n## Business-mode boundary\n\n- Model the homepage around identity, services\u002Fprograms, proof, process, team, insights, contact, and conversion CTAs.\n- Keep products\u002Fcatalogs secondary unless the brief explicitly requests commerce; never invent cart, checkout, stock, prices, or purchase claims.\n- Use the shared commerce contracts only when the ecommerce skill is active; otherwise use service\u002Fcontact CTAs and factual lead forms.\n- Preserve all contracts below as the reusable base inherited by `theme-cms-ecommerce`.\n\n## Load References By Phase\n\n1. Start with [core-runtime.md](references\u002Fcore-runtime.md), [theme-structure.md](references\u002Ftheme-structure.md), [cms-data-routes.md](references\u002Fcms-data-routes.md), [internal-links.md](references\u002Finternal-links.md), and [commerce-sell.md](references\u002Fcommerce-sell.md) whenever the brief, sitemap, seed, or menu contains products, prices, buying, ordering, shop\u002Fstore language, or a Sản phẩm destination.\n2. Before writing `widgets.php`, load [widgets-registry.md](references\u002Fwidgets-registry.md), [widget-schema.md](references\u002Fwidget-schema.md), and [seed-data.md](references\u002Fseed-data.md).\n3. Before writing views\u002FCSS, load [global-shell.md](references\u002Fglobal-shell.md), [frontend-quality.md](references\u002Ffrontend-quality.md), [review-cards.md](references\u002Freview-cards.md), and [canonical-theme.md](references\u002Fcanonical-theme.md).\n4. Before listing pages, load [pagination.md](references\u002Fpagination.md). Before publishing assets, load [assets-cache.md](references\u002Fassets-cache.md).\n5. Before QA, load [deterministic-quality-gates.md](references\u002Fdeterministic-quality-gates.md).\n6. Before handoff, load [seo-gate.md](references\u002Fseo-gate.md), [validation.md](references\u002Fvalidation.md), and [troubleshooting.md](references\u002Ftroubleshooting.md).\n\n## Required Workflow\n\n1. Read the sitemap\u002Fdesign and inspect the current CMS files before creating anything.\n2. Inspect `themes\\default` and real widget variants under `public\\admin-assets\\widgets`; never clone `satc`, `helmet`, spa, shop, or another industry theme.\n3. Create `theme.json`, `widgets.php`, `seed.php`, complete route views, isolated widget overrides only where required, and theme assets.\n4. Make every visible setting editable through widget schema or an admin model\u002FSetting. Do not hide content in Blade fallbacks.\n5. Verify every `style_key` and every route before activation. Seed realistic industry data and valid menu URLs.\n6. Run `scripts\u002Fcheck-theme-quality.mjs`; fix every error before activation.\n7. Activate the theme, publish assets, clear view\u002Fcache state, and reseed blocks only when testing changed defaults.\n8. Run deterministic Auto CMS QA first, then only the mutable fixtures it lists as pending.\n9. Rerun the quality script after the last edit; stale QA evidence is invalid.\n10. Run the SEO skill at `.agents\u002Fskills\u002Fseo\u002FSKILL.md` against the public URL. Fix Critical\u002FHigh findings before completion.\n11. Package with `php artisan theme:package {slug}` and inspect the ZIP contents.\n\n## Non-Negotiable Contracts\n\n- Public views extend one `layouts.app`; that layout owns header, footer, float zones, head metadata, versioned CSS\u002FJS, and global blocks.\n- Header\u002Ffooter use the same zone data on every route. Header logo reads admin `site_logo`; block `settings.logo` never overrides it.\n- Homepage is block-driven. Declare every admin zone, especially `footer_top`, `footer_1..3`, `footer_bottom`, and `float_left\u002Fright`.\n- Use `theme_asset()` for theme images and `versioned_theme_asset()` for CSS\u002FJS. Never use `filemtime()` or stale static versions.\n- Every admin-editable image resolver must distinguish seeded theme paths from uploaded storage paths. Never pass a raw widget image setting directly to `asset()`; follow the resolver contract in `assets-cache.md` and test an actual admin upload before packaging.\n- Use `pagination::theme`, preserve query strings, and constrain pagination SVGs to 15–16px.\n- Use `cms_content()` for admin-authored rich content. Use `role` for testimonials, `theme-assets\u002F{slug}\u002F...` for seeded asset paths, and real routes only.\n- Resolve every admin\u002Fwidget-provided internal CTA or menu URL through Laravel `url()`\u002Fnamed routes. Never output a raw leading-slash path such as `\u002Fsan-pham`: it escapes subfolder deployments such as `\u002Fcms\u002Fpublic` and can return Not Found.\n- Classify a theme as commerce-capable when its business type sells products or its intended primary menu contains Sản phẩm. Declare `supports.products` and `supports.commerce.purchase_action` in `theme.json`, and render every buy\u002Fprice action through `cms_product_purchase_button()` with a non-plugin fallback. Never hardcode a `sell.*` route in a theme.\n- Validate rendered anchors with browser-equivalent URL resolution against the actual public page URL. Do not prepend `APP_URL` manually during tests, because that can hide broken root-relative links.\n- Keep heading line breaks semantic and editable. Avoid `break-all`, global `anywhere`, random `\u003Cbr>`, or copied old-theme content.\n\n## Mandatory UI Quality Contracts\n\n### Footer: one source of truth\n\n- Render footer identity, contact, and navigation from shared footer zones and global Settings. Do not add a second hardcoded contact column beside footer_3.\n- Give every footer zone a deliberate fallback, but suppress that fallback when the corresponding admin zone has content.\n- Render the footer on every public route from the same layout block collection; never duplicate footer markup in a route view.\n- Verify the rendered footer has exactly one contact heading, one brand\u002Fcontact identity, no duplicate phone\u002Faddress blocks, and no unexpected wrapping to a new row at desktop widths.\n- Keep footer columns responsive: four columns on wide screens, two on tablet, one on mobile, without duplicate or orphan columns.\n\n### Listings and pagination\n\n- Apply this contract to every grid\u002Fcard listing that can grow: products, services, news\u002Fposts, testimonials\u002Freviews, destinations, galleries, portfolios, projects, FAQs, and any theme-specific collection—not only named core routes.\n- The desktop grid may use any deliberate column count. Keep at most two rows per page: page size = desktop columns × 2 (for example, 4 columns = 8 items\u002Fpage; 3 columns = 6 items\u002Fpage; 2 columns = 4 items\u002Fpage). Do not hardcode six globally.\n- Store the calculated page-size default in the theme seed Settings and keep it editable through the CMS pagination settings. If the responsive desktop column count changes by breakpoint, use the largest intended desktop count for pagination and document the choice.\n- Use the shared pagination::theme view for every paginated listing and preserve search\u002Fcategory query strings.\n- Test page 1 and page 2 for every listing with enough seed data to cross that theme’s calculated boundary. Confirm page 1 never renders a third row at the intended desktop width, page 2 returns the remainder, and mobile collapses predictably.\n- Add an intentional empty state and fixed card image aspect ratios\u002Fheights so one intrinsic image cannot stretch a row.\n\n### Review\u002Ftestimonial cards\n\n- Use the model avatar accessor or the full mixed-path resolver so uploaded, seeded, and remote avatars all resolve correctly.\n- Render initials underneath every remote avatar, not only when its URL is initially empty. Hide only the failed `\u003Cimg>` in `onerror`; never let an expired, blocked, or late-failing Google avatar expose a broken-image icon or an empty circle.\n- Derive stable initials from the first letters of the first two name words, preserve reviewer name, role\u002Fsource, rating, and full content, and use the same avatar partial on homepage and review listing\u002Fdetail surfaces.\n- Make review cards equal-height flex columns. The quote\u002Fcontent area grows with flex: 1; avatar, name, and role stay aligned at the bottom of every card in the row.\n- Clamp long review excerpts to a deliberate line count in the default grid. Provide an accessible `Xem đầy đủ` control that reveals the complete unmodified review in a dialog or equivalent bounded scroll surface; expanding content must not stretch the other cards in the row.\n- Keep the rating summary and review CTA editable and factual. Use a clear action label such as Viết đánh giá when linking to Google review submission.\n- Test missing avatars, valid local\u002Fuploaded avatars, valid remote avatars, deliberately broken remote URLs, slow\u002Flate failures, and short\u002Fmedium\u002Fvery long reviews. Authors must remain aligned per row on desktop and stack cleanly on mobile.\n\n### Typography and wrapping system\n\n- Define one theme-wide typography token scale (headline-xl, headline-lg, headline-md, body, label) in theme CSS. Apply the same tokens to hero, sections, cards, reviews, CTA, detail pages, and footer headings; do not fix one block with unrelated one-off sizes.\n- Set global heading rules to text-wrap: balance, word-break: normal, and overflow-wrap: normal. Set body\u002Fcopy rules to text-wrap: pretty; never use global white-space: nowrap for content.\n- All flex\u002Fgrid text columns must set min-width: 0; heading and copy wrappers must be allowed to grow before text wraps.\n- Avoid one-word orphan lines in hero titles, review summaries, navigation labels, CTA headings, card titles, and metadata. Prefer a wider text column, a coherent font scale, or an editable semantic break over arbitrary line-break tags.\n- Any intentional nowrap must be limited to compact UI labels and verified not to overflow at 320px.\n- Test rendered typography at 1440, 1024, 768, 390, 375, and 320px. Inspect every H1\u002FH2\u002FH3 and major paragraph for orphan words, clipped text, horizontal overflow, and inconsistent scale. Fix the shared token\u002Flayout rule, not only a screenshot-specific selector.\n\n## Completion Evidence\n\nReport the theme path, package path, active theme, routes tested, rendered internal-link audit, asset release URL, admin layout result, seed counts, SEO audit result, remaining risks, and whether `php artisan theme:package {slug}` succeeded. For commerce-capable themes, also report the manifest capability, product-detail\u002Fcard purchase surfaces, inactive-plugin fallback result, active-`sell` POST\u002FCSRF result, cart redirect, and out-of-stock state. Include footer duplicate audit, listing page-size\u002Fpage-2 audit, review avatar\u002Fequal-height audit, and typography\u002Fwrapping responsive audit. Do not report completion when the SEO gate, any internal CTA\u002Fmenu returns an unintended 404, any Critical\u002FHigh functional check, or any mandatory UI quality contract is unresolved.\n","# CMS Business Theme Builder\n\nCreate a complete installable business\u002Fservice theme for the configured Laravel CMS root. Treat `themes\\default` as the structural reference and a current industry theme as the quality example. Keep content, assets, widget settings, routes, and admin editing coherent. For a product catalog, ordering, cart, checkout, price, stock, or shop brief, activate `theme-cms-ecommerce` together with this foundation; do not use this skill alone to turn a service homepage into a storefront.\n\n## Business-mode boundary\n\n- Model the homepage around identity, services\u002Fprograms, proof, process, team, insights, contact, and conversion CTAs.\n- Keep products\u002Fcatalogs secondary unless the brief explicitly requests commerce; never invent cart, checkout, stock, prices, or purchase claims.\n- Use the shared commerce contracts only when the ecommerce skill is active; otherwise use service\u002Fcontact CTAs and factual lead forms.\n- Preserve all contracts below as the reusable base inherited by `theme-cms-ecommerce`.\n\n## Load References By Phase\n\n1. Start with [core-runtime.md](references\u002Fcore-runtime.md), [theme-structure.md](references\u002Ftheme-structure.md), [cms-data-routes.md](references\u002Fcms-data-routes.md), [internal-links.md](references\u002Finternal-links.md), and [commerce-sell.md](references\u002Fcommerce-sell.md) whenever the brief, sitemap, seed, or menu contains products, prices, buying, ordering, shop\u002Fstore language, or a Sản phẩm destination.\n2. Before writing `widgets.php`, load [widgets-registry.md](references\u002Fwidgets-registry.md), [widget-schema.md](references\u002Fwidget-schema.md), and [seed-data.md](references\u002Fseed-data.md).\n3. Before writing views\u002FCSS, load [global-shell.md](references\u002Fglobal-shell.md), [frontend-quality.md](references\u002Ffrontend-quality.md), [review-cards.md](references\u002Freview-cards.md), and [canonical-theme.md](references\u002Fcanonical-theme.md).\n4. Before listing pages, load [pagination.md](references\u002Fpagination.md). Before publishing assets, load [assets-cache.md](references\u002Fassets-cache.md).\n5. Before QA, load [deterministic-quality-gates.md](references\u002Fdeterministic-quality-gates.md).\n6. Before handoff, load [seo-gate.md](references\u002Fseo-gate.md), [validation.md](references\u002Fvalidation.md), and [troubleshooting.md](references\u002Ftroubleshooting.md).\n\n## Required Workflow\n\n1. Read the sitemap\u002Fdesign and inspect the current CMS files before creating anything.\n2. Inspect `themes\\default` and real widget variants under `public\\admin-assets\\widgets`; never clone `satc`, `helmet`, spa, shop, or another industry theme.\n3. Create `theme.json`, `widgets.php`, `seed.php`, complete route views, isolated widget overrides only where required, and theme assets.\n4. Make every visible setting editable through widget schema or an admin model\u002FSetting. Do not hide content in Blade fallbacks.\n5. Verify every `style_key` and every route before activation. Seed realistic industry data and valid menu URLs.\n6. Run `scripts\u002Fcheck-theme-quality.mjs`; fix every error before activation.\n7. Activate the theme, publish assets, clear view\u002Fcache state, and reseed blocks only when testing changed defaults.\n8. Run deterministic Auto CMS QA first, then only the mutable fixtures it lists as pending.\n9. Rerun the quality script after the last edit; stale QA evidence is invalid.\n10. Run the SEO skill at `.agents\u002Fskills\u002Fseo\u002FSKILL.md` against the public URL. Fix Critical\u002FHigh findings before completion.\n11. Package with `php artisan theme:package {slug}` and inspect the ZIP contents.\n\n## Non-Negotiable Contracts\n\n- Public views extend one `layouts.app`; that layout owns header, footer, float zones, head metadata, versioned CSS\u002FJS, and global blocks.\n- Header\u002Ffooter use the same zone data on every route. Header logo reads admin `site_logo`; block `settings.logo` never overrides it.\n- Homepage is block-driven. Declare every admin zone, especially `footer_top`, `footer_1..3`, `footer_bottom`, and `float_left\u002Fright`.\n- Use `theme_asset()` for theme images and `versioned_theme_asset()` for CSS\u002FJS. Never use `filemtime()` or stale static versions.\n- Every admin-editable image resolver must distinguish seeded theme paths from uploaded storage paths. Never pass a raw widget image setting directly to `asset()`; follow the resolver contract in `assets-cache.md` and test an actual admin upload before packaging.\n- Use `pagination::theme`, preserve query strings, and constrain pagination SVGs to 15–16px.\n- Use `cms_content()` for admin-authored rich content. Use `role` for testimonials, `theme-assets\u002F{slug}\u002F...` for seeded asset paths, and real routes only.\n- Resolve every admin\u002Fwidget-provided internal CTA or menu URL through Laravel `url()`\u002Fnamed routes. Never output a raw leading-slash path such as `\u002Fsan-pham`: it escapes subfolder deployments such as `\u002Fcms\u002Fpublic` and can return Not Found.\n- Classify a theme as commerce-capable when its business type sells products or its intended primary menu contains Sản phẩm. Declare `supports.products` and `supports.commerce.purchase_action` in `theme.json`, and render every buy\u002Fprice action through `cms_product_purchase_button()` with a non-plugin fallback. Never hardcode a `sell.*` route in a theme.\n- Validate rendered anchors with browser-equivalent URL resolution against the actual public page URL. Do not prepend `APP_URL` manually during tests, because that can hide broken root-relative links.\n- Keep heading line breaks semantic and editable. Avoid `break-all`, global `anywhere`, random `\u003Cbr>`, or copied old-theme content.\n\n## Mandatory UI Quality Contracts\n\n### Footer: one source of truth\n\n- Render footer identity, contact, and navigation from shared footer zones and global Settings. Do not add a second hardcoded contact column beside footer_3.\n- Give every footer zone a deliberate fallback, but suppress that fallback when the corresponding admin zone has content.\n- Render the footer on every public route from the same layout block collection; never duplicate footer markup in a route view.\n- Verify the rendered footer has exactly one contact heading, one brand\u002Fcontact identity, no duplicate phone\u002Faddress blocks, and no unexpected wrapping to a new row at desktop widths.\n- Keep footer columns responsive: four columns on wide screens, two on tablet, one on mobile, without duplicate or orphan columns.\n\n### Listings and pagination\n\n- Apply this contract to every grid\u002Fcard listing that can grow: products, services, news\u002Fposts, testimonials\u002Freviews, destinations, galleries, portfolios, projects, FAQs, and any theme-specific collection—not only named core routes.\n- The desktop grid may use any deliberate column count. Keep at most two rows per page: page size = desktop columns × 2 (for example, 4 columns = 8 items\u002Fpage; 3 columns = 6 items\u002Fpage; 2 columns = 4 items\u002Fpage). Do not hardcode six globally.\n- Store the calculated page-size default in the theme seed Settings and keep it editable through the CMS pagination settings. If the responsive desktop column count changes by breakpoint, use the largest intended desktop count for pagination and document the choice.\n- Use the shared pagination::theme view for every paginated listing and preserve search\u002Fcategory query strings.\n- Test page 1 and page 2 for every listing with enough seed data to cross that theme’s calculated boundary. Confirm page 1 never renders a third row at the intended desktop width, page 2 returns the remainder, and mobile collapses predictably.\n- Add an intentional empty state and fixed card image aspect ratios\u002Fheights so one intrinsic image cannot stretch a row.\n\n### Review\u002Ftestimonial cards\n\n- Use the model avatar accessor or the full mixed-path resolver so uploaded, seeded, and remote avatars all resolve correctly.\n- Render initials underneath every remote avatar, not only when its URL is initially empty. Hide only the failed `\u003Cimg>` in `onerror`; never let an expired, blocked, or late-failing Google avatar expose a broken-image icon or an empty circle.\n- Derive stable initials from the first letters of the first two name words, preserve reviewer name, role\u002Fsource, rating, and full content, and use the same avatar partial on homepage and review listing\u002Fdetail surfaces.\n- Make review cards equal-height flex columns. The quote\u002Fcontent area grows with flex: 1; avatar, name, and role stay aligned at the bottom of every card in the row.\n- Clamp long review excerpts to a deliberate line count in the default grid. Provide an accessible `Xem đầy đủ` control that reveals the complete unmodified review in a dialog or equivalent bounded scroll surface; expanding content must not stretch the other cards in the row.\n- Keep the rating summary and review CTA editable and factual. Use a clear action label such as Viết đánh giá when linking to Google review submission.\n- Test missing avatars, valid local\u002Fuploaded avatars, valid remote avatars, deliberately broken remote URLs, slow\u002Flate failures, and short\u002Fmedium\u002Fvery long reviews. Authors must remain aligned per row on desktop and stack cleanly on mobile.\n\n### Typography and wrapping system\n\n- Define one theme-wide typography token scale (headline-xl, headline-lg, headline-md, body, label) in theme CSS. Apply the same tokens to hero, sections, cards, reviews, CTA, detail pages, and footer headings; do not fix one block with unrelated one-off sizes.\n- Set global heading rules to text-wrap: balance, word-break: normal, and overflow-wrap: normal. Set body\u002Fcopy rules to text-wrap: pretty; never use global white-space: nowrap for content.\n- All flex\u002Fgrid text columns must set min-width: 0; heading and copy wrappers must be allowed to grow before text wraps.\n- Avoid one-word orphan lines in hero titles, review summaries, navigation labels, CTA headings, card titles, and metadata. Prefer a wider text column, a coherent font scale, or an editable semantic break over arbitrary line-break tags.\n- Any intentional nowrap must be limited to compact UI labels and verified not to overflow at 320px.\n- Test rendered typography at 1440, 1024, 768, 390, 375, and 320px. Inspect every H1\u002FH2\u002FH3 and major paragraph for orphan words, clipped text, horizontal overflow, and inconsistent scale. Fix the shared token\u002Flayout rule, not only a screenshot-specific selector.\n\n## Completion Evidence\n\nReport the theme path, package path, active theme, routes tested, rendered internal-link audit, asset release URL, admin layout result, seed counts, SEO audit result, remaining risks, and whether `php artisan theme:package {slug}` succeeded. For commerce-capable themes, also report the manifest capability, product-detail\u002Fcard purchase surfaces, inactive-plugin fallback result, active-`sell` POST\u002FCSRF result, cart redirect, and out-of-stock state. Include footer duplicate audit, listing page-size\u002Fpage-2 audit, review avatar\u002Fequal-height audit, and typography\u002Fwrapping responsive audit. Do not report completion when the SEO gate, any internal CTA\u002Fmenu returns an unintended 404, any Critical\u002FHigh functional check, or any mandatory UI quality contract is unresolved.\n",{"name":5,"license":15,"metadata":24,"description":7},{"version":25},"5.1.0","main","af64bb75a16e8bc1847a568059b9300e09f27c4a",".agents\u002Fskills\u002Ftheme-cms-business","https:\u002F\u002Fgithub.com\u002FTruc350\u002FWebHomeStay","https:\u002F\u002Fgithub.com\u002FTruc350","2026-09-04 21:59:58",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Truc350\u002FWebHomeStay --skill theme-cms-business",{"tool":38,"command":39},"bunx","bunx skills add Truc350\u002FWebHomeStay --skill theme-cms-business",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Truc350\u002FWebHomeStay --skill theme-cms-business","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTruc350\u002FWebHomeStay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftheme-cms-business\u002FSKILL.md",true,[46,52,56,60,64,68,72,76,80,84,88,92,96,100,104,108,112,116,120],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fassets-cache.md","REFERENCE","参考文档",3949,"https:\u002F\u002Fgithub.com\u002FTruc350\u002FWebHomeStay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftheme-cms-business\u002Freferences\u002Fassets-cache.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fcanonical-theme.md",2633,"https:\u002F\u002Fgithub.com\u002FTruc350\u002FWebHomeStay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftheme-cms-business\u002Freferences\u002Fcanonical-theme.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fcms-data-routes.md",3585,"https:\u002F\u002Fgithub.com\u002FTruc350\u002FWebHomeStay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftheme-cms-business\u002Freferences\u002Fcms-data-routes.md",{"path":61,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fcommerce-sell.md",4245,"https:\u002F\u002Fgithub.com\u002FTruc350\u002FWebHomeStay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftheme-cms-business\u002Freferences\u002Fcommerce-sell.md",{"path":65,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fcore-runtime.md",3146,"https:\u002F\u002Fgithub.com\u002FTruc350\u002FWebHomeStay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftheme-cms-business\u002Freferences\u002Fcore-runtime.md",{"path":69,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Fdeterministic-quality-gates.md",1620,"https:\u002F\u002Fgithub.com\u002FTruc350\u002FWebHomeStay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftheme-cms-business\u002Freferences\u002Fdeterministic-quality-gates.md",{"path":73,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Ffrontend-quality.md",3298,"https:\u002F\u002Fgithub.com\u002FTruc350\u002FWebHomeStay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftheme-cms-business\u002Freferences\u002Ffrontend-quality.md",{"path":77,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fglobal-shell.md",3155,"https:\u002F\u002Fgithub.com\u002FTruc350\u002FWebHomeStay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftheme-cms-business\u002Freferences\u002Fglobal-shell.md",{"path":81,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Finternal-links.md",3073,"https:\u002F\u002Fgithub.com\u002FTruc350\u002FWebHomeStay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftheme-cms-business\u002Freferences\u002Finternal-links.md",{"path":85,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fpagination.md",2430,"https:\u002F\u002Fgithub.com\u002FTruc350\u002FWebHomeStay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftheme-cms-business\u002Freferences\u002Fpagination.md",{"path":89,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Freview-cards.md",3676,"https:\u002F\u002Fgithub.com\u002FTruc350\u002FWebHomeStay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftheme-cms-business\u002Freferences\u002Freview-cards.md",{"path":93,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Fseed-data.md",2760,"https:\u002F\u002Fgithub.com\u002FTruc350\u002FWebHomeStay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftheme-cms-business\u002Freferences\u002Fseed-data.md",{"path":97,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":98,"sourceHtmlUrl":99},"references\u002Fseo-gate.md",1830,"https:\u002F\u002Fgithub.com\u002FTruc350\u002FWebHomeStay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftheme-cms-business\u002Freferences\u002Fseo-gate.md",{"path":101,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":102,"sourceHtmlUrl":103},"references\u002Ftheme-structure.md",3294,"https:\u002F\u002Fgithub.com\u002FTruc350\u002FWebHomeStay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftheme-cms-business\u002Freferences\u002Ftheme-structure.md",{"path":105,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":106,"sourceHtmlUrl":107},"references\u002Ftroubleshooting.md",6556,"https:\u002F\u002Fgithub.com\u002FTruc350\u002FWebHomeStay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftheme-cms-business\u002Freferences\u002Ftroubleshooting.md",{"path":109,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":110,"sourceHtmlUrl":111},"references\u002Fvalidation.md",4531,"https:\u002F\u002Fgithub.com\u002FTruc350\u002FWebHomeStay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftheme-cms-business\u002Freferences\u002Fvalidation.md",{"path":113,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":114,"sourceHtmlUrl":115},"references\u002Fwidget-schema.md",3079,"https:\u002F\u002Fgithub.com\u002FTruc350\u002FWebHomeStay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftheme-cms-business\u002Freferences\u002Fwidget-schema.md",{"path":117,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":118,"sourceHtmlUrl":119},"references\u002Fwidgets-registry.md",2943,"https:\u002F\u002Fgithub.com\u002FTruc350\u002FWebHomeStay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftheme-cms-business\u002Freferences\u002Fwidgets-registry.md",{"path":121,"resourceType":122,"resourceTypeDesc":123,"sizeBytes":124,"sourceHtmlUrl":125},"scripts\u002Fcheck-theme-quality.mjs","SCRIPT","脚本",3754,"https:\u002F\u002Fgithub.com\u002FTruc350\u002FWebHomeStay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftheme-cms-business\u002Fscripts\u002Fcheck-theme-quality.mjs",[127,134,141,148,156,163],{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":19},"01M7C3D9JFFHDYQ93YQ2NFSTXV","widget-cms","Tạo, sửa và kiểm thử widget Laravel CMS theo renderer theme\u002Fcore\u002Fplugin, layout builder, settings_schema, shortcode, hook, CSS\u002FJS và zone contract.","https:\u002F\u002Fgithub.com\u002FTruc350\u002FWebHomeStay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwidget-cms\u002FSKILL.md",[],[],{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":19},"01M7C3CNZVN589PK7ZJ1JZ98JB","website-sitemap","This skill should be used to create, crawl, map, redesign, or migrate website sitemaps and information architecture from briefs, ERP data, URLs, documents, or mixed inputs.","https:\u002F\u002Fgithub.com\u002FTruc350\u002FWebHomeStay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwebsite-sitemap\u002FSKILL.md",[],[],{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":147,"publishedAt":19},"01M7C3C36PECBZQR0RBXGE8781","web-frameworks","Build with Next.js (App Router, RSC, SSR, ISR), Turborepo monorepos. Use for React apps, server rendering, build optimization, caching strategies, shared dependencies.","https:\u002F\u002Fgithub.com\u002FTruc350\u002FWebHomeStay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fweb-frameworks\u002FSKILL.md",[],[],{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":152,"sourceHtmlUrl":153,"categories":154,"keywords":155,"publishedAt":19},"01M7C3A7X0WG8RWDDJFB9CHP0F","ui-styling","Style UIs with shadcn\u002Fui components (Radix UI + Tailwind CSS). Use for accessible components, themes, dark mode, responsive layouts, design systems, color customization.","https:\u002F\u002Fgithub.com\u002FTruc350\u002FWebHomeStay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fui-styling\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FTruc350\u002FWebHomeStay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fui-styling\u002FSKILL.md",[],[],{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":162,"publishedAt":19},"01M7C39497ER4DVF3R8P9R6K41","threejs","Build 3D web apps with Three.js (WebGL\u002FWebGPU). 556 searchable examples, 60 API classes, 20 use cases. Actions: create 3D scene, load model, add animation, implement physics, build VR\u002FXR. Topics: GLTF loader, PBR materials, particle effects, shadows, post-processing, compute shaders, TSL. Integrations: WebGPU, physics engines, spatial audio.","https:\u002F\u002Fgithub.com\u002FTruc350\u002FWebHomeStay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fthreejs\u002FSKILL.md",[],[],{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":169,"publishedAt":19},"01M7C38TQE66MV142R5K58QJM6","theme-cms-ecommerce","This skill should be used independently to create, update, validate, or package complete Laravel CMS storefronts with product catalogs, search, promotions, cart, checkout, and responsive shopping UX.","https:\u002F\u002Fgithub.com\u002FTruc350\u002FWebHomeStay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftheme-cms-ecommerce\u002FSKILL.md",[],[]]