Write AI Prompts for a Job-System RPG

Write AI prompts for a job-system RPG that connect switchable roles and cross-class abilities to working gameplay. Move from a first brief to a playable prototype.

Seele Editorial TeamUpdated November 17, 2026

Define a few jobs with different purposes

A job system becomes hard to balance when each role has many skills, passive bonuses, and switching rules before the player understands what a job changes. Begin with three jobs that solve different problems, then write down when a character can change roles and what progress remains. A staged prompt sequence is easier to inspect than a single request for a complete RPG with a large class tree.

This fictional example uses one adventurer preparing to stabilize three wardstones before dusk. The Vanguard can brace against an incoming physical hit and clear a blocked path. The Arcanist can channel a rune. The Warden can mend or protect an ally. Each job has one active job action in the first milestone. No extra jobs, random loot, or job-specific story branches are needed to see whether the role choice affects the quest.

A vanguard, arcanist, and warden prepare together beside a camp map showing three wardstones.
Concept art for a fictional three-job RPG, not a game screenshot.

Give every job one contribution that is easy to recognize. A Vanguard’s brace reduces the next physical hit by one. An Arcanist’s channel stabilizes one rune. A Warden’s mend restores one health or adds a ward to one ally. These effects are intentionally narrow. The Vanguard does not reduce every kind of damage, the Arcanist does not solve every puzzle, and the Warden does not heal the entire party unless a rule says so.

Keep the first quest compact: three wardstones along one mountain pass, one physical obstacle, one rune interaction, and one moment where an ally may need support. A job should affect an action or a risk, not just change the character portrait. Ask the builder to state the required role or effect at each wardstone and what alternate route remains available if the player arrives with a different job.

Set job switching and progression rules

State when a character may change jobs. In this example, switching is allowed only at the safe camp before entering the quest. It costs no currency and cannot happen during combat or while a wardstone interaction is resolving. If a player attempts to switch outside camp, reject the request without changing the active job, job rank, health, or learned abilities.

Separate character progression from the active role. Each job tracks its own rank and experience. Completing a successful mission while a job is active grants one experience point to that job. Two points unlock rank 2. Job rank and learned abilities persist after the character switches to another job. This makes experimenting with a different role possible without erasing earlier progress.

{
  "activeJob": "warden",
  "jobRanks": {"vanguard": 1, "arcanist": 2, "warden": 1},
  "jobExperience": {"vanguard": 0, "arcanist": 0, "warden": 0},
  "learnedAbilities": ["arcanist_spark"],
  "inheritedAbilitySlot": "arcanist_spark"
}

The example starts with the Arcanist at rank 2 from two earlier fictional missions while the Warden is active. That lets the sample quest demonstrate a cross-job ability without pretending the current quest has already been played. The rank and prior experience are sample setup data, not evidence of a real campaign.

An adventurer chooses one glowing inherited rune at a safe camp before setting out toward a wardstone.
Mechanism concept: choose one inherited skill at a safe camp before the quest begins.

Limit cross-job abilities to one clear slot

Cross-job skills can blur job identity if a character carries every ability from every role. Use one inherited-ability slot. At rank 2, a job grants one learned ability: the Vanguard’s Brace, the Arcanist’s Spark, or the Warden’s Mend. The player may equip one learned ability in the inherited slot. This grants that action only; it does not grant the source job’s full action set, stats, or progression bonuses.

Keep the active job action and inherited skill separate in the character record. If the Arcanist is active and Spark is equipped as an inherited ability, the two actions cannot occupy the same slot or trigger as one combined effect. If the player switches to Vanguard, the active action becomes Brace, while the selected inherited ability remains equipped if it is still valid. Define any exception explicitly instead of letting a builder infer that every skill persists in combat.

Ask for replacement behavior. Equipping a different learned skill replaces the current inherited skill; it does not add a second slot. An ability cannot be equipped before it is learned. Switching jobs at camp does not reset learned abilities. These constraints make cross-job customization meaningful without removing the role choice.

Trace the wardstone quest under different jobs

Ask for one expected route under each active job. The Vanguard braces before a stone guardian’s strike and clears a fallen beam that blocks the first wardstone. The Arcanist channels the rune at the second stone. The Warden reaches an injured companion near the third stone and restores one health or applies one ward. Each action should update a named quest state so the player can see which wardstones are stable.

For a cross-job case, set the Warden as active and equip the learned Arcanist Spark in the inherited slot. The character can use the Warden’s Mend and Spark as distinct actions. The prompt should prevent the Spark from duplicating the Arcanist’s entire action set. If it is an attack, name its target and cost; if it is an interaction, name the state it changes.

SetupExpected actionState to record
Vanguard activeBrace before the guardian hit; clear the fallen beamPhysical damage reduced once; first stone reachable
Arcanist activeChannel the second wardstone runeRune state changes from unstable to stable
Warden activeMend or ward an ally near the third stoneHealth or ward changes by one; third stone interaction remains available
Warden active, Spark inheritedUse one learned cross-job actionOnly Spark is inherited; no full Vanguard or Warden action set is granted
A vanguard, arcanist, and warden stabilize a glowing wardstone together in a mountain pass.
Outcome concept for a fictional quest plan, not a tested result.

This is a paper trace, not gameplay evidence. The prompts are unrun drafts, and the package contains no playable build or test result. When you generate a prototype, compare expected and observed job state separately: active job, job rank, learned abilities, inherited slot, health, and wardstone flags.

Turn the rules into prototype checks

Build the system in layers. First add the three job records and one quest interaction per job. Then implement camp-only switching. Add job experience and rank persistence next, followed by the inherited-ability slot. Do not add a fourth job or passive skill tree until switching, learning, and ability replacement behave consistently.

  • Check that only one job is active at a time.
  • Reject job switches outside camp without changing character state.
  • Confirm each job action affects only its named target or condition.
  • Grant one job experience point only after a successful mission with that job active.
  • Unlock the inherited ability at rank 2 and keep job rank after switching.
  • Allow exactly one learned ability in the inherited slot and replace it cleanly.
  • Verify an inherited ability does not grant the source job’s other actions or passive effects.
  • Confirm each wardstone flag changes only when its required interaction completes.

If the active job and inherited slot both show the same action, clarify the duplicate rule. If switching resets rank, repeat that progression belongs to each job record and persists between jobs. If the system allows a mid-combat switch, restate the camp boundary and make the invalid action leave all state unchanged.

SEELE’s AI RPG Maker overview provides general context for defining an RPG goal, scene, quest objective, and consequential choice. It does not document these job-switching or cross-job rules. Treat the product page as general planning context and verify any generated behavior in the builder you choose.

FAQ

What should a job-system RPG prompt define first?

Define the available jobs, when a character can switch, which stats or actions each job changes, and what progress persists after switching.

How do cross-job abilities work in an RPG?

Specify how an ability is learned, whether it occupies a limited slot, and which effects remain tied to the current job. Keep inherited abilities distinct from full job access.

Should job changes be allowed during combat?

That is a design choice. State the allowed location and timing, whether combat pauses, and how current-job effects update. A safe camp is a simple first-prototype rule.

How can I balance several RPG jobs?

Start with a few roles that solve different problems, then hand-trace the same encounter under each job. Compare options and costs without claiming balance from an untested paper example.

Were these job-system RPG prompts tested in a playable build?

No. The jobs, abilities, and quest are fictional planning material. The prompts are unrun drafts and no playable build or test results are included.

SEELE AI

Turn this guide into a playable build.

Start with a focused brief, then iterate in the Seele AI Workspace.

Start creating