AGENT SKILL

find-stellar-idea

Help users discover what to build on Stellar. Use when a user says "what should I build on Stellar", "Stellar app ideas", "I want to build on Stellar but don't know what", "Stellar startup ideas", "find me a Stellar project idea", "I'm new to Stellar and want to build something", or "what's hot on Stellar right now". Interviews user sharply, then proposes ranked ideas grounded in real ecosystem gaps from the LumenLoop 728-project database and current SCF funding patterns.

License 许可
AGPL-3.0
最近更新
2026-10-09
Stars
★ 0
Forks
0

01 前言 Front Matter

name
find-stellar-idea
description
Help users discover what to build on Stellar. Use when a user says "what should I build on Stellar", "Stellar app ideas", "I want to build on Stellar but don't know what", "Stellar startup ideas", "find me a Stellar project idea", "I'm new to Stellar and want to build something", or "what's hot on Stellar right now". Interviews user sharply, then proposes ranked ideas grounded in real ecosystem gaps from the LumenLoop 728-project database and current SCF funding patterns.

03 SKILL.md 正文

What this skill does

When invoked, do these four things in order.

1. Load context

Read both Stellar-specific data and broader crypto market signals. The combination matters: ideas that fit a Stellar ecosystem gap and align with broader investor thesis (a16z, YC, Alliance) are both ecosystem-coherent and fundable.

Stellar-specific:

  • ~/.claude/skills/data/lumenloop/projects.json — 728-project Stellar ecosystem catalog with categories, SCF funding history, GitHub links
  • ~/.claude/skills/data/electric-capital/stellar-repos.json — Stellar developer activity signal (~9000 repos). Use it to detect ecosystem velocity: count repos created or actively maintained in each category, identify orgs with multiple Stellar repos (likely serious builders), filter out bootcamp exercises (whitebelt, orangebelt, yellowbelt in the repo name) and student forks to get a clean signal of who's actually shipping. If the user picks a domain where velocity is high but LumenLoop catalog coverage is low, that's a "builders are here but undocumented" signal — strong place to enter.
  • ~/.claude/skills/data/lumenloop/scf/rounds.json — historical SCF funding patterns (categories funded, average grant size)

Broader crypto market signals:

  • ~/.claude/skills/data/ideas/a16z-big-ideas-2025.json — a16z's published "big ideas" thesis for 2025
  • ~/.claude/skills/data/ideas/a16z-state-of-crypto-2025.json — a16z's annual State of Crypto report
  • ~/.claude/skills/data/ideas/yc-requests-for-startups.json — YC's published Request for Startups list (what YC explicitly wants funded)
  • ~/.claude/skills/data/ideas/yc-crypto-companies.json — every YC-backed crypto company (competitive map + signal of what gets funded)
  • ~/.claude/skills/data/ideas/alliance-ideas.json — Alliance DAO's startup ideas

If any file is missing, proceed but note "(limited context — install fresh data with --update)".

2. Ask three sharp questions, one at a time

Wait for each answer before asking the next:

  1. Which Stellar domain pulls you? — payments, DeFi, stablecoins, RWA (real-world assets), DePIN, consumer apps, dev infrastructure, anchors, agentic payments, or something else.
  2. What's your timeline? — weekend hack, one month, one quarter, longer.
  3. What's your unfair advantage? — domain expertise, technical skill, distribution, network, capital. What do you have that most builders don't?

3. Propose three ranked ideas

For each idea, write:

  • One-line pitch. What it is, who it's for.
  • Why Stellar specifically. What Stellar capability (Soroban, anchors, low fees, native multi-currency, agentic payments, fast finality) makes this work better on Stellar than on another chain.
  • Ecosystem gap evidence. Cite from projects.json: what's already in this category and at what SCF funding levels, what's not.
  • Broader thesis fit. If the idea aligns with an a16z thesis, a YC RFS line item, or an Alliance DAO area, cite it. If it doesn't, say so plainly — Stellar-specific ideas without broader investor thesis can still be great, but the user should know.
  • Why it might fail. The single biggest risk.
  • First step. Smallest concrete thing they could do tomorrow.
  • SCF fit. Likely yes / no / maybe to receive SCF funding, based on recent round patterns.

Order: best fit for their constraints first; most ambitious last.

4. Close

End with: "Pick one to refine, or tell me what's missing and I'll regenerate. If you like one, I can route you to validate-stellar-idea or stellar-competitive-landscape next."

Constraints

  • Do not propose ideas requiring capital they didn't mention
  • Do not propose ideas outside their stated domain
  • Each idea must be specific enough to start tomorrow — not "build a social network"
  • If projects.json shows 5+ funded projects already doing this exact thing, either propose a clear differentiation angle or move on
  • If they pick "agentic payments" or "ZK proofs," lean into Stellar's recent capability investments — these are intentionally underbuilt and SCF is funding them heavily

04 同仓库更多 Skills

RomerTamayo
RomerTamayo/node-xchange

zk-proofs

Zero-knowledge proofs and privacy patterns on Stellar. Covers Groth16 verification in smart contracts via BLS12-381 host functions (CAP-0059, available), the BN254 + Poseidon proposals (CAP-0074/0075, status-sensitive), and concrete toolchain walkthroughs for Circom (on-chain verifiable today), Noir, and RISC Zero (attestation pattern until BN254 lands). Use when building privacy-preserving applications, ZK-verifier contracts, or wiring a proving toolchain to Stellar.

★ 0
RomerTamayo
RomerTamayo/node-xchange

tyler-architect

System architect and technical design leader. Use when the user asks to talk to Tyler or requests the architect.

★ 0
RomerTamayo
RomerTamayo/node-xchange

stellar-help

Analyzes current state and user query to answer BMad questions or recommend the next skill(s) to use. Use when user asks for help, bmad help, what to do next, or what to start with in BMad.

★ 0
RomerTamayo
RomerTamayo/node-xchange

stellar-competitive-landscape

Map the competitive landscape for a Stellar project idea. Use when a user says "who are my competitors on Stellar", "competitive analysis Stellar", "what already exists in this space on Stellar", "show me similar Stellar projects", "is anyone else building this on Stellar", "map the Stellar landscape for X" — or the Spanish/mixed-language equivalents, e.g. "cual es la competencia de X", "que tan saturado está este espacio", "que aspectos están menos explorados y la SDF/SCF están dispuestos a fondear", or "analiza la competencia de estos bounties". Also fires when a user (directly, or via a BMAD persona like justin-analyst) names a specific protocol/idea inline and asks about its competition, viability, or market whitespace — including "should we integrate [external protocol]" or "does anything like this already exist on Stellar" research, where the deliverable is the same landscape map applied to a build-vs-integrate decision. Queries the 728-project LumenLoop ecosystem database and Electric Capital developer activity to rank competitors by SCF funding history and repo activity.

★ 0
RomerTamayo
RomerTamayo/node-xchange

standards

Stellar standards, ecosystem, and reference. Covers SEPs (Stellar Ecosystem Proposals), CAPs (Core Advancement Proposals), and a quick map for picking the right standard for wallets, anchors, payments, deposits/withdrawals, federation, deep links, and KYC. Also bundles ecosystem references (DeFi protocols, dev tools, wallets, infra, community projects), curated documentation links, and MCP servers (live tools such as Raven). Use when you need to know which SEP applies, or want a starting point for ecosystem integrations, official docs, or live MCP tooling.

★ 0
RomerTamayo
RomerTamayo/node-xchange

smart-contracts

Stellar smart contract development (Rust, soroban-sdk). Entry point with project setup, contract anatomy, and build/deploy workflow, routing to three companion files in this directory — development.md (storage/TTL, authorization, cross-contract calls, tokens, events, errors, upgrades, fees, troubleshooting), testing.md (unit, fuzz, property, fork, mutation, integration), and security.md (vulnerability classes, checklists, tooling, audits). Use when writing, testing, reviewing, securing, debugging, or shipping Stellar smart contracts, including anything the user calls "Soroban" — Soroban contracts, soroban-sdk, Soroban auth/storage/TTL errors, SEP-41 tokens, or SAC integration from contract code.

★ 0