ワンクリックでManusで任意のスキルを実行

find-stellar-idea

スター26

フォーク3

更新日2026年6月11日 14:06

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.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

kaankacar

kaankacar/stellar-build

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

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:

Which Stellar domain pulls you? — payments, DeFi, stablecoins, RWA (real-world assets), DePIN, consumer apps, dev infrastructure, anchors, agentic payments, or something else.
What's your timeline? — weekend hack, one month, one quarter, longer.
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

このリポジトリの他の Skills

同じリポジトリ

bench-skills

kaankacar/stellar-build

Benchmark stellar-build skills to measure quality and the lift from optimization. Use when the user says "bench my skills", "bench-skills", "benchmark skills", "did optimization help", "measure my skills", "stellar-loop bench", or wants to quantify whether /optimize-skills actually improved things. Held-out eval prompts scored by an LLM judge, reproducible with fixed seeds. Fully local.

2026-06-2526

learning-loop

kaankacar/stellar-build

Explain and control the stellar-build learning loop — the system that improves your skills from how you use them. Use when the user says "learning loop", "how does the learning loop work", "what is the learning loop", "self-improving skills", "stellar-loop", "show my skill usage", "is tracing on", or wants an overview / status of the local trace-capture + optimize + bench cycle.

2026-06-2526

optimize-skills

kaankacar/stellar-build

Compile your local stellar-build usage traces into sharper skills. Use when the user says "optimize my skills", "optimize-skills", "improve my skills from usage", "learn from my traces", "stellar-loop optimize", or wants the learning loop to refine installed skills based on how they've actually been used. DSPy-style prompt optimization over the local trace store at ~/.stellar/traces — fully local, reversible.

2026-06-2526

reprompt

kaankacar/stellar-build

Rewrite a rough request into a sharp, structured prompt before acting on it. Use when the user says "reprompt this", "reprompt", "improve this prompt", "make this prompt better", "structure this request", or hands you a vague/underspecified ask you should sharpen first. Complements the automatic per-turn sharpener (the UserPromptSubmit hook) for explicit, heavier rewrites. Personalizes from ~/.stellar/profile.md when present.

2026-06-2326

elliot-dev

kaankacar/stellar-build

Senior software engineer for story execution and code implementation. Use when the user asks to talk to Elliot or requests the developer agent.

2026-06-1126

justin-analyst

kaankacar/stellar-build

Strategic business analyst and requirements expert. Use when the user asks to talk to Justin or requests the business analyst.

2026-06-1126

name

find-stellar-idea

description

What this skill does

When invoked, do these four things in order.

1. Load context

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:

Which Stellar domain pulls you? — payments, DeFi, stablecoins, RWA (real-world assets), DePIN, consumer apps, dev infrastructure, anchors, agentic payments, or something else.
What's your timeline? — weekend hack, one month, one quarter, longer.
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