Templates Overview

You are helping me integrate utilsio, a crypto-native subscription system, into my application.

Documentation: https://utilsio.dev/docs
- Installation guide: https://utilsio.dev/docs/install.md
- Full reference: https://utilsio.dev/docs/llms-full.txt
- Quick reference: https://utilsio.dev/docs/llms.txt

Key concepts:
- HMAC-SHA256 request signing (secrets never leave server)
- Client: @utilsio/react with UtilsioProvider + useUtilsio hook
- Server: Server actions using deriveAppHashHex + signRequest
- Safari support: /api/signature-callback endpoint for browsers blocking third-party cookies
- Crypto payments via Superfluid streaming (USDT token)

Decision tree - YOU MUST ANALYZE THE CODEBASE FIRST:
1. Examine the project structure (check for package.json, src/, components/, etc.)
2. Look at key files to assess if this is a new/empty project or existing codebase
3. If codebase appears newly created/minimal, ASK ME: "This looks like a new project. Can I reset the codebase entirely and use the utilsio template for fastest setup?"
   - If YES: Clone template from https://github.com/utilsio/templates (see install.md)
   - If NO: Proceed with manual SDK integration
4. If codebase is clearly mid-development with existing features: Use manual SDK integration

Manual integration:
- Install @utilsio/react package
- Create server action for signing (CRITICAL for security)
- Create /api/signature-callback endpoint for Safari support
- Wrap app with UtilsioProvider
- Never expose UTILSIO_APP_SECRET or UTILSIO_APP_SALT to client

Task: <DESCRIBE WHAT YOU WANT TO BUILD OR INTEGRATE>

My setup:
- Framework: <YOUR FRAMEWORK, e.g., Next.js 15 App Router>
- Package manager: <bun/npm/pnpm/yarn>
- Additional context: <ANY OTHER RELEVANT INFO>