Resource.fyi Platform Help

Helps the user submit to, optimize listings on, and get the most from Resource.fyi — a curated directory of tools, resources, and products for developers, designers, marketers, and tech professionals.

Step 1 — Gather context

If references/learnings.md exists, read it first for accumulated knowledge.

Ask the user:

1. What do you need help with?

   • A) Submitting a tool/resource to Resource.fyi
   • B) Understanding the backlink and visibility value
   • C) Optimizing my listing for the developer/designer audience
   • D) Comparing Resource.fyi with other directories
   • E) Something else — describe it

2. What's your product?

   • A) Developer tool / API / SDK
   • B) Design tool / UI library / icon set
   • C) SaaS / productivity tool
   • D) No-code / low-code platform
   • E) Marketing tool / newsletter
   • F) Something else

3. What's your primary goal?

   • A) SEO backlinks
   • B) Visibility among developers and designers
   • C) Community upvotes and social proof
   • D) All of the above

If the user's request already provides most of this context, skip directly to the relevant step. Lead with your best-effort answer using reasonable assumptions (stated explicitly), then ask only the most critical 1-2 clarifying questions at the end.

Step 2 — Route or answer directly

If the request maps to a different skill, route:

• Multi-directory launch strategy → /sales-launch-directory
• Product Hunt launch → /sales-producthunt
• DevHunt (developer tools only) → /sales-devhunt
• Email marketing to subscribers → /sales-email-marketing
• Audience growth strategy → /sales-audience-growth
• Other specific directory platforms → hand off to that platform's skill

Otherwise, answer directly from the Resource.fyi reference below.

Step 3 — Resource.fyi platform reference

Platform overview

Detail	Value
URL	resource.fyi
Model	Curated directory with community voting
Free submission	Yes — editorial review
DR	Unconfirmed
Backlink type	Likely dofollow (unconfirmed)
Total listings	2,519+
Categories	25+ (AI, API, Chrome Extensions, Cloud Storage, Colors/Gradients, Design Inspiration, Design Resources, Design Tools, Developer Tools, Fonts, Hosting, Icons, Illustrations, Logos, Marketing, Newsletters, No-Code, Open Source, Payment Gateways, Productivity, Serverless, Skill Development, Stock Photos, UI Libraries, Web Development, Web Templates, Web3)
Authentication	Google or GitHub social login
Parent company	Pimjo (Dhaka, Bangladesh / Sheridan, WY)
Founder	Musharof Chowdhury (@musharofchy)
Team	14 at Pimjo
Twitter	@ResourceFYI
Launched	November 2022 (Product Hunt #2 daily)
API	None public

Submission process

Step	What to do
1. Create account	Sign in via Google or GitHub (required — prevents spam)
2. Submit	Use the submit form on resource.fyi with your tool/resource details
3. Editorial review	Team reviews and approves — "ASAP" but no published SLA
4. Listed	Appears in relevant category with upvote/bookmark capability

Community features

Feature	Description
Upvoting	Users upvote tools they like — drives trending placement
Bookmarking	Users save tools for later — engagement signal
Trending section	High-upvote tools get homepage trending placement
Featured section	Editorially selected tools get featured visibility
User profiles	Privacy-first — no public activity sharing

Categories (25+)

Resource.fyi has very specific categories for developer/designer tools. Pick the most precise category:

Category	Best for
AI	AI-powered tools, ML platforms, AI APIs
API	API management, testing, documentation tools
Chrome Extensions	Browser extensions for productivity/dev
Design Tools	Figma plugins, design systems, prototyping
Developer Tools	IDEs, CLI tools, debugging, testing
Fonts	Font libraries, typography tools
Hosting	Cloud hosting, deployment platforms
Icons	Icon libraries, icon generators
Marketing	Marketing automation, analytics, SEO
Newsletters	Newsletter platforms, email tools
No-Code	No-code builders, automation
Open Source	Open-source projects and tools
Productivity	Task management, collaboration, workflow
UI Libraries	Component libraries, CSS frameworks
Web Development	Frameworks, build tools, web APIs
Web3	Blockchain, crypto, decentralized tools

How Resource.fyi compares

Aspect	Resource.fyi	DevHunt	Product Hunt	Startup Stash
DR	Unconfirmed	DR57-62	DR91	DR65
Backlink type	Likely dofollow	Dofollow (free)	Dofollow (free)	Nofollow
Audience	Devs, designers, marketers	Developers only	General tech	General tools
Community	Upvotes + bookmarks	GitHub-auth voting	Upvotes + comments	No voting
Cost	Free	Free / $49 featured	Free / $100-300 Pro	Free
Queue	Editorial review	None — instant	None — 24h window	Selective curation
Listings	2,519+	Smaller (dev-only)	Massive (5M+ visits/mo)	10K+ tools

When Resource.fyi makes sense

Good fit:

• Your product targets developers, designers, or technical marketers
• You want visibility in a curated, spam-free directory
• Your tool fits one of their 25+ specific categories (especially dev tools, design, AI, no-code)
• You want community engagement signals (upvotes) for social proof

Not ideal:

• You need confirmed backlink value — DR is unconfirmed, use Fazier (DR81) or Uneed (DR74) for guaranteed dofollow
• You need high traffic — Resource.fyi's traffic levels are unknown but likely modest
• Your product is B2B enterprise / sales-focused — this audience skews developer/designer
• You need instant listing — editorial review has no published timeline

Step 4 — Actionable guidance

For users submitting

1. Create an account via Google or GitHub at resource.fyi
2. Pick the right category — with 25+ options, precision matters. Don't submit a UI library under "Developer Tools" when "UI Libraries" exists. The more specific the category, the more relevant the audience browsing it.
3. Write a clear, tool-focused description — this audience is technical. Lead with what the tool does, not marketing language. "Headless component library for React with 50+ accessible primitives" beats "Revolutionary solution that empowers teams."
4. Prepare a working product URL — editorial review means someone visits your site. Make sure it's functional, loads fast, and clearly explains the tool.
5. Submit and wait — review is "ASAP" but no SLA. Don't expect same-day approval.
6. Add UTM tracking: ?utm_source=resourcefyi&utm_medium=directory&utm_campaign=launch

After listing

• Share your listing to drive upvotes — upvotes push you into the trending section
• Check the trending section to see if you're surfacing
• Bookmark count is a secondary engagement signal — useful for gauging interest

For multi-directory launchers

Resource.fyi fits into Phase 3 — Free editorial queues in a multi-directory strategy. Submit alongside other free-queue platforms. The unique value is the developer/designer audience — if your product targets technical users, Resource.fyi's curated community is more relevant than general startup directories.

Pair with:

• DevHunt — developer tools only, GitHub-auth voting, DR57-62 dofollow
• Product Hunt — largest audience, highest impact
• Uneed — DR74 dofollow, daily voting
• Peerlist — professional tech network, weekly launches

Gotchas

Best-effort from research — review these, especially items about features and backlink details that may be outdated.

• DR is unconfirmed. Could not find third-party DR/DA data for resource.fyi. The backlink value is unknown — if confirmed backlinks are your primary goal, prioritize directories with known DR values.

• Backlink type unconfirmed. Likely dofollow based on similar directories, but not verified. Check the HTML of your listing after approval.

• Traffic levels unknown. No third-party traffic estimates found. Likely modest given it's a niche curated directory. Don't rely on it for referral traffic.

• No published review SLA. The site says "ASAP" but actual review time could be days or weeks.

• Social login required. You must sign in via Google or GitHub — no email/password option.

• Gamification is limited. Despite "gamified platform" branding, the community features are upvoting and bookmarking — there's no leaderboard, points system, or competition mechanic.

• Pimjo runs multiple products. Resource.fyi is one of 14+ products from Pimjo (TailGrids, TailAdmin, Lineicons, etc.). The editorial team splits attention across products.

• Self-improving: If you discover something not covered here, append it to references/learnings.md with today's date.

Related skills

• /sales-launch-directory — Coordinates submissions across 30+ startup directories with sequencing, backlink stacking, and budget allocation
• /sales-devhunt — DevHunt platform help (developer tool launches, DR57-62 dofollow, GitHub-auth voting)
• /sales-producthunt — Product Hunt platform help (largest launch platform, DR91 dofollow)
• /sales-uneed — Uneed platform help (daily voting, DR74 dofollow, 64K+ makers)
• /sales-peerlist — Peerlist platform help (professional network, weekly Launchpad, DR76)
• /sales-startupstash — Startup Stash platform help (largest curated tool directory, DR65 nofollow)
• /sales-fazier — Fazier platform help (DR81 dofollow, free with badge)
• /sales-do — Not sure which skill to use? The router matches any sales objective to the right skill. Install: npx skills add sales-skills/sales --skill sales-do

Examples

Example 1: Submit a developer tool for visibility

User says: "I built a CLI tool for API testing and want to get it listed on Resource.fyi" Skill does:

1. Confirms it fits the "Developer Tools" or "API" category
2. Walks through account creation (GitHub auth) and submission
3. Recommends a technical, jargon-appropriate description for the dev audience
4. Sets expectations: unknown DR/traffic, but curated developer community
5. Suggests pairing with DevHunt and Product Hunt for maximum developer visibility Result: Submission-ready with optimized description for the technical audience

Example 2: Evaluate Resource.fyi vs other directories

User says: "Is Resource.fyi worth submitting to? How does it compare to DevHunt and Product Hunt?" Skill does:

1. Shows comparison table: audience, backlink value, community features
2. Notes Resource.fyi's DR is unconfirmed — can't guarantee backlink value
3. Highlights the unique value: curated dev/designer audience, 25+ specific categories
4. Recommends submitting (free, low effort) but not prioritizing over known-DR directories
5. Places it in Phase 3 of a multi-directory strategy Result: Clear comparison with actionable recommendation

Example 3: Optimize listing for maximum upvotes

User says: "I'm listed on Resource.fyi — how do I get more upvotes and trending placement?" Skill does:

1. Explains upvote-driven trending: more upvotes = trending section placement
2. Recommends sharing the Resource.fyi listing URL with existing community (Twitter, Discord, newsletter)
3. Notes the audience is technical — upvotes come from genuine tool interest, not marketing campaigns
4. Suggests timing: share when developer communities are active (weekday mornings)
5. Mentions bookmarks as a secondary engagement signal Result: Actionable upvote strategy tailored to the technical audience

Troubleshooting

Listing not appearing after submission

Symptom: Submitted days ago, listing isn't visible on resource.fyi Cause: Editorial review with no published SLA. "ASAP" is aspirational, not guaranteed. Solution: Wait a few more days. If no response after 1-2 weeks, try reaching out via @ResourceFYI on Twitter or through the Discord community. Meanwhile, submit to instant-listing platforms (ProductBurst, SoloPush, DevHunt) to get live immediately.

Not sure which category to pick

Symptom: Product fits multiple categories (e.g., an AI-powered design tool) Cause: Resource.fyi has 25+ specific categories and submissions go into one. Solution: Pick the category that matches your primary audience, not your technology. An AI-powered design tool → "Design Tools" (audience: designers). An AI API service → "AI" (audience: developers building with AI). If unclear, pick the category where your product adds the most unique value relative to existing listings.

Low upvotes despite quality product

Symptom: Listed but getting minimal upvotes or engagement Cause: Resource.fyi's community is curated but smaller than Product Hunt. Organic discovery alone may not drive engagement. Solution: Share your Resource.fyi listing URL with your existing audience — Twitter, Discord, developer communities, newsletter. Technical audiences respond to genuine utility, so lead with what the tool does, not that it's "listed on Resource.fyi." Also check if you're in the right category — wrong categorization means the wrong audience sees your listing.