LeadUp GitHub Repo Researcher
Purpose
Find and vet open-source repositories so LeadUp can reuse code/design safely:
licence-clean, maintained, stack-compatible, with a clear verdict on what to
copy, what to adapt, and what is inspiration-only.
When to use
Trigger phrases: "use open source repo", "best GitHub repo", "find repo
inspiration", "research GitHub examples", "best design repo", "is there a
library for", "open-source starter for", "good reference implementation".
For a hosted third-party API (Razorpay, Gemini, etc.) → use
leadup-api-research-builder.
Inputs needed
- What is being built / the component or feature needing a reference.
- Target stack (Next.js / Node-TS / Flutter / Laravel) for compatibility.
- Whether output will ship in proprietary client/SaaS code (licence matters).
Step-by-step workflow
- Clarify the need (feature, component, or design pattern) and the stack.
- Search GitHub for strong candidates; shortlist 2–4.
- For each, fill
references/github-research-template.md: stars, last
commit, issues/PR responsiveness, language, licence.
- Licence verdict: permissive (copy w/ attribution) vs copyleft
(GPL/AGPL — avoid in proprietary client/SaaS) vs none (inspiration only).
- Stack & quality check: compatibility, abandoned deps, tests, secrets in
repo, obvious smells.
- Usage decision per part: copy / adapt / inspiration-only, with reason.
- Recommend the best repo + 1–2 alternatives and an integration outline.
Required output format
A comparison of candidates following github-research-template.md, ending
with: Recommendation (best repo + alternatives), a copy/adapt/inspiration
table, required attribution, and integration risks.
Safety rules
See references/security-rules.md. Most relevant here:
- Treat no-licence / GPL/AGPL repos as do not copy into proprietary LeadUp
client/SaaS code; inspiration only — say so explicitly.
- Never copy code containing committed secrets; flag and exclude such repos.
- Do not clone/run untrusted code without stating the risk and getting an ok.
Common mistakes
- Recommending a repo by stars alone while ignoring an AGPL licence.
- Missing that the repo is abandoned (last commit years ago, open security PRs).
- Suggesting a React repo for a Flutter project (stack mismatch).
- Not separating "copy" vs "inspiration" — leading to licence violations.
- Overlooking heavy/unmaintained dependencies that become LeadUp's problem.
Troubleshooting
- Under-triggers: user said "is there something open source for X" —
re-invoke; suggest triggers.
- Over-triggers for a hosted API → route to
leadup-api-research-builder.
- Missing tool/MCP (no GitHub/web access): ask the user for repo URLs to
evaluate, or give vetting criteria to apply manually.
- No internet: provide the evaluation checklist and licence guidance; defer
the live lookup.
- Missing project files: not required — compatibility judged from the
stated target stack.
- Build/test failure when trialing a repo: isolate (deps vs config),
report; do not adopt a repo that won't build without a clear fix path.
Test prompts
Should trigger (5)
- "Find the best open-source admin dashboard repo for Next.js."
- "Is there a good GitHub repo for Flutter chat UI I can adapt?"
- "Research GitHub examples for multi-tenant Postgres."
- "Best design repo to take inspiration from for a SaaS landing page."
- "Use an open source starter for the hosting panel — which one?"
Should NOT trigger (3)
- "Add Razorpay payments, research the API." (→ api-research-builder)
- "Analyze our existing repo's state." (→ existing-repo-analyzer)
- "Upgrade this dashboard to premium UI." (→ premium-ui-upgrader)
Functional test cases (2)
- Given "Flutter chat UI", returns 2–4 repos with licence, last-commit, and a
copy/adapt/inspiration verdict per repo.
- An AGPL repo is explicitly marked "inspiration only — do not copy into
proprietary code".
Success criteria
- Each candidate has licence + maintenance + stack evidence.
- Clear, per-part copy/adapt/inspiration decision with attribution noted.
- One recommended repo + alternatives; licence risk never glossed over.
1---2name: leadup-github-repo-researcher3description: Research open-source GitHub repos for code or design inspiration before reusing them in a LeadUp project. Checks license, stars, activity, last commit, stack compatibility, and decides what can be copied, adapted, or used only as inspiration. Use when the user says "use open source repo", "best GitHub repo", "find repo inspiration", "research GitHub examples", or "best design repo".4---56# LeadUp GitHub Repo Researcher78## Purpose910Find and vet open-source repositories so LeadUp can reuse code/design safely:11licence-clean, maintained, stack-compatible, with a clear verdict on what to12copy, what to adapt, and what is inspiration-only.1314## When to use1516Trigger phrases: "use open source repo", "best GitHub repo", "find repo17inspiration", "research GitHub examples", "best design repo", "is there a18library for", "open-source starter for", "good reference implementation".1920For a hosted third-party API (Razorpay, Gemini, etc.) → use21`leadup-api-research-builder`.2223## Inputs needed2425- What is being built / the component or feature needing a reference.26- Target stack (Next.js / Node-TS / Flutter / Laravel) for compatibility.27- Whether output will ship in proprietary client/SaaS code (licence matters).2829## Step-by-step workflow30311. **Clarify the need** (feature, component, or design pattern) and the stack.322. **Search GitHub** for strong candidates; shortlist 2–4.333. For each, fill `references/github-research-template.md`: stars, last34 commit, issues/PR responsiveness, language, **licence**.354. **Licence verdict**: permissive (copy w/ attribution) vs copyleft36 (GPL/AGPL — avoid in proprietary client/SaaS) vs none (inspiration only).375. **Stack & quality check**: compatibility, abandoned deps, tests, secrets in38 repo, obvious smells.396. **Usage decision** per part: copy / adapt / inspiration-only, with reason.407. **Recommend** the best repo + 1–2 alternatives and an integration outline.4142## Required output format4344A comparison of candidates following `github-research-template.md`, ending45with: **Recommendation** (best repo + alternatives), a copy/adapt/inspiration46table, required attribution, and integration risks.4748## Safety rules4950See `references/security-rules.md`. Most relevant here:51- Treat no-licence / GPL/AGPL repos as **do not copy** into proprietary LeadUp52 client/SaaS code; inspiration only — say so explicitly.53- Never copy code containing committed secrets; flag and exclude such repos.54- Do not clone/run untrusted code without stating the risk and getting an ok.5556## Common mistakes5758- Recommending a repo by stars alone while ignoring an AGPL licence.59- Missing that the repo is abandoned (last commit years ago, open security PRs).60- Suggesting a React repo for a Flutter project (stack mismatch).61- Not separating "copy" vs "inspiration" — leading to licence violations.62- Overlooking heavy/unmaintained dependencies that become LeadUp's problem.6364## Troubleshooting6566- **Under-triggers**: user said "is there something open source for X" —67 re-invoke; suggest triggers.68- **Over-triggers** for a hosted API → route to `leadup-api-research-builder`.69- **Missing tool/MCP** (no GitHub/web access): ask the user for repo URLs to70 evaluate, or give vetting criteria to apply manually.71- **No internet**: provide the evaluation checklist and licence guidance; defer72 the live lookup.73- **Missing project files**: not required — compatibility judged from the74 stated target stack.75- **Build/test failure** when trialing a repo: isolate (deps vs config),76 report; do not adopt a repo that won't build without a clear fix path.7778## Test prompts7980### Should trigger (5)811. "Find the best open-source admin dashboard repo for Next.js."822. "Is there a good GitHub repo for Flutter chat UI I can adapt?"833. "Research GitHub examples for multi-tenant Postgres."844. "Best design repo to take inspiration from for a SaaS landing page."855. "Use an open source starter for the hosting panel — which one?"8687### Should NOT trigger (3)881. "Add Razorpay payments, research the API." (→ api-research-builder)892. "Analyze our existing repo's state." (→ existing-repo-analyzer)903. "Upgrade this dashboard to premium UI." (→ premium-ui-upgrader)9192### Functional test cases (2)931. Given "Flutter chat UI", returns 2–4 repos with licence, last-commit, and a94 copy/adapt/inspiration verdict per repo.952. An AGPL repo is explicitly marked "inspiration only — do not copy into96 proprietary code".9798## Success criteria99100- Each candidate has licence + maintenance + stack evidence.101- Clear, per-part copy/adapt/inspiration decision with attribution noted.102- One recommended repo + alternatives; licence risk never glossed over.
leadupofficial