[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79T2M9K49B95STS4G9V25EM":3,"skill-same:01M79T2M9K49B95STS4G9V25EM":53},{"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":32,"commitSha":33,"skillDirectory":34,"forksCount":14,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":37,"updatedAt":38,"install":39,"resources":52},"01M79T2M9K49B95STS4G9V25EM","adaptive-layouts-architect",null,"Architect-level adaptive UI — window size classes and breakpoints, split and multi-column layouts, foldables and large screens, orientation and keyboard handling, and the state model that survives a resize. Use when one app must look right on phones, tablets, foldables, and desktop-class windows.","SriAkhilSJ\u002FPulseAIRepo","SriAkhilSJ","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F206201543?v=4","01M79RWFD1Q09B89SXTTKKJY6Z","Sri Akhil SJ","01M79RWFE26NPG0BZ1FRNX376H",0,"MIT","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fmobile-architect\u002Fdevices-architect\u002Fadaptive-layouts-architect\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: adaptive-layouts-architect\ndescription: Architect-level adaptive UI — window size classes and breakpoints, split and multi-column layouts, foldables and large screens, orientation and keyboard handling, and the state model that survives a resize. Use when one app must look right on phones, tablets, foldables, and desktop-class windows.\nlicense: MIT\ncompatibility: WindowSizeClass, UIKit size classes, SwiftUI layout, Jetpack Compose\nmetadata:\n  crusor-domain: mobile-architect\n  crusor-path: mobile-architect\u002Fdevices-architect\u002Fadaptive-layouts-architect\n  crusor-origin: original\n  crusor-sources: \"developer.android.com\u002Fdevelop\u002Fui\u002Fcompose\u002Flayouts\u002Fadaptive; developer.apple.com\u002Fdesign\u002Fhuman-interface-guidelines\u002Flayout; developer.android.com\u002Fguide\u002Ftopics\u002Flarge-screens\"\n  crusor-triggers: \"adaptive layout, tablet, foldable, window size class, split view, multi pane, orientation change, large screen, responsive mobile\"\n  crusor-verified-on: \"2026-10-30\"\n---\n\n# Adaptive Layouts Architect\n\nA mobile app now runs on **phones, tablets, foldables, and desktop-class windows**.\nOne layout stretched across all of them is the default failure.\n\n## When to use\n\n- Tablet or foldable support is expected (store listings penalise phone-only).\n- ChromeOS\u002Fdesktop windows or split-screen multitasking matter.\n- Layout breaks on rotation or when the keyboard appears.\n\n## When NOT to use\n\n- A single-device, single-orientation kiosk app.\n\n## Decision 1 — Breakpoints\n\n| Size class | Typical width | Layout |\n|---|---|---|\n| compact | \u003C 600 dp | single column, bottom navigation |\n| medium | 600–840 dp | two-pane list\u002Fdetail, rail nav |\n| expanded | > 840 dp | persistent navigation, 2–3 columns |\n\n- Decide by **available width**, not device type — a foldable changes class mid-session.\n- Navigation should convert: bottom bar → navigation rail → permanent drawer.\n- Content max-width matters: text lines wider than ~70 characters are unreadable.\n\n## Decision 2 — Structure\n\n- List-detail is the canonical adaptive pattern: one pane when compact, two when\n  expanded.\n- Keep state in a place that survives pane changes (view model, not view).\n- Insets: system bars, display cutouts, and hinge areas are not usable space.\n- Foldables: avoid placing critical controls across the hinge; test posture changes.\n\n## Decision 3 — Input\n\n- Keyboard avoidance: scroll the focused field into view; never let it hide behind the\n  keyboard.\n- Mouse\u002Ftrackpad and stylus support where the platform allows (hover states, right-click,\n  drag).\n- Touch targets stay ≥ 44\u002F48 dp regardless of window size.\n- Orientation: support both unless the domain forbids it; test the transition mid-flow\n  (a video call, a form).\n\n## Decision 4 — State across resizes\n\n- Process death, rotation, and window resize are different events — handle all three.\n- Save scroll position and form input; losing either reads as a crash.\n- Multi-window: the app may be paused without being destroyed; do not reload data on\n  every resume.\n\n## Decision 5 — Testing\n\n- Emulators with resizable windows; a real foldable if you claim support.\n- Test at maximum font scale in every size class — the combination is where clipping\n  appears.\n- Screenshot tests per size class for key screens.\n\n## Failure modes at scale\n\n- Phone layout stretched to a tablet; content in a 1200 dp single column.\n- Bottom navigation on a tablet with a 15-inch-wide touch target row.\n- State lost on rotation because it lived in the view.\n- Hinge covered by a critical button on a foldable.\n- Keyboard hides the submit button; users cannot complete a form.\n\n## Verification receipts\n\n1. Breakpoint table with the layout per size class.\n2. Screenshots of three key screens in compact, medium, and expanded.\n3. Rotation and resize tests with state preserved.\n4. Keyboard-avoidance test on the longest form.\n5. Foldable posture test if support is claimed.\n","# Adaptive Layouts Architect\n\nA mobile app now runs on **phones, tablets, foldables, and desktop-class windows**.\nOne layout stretched across all of them is the default failure.\n\n## When to use\n\n- Tablet or foldable support is expected (store listings penalise phone-only).\n- ChromeOS\u002Fdesktop windows or split-screen multitasking matter.\n- Layout breaks on rotation or when the keyboard appears.\n\n## When NOT to use\n\n- A single-device, single-orientation kiosk app.\n\n## Decision 1 — Breakpoints\n\n| Size class | Typical width | Layout |\n|---|---|---|\n| compact | \u003C 600 dp | single column, bottom navigation |\n| medium | 600–840 dp | two-pane list\u002Fdetail, rail nav |\n| expanded | > 840 dp | persistent navigation, 2–3 columns |\n\n- Decide by **available width**, not device type — a foldable changes class mid-session.\n- Navigation should convert: bottom bar → navigation rail → permanent drawer.\n- Content max-width matters: text lines wider than ~70 characters are unreadable.\n\n## Decision 2 — Structure\n\n- List-detail is the canonical adaptive pattern: one pane when compact, two when\n  expanded.\n- Keep state in a place that survives pane changes (view model, not view).\n- Insets: system bars, display cutouts, and hinge areas are not usable space.\n- Foldables: avoid placing critical controls across the hinge; test posture changes.\n\n## Decision 3 — Input\n\n- Keyboard avoidance: scroll the focused field into view; never let it hide behind the\n  keyboard.\n- Mouse\u002Ftrackpad and stylus support where the platform allows (hover states, right-click,\n  drag).\n- Touch targets stay ≥ 44\u002F48 dp regardless of window size.\n- Orientation: support both unless the domain forbids it; test the transition mid-flow\n  (a video call, a form).\n\n## Decision 4 — State across resizes\n\n- Process death, rotation, and window resize are different events — handle all three.\n- Save scroll position and form input; losing either reads as a crash.\n- Multi-window: the app may be paused without being destroyed; do not reload data on\n  every resume.\n\n## Decision 5 — Testing\n\n- Emulators with resizable windows; a real foldable if you claim support.\n- Test at maximum font scale in every size class — the combination is where clipping\n  appears.\n- Screenshot tests per size class for key screens.\n\n## Failure modes at scale\n\n- Phone layout stretched to a tablet; content in a 1200 dp single column.\n- Bottom navigation on a tablet with a 15-inch-wide touch target row.\n- State lost on rotation because it lived in the view.\n- Hinge covered by a critical button on a foldable.\n- Keyboard hides the submit button; users cannot complete a form.\n\n## Verification receipts\n\n1. Breakpoint table with the layout per size class.\n2. Screenshots of three key screens in compact, medium, and expanded.\n3. Rotation and resize tests with state preserved.\n4. Keyboard-avoidance test on the longest form.\n5. Foldable posture test if support is claimed.\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":31},{"crusor-path":25,"crusor-domain":26,"crusor-origin":27,"crusor-sources":28,"crusor-triggers":29,"crusor-verified-on":30},"mobile-architect\u002Fdevices-architect\u002Fadaptive-layouts-architect","mobile-architect","original","developer.android.com\u002Fdevelop\u002Fui\u002Fcompose\u002Flayouts\u002Fadaptive; developer.apple.com\u002Fdesign\u002Fhuman-interface-guidelines\u002Flayout; developer.android.com\u002Fguide\u002Ftopics\u002Flarge-screens","adaptive layout, tablet, foldable, window size class, split view, multi pane, orientation change, large screen, responsive mobile","2026-10-30","WindowSizeClass, UIKit size classes, SwiftUI layout, Jetpack Compose","main","8fa4e240be65b98472c9b2d3a505ade2aea1a5c6","skills\u002Fmobile-architect\u002Fdevices-architect\u002Fadaptive-layouts-architect","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ","Studying in CMR institute of Technology\r\n2024 - 2028","2026-11-13 21:02:23",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add SriAkhilSJ\u002FPulseAIRepo --skill adaptive-layouts-architect",{"tool":45,"command":46},"bunx","bunx skills add SriAkhilSJ\u002FPulseAIRepo --skill adaptive-layouts-architect",{"tool":48,"command":49},"pnpm","pnpm dlx skills add SriAkhilSJ\u002FPulseAIRepo --skill adaptive-layouts-architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fmobile-architect\u002Fdevices-architect\u002Fadaptive-layouts-architect\u002FSKILL.md",true,[],[54,61,68,75,82,89],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M79TTAJNACCNXCEN3649CMMD","interaction-patterns-architect","Architect-level interaction design in code — choosing established patterns over invented ones, feedback and latency behaviour, destructive-action safeguards, navigation and overlay conventions, and the state model behind every interactive surface. Use when a screen has to behave, not just look.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Finteraction-patterns-architect\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M79TT2ESKB1TKZBYY9KYJHV9","design-system-ops-architect","Architect-level operation of a design system in code — token pipelines and versioning, component API and variant policy, the catalogue as the contract, adoption metrics, and the governance that stops a system from forking into three. Use when a component library must survive several teams.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fdesign-system-ops-architect\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M79TSV0PWGNK3PRX9P4JDR9N","design-handoff-architect","Architect-level design handoff — what must be specified before implementation starts, tokens over raw values, responsive and content-limit contracts, state matrices, and the review loop that catches drift between design and code. Use when a design is about to become code.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fdesign-handoff-architect\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M79TSJS9BFXNP696FMJ9GKDA","content-microcopy-architect","Architect-level UI content — where strings live, voice and terminology consistency, error and empty-state copy as part of the interface, translation-ready authoring, and the content model a product needs before it multiplies screens. Use when the words in the interface matter as much as the pixels.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fcontent-microcopy-architect\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M79TSCNBST3N1M68V1KPH9HQ","ui-ux-implementation-architect","Architect-level direction for turning a design into working UI — the handoff contract, component ownership versus screen-level layout, interaction and state conventions, design QA gates, and the review habits that keep an implementation faithful without frozen pixels. Use before any specific UI implementation skill.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M79TS4N6A4D2QQ433VXS5D0R","test-strategy-architect","Architect-level test strategy — allocating assertions across unit, integration, contract and end-to-end layers, designing for testability through dependency boundaries, fixture and data strategy, and the flake and coverage policies that keep a suite trustworthy. Use when defining how a codebase is tested.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Ftesting-and-deployment-architect\u002Ftest-strategy-architect\u002FSKILL.md",[],[]]