From f4390997edf365117d277ec0300d16fda2043285 Mon Sep 17 00:00:00 2001 From: Konstantin Wohlwend Date: Sun, 5 Jul 2026 22:56:26 -0700 Subject: [PATCH] Update AI setup prompt --- .../unified-prompts/skill-site-prompt-parts/ai-setup-prompt.ts | 2 ++ 1 file changed, 2 insertions(+) diff --git a/packages/shared/src/ai/unified-prompts/skill-site-prompt-parts/ai-setup-prompt.ts b/packages/shared/src/ai/unified-prompts/skill-site-prompt-parts/ai-setup-prompt.ts index 8869eab09..154da0407 100644 --- a/packages/shared/src/ai/unified-prompts/skill-site-prompt-parts/ai-setup-prompt.ts +++ b/packages/shared/src/ai/unified-prompts/skill-site-prompt-parts/ai-setup-prompt.ts @@ -559,6 +559,8 @@ const appSetupPrompt: Record = }; \`\`\` + For large OAuth providers like Google and GitHub, Hexclave automatically provides a client ID and secret, so no extra provider setup is needed. + Then wire the SDK setup above: create the Hexclave App object, wrap React apps in the provider, and add auth pages where your framework needs them. OAuth client IDs/secrets and trusted domains are environment-specific, so leave placeholders or ask the user for those instead of inventing them. See [Auth providers](https://docs.hexclave.com/guides/apps/authentication/auth-providers) and [hexclave.config.ts: Auth](https://docs.hexclave.com/guides/going-further/hexclave-config#auth). `, "fraud-protection": deindent`