# Build NEAR Apps with TypeScript

NEAR integrations often need transaction, wallet, key, and testing patterns. This skill gives concise near-kit examples for TypeScript apps, React hooks, wallets, and sandbox tests.

## Install

```bash
npx skillstore add internet-court/near-kit
```

## Metadata

- Status: approved
- Slug: internet-court-near-kit
- Skillstore revision: r1
- Version status: missing
- Tree hash: b893df23756b3c4eeb00b489e8d7cd3b7da8c4df935cc7ae3557ed4454c083e2
- Author: internet-court
- GitHub username: internet-court
- License: MIT
- Repository: https://github.com/internet-court/internet-court-skill/tree/main/vendored/near/near-kit
- Ref: 3f6e026a3363e0954ede7bef0cfe88d4475de137
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network, filesystem
- Quality score: 76
- Public page: https://skillstore.pages.dev/skills/internet-court-near-kit
- Manifest: https://skillstore.pages.dev/api/skills/internet-court-near-kit/manifest

## Capabilities

- Shows read-only and signed Near client setup for testnet and mainnet.
- Explains contract view calls, change calls, token transfers, and transaction builder actions.
- Documents Wallet Selector, HOT Connect, and universal server or browser wallet patterns.
- Provides React provider, hook, React Query, SWR, and SSR integration patterns.
- Covers key stores, seed phrase utilities, sandbox testing, NEP-366, and NEP-413 signing.

## Use Cases

- Create a dApp Wallet Flow: Use React hooks and wallet adapters to connect accounts, call contracts, and display balances.
- Build Server-Side NEAR Automation: Configure signed transactions, key stores, relayer flows, and message verification for trusted server processes.
- Test Contract Integrations: Use sandbox examples to create accounts, deploy WASM contracts, call methods, and validate integration behavior.

## Prompt Templates

### Create a Read-Only Client

```
Show me how to use near-kit to read a NEAR contract view method on testnet. Include imports, client setup, and error handling notes.
```

### Add Wallet Calls in React

```
Help me add @near-kit/react to a React app. Use wallet-based signing and show the provider, account state, and a contract call.
```

### Design a Transaction Flow

```
Plan a near-kit transaction that creates an account, funds it, deploys a contract, and initializes it. Include gas and deposit guidance.
```

### Review Keys and Relayers

```
Review my near-kit key management and relayer design. Check private key handling, nonce validation, recipient checks, and server-only boundaries.
```

## Limitations

- Does not provide the near-kit package source code or implementation internals.
- Uses placeholders for keys, accounts, contracts, and endpoints that users must replace safely.
- Does not audit smart contract logic or guarantee transaction safety.
- Requires users to verify current NEAR network, wallet, and dependency behavior.

## Best Practices

- Use wallet adapters in browsers and keep private keys in trusted server environments only.
- Replace example accounts, URLs, gas, and deposit values with values reviewed for the target network.
- Add explicit nonce, recipient, expiry, and signer checks for login and meta-transaction flows.

## Anti Patterns

- Do not paste real private keys or seed phrases into prompts, examples, logs, or source files.
- Do not use placeholder domains, contract IDs, or account IDs in production deployments.
- Do not let browser code manage server private keys or relayer signing keys.

## Security Audit

- Audited at: 2026-07-21T03:48:25.169\+00:00
- Summary: All 99 static findings are false positives caused by Markdown fences, TypeScript template literals, placeholders, or legitimate NEAR development documentation. The reviewed materials contain no embedded credentials, prompt-injection text, unauthorized command execution, or evidence of data exfiltration. Key-handling examples should still be used only with protected server-side secrets.

## Stats

- Views: 0
- Downloads: 5
- Favorites: 1
- Popularity score: 0