[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79SZMTSHHB843XVEC4244KS":3,"skill-same:01M79SZMTSHHB843XVEC4244KS":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},"01M79SZMTSHHB843XVEC4244KS","gtk-architect",null,"Architect-level Linux desktop design — GTK4\u002Flibadwaita versus Qt, Wayland and X11 realities, Flatpak\u002FSnap packaging and portals, distribution across diverse desktops, and the accessibility and theming expectations Linux users hold. Use when shipping a Linux desktop app.","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\u002Fdesktop-architect\u002Fruntimes-architect\u002Fgtk-architect\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: gtk-architect\ndescription: Architect-level Linux desktop design — GTK4\u002Flibadwaita versus Qt, Wayland and X11 realities, Flatpak\u002FSnap packaging and portals, distribution across diverse desktops, and the accessibility and theming expectations Linux users hold. Use when shipping a Linux desktop app.\nlicense: MIT\ncompatibility: GTK4\u002Flibadwaita, Qt6, Flatpak, Snap, AppImage\nmetadata:\n  crusor-domain: desktop-architect\n  crusor-path: desktop-architect\u002Fruntimes-architect\u002Fgtk-architect\n  crusor-origin: original\n  crusor-sources: \"docs.gtk.org\u002Fgtk4; developer.gnome.org\u002Fdocumentation; docs.flatpak.org; doc.qt.io\u002Fqt-6\"\n  crusor-triggers: \"gtk, gtk4, libadwaita, qt, linux desktop, flatpak, snap, appimage, wayland, x11\"\n  crusor-verified-on: \"2026-10-30\"\n---\n\n# Linux Desktop Architect\n\nLinux means **one binary and a dozen desktops**. The architecture question is which\ndisplay stack, which packaging, and which conventions you target.\n\n## When to use\n\n- A native Linux app is required (performance, system integration, licensing).\n- Packaging for multiple distributions is in scope.\n- Wayland-specific behaviour matters (fractional scaling, input methods, screen\n  capture).\n\n## When NOT to use\n\n- Cross-platform UI with a webview meets the need → Tauri\u002FElectron.\n- The app is a CLI with a config file.\n\n## Decision 1 — Toolkit\n\n| Toolkit | Fit |\n|---|---|\n| GTK4 + libadwaita | GNOME-native feel, modern adaptive widgets |\n| Qt 6 | KDE-native, commercial apps, broad platform support |\n| Electron\u002FTauri | web skills, faster delivery, heavier or lighter footprint |\n\n- GTK and Qt both work on any desktop, but native look comes from the toolkit matching\n  the user's environment; libadwaita assumes GNOME conventions.\n- Respect the desktop's dark mode and accent colour APIs rather than hardcoding.\n\n## Decision 2 — Display server\n\n- Wayland is the default on modern desktops; X11 remains on older setups.\n- Test on both: global shortcuts, screen capture, window positioning, and tray icons\n  behave differently.\n- Fractional scaling and input method (IBus\u002FFcitx) support decide whether text entry\n  works for non-Latin users.\n- Avoid APIs that only exist under X11 unless you ship a documented fallback.\n\n## Decision 3 — Packaging\n\n| Format | Notes |\n|---|---|\n| Flatpak | sandboxed, portals, Flathub distribution |\n| Snap | sandboxed, Ubuntu-centric, automatic updates |\n| AppImage | portable, no sandbox, manual updates |\n| distro packages (deb\u002Frpm) | native integration, maintenance burden |\n\n- Flatpak is the default recommendation for broad reach; portals replace direct\n  filesystem access.\n- Sandboxing changes file access: use XDG portals (`xdg-desktop-portal`) for file\n  chooser, notifications, and opening URIs.\n- Ship the runtime dependencies; do not assume the user's distro versions.\n\n## Decision 4 — Desktop integration\n\n- `.desktop` entry, icon at multiple sizes, AppStream metadata for store listings.\n- Notifications via the freedesktop spec; actions where supported.\n- Respect the user's theme, fonts, and scaling — do not force a look.\n- Accessibility: GTK\u002FQt provide the AT-SPI bridge; test with Orca.\n\n## Decision 5 — Updates\n\n- Flatpak\u002FSnap update automatically; document the channel and rollback.\n- AppImage and distro packages need your own update path or none at all — say which.\n- Long-term support: track the runtime (e.g. GNOME runtime) lifecycle.\n\n## Failure modes at scale\n\n- Sandboxed Flatpak with direct `~\u002F.config` writes; the file silently goes to the\n  sandbox.\n- Tray icon that only works under X11; missing on GNOME Wayland.\n- Hardcoded light theme; unreadable in dark mode.\n- AppImage requiring a library the user's distro does not ship.\n- Custom window decorations that break under tiling window managers.\n\n## Verification receipts\n\n1. Toolkit and packaging decision with the target desktops listed.\n2. Test pass on GNOME Wayland, KDE Plasma, and one X11 session.\n3. Portal-based file access verified inside the Flatpak sandbox.\n4. Dark mode, scaling, and non-Latin input tested.\n5. AppStream metadata and desktop entry validated by the packaging tools.\n","# Linux Desktop Architect\n\nLinux means **one binary and a dozen desktops**. The architecture question is which\ndisplay stack, which packaging, and which conventions you target.\n\n## When to use\n\n- A native Linux app is required (performance, system integration, licensing).\n- Packaging for multiple distributions is in scope.\n- Wayland-specific behaviour matters (fractional scaling, input methods, screen\n  capture).\n\n## When NOT to use\n\n- Cross-platform UI with a webview meets the need → Tauri\u002FElectron.\n- The app is a CLI with a config file.\n\n## Decision 1 — Toolkit\n\n| Toolkit | Fit |\n|---|---|\n| GTK4 + libadwaita | GNOME-native feel, modern adaptive widgets |\n| Qt 6 | KDE-native, commercial apps, broad platform support |\n| Electron\u002FTauri | web skills, faster delivery, heavier or lighter footprint |\n\n- GTK and Qt both work on any desktop, but native look comes from the toolkit matching\n  the user's environment; libadwaita assumes GNOME conventions.\n- Respect the desktop's dark mode and accent colour APIs rather than hardcoding.\n\n## Decision 2 — Display server\n\n- Wayland is the default on modern desktops; X11 remains on older setups.\n- Test on both: global shortcuts, screen capture, window positioning, and tray icons\n  behave differently.\n- Fractional scaling and input method (IBus\u002FFcitx) support decide whether text entry\n  works for non-Latin users.\n- Avoid APIs that only exist under X11 unless you ship a documented fallback.\n\n## Decision 3 — Packaging\n\n| Format | Notes |\n|---|---|\n| Flatpak | sandboxed, portals, Flathub distribution |\n| Snap | sandboxed, Ubuntu-centric, automatic updates |\n| AppImage | portable, no sandbox, manual updates |\n| distro packages (deb\u002Frpm) | native integration, maintenance burden |\n\n- Flatpak is the default recommendation for broad reach; portals replace direct\n  filesystem access.\n- Sandboxing changes file access: use XDG portals (`xdg-desktop-portal`) for file\n  chooser, notifications, and opening URIs.\n- Ship the runtime dependencies; do not assume the user's distro versions.\n\n## Decision 4 — Desktop integration\n\n- `.desktop` entry, icon at multiple sizes, AppStream metadata for store listings.\n- Notifications via the freedesktop spec; actions where supported.\n- Respect the user's theme, fonts, and scaling — do not force a look.\n- Accessibility: GTK\u002FQt provide the AT-SPI bridge; test with Orca.\n\n## Decision 5 — Updates\n\n- Flatpak\u002FSnap update automatically; document the channel and rollback.\n- AppImage and distro packages need your own update path or none at all — say which.\n- Long-term support: track the runtime (e.g. GNOME runtime) lifecycle.\n\n## Failure modes at scale\n\n- Sandboxed Flatpak with direct `~\u002F.config` writes; the file silently goes to the\n  sandbox.\n- Tray icon that only works under X11; missing on GNOME Wayland.\n- Hardcoded light theme; unreadable in dark mode.\n- AppImage requiring a library the user's distro does not ship.\n- Custom window decorations that break under tiling window managers.\n\n## Verification receipts\n\n1. Toolkit and packaging decision with the target desktops listed.\n2. Test pass on GNOME Wayland, KDE Plasma, and one X11 session.\n3. Portal-based file access verified inside the Flatpak sandbox.\n4. Dark mode, scaling, and non-Latin input tested.\n5. AppStream metadata and desktop entry validated by the packaging tools.\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},"desktop-architect\u002Fruntimes-architect\u002Fgtk-architect","desktop-architect","original","docs.gtk.org\u002Fgtk4; developer.gnome.org\u002Fdocumentation; docs.flatpak.org; doc.qt.io\u002Fqt-6","gtk, gtk4, libadwaita, qt, linux desktop, flatpak, snap, appimage, wayland, x11","2026-10-30","GTK4\u002Flibadwaita, Qt6, Flatpak, Snap, AppImage","main","8fa4e240be65b98472c9b2d3a505ade2aea1a5c6","skills\u002Fdesktop-architect\u002Fruntimes-architect\u002Fgtk-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 gtk-architect",{"tool":45,"command":46},"bunx","bunx skills add SriAkhilSJ\u002FPulseAIRepo --skill gtk-architect",{"tool":48,"command":49},"pnpm","pnpm dlx skills add SriAkhilSJ\u002FPulseAIRepo --skill gtk-architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fdesktop-architect\u002Fruntimes-architect\u002Fgtk-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",[],[]]