Skip to content
Back to search

ssgoi

MarketplaceWorks with Claude CodeGitHub

Official SSGOI skills for native app-like mobile web apps.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/meursyphus/ssgoi with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/meursyphus/ssgoi'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/meursyphus--ssgoi/badge.svg)](/listings/meursyphus--ssgoi)

HTML

<a href="/listings/meursyphus--ssgoi"><img src="/api/listings/meursyphus--ssgoi/badge.svg" alt="findsafeskills safety rating" /></a>

Install

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 28 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. {
  2. "name": "ssgoi",
  3. "owner": {
  4. "name": "MeurSyphus",
  5. "email": "tmdeoans@snu.ac.kr"
  6. },
  7. "description": "Official SSGOI skills for native app-like mobile web apps.",
  8. "plugins": [
  9. {
  10. "name": "ssgoi",
  11. "source": "./plugins/ssgoi",
  12. "description": "Build mobile web app routing, layouts, and native app-like page transitions with SSGOI.",
  13. "author": {
  14. "name": "MeurSyphus",
  15. "email": "tmdeoans@snu.ac.kr"
  16. },
  17. "homepage": "https://ssgoi.dev",
  18. "repository": "https://github.com/meursyphus/ssgoi",
  19. "license": "MIT",
  20. "category": "development",
  21. "tags": [
  22. "mobile-web",
  23. "page-transitions",
  24. "animation"
  25. ]
  26. }
  27. ]
  28. }
README.md · README · 211 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. # SSGOI
  2. Native app-like page transitions for mobile web apps, PWAs, and WebView apps.
  3. **Router agnostic · Cross-browser · SSR ready · Web Animations API powered**
  4. [Live showcase](https://ssgoi.dev) · [Documentation](https://ssgoi.dev/docs)
  5. | Drill | Sheet |
  6. | :---------------------------------------------------------------------------------------------------------------------------------: | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
  7. | <img src="./apps/docs/public/readme-drill.gif" alt="Drill transition opening and closing a chat in a mobile web app" width="280" /> | <img src="./apps/docs/public/blog/view-transition-api-limitations/sheet-blur-full.gif" alt="Sheet transition opening a compose screen above a mobile web app" width="280" /> |
  8. | Navigate through a mobile app with spatial depth | Present focused tasks above the current page |
  9. ## Why SSGOI?
  10. | | |
  11. | ---------------------------------- | --------------------------------------------------------------------------- |
  12. | **Router agnostic** | Keep your existing router and let it own navigation. |
  13. | **Cross-browser** | Use the same transitions across Chrome, Safari, Firefox, and Edge. |
  14. | **Optimized motion** | Spring physics are precomputed into Web Animations API keyframes. |
  15. | **Beyond the View Transition API** | Build transitions that need live DOM, runtime layers, and precise geometry. |
  16. | **Easy to adopt** | Add SSGOI by changing only two files. |
  17. ---
  18. ## Set it up with one link
  19. Give this URL to Claude, Codex, Cursor, or another coding agent:
  20. ```text
  21. https://ssgoi.dev/llms.txt
  22. ```
  23. It contains the full setup for React and Next.js, Svelte and SvelteKit, Vue and
  24. Nuxt, Solid and SolidStart, Angular, and Qwik.
  25. ---
  26. ## Or install the agent plugin
  27. The same `mobile-web-app` skill works in Codex and Claude Code.
  28. Codex:
  29. ```bash
  30. codex plugin marketplace add meursyphus/ssgoi
  31. codex plugin add ssgoi@ssgoi
  32. ```
  33. Claude Code:
  34. ```bash
  35. claude plugin marketplace add meursyphus/ssgoi
  36. claude plugin install ssgoi@ssgoi
  37. ```
  38. Then ask the agent to apply SSGOI to the current mobile web app. The skill reads
  39. the canonical `llms.txt`, selects the matching framework guide, and follows the
  40. app's existing router and layout structure.
  41. ---
  42. ## Or add it in just two files
  43. The Next.js setup is one config, one provider that knows how to read the
  44. Next.js route, and one ready-made layout boundary.
  45. ```bash
  46. npm install @ssgoi/react
  47. ```
  48. ```tsx
  49. // app/ssgoi-provider.tsx
  50. "use client";
  51. import { type ReactNode } from "react";
  52. import { usePathname, useSelectedLayoutSegments } from "next/navigation";
  53. import { Ssgoi, type SsgoiFramework } from "@ssgoi/react";
  54. import { drill } from "@ssgoi/react/view-transitions";
  55. const config = {
  56. transitions: [{ on: "/**", except: "/", transition: drill() }],
  57. };
  58. const INTERCEPTION_PREFIX = /^(?:\(\.\.\.\)|\(\.\.\)|\(\.\))+/;
  59. const framework: SsgoiFramework = {
  60. useRoute: () => {
  61. const pathname = usePathname();
  62. // The page the children slot renders. During a soft intercept it is still
  63. // the background page, so no background boundary moves.
  64. const segments = useSelectedLayoutSegments();
  65. if (pathname == null) return null;
  66. const renderedPath = `/${segments
  67. .filter((segment) => !(segment.startsWith("(") && segment.endsWith(")")))
  68. .map((segment) => segment.replace(INTERCEPTION_PREFIX, ""))
  69. .filter(Boolean)
  70. .join("/")}`;
  71. return { pathname, renderedPath };
  72. },
  73. };
  74. export function SsgoiProvider({ children }: { children: ReactNode }) {
  75. return (
  76. <Ssgoi config={config} framework={framework}>
  77. {children}
  78. </Ssgoi>
  79. );
  80. }
  81. ```
  82. Import the layout boundary from the same package. It takes no props: the first
  83. boundary reads the route for the ones inside it (and throws without a
  84. `framework`), and
  85. `renderedPath` keeps an intercepted modal's background in place:
  86. ```tsx
  87. import { SsgoiLayoutBoundary } from "@ssgoi/react";
  88. <SsgoiLayoutBoundary>{children}</SsgoiLayoutBoundary>;
  89. ```
  90. ```tsx
  91. // app/layout.tsx
  92. import { type ReactNode } from "react";
  93. import { SsgoiLayoutBoundary } from "@ssgoi/react";
  94. import { SsgoiProvider } from "./ssgoi-provider";
  95. export default function RootLayout({ children }: { children: ReactNode }) {
  96. return (
  97. <html lang="en">
  98. <body>
  99. <main className="relative z-0 min-h-dvh overflow-x-clip">
  100. <SsgoiProvider>
  101. <SsgoiLayoutBoundary>{children}</SsgoiLayoutBoundary>
  102. </SsgoiProvider>
  103. </main>
  104. </body>
  105. </html>
  106. );
  107. }
  108. ```
  109. The class string above is Tailwind shorthand. Without Tailwind, apply
  110. `position: relative; z-index: 0; min-height: 100dvh; overflow-x: clip` to the
  111. shell. Use `100vh` only where `dvh` is unsupported.
  112. That is enough for a simple app. `@ssgoi/react` never imports Next.js; it calls
  113. the `useRoute` hook you wrote. Other frameworks use the same small boundary
  114. model with their own router state passed as `framework`. For complete files,
  115. persistent layouts, nested boundaries, and framework-specific setup, see the
  116. [documentation](https://ssgoi.dev/docs/install). Upgrading from 7.x, where
  117. router subpaths such as `@ssgoi/react/nextjs` were still available? See the
  118. [8.0 migration guide](https://ssgoi.dev/docs/migration-v8).
  119. ---
  120. ## Compatibility
  121. SSGOI depends on the broadly available Web Animations API instead of requiring
  122. the View Transition API.
  123. | <img src="./apps/docs/public/logos/chrome.svg" alt="Chrome" width="36" /><br />Chrome 84+ | <img src="./apps/docs/public/logos/safari.svg" alt="Safari" width="36" /><br />Safari 13.1+ | <img src="./apps/docs/public/logos/firefox.svg" alt="Firefox" width="36" /><br />Firefox 75+ | <img src="./apps/docs/public/logos/edge.svg" alt="Edge" width="36" /><br />Edge 84+ |
  124. | :---------------------------------------------------------------------------------------: | :-----------------------------------------------------------------------------------------: | :------------------------------------------------------------------------------------------: | :---------------------------------------------------------------------------------: |
  125. These are core Web Animations API runtime targets. The blur types in Sheet and
  126. Zoom also use `backdrop-filter` (Firefox 103+); earlier Firefox keeps the
  127. transition, scale, and dimming but omits the backdrop blur.
  128. The same build runs inside WebView shells — Capacitor, Ionic, Tauri, React
  129. Native WebView — and as an installed PWA, with no native plugin. iOS and Android
  130. back swipes are left to the OS.
  131. [Make a web app feel native →](https://ssgoi.dev/docs/native-app-feel)
  132. It observes the DOM lifecycle your framework already owns, so routing and SSR
  133. stay with your existing stack.
  134. | <img src="./apps/docs/public/logos/nextjs.svg" alt="Next.js" width="42" /><br />Next.js | <img src="./apps/docs/public/logos/react-router.svg" alt="React Router" width="42" /><br />React Router | <img src="./apps/docs/public/logos/tanstack.svg" alt="TanStack Router" width="42" /><br />TanStack Router | <img src="./apps/docs/public/logos/svelte.svg" alt="SvelteKit" width="42" /><br />SvelteKit | <img src="./apps/docs/public/logos/nuxt.svg" alt="Nuxt" width="42" /><br />Nuxt |
  135. | :-------------------------------------------------------------------------------------: | :-----------------------------------------------------------------------------------------------------: | :-------------------------------------------------------------------------------------------------------: | :-----------------------------------------------------------------------------------------: | :-----------------------------------------------------------------------------: |
  136. React · Svelte · Vue · Solid · Angular · Qwik · framework-agnostic core
  137. An experimental [React Native / Expo Router integration](./packages/react-native/README.md)
  138. adds native `fade`/`slide` transitions with the same `SsgoiLayoutBoundary` naming.
  139. Try the [Expo template](./templates/expo) for the current implementation and device checks.
  140. [See complete compatibility and framework guides →](https://ssgoi.dev/docs/compatibility)
  141. Need the app screens too? [Comwit UI](https://library.comwit.io/ui) is a mobile
  142. app component kit built on SSGOI: app shell, app bar, bottom nav, bottom sheet,
  143. pull to refresh, and page transitions.
  144. ---
  145. ## Why SSGOI doesn't use the View Transition API
  146. SSGOI owns the geometry, temporary visual layers, live outgoing DOM, and
  147. navigation policy needed to turn complex motion into reusable presets.
  148. | Zoom | Film | Sheet |
  149. | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------: | :--------------------------------------------------------------------------------------------------------------------------------------------------------------: | :-----------------------------------------------------------------------------------------------------------------------------------------------------------------: |
  150. | <img src="./apps/docs/public/blog/view-transition-api-limitations/zoom-blur.gif" alt="Zoom transition that transforms and clips a detail page around its image" width="240" /> | <img src="./apps/docs/public/blog/view-transition-api-limitations/film.gif" alt="Film transition with runtime visual pieces and multiple springs" width="320" /> | <img src="./apps/docs/public/blog/view-transition-api-limitations/sheet-blur-full.gif" alt="Sheet transition with a live backdrop between two pages" width="240" /> |
  151. | The whole detail page unfolds from its image | Runtime scene, live video, and multiple springs | A live backdrop sits between the two pages |
  152. [Read why SSGOI doesn't use the View Transition API →](https://ssgoi.dev/blog/view-transition-api-limitations)
  153. ---
  154. ## License
  155. [MIT Licensed](./LICENSE) © [MeurSyphus](https://github.com/meursyphus)

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.