PartyLayer
Try Demo

Integrate with an AI coding assistant

Give your coding assistant the current setup guides so it can use the right packages, connection boundary and wallet requirements. This is documentation for generating application code; it does not require an AI runtime, a new API key or wallet access.

Start with a precise task

text
Add PartyLayer wallet connection to this existing app. Inspect its framework,
package manager, installed versions and existing providers first. Follow
https://partylayer.xyz/llms-full.txt and https://partylayer.xyz/docs/quick-start.
Use the default branded ConnectButton, one PartyLayerKit and Devnet. Preserve
working behavior and avoid a second client. Install @partylayer/react and
@tanstack/react-query together for React. Keep the Next.js root layout server-side.
Run the app's build/typecheck and explain any wallet configuration still needed.
Do not create a wallet-specific package or submit ledger transactions.

Replace Devnet with your intended supported network. Tell the assistant about an existing custom client, UI or authentication rather than letting it wrap the application twice.

Optional repository skill

  • llms.txt is the documentation index; llms-full.txt contains the quick start, SDK reference and network constraints.
  • The quick start supplies complete React/Next.js setup. Use the migration guide for an existing PartyLayer app.
  • The repository includes an optional PartyLayer integration skill. Supply it as project context or use your assistant’s supported skill setup. Installing the npm package does not install or activate this skill.

What the assistant should generate

bash
npm install @partylayer/react @tanstack/react-query

Mount one kit at the application boundary, then render this client component inside it. No per-wallet package or stylesheet import is needed.

tsx
'use client';
import { ConnectButton, useAccount } from '@partylayer/react';

export function WalletConnection() {
  const { isConnected, party, networkId } = useAccount();
  return (
    <section>
      <ConnectButton />
      {isConnected && <p>{party} · {networkId}</p>}
    </section>
  );
}

Review generated code

  • Send is Mainnet-only; Vala is Devnet beta. Do not bypass catalog filtering. WalletConnect and Bron need the application’s own configuration.
  • Preserve one native discovery owner and complete CIP-0103 results/events. Cached UI state is not wallet authorization.
  • A connected party or message signature does not prove application login, a transfer or a swap. Use independent backend/ledger verification.
  • Run the generated application’s build, typecheck and relevant tests. CLI 0.7.0 adds read-only --doctor diagnostics; check its published version before use.
ℹ️ Note
Repository checks compile the maintained examples and detect stale plain-text references. They cannot guarantee every response generated by an AI assistant is correct, or guarantee search rankings and AI citations.

Read the full AI integration guide for scope, validation and reference details.

Maintained references

The plain-text index and full reference are generated from maintained guides, manifests and wallet catalogs. A drift check rejects stale output. Share those URLs for current setup context; they do not guarantee search indexing or citations.

PreviousMigrationNextRainbowKit for Canton