Magic or power system: costs and limits first
When to use it
Designing a power system by what it cannot do before what it can.
Fill in the variables
Assembled prompt
621The instruction exceeds 500 characters; the free run applies only the beginning. Copying applies the whole prompt.
Free runs use the fast model and return a short preview (about 300 words). Only the first ~1,000 words of manuscript are read.
How to use this prompt
- 1Fill in the variables
Enter your manuscript, characters or situation in the fields below. The example values are hints.
- 2Check the assembled prompt
The prompt is assembled below with placeholders filled. Edit any rule to fit your work.
- 3Copy it or run it
Copy it into the tool you already use, or run it in SparkLore for a short preview.
- 4Revise the result into your manuscript
The output is a draft. Follow the tips and rewrite half of it by hand.
How to get the most from it
- A stamina cost creates no tension. A memory cost makes the reader do arithmetic every time.
- Item 4 becomes the climax's solution. Glimpse it in chapter one and pay it off at the end.
Use it with
- WorldDesigning a status window that scares with words, not numbers
Choosing the status-window format for a system/dungeon story, without turning every screen into a stat table.
- WorldFind contradictions against the story bible
Cross-check a chapter against the bible. Past chapter thirty, run it weekly.
- DialogueHide exposition in dialogue (no 'as you know')
You must convey a world rule or past event without characters telling each other what they both know.
Use it in the studio with your story bible
Sign up and get full-length results with free credits.
Sign up free and continue