[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6BSTWDNE049GH977VC3QBVR":3,"skill-same:01M6BSTWDNE049GH977VC3QBVR":98},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":6,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":56,"updatedAt":57,"install":58,"resources":71},"01M6BSTWDNE049GH977VC3QBVR","stripe-best-practices",null,"Guides Stripe integration decisions across development and test environment planning (separate sandboxes vs the shared test mode sandbox), API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing\u002Fsubscriptions, tax and registrations (Stripe Tax, automatic_tax, product tax codes), Treasury financial accounts, integration options (Checkout, Payment Element), migrating from deprecated Stripe APIs, and security best practices (API key management, API key permissions, webhooks, OAuth). Use when planning, building, modifying, testing, or reviewing any Stripe integration, including choosing a development environment, accepting payments, building marketplaces, integrating Stripe, processing payments, setting up subscriptions, collecting sales tax, VAT, or GST, creating connected accounts, or implementing secure key handling.","mikker\u002Fdotfiles","mikker","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F2819?v=4","01M6BSPF9WRVEQ89CW9NNJ7JK4","Mikkel Malmberg","01M6BSPFEEZKZSB4B603CZGV9W",115,"MIT","https:\u002F\u002Fgithub.com\u002Fmikker\u002Fdotfiles\u002Fblob\u002Fmaster\u002Fagents.symlink\u002Fskills\u002Fstripe-best-practices\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"stripe best practices","best practices","permissions","api","stripe integration","controller","OAuth","payments","integration","security best practices","product","testing","planning","connect","development","secure","sessions","test","security","sandbox","2026-11-10 10:12:30",false,"---\nname: stripe-best-practices\ndescription: >-\n  Guides Stripe integration decisions across development and test environment\n  planning (separate sandboxes vs the shared test mode sandbox), API selection\n  (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2,\n  controller properties), billing\u002Fsubscriptions, tax and registrations (Stripe\n  Tax, automatic_tax, product tax codes), Treasury financial accounts,\n  integration options (Checkout, Payment Element), migrating from deprecated\n  Stripe APIs, and security best practices (API key management, API key\n  permissions, webhooks, OAuth). Use when planning, building, modifying,\n  testing, or reviewing any Stripe integration, including choosing a development\n  environment, accepting payments, building marketplaces, integrating Stripe,\n  processing payments, setting up subscriptions, collecting sales tax, VAT, or\n  GST, creating connected accounts, or implementing secure key handling.\n\n---\n\nLatest Stripe API version: **2026-08-26.dahlia**. Always use the latest API version and SDK unless the user specifies otherwise.\n\nDevelopment and testing environment default: For new integration development, use separate [sandboxes](https:\u002F\u002Fdocs.stripe.com\u002Fsandboxes.md) instead of the account’s shared test mode sandbox. Sandboxes isolate settings and test data from live mode. Use separate sandboxes for local development and CI. When stronger isolation is useful, dedicate sandboxes to development teams or testing scenarios. Use the shared test mode sandbox only for an existing integration that depends on it or when a required feature doesn’t support general sandboxes.\n\nLatest SDK versions:\n\n| Language | Latest version |\n| --- | --- |\n| Ruby | 19.6.0 |\n| Python | 15.6.0 |\n| Node.js | 22.6.0 |\n| PHP | 21.3.0 |\n| Java | 33.4.0 |\n| Go | 86.4.0 |\n| .NET | 52.4.0 |\n\nIf you don’t have a Stripe account, you can use the CLI to generate a sandbox test account with no registration required. Install the Stripe CLI (`npm i -g @stripe\u002Fcli`) and run the command `stripe sandbox create`, which creates test API keys for you. When you recommend this, explain that [a sandbox is a Stripe test environment](https:\u002F\u002Fdocs.stripe.com\u002Fsandboxes.md).\n\nIf `stripe sandbox create` is used, don’t use MCP.\n\nIf you try to use MCP after running sandbox creation, first make sure `stripe sandbox claim` is run. Use `stripe whoami --format json` for CLI auth checks; do not run `stripe config --list`.\n\nAPI key default: Always recommend a [restricted API key (RAK)](https:\u002F\u002Fdocs.stripe.com\u002Fkeys.md#manage-your-api-keys) (`rk_` prefix) over a secret key (`sk_` prefix).\n\n## Integration routing\n\n| Building… | Recommended API | Details |\n| --- | --- | --- |\n| One-time payments | Checkout Sessions | \u003Creferences\u002Fpayments.md> |\n| Custom payment form with embedded UI | Checkout Sessions + Payment Element | \u003Creferences\u002Fpayments.md> |\n| Saving a payment method for later | Setup Intents | \u003Creferences\u002Fpayments.md> |\n| Connect platform or marketplace | Accounts v2 (`\u002Fv2\u002Fcore\u002Faccounts`) | \u003Creferences\u002Fconnect.md> |\n| Usage-based billing (new integration) | Metronome | \u003Creferences\u002Fbilling.md> |\n| Subscriptions or recurring billing | Billing APIs + Checkout Sessions | \u003Creferences\u002Fbilling.md> |\n| Sales tax, VAT, or GST compliance | Stripe Tax + Registrations API | \u003Creferences\u002Ftax.md> |\n| Embedded financial accounts \u002F banking | v2 Financial Accounts | \u003Creferences\u002Ftreasury.md> |\n| Security (key management, RAKs, webhooks, OAuth, 2FA, Connect liability) | See security reference | \u003Creferences\u002Fsecurity.md> |\n\nRead the relevant reference file before answering any integration question or writing code.\n\n## Critical rules\n\n- *Before enabling `automatic_tax: { enabled: true }`* (or calculating tax for a custom PaymentIntent), read the [tax reference](references\u002Ftax.md) and confirm the user has an active registration. Without one, Stripe calculates and collects no tax while the user believes tax is on (the most common Stripe Tax mistake).\n\n- *Never include `payment_method_types` in any Stripe API call*, with one exception: Terminal (in-person payments) integrations must pass `payment_method_types: ['card_present']` on the PaymentIntent. For all other integrations, omit this parameter entirely to enable dynamic payment methods, which enables you to configure payment method settings from the Dashboard and dynamically display the most relevant eligible payment methods to each customer to maximize conversion. To customize which payment methods you accept, use [`payment_method_configurations`](https:\u002F\u002Fdocs.stripe.com\u002Fpayments\u002Fpayment-method-configurations.md) or `excluded_payment_method_types` instead of `payment_method_types`.\n\n- When a PaymentIntent or SetupIntent integration requires an explicit allowlist, use `allowed_payment_method_types` instead of `payment_method_types`.\n\n- *Never present webhooks as optional.* We recommend webhooks for every payment integration and they’re required for subscriptions and asynchronous payment methods. Fulfillment belongs in a handler for both `checkout.session.completed` and `checkout.session.async_payment_succeeded` (gated on `payment_status`), not the success page. See \u003Creferences\u002Fpayments.md>.\n\n- On API version `2026-03-25.dahlia` or later, pass the parameter `integration_identifier` to `checkout.sessions.create` to tag sessions with a custom label for tracking and comparing checkout flows in the Dashboard. The label should include a suffix of 8 random letters.\n\n- *Always instantiate a `StripeClient` and call methods on that instance.* Do **not** use the deprecated global\u002Fmodule-level API key pattern (`stripe.api_key = …`, `Stripe.setApiKey`, `stripe.Key = …`, `StripeConfiguration.ApiKey = …`). The global pattern is deprecated in all current SDKs.\n\n## Key documentation\n\nWhen the user’s request does not clearly fit a single domain above, consult:\n\n- [Integration Options](https:\u002F\u002Fdocs.stripe.com\u002Fpayments\u002Fpayment-methods\u002Fintegration-options.md) — Start here when designing any integration.\n- [API Tour](https:\u002F\u002Fdocs.stripe.com\u002Fpayments-api\u002Ftour.md) — Overview of Stripe’s API surface.\n- [Go Live Checklist](https:\u002F\u002Fdocs.stripe.com\u002Fget-started\u002Fchecklist\u002Fgo-live.md) — Review before launching.\n","Latest Stripe API version: **2026-08-26.dahlia**. Always use the latest API version and SDK unless the user specifies otherwise.\n\nDevelopment and testing environment default: For new integration development, use separate [sandboxes](https:\u002F\u002Fdocs.stripe.com\u002Fsandboxes.md) instead of the account’s shared test mode sandbox. Sandboxes isolate settings and test data from live mode. Use separate sandboxes for local development and CI. When stronger isolation is useful, dedicate sandboxes to development teams or testing scenarios. Use the shared test mode sandbox only for an existing integration that depends on it or when a required feature doesn’t support general sandboxes.\n\nLatest SDK versions:\n\n| Language | Latest version |\n| --- | --- |\n| Ruby | 19.6.0 |\n| Python | 15.6.0 |\n| Node.js | 22.6.0 |\n| PHP | 21.3.0 |\n| Java | 33.4.0 |\n| Go | 86.4.0 |\n| .NET | 52.4.0 |\n\nIf you don’t have a Stripe account, you can use the CLI to generate a sandbox test account with no registration required. Install the Stripe CLI (`npm i -g @stripe\u002Fcli`) and run the command `stripe sandbox create`, which creates test API keys for you. When you recommend this, explain that [a sandbox is a Stripe test environment](https:\u002F\u002Fdocs.stripe.com\u002Fsandboxes.md).\n\nIf `stripe sandbox create` is used, don’t use MCP.\n\nIf you try to use MCP after running sandbox creation, first make sure `stripe sandbox claim` is run. Use `stripe whoami --format json` for CLI auth checks; do not run `stripe config --list`.\n\nAPI key default: Always recommend a [restricted API key (RAK)](https:\u002F\u002Fdocs.stripe.com\u002Fkeys.md#manage-your-api-keys) (`rk_` prefix) over a secret key (`sk_` prefix).\n\n## Integration routing\n\n| Building… | Recommended API | Details |\n| --- | --- | --- |\n| One-time payments | Checkout Sessions | \u003Creferences\u002Fpayments.md> |\n| Custom payment form with embedded UI | Checkout Sessions + Payment Element | \u003Creferences\u002Fpayments.md> |\n| Saving a payment method for later | Setup Intents | \u003Creferences\u002Fpayments.md> |\n| Connect platform or marketplace | Accounts v2 (`\u002Fv2\u002Fcore\u002Faccounts`) | \u003Creferences\u002Fconnect.md> |\n| Usage-based billing (new integration) | Metronome | \u003Creferences\u002Fbilling.md> |\n| Subscriptions or recurring billing | Billing APIs + Checkout Sessions | \u003Creferences\u002Fbilling.md> |\n| Sales tax, VAT, or GST compliance | Stripe Tax + Registrations API | \u003Creferences\u002Ftax.md> |\n| Embedded financial accounts \u002F banking | v2 Financial Accounts | \u003Creferences\u002Ftreasury.md> |\n| Security (key management, RAKs, webhooks, OAuth, 2FA, Connect liability) | See security reference | \u003Creferences\u002Fsecurity.md> |\n\nRead the relevant reference file before answering any integration question or writing code.\n\n## Critical rules\n\n- *Before enabling `automatic_tax: { enabled: true }`* (or calculating tax for a custom PaymentIntent), read the [tax reference](references\u002Ftax.md) and confirm the user has an active registration. Without one, Stripe calculates and collects no tax while the user believes tax is on (the most common Stripe Tax mistake).\n\n- *Never include `payment_method_types` in any Stripe API call*, with one exception: Terminal (in-person payments) integrations must pass `payment_method_types: ['card_present']` on the PaymentIntent. For all other integrations, omit this parameter entirely to enable dynamic payment methods, which enables you to configure payment method settings from the Dashboard and dynamically display the most relevant eligible payment methods to each customer to maximize conversion. To customize which payment methods you accept, use [`payment_method_configurations`](https:\u002F\u002Fdocs.stripe.com\u002Fpayments\u002Fpayment-method-configurations.md) or `excluded_payment_method_types` instead of `payment_method_types`.\n\n- When a PaymentIntent or SetupIntent integration requires an explicit allowlist, use `allowed_payment_method_types` instead of `payment_method_types`.\n\n- *Never present webhooks as optional.* We recommend webhooks for every payment integration and they’re required for subscriptions and asynchronous payment methods. Fulfillment belongs in a handler for both `checkout.session.completed` and `checkout.session.async_payment_succeeded` (gated on `payment_status`), not the success page. See \u003Creferences\u002Fpayments.md>.\n\n- On API version `2026-03-25.dahlia` or later, pass the parameter `integration_identifier` to `checkout.sessions.create` to tag sessions with a custom label for tracking and comparing checkout flows in the Dashboard. The label should include a suffix of 8 random letters.\n\n- *Always instantiate a `StripeClient` and call methods on that instance.* Do **not** use the deprecated global\u002Fmodule-level API key pattern (`stripe.api_key = …`, `Stripe.setApiKey`, `stripe.Key = …`, `StripeConfiguration.ApiKey = …`). The global pattern is deprecated in all current SDKs.\n\n## Key documentation\n\nWhen the user’s request does not clearly fit a single domain above, consult:\n\n- [Integration Options](https:\u002F\u002Fdocs.stripe.com\u002Fpayments\u002Fpayment-methods\u002Fintegration-options.md) — Start here when designing any integration.\n- [API Tour](https:\u002F\u002Fdocs.stripe.com\u002Fpayments-api\u002Ftour.md) — Overview of Stripe’s API surface.\n- [Go Live Checklist](https:\u002F\u002Fdocs.stripe.com\u002Fget-started\u002Fchecklist\u002Fgo-live.md) — Review before launching.\n",{"name":5,"description":7},"master","8d883d350240b10cc23da854de1fb212e889caed","agents.symlink\u002Fskills\u002Fstripe-best-practices",4,"https:\u002F\u002Fgithub.com\u002Fmikker\u002Fdotfiles","https:\u002F\u002Fgithub.com\u002Fmikker","https:\u002F\u002Fmikkelmalmberg.com\u002Fama","Top Highlight – research at @githubnext","2026-11-10 22:09:39",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add mikker\u002Fdotfiles --skill stripe-best-practices",{"tool":64,"command":65},"bunx","bunx skills add mikker\u002Fdotfiles --skill stripe-best-practices",{"tool":67,"command":68},"pnpm","pnpm dlx skills add mikker\u002Fdotfiles --skill stripe-best-practices","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmikker\u002Fdotfiles\u002Fblob\u002Fmaster\u002Fagents.symlink\u002Fskills\u002Fstripe-best-practices\u002FSKILL.md",true,[72,78,82,86,90,94],{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fbilling.md","REFERENCE","参考文档",6036,"https:\u002F\u002Fgithub.com\u002Fmikker\u002Fdotfiles\u002Fblob\u002Fmaster\u002Fagents.symlink\u002Fskills\u002Fstripe-best-practices\u002Freferences\u002Fbilling.md",{"path":79,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fconnect.md",11016,"https:\u002F\u002Fgithub.com\u002Fmikker\u002Fdotfiles\u002Fblob\u002Fmaster\u002Fagents.symlink\u002Fskills\u002Fstripe-best-practices\u002Freferences\u002Fconnect.md",{"path":83,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fpayments.md",8980,"https:\u002F\u002Fgithub.com\u002Fmikker\u002Fdotfiles\u002Fblob\u002Fmaster\u002Fagents.symlink\u002Fskills\u002Fstripe-best-practices\u002Freferences\u002Fpayments.md",{"path":87,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fsecurity.md",10047,"https:\u002F\u002Fgithub.com\u002Fmikker\u002Fdotfiles\u002Fblob\u002Fmaster\u002Fagents.symlink\u002Fskills\u002Fstripe-best-practices\u002Freferences\u002Fsecurity.md",{"path":91,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Ftax.md",21704,"https:\u002F\u002Fgithub.com\u002Fmikker\u002Fdotfiles\u002Fblob\u002Fmaster\u002Fagents.symlink\u002Fskills\u002Fstripe-best-practices\u002Freferences\u002Ftax.md",{"path":95,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Ftreasury.md",793,"https:\u002F\u002Fgithub.com\u002Fmikker\u002Fdotfiles\u002Fblob\u002Fmaster\u002Fagents.symlink\u002Fskills\u002Fstripe-best-practices\u002Freferences\u002Ftreasury.md",[99,109,138,161,178,191],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":44},"01M6WFXRC2WZQA9G5AT4D6PCAY","unslop","Cut AI tells from any writing.","https:\u002F\u002Fgithub.com\u002Fmikker\u002Fdotfiles\u002Fblob\u002Fmaster\u002Fagents.symlink\u002Fskills\u002Funslop\u002FSKILL.md",[],[101,106,107,108],"writing","cut","true",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":113,"sourceHtmlUrl":114,"categories":115,"keywords":119,"publishedAt":44},"01M6WFWGJTZWZTVED8A7DHZSCB","stageshow","Build faux product UI that looks like a real product, as a still illustration or an animated demo with a cursor. Browser and app windows, dashboards, phones, notifications, terminals, bento grids and cursor walkthroughs, framed, masked and cropped the way a marketing page, feature card or docs hero needs them. Use whenever someone wants a fake or mocked UI, a product demo or walkthrough animation, a hero or feature-card illustration of an app, a product shot in the style of a polished marketing site, or an animated cursor doing things in an interface, even if they never say \"faux UI\". React and plain CSS.","https:\u002F\u002Fgithub.com\u002Fmikker\u002Fdotfiles\u002Fblob\u002Fmaster\u002Fagents.symlink\u002Fskills\u002Fstageshow\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fmikker\u002Fdotfiles\u002Fblob\u002Fmaster\u002Fagents.symlink\u002Fskills\u002Fstageshow\u002FSKILL.md",[116],{"categoryNo":117,"categoryName":118,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[111,120,121,122,123,124,34,125,126,127,128,129,130,131,132,133,134,135,136,137],"css","react","windows","browser","dashboards","ui","notifications","Animation","walkthrough","marketing","never","feature","as","app","framed","card","interface","hero",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":44},"01M6WFW0TZQ1H9C9X4HMZBTBYZ","clean-copy","Cut interface copy that shouldn't exist — captions that restate a label, hints that pre-empt a worry the user never had, warnings that are scar tissue from a fixed bug. Use when writing or reviewing any user-facing string (labels, hints, empty states, toasts, confirmations, button text), or when asked to clean up \u002F tighten copy.","https:\u002F\u002Fgithub.com\u002Fmikker\u002Fdotfiles\u002Fblob\u002Fmaster\u002Fagents.symlink\u002Fskills\u002Fclean-copy\u002FSKILL.md",[],[145,146,147,136,148,149,150,151,152,153,106,154,155,156,157,130,158,159,107,160],"copy","clean copy","clean","labels","states","when","restate","empty","STRING","Captions","text","user","use","up","bug","tighten",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":167,"publishedAt":44},"01M6BSWBGGT11ZA2BQ0EJH2ZBN","elyx","Elyx is a design tool with local, AI-friendly `.elyx` files for screens, components, layouts, flows, and design systems. This skill is only available to agents running in external harnesses while using the Elyx CLI. It is unavailable and must not be used when running in the ACP harness inside the Elyx app. In external harnesses, use this skill before reading, reasoning about, or answering any question that touches Elyx or `.elyx` files — authoring, editing, validating, inspecting, reviewing, refactoring, comparing, or recommending changes, including read-only analysis where you produce no edit. Do not reason about `.elyx` from source text alone; imports, instances, overrides, and layout only resolve through the tools.","https:\u002F\u002Fgithub.com\u002Fmikker\u002Fdotfiles\u002Fblob\u002Fmaster\u002Fpi\u002Fskills\u002Felyx\u002FSKILL.md",[],[163,168,169,170,171,172,173,174,175,176,177],"acp","design","cli","components","reasoning","design systems","harness","produce","Tools","analysis",{"skillNo":179,"name":180,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":182,"categories":183,"keywords":184,"publishedAt":44},"01M6BSW8K6Z805WVG0670SHXY9","uikit-app-modernization","Modernizes UIKit apps for multi-window environments by replacing legacy shared-state APIs with context-appropriate modern alternatives. This includes references to mainScreen, interfaceOrientation, application and scene lifecycle, as well as safe area inset updates.","https:\u002F\u002Fgithub.com\u002Fmikker\u002Fdotfiles\u002Fblob\u002Fmaster\u002Fagents.symlink\u002Fskills\u002Fxcode-skills\u002Fuikit-app-modernization\u002FSKILL.md",[],[185,186,187,188,189,190],"uikit app modernization","app modernization","modernization","safe","state","lifecycle",{"skillNo":192,"name":193,"nameZh":6,"description":194,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":195,"categories":196,"keywords":197,"publishedAt":44},"01M6BSW5SCT7GQ4QX7CBSB4WF1","swiftui-whats-new-27","New SwiftUI APIs, behaviors, and deprecations in the 2027 OS releases (iOS 27 and aligned macOS\u002FwatchOS\u002FtvOS\u002FvisionOS). Consult when asked what's new in SwiftUI 27, or when working with: - @State compile errors after an SDK update (\"used before being initialized\", \"invalid redeclaration of synthesized property\") or @State becaming a macro - @ViewBuilder\u002F@ContentBuilder ambiguous overloads or type-check regressions; drag-to-reorder in any container (List, stacks, grids, custom layouts) via reorderable()\u002FreorderContainer and its drag-and-drop - AsyncImage caching, reloading on scroll, or a custom URLSession - Swipe actions outside List (ScrollView, LazyVStack, LazyVGrid) via swipeActions()\u002FswipeActionsContainer() - Toolbar overflow, visibility (visibilityPriority, ToolbarOverflowMenu, toolbarMinimizeBehavior), and pinning - Presenting a confirmationDialog or alert from an optional item binding","https:\u002F\u002Fgithub.com\u002Fmikker\u002Fdotfiles\u002Fblob\u002Fmaster\u002Fagents.symlink\u002Fskills\u002Fxcode-skills\u002Fswiftui-whats-new-27\u002FSKILL.md",[],[198,199,200,189,201,202,203,204,205],"swiftui whats new 27","sdk","update","compile","actions","ios","macro","macos"]