Add seeker-app/: end-to-end skills for the Seeker dApp lifecycle

[Sarthib7]

Adds a sixth skill group at seeker-app/ covering the lifecycle phases not addressed by the existing mwa/, genesis-token/, and skr-address-resolution/ skills:

• seeker-app-builder: router that assesses project state and routes through scaffold -> MWA -> tx -> UX -> publish. References mwa-setup, mwa-connection, mwa-transactions, genesis-token, and skr-address-resolution as siblings.
• seeker-app-scaffold: npm create solana-dapp / create-expo-app paths, Android toolchain (JDK 17, adb, ANDROID_HOME), crypto polyfill must-be- first rule, APP_IDENTITY / SOLANA_CHAIN constants (CAIP-2 format), New Architecture / Fabric note.
• seeker-ux: one-tap approval, batched instructions, haptic ladder, AMOLED palette, 48/56 px tap targets, react-native-reanimated v4 + worklets, RN pitfalls (Buffer, address.toString).
• solana-pay-mobile: SOL/USDC transfers via the useMobileWallet hook from @wallet-ui/react-native-web3js (matching the existing mwa skills), Solana Pay URL spec, raw transact() fallback for SIWS/remote scenarios.
• seed-vault: audience-boundary skill - wallet developers only; routes dApp builders back to MWA.
• dapp-store-publishing: keystore + assembleRelease + @solana-mobile/ dapp-store-cli, publisher wallet and App NFT, ProGuard footgun for release builds with minifyEnabled.

Each SKILL.md opens with Use / Not blocks so an agent can confirm fit before reading further. All cross-references treat the existing skills as siblings of the new group. Frontmatter matches the existing repo convention (name + description only).

README.md gains a 'Seeker App Lifecycle' section under Available Skills and the new install line, mirroring the format of the existing entries.

Style choices

• Frontmatter matches the existing convention: name + description only, trigger phrases inside the description.
• Router-with-sub-skills pattern: parallels mwa/'s mobile-wallet-adapter-react-native/ router + mwa-setup / mwa-connection / mwa-transactions
  sub-skills.
• Every SKILL.md opens with Use / Not blocks so an agent can confirm fit before reading further. Mirrors the "When to Use / When NOT to Use"
  structure of mwa-setup.
• Pitfall tables (Issue | Fix) for non-obvious failure modes.
• Cross-references treat existing skills as siblings (not as external repos), so an agent following the router lands on the right mwa/ skill directly.

Currency check

Verified against authoritative sources at commit time:

• MWA web3.js transact.ts source for hook + raw API shapes
• @solana-mobile/dapp-store-cli@1.0.0 (Node ≥18), CLI form dapp-store --apk-file ... --whats-new "..." (legacy init/create/validate/publish removed)
• @wallet-ui/react-native-web3js@4.1.0
• react-native-reanimated@4.3.1 + react-native-worklets companion (requires New Architecture)
• seedvault-wallet-sdk@0.4.0 (Gradle)
• USDC mainnet EPjFW…Dt1v and devnet 4zMMC…ncDU
• expo-haptics API names

Why upstream this

These skills currently live at Sarthib7/seeker-skills (CC0, working today, installable via cp -r). Upstreaming
makes sense because:

• They explicitly fill gaps in this repo (scaffold, UX, payments, Seed Vault audience boundary, publishing).
• The canonical install path is cp -r solana-mobile-dev-skill/...; bundling here means agents picking up the official skills automatically get the
  lifecycle coverage too.
• Style and frontmatter convention already match.

Happy to take any structural feedback — split into separate top-level folders, rename, etc.

License is CC0 / public domain, no attribution required.