@@ -6,17 +6,32 @@ scope: heading
 # AGENTS.md: "Sentence case for headings." Only the first word and proper nouns
 # are capitalized. Proper nouns below are exempt so they may appear mid-heading.
 match: $sentence
+# A colon starts a new sentence, so "Step 1: Evaluate compatibility" is still
+# sentence case.
+indicators:
+  - ':'
 exceptions:
   - Sei
   - Sei Giga
   - Sei EVM
   - Sei Network
+  - Sei Mainnet
+  - Sei Testnet
   - SeiDB
   - EVM
   - ERC
   - CosmWasm
   - Cosmos
   - Ethereum
+  - Ethereum Mainnet
+  - Arbitrum
+  # Scoped to the migration heading so the rule still catches "Base fee" and
+  # "Base layer" elsewhere.
+  - Migrating from Base
+  - Polygon PoS
+  - Avalanche C-Chain
+  - LayerZero V2
+  - Uniswap V3
   - Solidity
   - Hardhat
   - Foundry
 
@@ -10,6 +10,15 @@ action:
 swap:
   'the Sei blockchain': Sei
   'Sei [Cc]hain': Sei
+  # Capitalized forms are reader-facing prose; the lowercase literals
+  # 'pacific-1' and 'atlantic-2' are intentionally kept for CLI, config,
+  # registry keys, and API paths, and don't match here (ignorecase: false).
+  'Pacific-1': Sei Mainnet
+  'Atlantic-2': Sei Testnet
+  # The network names are proper nouns, so the lowercase prose forms are wrong
+  # too. 'Sei Mainnet' and 'Sei Testnet' never match these patterns.
+  'Sei mainnet': Sei Mainnet
+  'Sei testnet': Sei Testnet
   'gas fees?': gas
   # Bare 'CW' is accepted shorthand for CosmWasm here — the standard names
   # CW20/CW721/CW1155 plus phrases like "CW pointer", "CW-based", and "CW NFT".
 
@@ -14,7 +14,7 @@
 - **Sei Giga** is the next-generation architecture upgrade
 - **seid** is the CLI binary; always lowercase and code-formatted
 - **sei-js** (lowercase, hyphenated) for the JS/TS SDK
-- Use **Sei Mainnet** (EVM chain ID `1329`) and **Sei Testnet** (EVM chain ID `1328`) in reader-facing copy. Keep the literal identifiers `pacific-1` and `atlantic-2` only where technically required, especially in node-operator instructions, CLI or config values, API paths, and registry keys.
+- Use **Sei Mainnet** (EVM chain ID `1329`) and **Sei Testnet** (EVM chain ID `1328`) in reader-facing copy. Both are proper nouns, so "Sei mainnet" and "Sei testnet" are wrong. Keep the literal identifiers `pacific-1` (mainnet) and `atlantic-2` (testnet) only where technically required, especially in node-operator instructions, CLI or config values, API paths, and registry keys.
 - Precompiles live at specific addresses — always reference exact address when mentioning
 - **Twin Turbo Consensus** and **parallelization engine** are proper nouns
 - Prefer "dApp" over "app" when the context is blockchain
 
@@ -285,7 +285,8 @@ Use tables for comparing features, listing network information, or presenting st
 
 When referencing network information, always include:
 
-- Chain ID (both decimal and hex format where applicable)
+- EVM chain ID (both decimal and hex format where applicable)
+- Cosmos chain ID (`pacific-1`, `atlantic-2`) when the table documents `seid` or Cosmos endpoints
 - RPC URLs
 - Explorer links
 
 
@@ -157,7 +157,7 @@ account = Account.from_key("YOUR_PRIVATE_KEY")
 wallet_provider = EthAccountWalletProvider(
     config=EthAccountWalletProviderConfig(
         account=account,
-        chain_id=1329,  # Sei mainnet
+        chain_id=1329,  # Sei Mainnet
         rpc_url="https://evm-rpc.sei-apis.com",
     )
 )
@@ -215,7 +215,7 @@ For Sei-native DeFi actions (swaps on Symphony/DragonSwap, staking via Silo, len
 
 ### Known Quirks on Sei
 
-Verified by running AgentKit `0.10.4` against Sei testnet (`chain 1328`). These quirks sit in AgentKit's network and action-provider layer and apply to **both** `ViemWalletProvider` and `PrivyWalletProvider`:
+Verified by running AgentKit `0.10.4` against Sei Testnet (`chain 1328`). These quirks sit in AgentKit's network and action-provider layer and apply to **both** `ViemWalletProvider` and `PrivyWalletProvider`:
 
 - **Balances are labeled "ETH" in action output.** `walletActionProvider` hard-codes the native-currency symbol, so `get_wallet_details` returns strings like `Native Balance: 512993.50 ETH` and `native_transfer` responses say `Transferred 0.05 ETH to 0x...` even on Sei. Signing and arithmetic are unaffected — it's a display-only quirk. If the LLM will quote balances or transfer confirmations to users, add a post-processing step or a system-prompt instruction to rewrite `ETH` → `SEI` when `chain_id == 1329 || 1328`.
 - **`networkId` is `undefined`.** Coinbase's internal `CHAIN_ID_TO_NETWORK_ID` map only includes Ethereum, Polygon, Base, Arbitrum, and Optimism (mainnet + testnet). Sei's chain IDs aren't in it, so `walletProvider.getNetwork()` returns `{ protocolFamily: 'evm', chainId: '1328', networkId: undefined }`. This is harmless for signing/sending, but **any action provider that branches on `networkId`** will refuse to run on Sei. In practice, `AgentKit.from({...})` prints a warning like `The following action providers are not supported on the current network and will be unavailable: weth, x402` and silently drops them — if you expect an action and it's missing from `agentKit.getActions()`, check this warning first.
@@ -273,7 +273,7 @@ Response:
 </Step>
 
 <Step title="Send a transaction on Sei">
-Use `eip155:1329` (CAIP-2 format) to target Sei mainnet:
+Use `eip155:1329` (CAIP-2 format) to target Sei Mainnet:
 
 ```bash
 curl --request POST https://api.privy.io/v1/wallets/wallet_abc123/rpc \
@@ -343,7 +343,7 @@ console.log('Wallet address:', wallet.address);
 // serialize a BigInt, so don't pass `parseEther(...)` directly.
 const { hash } = await privy.walletApi.ethereum.sendTransaction({
   walletId: wallet.id,
-  caip2: 'eip155:1329', // Sei mainnet
+  caip2: 'eip155:1329', // Sei Mainnet
   transaction: {
     to: '0x742d35Cc6634C0532925a3b844Bc454e4438f44e',
     value: '0x' + parseEther('0.01').toString(16),
@@ -381,7 +381,7 @@ print(f"Wallet address: {wallet.address}")
 result = client.wallets.rpc(
     wallet_id=wallet.id,
     method="eth_sendTransaction",
-    caip2="eip155:1329",  # Sei mainnet
+    caip2="eip155:1329",  # Sei Mainnet
     params={
         "transaction": {
             "to": "0x742d35Cc6634C0532925a3b844Bc454e4438f44e",
@@ -401,7 +401,7 @@ print(f"Transaction hash: {result.hash}")
 
 ### Known Quirks on Sei (Privy)
 
-Verified by running `@privy-io/server-auth` `1.32.5` against Sei testnet (`eip155:1328`):
+Verified by running `@privy-io/server-auth` `1.32.5` against Sei Testnet (`eip155:1328`):
 
 - **`value` must be a hex string, not a `BigInt`.** Privy's request signer uses RFC 8785 JSON canonicalization (`canonicalize`), which throws `TypeError: Do not know how to serialize a BigInt` if you pass a `BigInt` in any field of the `transaction` object. Convert viem's `parseEther(...)` output with `'0x' + parseEther('0.01').toString(16)` before sending.
 - **`authorizationKeyIds` on `createWallet` expects the public-key registration ID, not the dashboard key ID.** Passing the ID shown next to a key in the Privy dashboard can fail with `400 Invalid authorization key IDs`. If you only need an app-owned wallet (app credentials + `authorizationPrivateKey` for request signing), omit `authorizationKeyIds` — the wallet is still fully operable.
@@ -519,7 +519,7 @@ const wallet = await privy.walletApi.createWallet({ chainType: 'ethereum' });
 const walletProvider = await PrivyWalletProvider.configureWithWallet({
   appId: process.env.PRIVY_APP_ID!,
   appSecret: process.env.PRIVY_APP_SECRET!,
-  chainId: '1329', // Sei mainnet
+  chainId: '1329', // Sei Mainnet
   walletId: wallet.id,
   authorizationPrivateKey: process.env.PRIVY_AUTH_KEY,
 });
 
@@ -210,7 +210,7 @@ Network arguments accept `sei`, `sei-testnet`, `1329`, `1328`, `0x531`, or `0x53
 | --- | --- | --- | --- |
 | `search_docs` | Search the official Sei docs | "How do I use the staking precompile?" | No |
 | `get_supported_networks` | List supported networks | "Which Sei networks are available?" | No |
-| `get_chain_info` | Network chain ID and latest block | "Show Sei mainnet info" | No |
+| `get_chain_info` | Network chain ID and latest block | "Show Sei Mainnet info" | No |
 | `get_balance` | Native SEI balance | "Check balance of 0x123..." | No |
 | `is_contract` | Verify a contract address | "Is 0x789... a contract?" | No |
 | `read_contract` | Call a read-only contract function | "Read DEX reserves" | No |
 
@@ -24,7 +24,7 @@ The default install targets Claude Code, placing the skill in `~/.claude/skills/
 ./install.sh
 ```
 
-The skill loads automatically in every Claude Code session. To verify it's active, ask: *"What is the SSTORE gas cost on Sei testnet?"*
+The skill loads automatically in every Claude Code session. To verify it's active, ask: *"What is the SSTORE gas cost on Sei Testnet?"*
 
 </Tab>
 
 
@@ -10,10 +10,10 @@ Once sei-skill is installed, your AI assistant has accurate, up-to-date context
 ## Contracts
 
 ```
-Set up Foundry for Sei testnet
+Set up Foundry for Sei Testnet
 ```
 ```
-Deploy a Solidity contract to Sei mainnet and verify it on Seiscan
+Deploy a Solidity contract to Sei Mainnet and verify it on Seiscan
 ```
 ```
 How do I call the Staking precompile from Solidity to delegate SEI?
@@ -49,7 +49,7 @@ Migrate my Ethereum contract to Sei — what do I need to change?
 ## Frontend
 
 ```
-Set up Wagmi v2 with Sei mainnet and testnet chain configs
+Set up Wagmi v2 with Sei Mainnet and Sei Testnet chain configs
 ```
 ```
 How do I integrate Sei Global Wallet for social login in my dApp?
@@ -79,7 +79,7 @@ Set up wagmi useWriteContract for delegating SEI to a validator
 ## Ecosystem
 
 ```
-What are reliable RPC endpoints for Sei mainnet with failover?
+What are reliable RPC endpoints for Sei Mainnet with failover?
 ```
 ```
 How do I bridge USDC to Sei using LayerZero V2?
 
@@ -170,7 +170,7 @@ cast chain-id --rpc-url=$EVM_RPC_URL
 
 ## Try it live
 
-Each `cast` diagnostic above is a plain read-only JSON-RPC call. Run the same four against Sei mainnet right here — the example address (`0xAa55…3d96`) is the sender from the `cast tx` output earlier on this page.
+Each `cast` diagnostic above is a plain read-only JSON-RPC call. Run the same four against Sei Mainnet right here — the example address (`0xAa55…3d96`) is the sender from the `cast tx` output earlier on this page.
 
 <RunSnippet method="eth_chainId" network="mainnet" title="cast chain-id" description="eth_chainId — decodes to 1329. A mismatch here is the most common cause of a rejected transaction." />
 
 
@@ -239,7 +239,7 @@ Existing OpenZeppelin contracts and tools work unchanged.
 
 ## Testing & Migration Checklist
 
-- ✅ Re‑deploy your Solidity code to Sei testnet; most contracts need no changes.
+- ✅ Re‑deploy your Solidity code to Sei Testnet; most contracts need no changes.
 - ✅ If you used SELFDESTRUCT, refactor to a soft‑close pattern.
 - ✅ Remove EIP‑1559 fee UI complexity; use a single `gasPrice` input in frontends.
 - ✅ If you rely on on‑chain “randomness,” integrate an oracle/VRF.