sales-resourcefyi
Resource.fyi platform help — curated tools and resources directory for developers, designers, and marketers with 2,500+ listings across 25+ categories (AI, API, Design, Dev Tools, Marketing, No-Code, Web3). Covers free submission process (editorial review, social auth via Google/GitHub), community features (upvoting, bookmarking, trending), listing optimization for developer/designer audience, and category selection. Use when your dev tool needs more visibility with developers and designers, your Resource.fyi listing isn't getting traction, or you want to reach a technical audience through a curated directory. Do NOT use for multi-directory launch strategy (use /sales-launch-directory). Do NOT use for Product Hunt launches (use /sales-producthunt).
What this skill does
# 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
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.