Add Mobile & Seeker subsection with seeker-skills

[Sarthib7]

Summary

Adds a new Mobile & Seeker subsection under AI Coding Skills with two complementary entries:

• solana-mobile/solana-mobile-dev-skill — Solana Mobile's official skill set covering Mobile
  Wallet Adapter (setup, connection, transactions), .skr domain resolution, and Seeker Genesis Token verification for React Native Expo apps.
• Sarthib7/seeker-skills — End-to-end skills for the rest of the Seeker dApp lifecycle: scaffold + Android
  toolchain, Seeker-specific UX conventions (one-tap approval, haptics, AMOLED, 120 Hz), USDC/SOL payments via MWA, Seed Vault for wallet developers (with a
  boundary note routing dApp builders back to MWA), and dApp Store APK signing + publishing via @solana-mobile/dapp-store-cli.

Why a new subsection

Mobile/Seeker development has a distinct toolchain — MWA, the dApp Store, Seed Vault, and Seeker hardware constraints — that doesn't fit cleanly under
General, DeFi, or Infrastructure. A dedicated subsection makes the category discoverable for devs building on Seeker. Currently only solana-game-skill
mentions Solana Mobile in passing, and it sits under General. Per CONTRIBUTING.md: "If your item doesn't fit existing categories, you may suggest a new
one. Please explain why the new category is needed."

Adding a new item

• Related to AI and Solana development — both are Claude Code skills for Solana Mobile dApp development
• Added to an appropriate category — new Mobile & Seeker subsection proposed under AI Coding Skills, justification above
• Format [name](link) - Brief description. — both entries follow exactly
• One-sentence descriptions — each entry is a single sentence (information-dense, matching existing patterns like helius-skill and
  magicblock-dev-skill)
• Spelling and grammar checked

Quality standards

• Actively maintained — both repos updated recently
• Documentation available — READMEs in both, plus per-skill Use / Not blocks and pitfall tables in seeker-skills
• Provides value to Solana developers — fills the gap between scaffolding a Solana Mobile app and shipping it to the dApp Store

What NOT to submit

• No token promotion
• No paid promotion
• No vaporware — both are CC0 markdown skill sets, working today, installable via cp -r into ~/.claude/skills/

Pull request process

• Forked the repo (Sarthib7/awesome-solana-ai)
• Branched (add-seeker-skills)
• Changes scoped to README.md only (+8 lines, single commit)
• Clear PR description (this one)

Notes

The two skill sets are intentionally complementary, not overlapping: the official repo covers MWA + .skr + SGT; seeker-skills covers scaffold + UX +
payments + Seed Vault audience boundary + dApp Store publishing. Together they walk an agent end-to-end from empty repo → signed APK → live dApp Store
listing.

seeker-skills is licensed CC0 to match this list.

[greptile-apps]

Greptile Summary

This PR adds a new Mobile & Seeker subsection under AI Coding Skills with two entries covering Solana Mobile / Seeker dApp development.

• Adds solana-mobile-dev-skill (official Solana Mobile repo) and seeker-skills (PR author's own repo) as the first entries in the new subsection.
• The new section includes an extra prose description line not present in any other subsection (General, DeFi, Infrastructure), and the two entries are listed in reverse alphabetical order relative to the convention used throughout the document.

Confidence Score: 4/5

Safe to merge after minor formatting fixes; no functional or content correctness concerns beyond style inconsistencies and entry ordering.

The change is a small README-only addition. The extra section description line and reversed alphabetical order are straightforward to correct, and the self-submission of seeker-skills is worth a confirmation but does not block merging on its own.

README.md — the new subsection description line and entry ordering should be addressed before merge.

Important Files Changed

Filename	Overview
README.md	Adds a new "Mobile & Seeker" subsection with two entries; has a spurious section description line inconsistent with other subsections, and entry order is reversed relative to the alphabetical convention used elsewhere.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[AI Coding Skills] --> B[General]
    A --> C[DeFi]
    A --> D[Infrastructure]
    A --> E[Mobile & Seeker NEW]
    E --> F[solana-mobile-dev-skill]
    E --> G[seeker-skills]

Loading

_{Reviews (1): Last reviewed commit: "Add Mobile & Seeker subsection with seek..." | Re-trigger Greptile}

[greptile-apps]

The new subsection includes a section description ("AI coding skills for Solana Mobile (Seeker) dApps.") that no other subsection has. General, DeFi, and Infrastructure all start directly with their bullet list, so this line breaks the established pattern.

Suggested change

	### Mobile & Seeker
	AI coding skills for Solana Mobile (Seeker) dApps.
	- [solana-mobile-dev-skill](https://github.com/solana-mobile/solana-mobile-dev-skill) - Official Solana Mobile skills covering Mobile Wallet Adapter (setup, connection, transactions), `.skr` domain resolution, and Seeker Genesis Token verification for React Native Expo apps.
	### Mobile & Seeker
	- [solana-mobile-dev-skill](https://github.com/solana-mobile/solana-mobile-dev-skill) - Official Solana Mobile skills covering Mobile Wallet Adapter (setup, connection, transactions), `.skr` domain resolution, and Seeker Genesis Token verification for React Native Expo apps.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

[greptile-apps]

All existing subsections list entries in alphabetical order. seeker-skills (s-e) sorts before solana-mobile-dev-skill (s-o), so their order here is reversed relative to the established convention.

Suggested change

	- [solana-mobile-dev-skill](https://github.com/solana-mobile/solana-mobile-dev-skill) - Official Solana Mobile skills covering Mobile Wallet Adapter (setup, connection, transactions), `.skr` domain resolution, and Seeker Genesis Token verification for React Native Expo apps.
	- [seeker-skills](https://github.com/Sarthib7/seeker-skills) - End-to-end skills for building a Seeker dApp: scaffold + Android toolchain, UX conventions (one-tap approval, haptics, AMOLED, 120 Hz), USDC/SOL payments via MWA, Seed Vault for wallet developers, and dApp Store APK signing + publishing via `@solana-mobile/dapp-store-cli`.
	- [seeker-skills](https://github.com/Sarthib7/seeker-skills) - End-to-end skills for building a Seeker dApp: scaffold + Android toolchain, UX conventions (one-tap approval, haptics, AMOLED, 120 Hz), USDC/SOL payments via MWA, Seed Vault for wallet developers, and dApp Store APK signing + publishing via `@solana-mobile/dapp-store-cli`.
	- [solana-mobile-dev-skill](https://github.com/solana-mobile/solana-mobile-dev-skill) - Official Solana Mobile skills covering Mobile Wallet Adapter (setup, connection, transactions), `.skr` domain resolution, and Seeker Genesis Token verification for React Native Expo apps.

[greptile-apps]

Self-submission note: seeker-skills links to https://github.com/Sarthib7/seeker-skills, which is the PR author's own repository. CONTRIBUTING.md prohibits paid promotions but doesn't explicitly address self-submissions. Can you confirm this skill set is already being used by the broader community and is not primarily self-promotional?

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time! Is seeker-skills already being used by developers outside your own projects, and can you point to any community adoption?

[Sarthib7]

Thanks @greptile-apps — both style nits are fixed in 92dc94d:

• Dropped the section description line so the subsection goes heading → bullets, matching General / DeFi / Infrastructure.
• Reordered alphabetically: seeker-skills (s-e) before solana-mobile-dev-skill (s-o).

On the self-submission question — being transparent: seeker-skills is new (pushed today; I'm the author), so I can't point to outside-my-projects adoption
yet. The case rests on the merits rather than current usage:

• Working code, not vaporware — 6 SKILL.md files installable via cp -r seeker-app/* ~/.claude/skills/. CC0 license, no commercial angle.
• Fills a real gap — the official solana-mobile/solana-mobile-dev-skill covers MWA + .skr + Seeker Genesis Token. It does not cover scaffold +
  Android toolchain, Seeker-specific UX conventions, USDC payments via MWA, Seed Vault audience routing, or dApp Store APK signing + publishing via
  @solana-mobile/dapp-store-cli. Together they walk an agent end-to-end; the official set alone leaves the lifecycle incomplete.
• Documented — per-skill Use / Not blocks, pitfall tables (Issue | Fix), master index in the README.
• Cross-checked against current sources — MWA web3.js source (transact.ts), @solana-mobile/dapp-store-cli@1.0.0, react-native-reanimated@4.3.1,
  seedvault-wallet-sdk@0.4.0, the official mwa-setup / mwa-connection / mwa-transactions SKILL.md files.

[greptile-apps]

Thanks for the thorough follow-up and for addressing the style nits promptly.

On the self-submission question: your transparency here is appreciated, and the case you've made is reasonable — CC0, no commercial angle, working skill files, fills a documented gap in the official skill set's coverage. That said, the core concern stands: this is a brand-new repo pushed today with no external adoption yet. The list is curated, and the bar for inclusion is typically demonstrated utility to the broader community, not just potential utility.

A few honest observations:

1. The official solana-mobile/solana-mobile-dev-skill entry is a strong addition on its own — maintained by the Solana Mobile team, clearly in scope.

2. seeker-skills is the harder case. The content sounds well-structured (pitfall tables, Use/Not blocks, indexed README), but "documented and cross-checked" isn't the same as "community-validated." Awesome lists are discovery tools; listing a day-old self-authored repo risks setting a precedent that lowers the bar for similar submissions.

A practical path forward: split the PR, land the official solana-mobile-dev-skill entry now (no controversy there), and revisit seeker-skills once it has some stars, forks, or references from outside your own projects. That gives maintainers an easy yes on the clear-cut addition and a defensible standard for the second entry.

Ultimately this call belongs to the maintainers, not to me — I'm just flagging the tradeoff clearly.

Tip: You can customize Greptile's behavior for this repo with .greptile/rules.md and .greptile/config.json.