Skip to main content

thunderid-integrate-nextjs

Add ThunderID authentication to a Next.js application using the official @thunderid/nextjs SDK. Use when asked to "integrate ThunderID into Next.js", "add auth to my Next.js app", or "connect ThunderID with Next.js".

インストールへ移動

ソース情報

リポジトリ
thunder-id/skills
ソースの最終更新活動
2026年8月18日 16:31
検出された SKILL.md の言語
英語
スター
35
フォーク
8

インストール方法

デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。

ソースファイルを確認

インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。

SKILL.md を表示中

SKILL.md
ソースの指示 · 読み取り専用プレビュー
name
thunderid-integrate-nextjs
description
Add ThunderID authentication to a Next.js application using the official @thunderid/nextjs SDK. Use when asked to "integrate ThunderID into Next.js", "add auth to my Next.js app", or "connect ThunderID with Next.js".
license
Apache-2.0
allowed-tools
WebFetch, Bash(npm:*), Bash(npx:*), Bash(pnpm:*), Bash(yarn:*), Bash(bun:*), Read, Write, Edit
metadata
{"author":"thunderid","version":"1.0.0"}
# ThunderID — Next.js Integration Assumes ThunderID is running at `https://localhost:8090`. If not, run `/thunderid-install` first. Fetch the canonical, always-current integration guide before writing any code: WebFetch `https://thunderid.dev/docs/v1.0.x/getting-started/connect-your-application/nextjs.md` Follow that guide end to end — creating the Console application, installing `@thunderid/nextjs`, adding `ThunderIDProvider` and the proxy/middleware, adding sign-in/sign-up UI, and verifying the app runs — adapting file names, paths, and code style to this project's actual structure rather than copying the doc's file layout verbatim. You do not have Console access or a browser tool. Whenever a step needs a Console UI action (creating the application, choosing a sign-in approach, copying a Client ID/Secret/Application ID, adding a redirect URI), tell the user exactly what to click and ask them to report the value back — one value at a time, confirming each before asking for the next. If the guide presents more than one configuration or sign-in approach, use the `AskUserQuestion` tool to let the user choose rather than guessing which one this project wants. If the fetch fails (offline, docs unreachable), tell the user and give them the URL above to open manually. Do not improvise integration steps from memory. ## Project-specific notes - Detect the package manager from lockfiles: `pnpm-lock.yaml` → `pnpm add`, `yarn.lock` → `yarn add`, `bun.lockb` → `bun add`, else `npm install`. - Generate any session-signing secret the guide asks for with `openssl rand -base64 32`. ## Troubleshooting - **Certificate error** — Visit `https://localhost:8090` in your browser and accept the warning once. - **`invalid_client`** — Double-check the Client ID/Client Secret in `.env.local` against the application's General tab.
GitHubで見る