Platform

How to Fork and Improve Prompts

Learn what forking means on fireflare, when to fork vs. create from scratch, how attribution works, and best practices for building on others' prompts while respecting their work.

How to Fork and Improve Prompts

Forking is one of fireflare's most powerful features. It lets you take any published prompt, create your own version, and share it — while automatically maintaining a link to the original. This guide explains when and how to fork effectively.

What Is Forking?

When you fork a prompt, you:

  1. Create a copy in your own account
  2. Are free to modify it however you like
  3. Automatically credit the original author with an attribution link
  4. Become part of that prompt's "lineage tree" — a visual history of how the prompt evolved

Forking is to prompts what forking is to open-source code: it acknowledges that good ideas build on each other, and it creates a transparent history of that evolution.

When to Fork

Fork when you want to:

Customize for your context. A great code review prompt written for Python needs adjustment for Rust. Fork it, adapt the language-specific instructions, and publish your version for the Rust community.

Improve quality. You found a prompt that almost works, but the output format isn't quite right. Fork it, fix the format instructions, and share the improved version.

Specialize a general prompt. Someone wrote a general "cold email" prompt. You want one specifically for developer tools. Fork it and add the domain-specific context.

Combine ideas. You love the structure of one prompt and the tone guidance from another. Fork the one you'll use as the base and incorporate elements from the other.

Experiment safely. You don't want to break a working prompt. Fork it to experiment with changes, then decide whether to publish your variant.

Don't fork when you should create from scratch:

  • Your changes would be so extensive that the original is unrecognizable
  • The original uses a completely different approach for the same task
  • You'd be creating confusion in the lineage tree without adding value

A good rule of thumb: if less than 50% of the original text survives in your version, consider starting fresh.

How to Fork on fireflare

  1. Open any prompt page
  2. Click the Fork button (below the prompt title, next to Like and Save)
  3. The prompt editor opens with the original text pre-loaded
  4. Make your changes
  5. Update the title to reflect your version (e.g., "Cold Email Prompt — Developer Tools Edition")
  6. Update the description to explain what you changed and why
  7. Add or adjust tags as appropriate
  8. Click Publish

Your fork is now live, attributed to you, with a visible link back to the original.

Attribution and Lineage

What Attribution Looks Like

Every forked prompt displays:

  • "Forked from [original title]" by [original author]
  • A clickable link to the original prompt
  • The fork count on the original prompt increases

The original author is notified when someone forks their prompt.

The Lineage Tree

Click View Lineage on any prompt to see its full fork history — the original, all forks, forks of forks, and so on. Popular prompts develop rich lineage trees with specialized variants for different tools, languages, industries, and use cases.

Being in a popular prompt's lineage tree is valuable for discovery — users browsing the original often explore related forks.

Writing a Great Fork Description

The description of your fork should clearly communicate:

  1. What you changed — be specific
  2. Why you changed it — what problem were you solving?
  3. Who benefits — who should use your version over the original?

Poor fork description:

"Improved version of the original prompt."

Good fork description:

"Forked from [original]. Modified for Rust development: replaced Python-specific instructions with Rust idioms, added instructions for handling lifetimes and ownership errors, and updated the output format to use Rust-style error messages. Best for: backend Rust developers using Claude or GPT-4."

Best Practices for Forking

Credit beyond attribution

If the original prompt significantly inspired your approach, say so in the description even if you changed most of the text. The community values intellectual honesty.

Communicate with the original author

Leave a comment on the original prompt explaining what you forked it for and what you changed. Authors appreciate knowing how their work is being used, and it often starts a productive conversation.

Keep forks focused

The best forks have a clear, specific purpose. A fork that changes everything for no clear reason creates confusion. A fork that adds support for a specific tool or use case adds genuine value.

Don't fork to spam

Forking a popular prompt with minimal changes just to get visibility on your profile is bad practice. The community and recommendation algorithm both deprioritize shallow forks.

Forking Private and Unlisted Prompts

  • Public prompts — anyone can fork
  • Unlisted prompts — only people with the direct link can fork
  • Private prompts — cannot be forked

If you can view a prompt, you can see whether forking is enabled. Authors can disable forking on any of their prompts in the prompt settings.

Building on a Fork Chain

Sometimes the best base for your fork isn't the original — it's an existing fork that already solved some of the problems you're working on. You can fork a fork. The lineage tree tracks the full ancestry chain, crediting everyone in the line.

Key Takeaways

  • Fork when you're building on an existing idea, not replacing it entirely
  • Attribution is automatic — the lineage tree is maintained by the platform
  • A good fork description explains what changed and why
  • Forks are most valuable when they specialize, improve quality, or extend to a new context
  • Engage with original authors — forking starts conversations
All Guides