At what level should you reuse a trope?
Moving from concrete to abstract, distinguish wording and details, distinctive combinations of events, dramatic functions, and emotional needs. The earlier layers are closer to the work’s particular expression; the later ones are easier to transfer.
For example, “an underestimated underdog uses professional expertise to solve a problem everyone else failed at” describes a function. The profession, props, relationships among witnesses, solution steps and dialogue still need fresh design. Replacing a sword sect with a school and renaming the characters while keeping the same event sequence is only a surface imitation.
Five steps from close reading to original design
- Record the function you can directly observe. What does the reader know and expect on entering the passage?
- State the dramatic problem. Does the passage need to change information, power, a relationship, a route or a cost?
- Extract possible mechanisms. Examples include mistaken identity, a loophole or forced cooperation. Record the conditions they need and the signs that they will fail.
- List what not to copy. Include prose style, sentences, distinctive plot sequences, distinctive worldbuilding and particular combinations of relationships.
- Rebuild in another genre. Use entirely different characters, circumstances and causes to express the same function. If you cannot explain it without the reference work, the abstraction is not yet sufficient.
For recording observations while reading, see how to deconstruct fiction. This page takes those observations forward into original design.
Original redesign: an underestimated ferry scheduler checks tickets
The abstract function is an underestimated person using established expertise to resolve a checkable problem, gaining limited participation and provoking resistance. This original ferry scene comes from no real reference work.
Returning scheduler Gu Yao is dismissed as a student who draws tables. Lists repeatedly appear over capacity. The manager considers extra sailings, but established constraints limit them. Gu compares two ticket lists: one number and payment appear twice. The passenger confirms buying one ticket; the seller checks the original entry.
That proves this duplicate, not the cause of every excess. The manager lets Gu join the present list review without granting control of the whole ferry. The checked list replaces the old version and passengers receive confirmed departures. Losing record control, the seller hides another old ledger, creating further resistance.
Carry over recognition, proof and counteraction as functions. Rebuild prose, props, relationships and events. The new scene needs independent causality; renamed characters do not supply it.
Complete original scene: check one duplicate and gain a limited role
Keep Gu's ferry example in close third person. Expertise earns limited recognition; the original lists, sales records and authority support the function without mapping onto another work's fixed action sequence.
The manager looked at the two lists and proposed another sailing. Gu asked, “Can you add one today?”
“These are all the available departures.” He paused. “First reduce the excess.”
She brought two rows with the same number together. “These record one payment.”
“Two points submitted them,” the seller said. “They needn't be one passenger.”
Gu did not delete either yet. She asked the passenger to produce the ticket and confirm how many they had bought. One. At her request they identified the payment. The seller retrieved the original entry, matched the transaction and acknowledged the duplicate.
“That one can go,” the manager said.
“One. The other excess still needs checking.” Gu left the remaining entries in place.
The manager let her join the current list review while retaining departure approval. Gu and the seller checked this round's list against original records and submitted it for confirmation. The manager replaced the old list and had passengers receive their confirmed departures.
Gu took the review sheet. Her name had been added; the manager still signed the sailing arrangement.
The gain is participation in this review. Passenger and original entry support one duplicate, not every excess or command of the ferry. The original seller-lead's concealment of another ledger belongs later; Gu cannot know an unseen act through this viewpoint.
Review the redesign through three questions: why is the expertise valid, who can recognize its result, and how is participation enacted? Preserve those functions without turning ferry materials or sentences into the next book's fixed template. Native analysis records replaceable elements and what must not be copied; writing methods then dramatize this original causality.
Different mechanisms can serve the same emotional need
For readers who want an underestimated person to gain recognition, public proof is one option. Others include letting results accumulate over time, a key person privately changing their view, or a protagonist rejecting recognition while still achieving the goal. Each choice has different consequences: public proof is forceful but becomes repetitive; accumulated results are steadier but must remain visible beforehand; rejecting recognition emphasizes character but cannot replace a real outcome.
Compare at least one alternative mechanism, then choose the one that fits the character and genre. A reference supplies possibilities, not proof that the current story works.
Common forms of imitation and how to repair them
| Imitation | Repair |
|---|---|
| Rename characters but retain the event sequence | Return to the dramatic problem and redesign the causal chain |
| Assemble famous scenes from several works | Take only the few mechanisms needed for the current problem |
| Imitate the prose’s feel and sentence patterns | Record the function, then rewrite in this story’s voice |
| Treat the reference as proof of quality | Independently check the current characters’ motives, causality and payoff |
| Reverse a trope merely to subvert it | Check that the reversal still serves the intended reader’s central emotional need |
| Reduce the lesson to “add conflict” | Specify how the mechanism changes information, power, relationships or costs |
FAQ
What are some common web-fiction tropes?
Think of them through emotional functions: proving oneself after being underestimated, gaining a scarce opportunity, revealing an identity, moving from hostility to cooperation, or recovering something lost. For actual writing, identify the conditions and visible effects rather than simply applying a label.
Is combining two tropes enough to make something original?
A combination is only a starting point. Both mechanisms must interact through the same character goal and causal chain. If each plays out separately, the result still feels like a collection of borrowed story beats.
Do it with the skill
In Claude Code, ask: “Use /story-long-write to abstract my reference into the reader’s state, the dramatic problem, possible mechanisms, visible effects and failure conditions only. List what must not be copied, then generate original candidates in an entirely different genre. Do not draft prose.” In Codex, use $story-long-write.
Read the method: Abstract functions, replaceable roles and prohibited copying · Dramatize established action, response and result · Original-scene voice and facts