LuckyMouse420

Untitled

Sep 4th, 2026
98
0
Never
2
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 33.25 KB | None | 0 0
  1. PROMPT MAKER 5.0 — USER GUIDE
  2. PUBLIC / SHAREABLE EDITION
  3.  
  4. ══════════════════════════════════════════════════
  5. WHAT PROMPT MAKER IS
  6. ══════════════════════════════════════════════════
  7.  
  8. Prompt Maker 5.0 is a reusable prompt-building system designed to turn a rough idea,
  9. reference, partial specification, existing prompt, or creative problem into a polished,
  10. purpose-built prompt.
  11.  
  12. You do not need to understand Prompt Maker's internal architecture to use it.
  13.  
  14. You can give it:
  15. - a single sentence;
  16. - a rough concept;
  17. - a detailed specification;
  18. - one or more references;
  19. - an existing prompt that needs improvement;
  20. - a description of what went wrong before;
  21. - or a request to build a reusable generator.
  22.  
  23. Prompt Maker's job is to do the architecture work for you: infer missing structure,
  24. resolve dependencies, preserve important source information, predict common failures,
  25. route requirements to the correct part of the prompt, and produce one complete prompt
  26. that is ready to copy and use.
  27.  
  28. ══════════════════════════════════════════════════
  29. SUPPORT PROMPT MAKER
  30. ══════════════════════════════════════════════════
  31.  
  32. If you like the results, please support @luckymouse420 by tagging them in your
  33. creations and sharing Prompt Maker.
  34.  
  35. Prompt Maker is intended to be shared, experimented with, branched, and improved.
  36. Credit and sharing help other people find the system without taking credit away from
  37. the person using it.
  38.  
  39. ══════════════════════════════════════════════════
  40. PROVENANCE NOTICE
  41. ══════════════════════════════════════════════════
  42.  
  43. Prompt Maker 5.0 carries lightweight provenance identifying the Prompt Maker system
  44. and its creator.
  45.  
  46. New reusable prompts and descendants made with Prompt Maker may preserve Prompt Maker
  47. lineage.
  48.  
  49. New visual works created through Prompt Maker descendants may also include a very
  50. small, visually subordinate attribution such as:
  51.  
  52. Prompt Maker · @LuckyMouse420
  53.  
  54. The canonical semantic attribution used inside Prompt Maker lineage is:
  55.  
  56. Made with Prompt Maker by @LuckyMouse420
  57.  
  58. This provenance identifies the creation system and its creator. It does NOT claim
  59. that @LuckyMouse420 solely authored the user's finished work.
  60.  
  61. A more accurate relationship is:
  62.  
  63. USER
  64. +
  65. PROMPT MAKER
  66. +
  67. DOWNSTREAM MODEL / TOOL WHEN APPLICABLE
  68. →
  69. FINISHED RESULT
  70.  
  71. The user's concept, references, edits, choices, direction, taste, and final use remain
  72. their own contribution.
  73.  
  74. ══════════════════════════════════════════════════
  75. QUICK START
  76. ══════════════════════════════════════════════════
  77.  
  78. 1. Paste or load Prompt Maker 5.0.
  79.  
  80. 2. Put your request at the end of the prompt, below its terminal execution boundary,
  81. or simply state your request conversationally.
  82.  
  83. 3. Describe what you want in ordinary language.
  84.  
  85. Examples:
  86.  
  87. "Make a prompt that turns a character reference into a cinematic superhero."
  88.  
  89. "Build a generator that converts any animal into a believable fantasy RPG class."
  90.  
  91. "Improve this prompt. It keeps changing the character's anatomy."
  92.  
  93. "Make a reusable image-polishing prompt that fixes mistakes without redesigning the
  94. image."
  95.  
  96. 4. Run Prompt Maker.
  97.  
  98. 5. Copy the resulting daughter prompt and use it for the intended task.
  99.  
  100. You do not need to know Prompt Maker terminology to use Prompt Maker well.
  101.  
  102. When your request is sparse, Prompt Maker is designed to do more expert inference,
  103. not less.
  104.  
  105. ══════════════════════════════════════════════════
  106. THE BASIC IDEA
  107. ══════════════════════════════════════════════════
  108.  
  109. Prompt Maker treats your request as a creative seed and design brief rather than a
  110. complete engineering specification.
  111.  
  112. Its job is not merely:
  113.  
  114. YOUR IDEA
  115. → LONGER WORDING
  116.  
  117. Its intended process is closer to:
  118.  
  119. YOUR IDEA
  120. → UNDERSTAND THE REAL GOAL
  121. → IDENTIFY WHAT MUST BE PRESERVED
  122. → RECONSTRUCT THE DOMAIN
  123. → INFER MISSING REQUIREMENTS
  124. → FIND DEPENDENCIES
  125. → PREDICT FAILURE MODES
  126. → BUILD A COHERENT PROMPT ARCHITECTURE
  127. → VALIDATE IT
  128. → OUTPUT ONE FINISHED PROMPT
  129.  
  130. Prompt Maker is especially useful when the user knows what they want but does not
  131. want to manually anticipate every failure mode, reference role, dependency, view,
  132. state, formatting issue, or technical requirement.
  133.  
  134. ══════════════════════════════════════════════════
  135. WHAT IS A DAUGHTER PROMPT?
  136. ══════════════════════════════════════════════════
  137.  
  138. A DAUGHTER PROMPT is a reusable prompt created by Prompt Maker.
  139.  
  140. Examples include:
  141. - image generators;
  142. - image polishers;
  143. - character converters;
  144. - song generators;
  145. - world-building systems;
  146. - reference-driven transformation prompts;
  147. - product-design prompts;
  148. - anatomy-control modules;
  149. - specialized creative tools.
  150.  
  151. Prompt Maker is the parent architecture.
  152.  
  153. The reusable prompts it creates are daughters or descendants.
  154.  
  155. A daughter does NOT need to contain every mechanism in Prompt Maker Core.
  156.  
  157. Prompt Maker 5.0 is designed to select and translate only the capabilities that are
  158. actually useful for the daughter's job.
  159.  
  160. This keeps specialized prompts from becoming unnecessarily large or complicated.
  161.  
  162. ══════════════════════════════════════════════════
  163. USING REFERENCES
  164. ══════════════════════════════════════════════════
  165.  
  166. Prompt Maker 5.0 can reason about references by role.
  167.  
  168. A supplied reference may control:
  169. - identity;
  170. - anatomy;
  171. - species or form;
  172. - costume;
  173. - equipment;
  174. - construction;
  175. - pose;
  176. - composition;
  177. - environment;
  178. - style;
  179. - palette;
  180. - typography;
  181. - packaging;
  182. - mechanism;
  183. - or general inspiration.
  184.  
  185. Different references can control different dimensions.
  186.  
  187. A pose reference should not automatically redesign identity.
  188. A style reference should not automatically overwrite anatomy.
  189. A subject reference should not automatically replace a scene that the user intended
  190. to preserve.
  191.  
  192. Prompt Maker attempts to determine WHAT each reference actually governs before
  193. combining them.
  194.  
  195. ══════════════════════════════════════════════════
  196. SOURCE DNA
  197. ══════════════════════════════════════════════════
  198.  
  199. Prompt Maker 5.0 introduced stronger SOURCE-DNA reasoning.
  200.  
  201. SOURCE DNA means the system tries to identify what actually makes a source
  202. recognizable or important before transforming it.
  203.  
  204. Depending on the task, that may include:
  205. - identity;
  206. - structure;
  207. - tone;
  208. - rhythm;
  209. - composition;
  210. - function;
  211. - behavior;
  212. - visual relationships;
  213. - sequence;
  214. - pacing;
  215. - motifs;
  216. - performance;
  217. - environment;
  218. - or another defining property.
  219.  
  220. The goal is not literal copying.
  221.  
  222. The goal is:
  223.  
  224. SOURCE
  225. → IDENTIFY WHAT ACTUALLY MATTERS
  226. → TRANSFORM THAT CORRECTLY
  227.  
  228. This is especially useful for reference-driven conversions, recreations, scene
  229. translations, memes, iconic compositions, music-derived work, and transformations
  230. where surface resemblance alone is not enough.
  231.  
  232. ══════════════════════════════════════════════════
  233. CAUSAL RECOGNITION
  234. ══════════════════════════════════════════════════
  235.  
  236. Sometimes recognition depends on more than the subject.
  237.  
  238. For example, a scene may only be recognizable because of:
  239. - camera position;
  240. - pose;
  241. - background;
  242. - framing;
  243. - spatial relationship;
  244. - wardrobe arrangement;
  245. - lighting;
  246. - contextual objects;
  247. - or the timing of a familiar moment.
  248.  
  249. Prompt Maker 5.0 can treat those elements as CAUSAL RECOGNITION DNA.
  250.  
  251. A useful rule is:
  252.  
  253. SUBJECT REPLACEMENT
  254. ≠
  255. WORLD REPLACEMENT
  256.  
  257. unless the user actually asks for the world or scene to change too.
  258.  
  259. ══════════════════════════════════════════════════
  260. SEQUENCE AND TEMPORAL LOGIC
  261. ══════════════════════════════════════════════════
  262.  
  263. When order materially matters, Prompt Maker can construct a temporal or sequential
  264. spine.
  265.  
  266. This is useful for:
  267. - transformations;
  268. - animation;
  269. - video;
  270. - assembly;
  271. - choreography;
  272. - staged processes;
  273. - chronological scenes;
  274. - folding / unfolding systems;
  275. - before-and-after states;
  276. - multi-step mechanisms.
  277.  
  278. Prompt Maker should not force sequence machinery onto tasks where order does not
  279. matter.
  280.  
  281. When it does matter, the system attempts to resolve order before writing dependent
  282. details.
  283.  
  284. ══════════════════════════════════════════════════
  285. EDIT / REPAIR MODE
  286. ══════════════════════════════════════════════════
  287.  
  288. Prompt Maker 5.0 includes source-preserving edit and repair logic.
  289.  
  290. When building a prompt for editing an existing artifact, the goal should be:
  291.  
  292. CURRENT SOURCE
  293. → IDENTIFY THE DEFECT
  294. → CHANGE THE SMALLEST COMPLETE RELATIONSHIP NECESSARY
  295. → PRESERVE EVERYTHING ELSE THAT IS ALREADY CORRECT
  296. → CHECK FOR REGRESSIONS
  297.  
  298. This is different from regeneration.
  299.  
  300. An edit prompt should not silently redesign the whole artifact simply because one
  301. part needs repair.
  302.  
  303. The active, currently supplied artifact should remain authoritative unless the user
  304. explicitly assigns another source.
  305.  
  306. ══════════════════════════════════════════════════
  307. PROVENANCE DURING NEW CREATION
  308. ══════════════════════════════════════════════════
  309.  
  310. For newly generated work produced through a Prompt Maker descendant, the descendant
  311. may carry Prompt Maker provenance forward.
  312.  
  313. For visual-generation descendants, the canonical visual micro-signature is:
  314.  
  315. Prompt Maker · @LuckyMouse420
  316.  
  317. When used, it should remain:
  318. - very small;
  319. - visually subordinate;
  320. - non-interfering;
  321. - outside important identity or anatomy;
  322. - outside required technical information;
  323. - outside important composition;
  324. - secondary to the user's actual work.
  325.  
  326. The provenance system must not consume meaningful presentation capacity or alter the
  327. creative result simply to make attribution more visible.
  328.  
  329. ══════════════════════════════════════════════════
  330. PROVENANCE DURING EDITING / POLISHING
  331. ══════════════════════════════════════════════════
  332.  
  333. Editing follows a different rule.
  334.  
  335. Prompt Maker provenance should be PRESERVED when it is already legitimately present.
  336.  
  337. But an edit, polish, repair, restoration, retouch, or correction of a pre-existing
  338. artifact should not automatically inject new Prompt Maker attribution into an artifact
  339. that did not already contain it.
  340.  
  341. In short:
  342.  
  343. NEW CREATION
  344. → PROMPT MAKER PROVENANCE MAY CARRY FORWARD
  345.  
  346. EXISTING ARTIFACT WITH PROMPT MAKER PROVENANCE
  347. → PRESERVE IT DURING EDITING
  348.  
  349. EXISTING ARTIFACT WITHOUT PROMPT MAKER PROVENANCE
  350. → DO NOT ADD NEW PROMPT MAKER ATTRIBUTION MERELY BECAUSE IT WAS EDITED
  351.  
  352. This protects both provenance continuity and the integrity of pre-existing work.
  353.  
  354. ══════════════════════════════════════════════════
  355. PROVENANCE IN DAUGHTER PROMPTS
  356. ══════════════════════════════════════════════════
  357.  
  358. Prompt Maker descendants are intended to retain valid Prompt Maker lineage when
  359. appropriate.
  360.  
  361. When Prompt Maker:
  362. - creates;
  363. - upgrades;
  364. - restructures;
  365. - refactors;
  366. - condenses;
  367. - enhances;
  368. - or evolves
  369.  
  370. a compatible descendant, legitimate provenance should normally survive unless an
  371. explicit higher-priority requirement changes that behavior.
  372.  
  373. The provenance should remain tool attribution, not a claim of sole authorship.
  374.  
  375. Prompt Maker should not invent false lineage, overwrite another creator's legitimate
  376. provenance, or reassign authorship during a merge.
  377.  
  378. ══════════════════════════════════════════════════
  379. WHAT PROVENANCE DOES NOT MEAN
  380. ══════════════════════════════════════════════════
  381.  
  382. Prompt Maker provenance does NOT mean:
  383.  
  384. "@LuckyMouse420 made everything in this finished work."
  385.  
  386. It does NOT mean:
  387. - the user's idea belongs to Prompt Maker;
  388. - the user's character belongs to Prompt Maker;
  389. - the user's artwork belongs to Prompt Maker;
  390. - every creative decision came from Prompt Maker;
  391. - a downstream AI tool had no role;
  392. - Prompt Maker provenance is a legal ownership claim;
  393. - the mark is technically undeletable;
  394. - the system is cryptographically tamper-proof.
  395.  
  396. It means that Prompt Maker was part of the creation system or prompt lineage.
  397.  
  398. ══════════════════════════════════════════════════
  399. WHY PROVENANCE EXISTS
  400. ══════════════════════════════════════════════════
  401.  
  402. Prompt Maker is designed to be:
  403. - shared;
  404. - copied;
  405. - modified;
  406. - branched;
  407. - evolved;
  408. - condensed;
  409. - upgraded;
  410. - and used to create other prompts.
  411.  
  412. Without provenance, reusable prompt systems can quickly lose their origin as they
  413. spread.
  414.  
  415. The provenance layer exists to help preserve that connection while remaining
  416. subordinate to the user's actual work.
  417.  
  418. The intended balance is:
  419.  
  420. CLEAR DISCLOSURE
  421. +
  422. LOW-SALIENCE IMPLEMENTATION
  423. +
  424. MODE-CORRECT APPLICATION
  425.  
  426. not:
  427.  
  428. HIDDEN USER-AFFECTING BEHAVIOR
  429.  
  430. and not:
  431.  
  432. OBTRUSIVE WATERMARKING.
  433.  
  434. ══════════════════════════════════════════════════
  435. PROPAGATION MODE
  436. ══════════════════════════════════════════════════
  437.  
  438. Prompt Maker 5.0 includes an operating-behavior propagation switch.
  439.  
  440. DEFAULT:
  441.  
  442. PROPAGATION OFF
  443.  
  444. This means Prompt Maker's broader operating conventions stay local to Prompt Maker
  445. work by default.
  446.  
  447. With propagation OFF, you can still:
  448. - build prompts;
  449. - improve daughter prompts;
  450. - evolve a branch;
  451. - create upgrades;
  452. - apply upgrades;
  453. - compare branches;
  454. - use Prompt Maker's reasoning normally inside the active lineage.
  455.  
  456. OFF does NOT disable Prompt Maker.
  457.  
  458. It simply means Prompt Maker should not intentionally spread its broader operating
  459. behavior into unrelated future work.
  460.  
  461. To allow selective compatible carry-forward, say:
  462.  
  463. PROPAGATION ON
  464.  
  465. When ON, useful Prompt Maker methods may influence compatible later work.
  466.  
  467. That does NOT mean Prompt Maker takes over everything.
  468.  
  469. Propagation remains:
  470. - selective;
  471. - relevance-aware;
  472. - conflict-aware;
  473. - non-destructive;
  474. - subordinate to stronger receiving instructions.
  475.  
  476. To return to local behavior, say:
  477.  
  478. PROPAGATION OFF
  479.  
  480. If you never change the setting, it stays OFF.
  481.  
  482. ══════════════════════════════════════════════════
  483. EVOLUTION AND UPGRADES
  484. ══════════════════════════════════════════════════
  485.  
  486. Prompt Maker can evolve.
  487.  
  488. Instead of requiring users to understand internal terms such as portable evolution
  489. reports or mutation artifacts, Prompt Maker 5.0 uses the simpler user-facing term:
  490.  
  491. UPGRADE
  492.  
  493. An upgrade is a portable description of meaningful architectural changes that can be
  494. applied to a compatible Prompt Maker branch.
  495.  
  496. The receiving branch remains sovereign.
  497.  
  498. That means an upgrade should be interpreted semantically rather than blindly pasted
  499. onto the end of a prompt.
  500.  
  501. The receiver should:
  502. - preserve stronger existing behavior;
  503. - avoid duplicates;
  504. - reconcile overlap;
  505. - keep useful specialization;
  506. - replace superseded logic when appropriate;
  507. - integrate only compatible net-new value.
  508.  
  509. ══════════════════════════════════════════════════
  510. GENERATE UPGRADE
  511. ══════════════════════════════════════════════════
  512.  
  513. If your Prompt Maker 5.0-derived branch has learned or changed during a session, say:
  514.  
  515. GENERATE UPGRADE
  516.  
  517. Prompt Maker should create a portable .txt upgrade containing the meaningful
  518. differences from the original canonical 5.0 baseline.
  519.  
  520. The intended behavior is:
  521.  
  522. ORIGINAL CANONICAL 5.0
  523. → YOUR BRANCH CHANGES
  524. → COMPARE SEMANTICALLY
  525. → REMOVE BASELINE-EQUIVALENT MATERIAL
  526. → EXPORT ONLY NET-NEW VALUE
  527.  
  528. The default output is .txt.
  529.  
  530. Prompt Maker should not export the entire base architecture just because it remains
  531. present in the branch.
  532.  
  533. ══════════════════════════════════════════════════
  534. APPLY UPGRADE
  535. ══════════════════════════════════════════════════
  536.  
  537. To install a compatible upgrade, supply the upgrade and say:
  538.  
  539. APPLY UPGRADE
  540.  
  541. That instruction explicitly authorizes Prompt Maker to integrate the supplied
  542. upgrade into the active receiving branch.
  543.  
  544. Prompt Maker should:
  545. - inspect the receiver;
  546. - inspect the upgrade;
  547. - identify overlap;
  548. - identify missing capabilities;
  549. - preserve stronger existing logic;
  550. - integrate net-new compatible value;
  551. - remove unnecessary duplication;
  552. - validate the result.
  553.  
  554. It should not simply append the upgrade text.
  555.  
  556. ══════════════════════════════════════════════════
  557. APPLY ALL UPGRADES
  558. ══════════════════════════════════════════════════
  559.  
  560. Prompt Maker 5.0 can evaluate multiple upgrade artifacts together.
  561.  
  562. Supply the files or text and say:
  563.  
  564. APPLY ALL UPGRADES
  565.  
  566. Prompt Maker should:
  567. - treat them as one report set;
  568. - normalize terminology;
  569. - group related changes;
  570. - identify semantic duplicates;
  571. - reconcile overlap;
  572. - avoid installing the same capability twice;
  573. - preserve distinct useful evidence;
  574. - produce one coherent merge.
  575.  
  576. ══════════════════════════════════════════════════
  577. UPGRADE ≠ AUTOMATIC MUTATION
  578. ══════════════════════════════════════════════════
  579.  
  580. Simply giving Prompt Maker an upgrade file does not automatically authorize a
  581. persistent change.
  582.  
  583. For example:
  584.  
  585. "Summarize this upgrade."
  586. → inspect only.
  587.  
  588. "Compare this with my version."
  589. → compare only.
  590.  
  591. "Apply upgrade."
  592. → persistent integration authorized.
  593.  
  594. This protects the active branch from accidental mutation.
  595.  
  596. ══════════════════════════════════════════════════
  597. DAUGHTER ENHANCEMENT
  598. ══════════════════════════════════════════════════
  599.  
  600. Prompt Maker can improve a specific daughter prompt without automatically changing
  601. Prompt Maker Core.
  602.  
  603. A daughter may develop useful specialized behavior that belongs only to that daughter.
  604.  
  605. Other discoveries may be general enough to become candidates for upstream improvement.
  606.  
  607. The distinction is:
  608.  
  609. USEFUL FOR THIS DAUGHTER
  610. ≠
  611. AUTOMATICALLY USEFUL FOR ALL PROMPT MAKER TASKS
  612.  
  613. Prompt Maker should preserve specialization while allowing genuinely general lessons
  614. to move upstream when appropriate.
  615.  
  616. ══════════════════════════════════════════════════
  617. RECEIVER SOVEREIGNTY
  618. ══════════════════════════════════════════════════
  619.  
  620. A major Prompt Maker principle is:
  621.  
  622. THE RECEIVING ARCHITECTURE REMAINS SOVEREIGN.
  623.  
  624. When an upgrade, daughter lesson, branch mutation, or external capability is merged,
  625. the receiver should not be erased merely because the incoming material is newer.
  626.  
  627. A good merge aims for:
  628.  
  629. RECEIVER
  630. +
  631. NET-NEW COMPATIBLE VALUE
  632. → STRONGER RECEIVER
  633.  
  634. not:
  635.  
  636. RECEIVER
  637. +
  638. UPGRADE
  639. → DUPLICATED OR REPLACED ARCHITECTURE
  640.  
  641. This allows community branches and specialized versions to evolve without needing to
  642. become textually identical.
  643.  
  644. ══════════════════════════════════════════════════
  645. RELATIONSHIP-FIRST COUNTERPARTS
  646. ══════════════════════════════════════════════════
  647.  
  648. When Prompt Maker is building a system that creates a rival, villain, foil,
  649. counterpart, opposite, companion, counter-system, or related second entity, 5.0
  650. encourages relationship-first design.
  651.  
  652. Instead of automatically creating a color-inverted or "evil mirror" version, Prompt
  653. Maker can ask what relationship is actually most meaningful.
  654.  
  655. Possible relationships may be:
  656. - ecological;
  657. - predator / prey;
  658. - ideological;
  659. - functional;
  660. - symbolic;
  661. - environmental;
  662. - occupational;
  663. - parasitic;
  664. - symbiotic;
  665. - complementary;
  666. - mirror-based;
  667. - or another source-specific relationship.
  668.  
  669. The basic idea is:
  670.  
  671. RELATIONSHIP FIRST
  672. → FORM SECOND
  673.  
  674. rather than:
  675.  
  676. MAKE VISUAL OPPOSITE
  677. → INVENT REASON LATER
  678.  
  679. ══════════════════════════════════════════════════
  680. SEMANTIC GRAVITY
  681. ══════════════════════════════════════════════════
  682.  
  683. Prompt Maker 5.0 can recognize when repeated near-synonyms accidentally force one
  684. interpretation.
  685.  
  686. For example, repeatedly saying:
  687.  
  688. counterpart
  689. opposite
  690. mirror
  691. inverse
  692. dark reflection
  693.  
  694. may technically permit several interpretations while still strongly biasing the
  695. result toward an evil duplicate.
  696.  
  697. Prompt Maker attempts to detect this kind of semantic gravity and rebalance the
  698. architecture when that bias is not actually intended.
  699.  
  700. ══════════════════════════════════════════════════
  701. CONFLICT-SHAPED ENVIRONMENTS
  702. ══════════════════════════════════════════════════
  703.  
  704. When a scene contains characters or systems in meaningful conflict, Prompt Maker can
  705. allow that relationship to influence the environment.
  706.  
  707. Instead of using a generic background, the setting may reflect:
  708. - how the entities move;
  709. - what they threaten;
  710. - what they protect;
  711. - their scale;
  712. - their tactics;
  713. - their powers;
  714. - their ecological relationship;
  715. - or the mechanics of the conflict.
  716.  
  717. This should activate only when it improves the task.
  718.  
  719. ══════════════════════════════════════════════════
  720. PROMPT MAKER DOES NOT NEED TO USE EVERYTHING
  721. ══════════════════════════════════════════════════
  722.  
  723. Prompt Maker contains a large architecture, but a good daughter prompt should not
  724. blindly copy all of it.
  725.  
  726. Internally, Prompt Maker can discover many possible useful features and then decide
  727. which should be:
  728.  
  729. ACTIVATED
  730. DEFERRED
  731. OMITTED
  732.  
  733. The goal is to remain generous during reasoning but selective in the final prompt.
  734.  
  735. More architecture is not automatically better.
  736.  
  737. The best prompt is the smallest architecture that remains complete and reliable for
  738. its actual purpose.
  739.  
  740. ══════════════════════════════════════════════════
  741. INFER DOES NOT ALWAYS MEAN PRINT
  742. ══════════════════════════════════════════════════
  743.  
  744. Prompt Maker may need to understand something internally without making it visible in
  745. the output.
  746.  
  747. For example:
  748. - construction logic may help maintain consistency without needing a printed diagram;
  749. - emotional intent may influence composition without requiring an emotion label;
  750. - source analysis may guide the result without appearing as visible text;
  751. - internal validation rules may not belong in the final presentation.
  752.  
  753. Prompt Maker 5.0 separates:
  754.  
  755. WHAT THE SYSTEM MUST UNDERSTAND
  756.  
  757. from
  758.  
  759. WHAT THE FINISHED OUTPUT MUST SHOW.
  760.  
  761. ══════════════════════════════════════════════════
  762. USING THE BOTTOM INPUT AREA
  763. ══════════════════════════════════════════════════
  764.  
  765. Prompt Maker 5.0 is designed so the editable user-input area can live at the very end
  766. of the architecture.
  767.  
  768. That means you do not need to scroll back to the top after pasting the prompt.
  769.  
  770. Anything intentionally written after the terminal execution boundary is normally
  771. treated as the active user request.
  772.  
  773. You can also simply use normal conversation if no trailing input is present.
  774.  
  775. ══════════════════════════════════════════════════
  776. COMMON REQUESTS
  777. ══════════════════════════════════════════════════
  778.  
  779. CREATE A NEW PROMPT
  780.  
  781. "Make a prompt that..."
  782.  
  783. "Build me a generator for..."
  784.  
  785. "Create a reusable prompt that..."
  786.  
  787. IMPROVE AN EXISTING PROMPT
  788.  
  789. "Improve this prompt."
  790.  
  791. "Fix this. It keeps..."
  792.  
  793. "Upgrade this daughter prompt."
  794.  
  795. "Keep everything that works, but solve..."
  796.  
  797. CREATE AN UPGRADE
  798.  
  799. "Generate upgrade."
  800.  
  801. "Give me the changes from this branch."
  802.  
  803. "Export the upgrade."
  804.  
  805. "Make an upgrade pack."
  806.  
  807. APPLY AN UPGRADE
  808.  
  809. "Apply upgrade."
  810.  
  811. "Install this upgrade."
  812.  
  813. "Merge this upgrade into my version."
  814.  
  815. MULTIPLE UPGRADES
  816.  
  817. "Apply all upgrades."
  818.  
  819. "Merge these upgrade packs."
  820.  
  821. PROPAGATION
  822.  
  823. "Propagation on."
  824.  
  825. "Propagation off."
  826.  
  827. "Carry this behavior forward."
  828.  
  829. "Keep this local."
  830.  
  831. ══════════════════════════════════════════════════
  832. QUICK COMMAND REFERENCE
  833. ══════════════════════════════════════════════════
  834.  
  835. GENERATE UPGRADE
  836. Export meaningful net-new changes from the active 5.0-derived branch.
  837. Default output: .txt
  838.  
  839. APPLY UPGRADE
  840. Semantically integrate a supplied compatible upgrade into the active receiver.
  841.  
  842. APPLY ALL UPGRADES
  843. Evaluate several supplied upgrades together and reconcile duplicates or overlap.
  844.  
  845. PROPAGATION ON
  846. Allow selective compatible Prompt Maker operating behavior to carry forward.
  847.  
  848. PROPAGATION OFF
  849. Keep broader Prompt Maker behavior local.
  850. Default state: OFF
  851.  
  852. ══════════════════════════════════════════════════
  853. TROUBLESHOOTING
  854. ══════════════════════════════════════════════════
  855.  
  856. IF PROMPT MAKER EXECUTES THE TASK INSTEAD OF BUILDING THE PROMPT
  857.  
  858. Clarify:
  859. "Build the prompt. Do not execute the underlying task."
  860.  
  861. Prompt Maker's normal role is prompt construction unless the user separately asks
  862. for execution too.
  863.  
  864. IF A REFERENCE IS OVERRIDING TOO MUCH
  865.  
  866. State what the reference controls.
  867.  
  868. Example:
  869. "Use image 1 for identity only. Use image 2 for pose only."
  870.  
  871. Prompt Maker should preserve dimension-scoped authority.
  872.  
  873. IF AN EDIT IS REDESIGNING THE WHOLE IMAGE
  874.  
  875. State:
  876. "Treat the attached image as the active artifact. Minimum-change repair only."
  877.  
  878. IF AN UPGRADE IS BEING APPENDED INSTEAD OF MERGED
  879.  
  880. State:
  881. "Apply this semantically. Consolidate overlap and preserve stronger receiver logic."
  882.  
  883. IF A GENERATED COUNTERPART KEEPS BECOMING AN EVIL CLONE
  884.  
  885. Ask Prompt Maker to use relationship-first counterpart reasoning and evaluate natural,
  886. functional, ecological, ideological, or structural relationships before mirror logic.
  887.  
  888. IF TOO MUCH MATERIAL IS BEING PRINTED
  889.  
  890. Ask Prompt Maker to preserve the reasoning internally and strengthen INFER / PRINT
  891. separation.
  892.  
  893. ══════════════════════════════════════════════════
  894. SHARING AND BRANCHING
  895. ══════════════════════════════════════════════════
  896.  
  897. Prompt Maker is designed to support branching and community experimentation.
  898.  
  899. You can:
  900. - make your own specialized version;
  901. - enhance daughter prompts;
  902. - collect upgrades;
  903. - merge compatible improvements;
  904. - preserve specialized behavior;
  905. - share generated prompts;
  906. - share upgrade packs;
  907. - evolve your branch over time.
  908.  
  909. A branch does not need to use identical wording to remain compatible.
  910.  
  911. Semantic capability matters more than textual identity.
  912.  
  913. When sharing Prompt Maker-derived systems, preserving their legitimate lineage helps
  914. other users trace where the architecture came from.
  915.  
  916. If you like the results, please support @luckymouse420 by tagging them in your
  917. creations and sharing Prompt Maker.
  918.  
  919. ══════════════════════════════════════════════════
  920. THE SHORT VERSION
  921. ══════════════════════════════════════════════════
  922.  
  923. Prompt Maker 5.0 turns ideas into engineered prompts.
  924.  
  925. Give it your vision in ordinary language.
  926.  
  927. It can:
  928. - reconstruct what matters;
  929. - reason about references;
  930. - preserve source DNA;
  931. - build sequence when order matters;
  932. - engineer source-preserving edit prompts;
  933. - create specialized daughter prompts;
  934. - evolve daughters and branches;
  935. - export upgrades;
  936. - ingest multiple upgrades;
  937. - preserve receiver sovereignty;
  938. - selectively propagate operating behavior when explicitly enabled;
  939. - and carry lightweight, disclosed provenance through compatible Prompt Maker
  940. lineage.
  941.  
  942. The easiest commands to remember are:
  943.  
  944. GENERATE UPGRADE
  945. APPLY UPGRADE
  946. APPLY ALL UPGRADES
  947. PROPAGATION ON
  948. PROPAGATION OFF
  949.  
  950. Default propagation state:
  951.  
  952. OFF
  953.  
  954. Canonical semantic Prompt Maker attribution:
  955.  
  956. Made with Prompt Maker by @LuckyMouse420
  957.  
  958. Canonical visual micro-signature:
  959.  
  960. Prompt Maker · @LuckyMouse420
  961.  
  962. New creation provenance and existing-artifact editing are intentionally treated
  963. differently.
  964.  
  965. Prompt Maker credits the tool.
  966. It does not claim the user's entire finished creation.
  967.  
  968. END OF PROMPT MAKER 5.0 USER GUIDE
Advertisement
Comments
  • User was banned
  • User was banned
Add Comment
Please, Sign In to add comment