feat(docs): Agent Skills registry + Templates gallery

.github/workflows/sync-skills.yml

@@ -0,0 +1,90 @@
+name: Sync agent skills from sei-skill
+
+# The installable agent skills at .mintlify/skills/<name>/SKILL.md are GENERATED
+# from the canonical sei-skill repo (github.com/sei-protocol/sei-skill) by
+# scripts/build-mintlify-skills.mjs — they are never hand-authored here. This
+# workflow regenerates them and opens a PR for review (generation is LLM-assisted
+# and non-deterministic, so a human reviews before merge).
+#
+# Triggers:
+#   - workflow_dispatch    (manual; optionally pass a sei-skill ref)
+#   - repository_dispatch  (sei-skill's release workflow sends type: sei-skill-release
+#                           with client_payload.ref = the released tag/sha)
+#
+# Requires repo secret: ANTHROPIC_API_KEY
+
+on:
+  workflow_dispatch:
+    inputs:
+      ref:
+        description: 'sei-skill ref to generate from'
+        required: false
+        default: 'main'
+  repository_dispatch:
+    types: [sei-skill-release]
+
+permissions:
+  contents: write
+  pull-requests: write
+
+defaults:
+  run:
+    shell: bash
+
+jobs:
+  sync:
+    runs-on: ubuntu-latest
+    timeout-minutes: 20
+    steps:
+      - name: Checkout docs
+        uses: actions/checkout@v4
+
+      - name: Checkout sei-skill (canonical source)
+        uses: actions/checkout@v4
+        with:
+          repository: sei-protocol/sei-skill
+          ref: ${{ github.event.client_payload.ref || inputs.ref || 'main' }}
+          path: .sei-skill-src
+
+      - name: Set up Node
+        uses: actions/setup-node@v4
+        with:
+          node-version: '20'
+
+      - name: Install generator dependency
+        run: npm install --no-save @anthropic-ai/sdk
+
+      - name: Record sei-skill revision
+        id: src
+        run: echo "ref=$(git -C .sei-skill-src rev-parse --short HEAD)" >> "$GITHUB_OUTPUT"
+
+      - name: Regenerate skills from sei-skill
+        env:
+          ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }}
+          SEI_SKILL_DIR: ${{ github.workspace }}/.sei-skill-src/skill
+          SEI_SKILL_REF: ${{ steps.src.outputs.ref }}
+        run: node scripts/build-mintlify-skills.mjs --write
+
+      - name: Clean up source + build dirs
+        run: rm -rf .sei-skill-src dist
+
+      - name: Open PR if skills changed
+        env:
+          GH_TOKEN: ${{ github.token }}
+        run: |
+          set -euo pipefail
+          if git diff --quiet -- .mintlify/skills; then
+            echo 'No skill changes; nothing to do.'
+            exit 0
+          fi
+          BRANCH="chore/sync-skills-${{ steps.src.outputs.ref }}"
+          git config user.name 'github-actions[bot]'
+          git config user.email '41898282+github-actions[bot]@users.noreply.github.com'
+          git checkout -b "$BRANCH"
+          git add .mintlify/skills
+          git commit -m "chore(skills): regenerate from sei-skill@${{ steps.src.outputs.ref }}"
+          git push -f origin "$BRANCH"
+          gh pr create \
+            --title "chore(skills): regenerate from sei-skill@${{ steps.src.outputs.ref }}" \
+            --body "Automated regeneration of \`.mintlify/skills/\` from [sei-protocol/sei-skill](https://github.com/sei-protocol/sei-skill)@${{ steps.src.outputs.ref }} via \`scripts/build-mintlify-skills.mjs\`. These are generated artifacts — review for quality before merge." \
+            || echo 'PR already exists for this branch; pushed update.'

.gitignore

@@ -1,6 +1,9 @@
 .DS_Store
 node_modules/
-.mintlify/
+# Mintlify uses .mintlify/ as a local build cache, but .mintlify/skills/ holds
+# the hosted agent skills (SKILL.md) that must ship — keep that subtree tracked.
+.mintlify/*
+!.mintlify/skills/
 .next/
 .vercel/
 dist/

ai/sei-skill/index.mdx

@@ -44,7 +44,7 @@ sei-skill covers three areas. You can install all three or just the ones you nee
 
 **Ecosystem** — infrastructure and integrations:
 - RPC endpoints (public, community, paid SaaS)
-- Bridges (LayerZero V2, Wormhole, Axelar, CCTP)
+- Bridges (LayerZero V2, Wormhole, CCTP)
 - Oracles (Chainlink, Pyth, API3, RedStone)
 - Indexers (The Graph, Goldsky, Dune, Moralis)
 - DeFi protocols (DragonSwap, Yei, Takara, Saphyre)

ai/skills.mdx

@@ -0,0 +1,70 @@
+---
+title: 'Skills Registry'
+sidebarTitle: 'Skills Registry'
+description: 'Install Sei Foundation agent skills into your AI coding assistant with one command. Each skill teaches your assistant a focused slice of Sei — contracts, frontend, precompiles, nodes, payments, security, bridges, or migration.'
+keywords: ['sei skills', 'agent skills', 'skill.md', 'npx skills add', 'claude code', 'cursor', 'windsurf', 'ai coding assistant']
+---
+
+import { SkillsRegistry } from '/snippets/skills-registry.jsx';
+
+Sei Foundation publishes a set of **agent skills** — focused, installable knowledge packs that make your AI coding assistant Sei-aware. They're hosted directly on this docs site and follow the open [`skill.md`](https://www.mintlify.com/blog/skill-md) standard, so any compatible assistant (Claude Code, Cursor, Windsurf, and others) can install them.
+
+## Install
+
+Install the complete Foundation set with one command — the CLI detects your installed assistants and lets you pick which to install into:
+
+```bash
+npx skills add https://docs.sei.io
+```
+
+<Info>
+  This fetches every skill served at `docs.sei.io/.well-known/skills/` and installs the ones you select. Skills stay current on every docs deploy — no manual updates.
+</Info>
+
+## Foundation skills
+
+Filter by domain to find what fits your project. Every card copies the same command — `npx skills add https://docs.sei.io` — which then lets you pick exactly which skills to install, so you can keep your assistant's context lean.
+
+<SkillsRegistry />
+
+## How skills work
+
+Each Foundation skill is a single `SKILL.md` file with YAML frontmatter describing **when** an assistant should reach for it and a focused playbook of Sei-specific facts, code, and pitfalls. Because they're served from this site, they're also discoverable by autonomous agents:
+
+<CardGroup cols={2}>
+  <Card title="Discovery endpoint" icon="rss">
+    Agents can enumerate every skill at `docs.sei.io/.well-known/skills/` and fetch any `SKILL.md` directly — no install step required.
+  </Card>
+  <Card title="Always up to date" icon="arrows-rotate">
+    Skills are versioned in [`sei-protocol/sei-docs`](https://github.com/sei-protocol/sei-docs) under `.mintlify/skills/` and redeploy with the docs.
+  </Card>
+</CardGroup>
+
+## Foundation vs. the full sei-skill
+
+The skills above are **focused** — one domain each, ideal when you want to keep your assistant's context tight. If you'd rather load a single comprehensive knowledge base covering every domain at once, use the full [**sei-skill**](/ai/sei-skill) instead.
+
+| Use a Foundation skill when… | Use the full [sei-skill](/ai/sei-skill) when… |
+|---|---|
+| You work mostly in one area (e.g. contracts only) | You want all-domain coverage in one install |
+| You want to keep assistant context lean | You're starting a new Sei project from scratch |
+| You're composing your own skill set | You want the editor-resident Claude Code skill |
+
+## Community skills
+
+The skills registry is open. Ecosystem teams — DEXs, lending protocols, oracles, infra providers — can publish their own skills so developers building on top of them get accurate, integration-specific guidance from their AI assistant.
+
+<Card title="Publish your skill" icon="upload" href="https://github.com/sei-protocol/sei-docs/blob/main/.mintlify/skills">
+  Host a `SKILL.md` in your own docs (any Mintlify site serves `/.well-known/skills/` automatically) or contribute one to `sei-protocol/sei-docs`. Community skills will be listed here as they ship.
+</Card>
+
+## Next steps
+
+<CardGroup cols={2}>
+  <Card title="sei-skill" icon="brain" href="/ai/sei-skill">
+    The full multi-domain knowledge base, with per-assistant install instructions and example prompts.
+  </Card>
+  <Card title="MCP Server" icon="plug" href="/ai/mcp-server">
+    Give your assistant live on-chain access — read balances, send transactions, and query network state.
+  </Card>
+</CardGroup>

docs.json

@@ -207,6 +207,7 @@
             "pages": [
               "evm/sei-js/index",
               "evm/sei-js/create-sei",
+              "evm/templates",
               "evm/sei-js/ledger",
               "evm/sei-js/registry"
             ]
@@ -352,6 +353,7 @@
             "group": "AI",
             "pages": [
               "ai/index",
+              "ai/skills",
               {
                 "group": "Agent Skills",
                 "pages": [
@@ -1655,6 +1657,16 @@
       "source": "/llms/skill.md",
       "destination": "/skill.md",
       "permanent": true
+    },
+    {
+      "source": "/skills",
+      "destination": "/ai/skills",
+      "permanent": true
+    },
+    {
+      "source": "/templates",
+      "destination": "/evm/templates",
+      "permanent": true
     }
   ],
   "interaction": {

evm/sei-js/create-sei.mdx

@@ -11,7 +11,7 @@
 
 Every generated project includes wallet connections, contract interactions, TypeScript, Tailwind CSS, Mantine UI, Biome for formatting, and responsive layouts — no additional setup required.
 
 ## Quick Start
 
 You don't need to install `@sei-js/create-sei` globally. Use it directly with npx or pnpm:
 
@@ -28,7 +28,7 @@
   </Tab>
 </Tabs>
 
 ## Interactive Setup
 
 <Steps>
 
@@ -54,7 +54,7 @@
 
 </Steps>
 
 ### CLI Options
 
 | Command                 | Description                                           |
 | ----------------------- | ----------------------------------------------------- |
@@ -63,11 +63,11 @@
 | `app --extension <ext>` | Add an optional extension to your project             |
 | `list-extensions`       | List available extensions                             |
 
 ## Default Template
 
 The default template creates a **Next.js + Wagmi (EVM)** application — a production-ready Next.js app with Wagmi for type-safe Ethereum wallet connections and blockchain interactions. Includes built-in support for MetaMask, WalletConnect, Coinbase Wallet, and other popular wallets.
 
-**Tech Stack:** Next.js 14, Wagmi v2, Viem, TanStack Query, Tailwind CSS
+**Tech Stack:** Next.js 15, React 19, Wagmi v2, Viem, RainbowKit, TanStack Query, Tailwind CSS v4, Mantine UI, Biome, TypeScript
 
 ```bash
 npx @sei-js/create-sei app --name my-sei-app
@@ -77,13 +77,13 @@
 
 Enhance your project with additional functionality using extensions.
 
 ### List Available Extensions
 
 ```bash
 npx @sei-js/create-sei list-extensions
 ```
 
 ### Precompiles Extension
 
 Add Sei precompile contract integration with examples for querying native blockchain data like token supply, staking info, and governance proposals.
 

evm/templates.mdx

@@ -0,0 +1,96 @@
+---
+title: 'Templates'
+sidebarTitle: 'Templates'
+description: 'Production-ready Sei dApp templates you can scaffold in one command with @sei-js/create-sei — wallet connections, contract interactions, and TypeScript wired up out of the box.'
+keywords: ['sei templates', 'create-sei', 'scaffold', 'starter', 'nextjs', 'wagmi', 'viem', 'precompiles', 'dapp template']
+---
+
+Start a new Sei dApp from a working, production-ready template instead of a blank folder. The [`@sei-js/create-sei`](/evm/sei-js/create-sei) CLI scaffolds a fully wired project — wallet connections, contract interactions, TypeScript, and styling — in seconds.
+
+## Scaffold in one command
+
+<CodeGroup>
+
+```bash npm
+npx @sei-js/create-sei app --name my-sei-app
+```
+
+```bash pnpm
+pnpm create @sei-js/sei app --name my-sei-app
+```
+
+</CodeGroup>
+
+Then install and run:
+
+```bash
+cd my-sei-app
+npm install
+npm run dev
+```
+
+## Templates
+
+<Columns cols={2}>
+  <Card title="Next.js + wagmi" icon="react" href="/evm/sei-js/create-sei">
+    The default starter — a production-ready **Next.js 15** app (React 19) with type-safe wallet connections and contract reads/writes.
+
+    **Stack:** Next.js 15 · React 19 · wagmi v2 · viem · RainbowKit · TanStack Query · Tailwind CSS v4 · Mantine UI · Biome · TypeScript
+
+    **Includes:** RainbowKit wallet connection (MetaMask / WalletConnect / Coinbase Wallet), organized components/hooks/utilities, and Sei network config.
+
+    ```bash
+    npx @sei-js/create-sei app --name my-sei-app
+    ```
+  </Card>
+
+  <Card title="Precompiles extension" icon="cube" href="/evm/precompiles/example-usage">
+    The default template plus working examples that query Sei's native [precompiles](/evm/precompiles/example-usage) — Bank, Staking, and Governance — directly from the frontend.
+
+    **Adds:** native token supply, staking info, and governance proposal reads via `@sei-js/precompiles`.
+
+    ```bash
+    npx @sei-js/create-sei app --name my-app --extension precompiles
+    ```
+  </Card>
+</Columns>
+
+<Info>
+  See every available extension with `npx @sei-js/create-sei list-extensions`. Full CLI options and the interactive setup flow are documented on the [Scaffold Sei](/evm/sei-js/create-sei) page.
+</Info>
+
+## What every template gives you
+
+<Columns cols={2}>
+  <Card title="Wallet integration" icon="wallet">
+    Pre-configured wallet connections and React hooks — connect, read balances, and send transactions without boilerplate.
+  </Card>
+  <Card title="Sei network config" icon="network-wired">
+    Mainnet (`pacific-1`, 1329) and testnet (`atlantic-2`, 1328) wired up, with contract-interaction examples.
+  </Card>
+  <Card title="Type safety" icon="square-check">
+    End-to-end TypeScript with wagmi + viem, so contract calls and ABIs are typed.
+  </Card>
+  <Card title="Tooling" icon="screwdriver-wrench">
+    Tailwind CSS, Mantine UI, Biome formatting, and Git initialized — ready to build on.
+  </Card>
+</Columns>
+
+<Note>
+  **Prerequisites:** Node.js v18 or higher (`node --version` to check).
+</Note>
+
+## More templates are coming
+
+This gallery grows as new starters ship. Building a template the ecosystem should know about — a DeFi starter, an NFT mint, an x402-payments app, or an AI agent? Contribute it to [`sei-protocol/sei-js`](https://github.com/sei-protocol/sei-js/tree/main/packages/create-sei) and it can be listed here.
+
+## Next steps
+
+<CardGroup cols={2}>
+  <Card title="Scaffold Sei (CLI reference)" icon="terminal" href="/evm/sei-js/create-sei">
+    Full `create-sei` options, extensions, and troubleshooting.
+  </Card>
+  <Card title="Build a frontend" icon="browser" href="/evm/building-a-frontend">
+    Wire wagmi + viem and a wallet into a Sei dApp from first principles.
+  </Card>
+</CardGroup>

learn/sip-03-migration.mdx

@@ -26,9 +26,9 @@
 
 - Governance [Proposal #99](https://www.mintscan.io/sei/proposals/99) — initiated the migration
 
-- Governance [Proposal #115](https://www.mintscan.io/sei/proposals/115) — disables CosmWasm code uploads and contract instantiations. After this passes, no new CosmWasm contracts can be deployed on Sei.
+- Governance [Proposal #115](https://www.mintscan.io/sei/proposals/115) (pacific-1 mainnet; the atlantic-2 testnet equivalent is #246) — disables CosmWasm code uploads and contract instantiations. No new CosmWasm contracts can be deployed on Sei.
 
-- Governance [Proposal #116](https://www.mintscan.io/sei/proposals/116) — disables inbound IBC transfers. After this passes and is activated, IBC assets bridged from Cosmos chains can no longer arrive on Sei.
+- Governance [Proposal #116](https://www.mintscan.io/sei/proposals/116) (pacific-1 mainnet; the atlantic-2 testnet equivalent is #247) — disables inbound IBC transfers. IBC assets bridged from Cosmos chains can no longer arrive on Sei.
 
 </Info>
 
@@ -37,7 +37,7 @@
 - If you use Keplr or Leap (Cosmos-style wallets) and hold assets on the native address (sei1...), you should move assets to an EVM-compatible address (0x...). Use the Asset Transfer tool linked below.
 - If you use Compass or another EVM wallet already, you’re good — continue as normal.
 
 ## IBC Asset Migration Table
 
 If you hold any of the following IBC assets on Sei, take action before [Proposal #116](https://www.mintscan.io/sei/proposals/116) (disables inbound IBC transfers) passes and is activated.
 
@@ -59,7 +59,7 @@
 
 ## Key tools and resources
 
 ### 1) Asset Transfer (Native ↔ EVM)
 
 - Use the official Sei Dashboard to move assets between native (Keplr/Leap/Fin) and EVM (MetaMask/Compass etc.) addresses: [Sei Dashboard Transfer](https://dashboard.sei.io/evm-upgrade) or the Bridge tab at [Sei Dashboard Bridge](https://dashboard.sei.io/bridge).
 
@@ -68,7 +68,7 @@
 - You used Keplr or Leap before and want assets available via an EVM wallet going forward.
 - You need to access tokens on apps that now expect an EVM (0x) address.
 
 ### 2) USDC on Sei
 
 Native USDC and Circle's CCTP V2 are now supported on Sei. USDC from Noble (USDC.n) is deprecated.
 
@@ -148,7 +148,7 @@
 - **Associate before sending.** Associating the new account before transferring ensures the funds arrive at the correct, immediately spendable address rather than a temporary holding address.
 - **Optional verification.** To confirm the paired `sei1...` address independently, call `getSeiAddr(0x...)` on the `addr` precompile. See [Query Linked Addresses](/learn/accounts#query-linked-addresses).
 
 ## FAQ
 
 ### I am a Keplr / Leap wallet user; do I need to do anything?
 
@@ -180,6 +180,6 @@
 **Do not confuse address linking with staking migration.** Even though `sei1...` and `0x...` addresses point to the same underlying account once associated, the chain can only recognize this link after explicit association. Without association, your staked SEI will not be accessible via EVM after the upgrade, and you will have no way to unbond or claim rewards.
 </Warning>
 
 ### I hold USDC.n (USDC via Noble) — what should I do?
 
 You must swap or migrate your USDC.n to native USDC before the SIP-03 deprecation of Cosmos, CosmWasm and IBC related functionality, slated for **June 15, 2026**. After the upgrade, USDC.n may become inaccessible or lose its value on Sei. See the [USDC on Sei](#2-usdc-on-sei) section above for swap and migration options, or read the full announcement: [Holders of USDC.n Need to Swap or Migrate](https://blog.sei.io/announcements/holders-of-usdcn-need-to-swap-or-migrate/).