Define the kit before building effects
Write one sentence describing the intended play pattern: mobile close-range pressure, patient space control, counter-focused defense, or another clear identity. Then assign jobs to the base slots. A practical starting structure is neutral tool, conversion or extender, mobility or defense, and finisher or area control.
Avoid giving every move high range, fast startup, safety, and large reward. Weaknesses create decisions. Decide how opponents can approach, interrupt, block, escape, or punish before opening the editor.
Build the base kit
Create and test one move at a time using the Skill Builder. After each move passes its solo matrix, combine two and look for unintended loops. Add the third and fourth only when earlier interactions are stable.
Give moves distinct silhouettes and sounds. A player should recognize the threat before the hitbox lands. Align visual reach with actual reach, and keep recovery visible. If two moves use similar animations for very different outcomes, revise one.
Check that the kit has a useful option when a flashy cooldown is unavailable. Basic attacks, movement, and block should remain part of the plan.
Special and awakening structure
The special should deepen the identity rather than erase its limits. It might change state, empower a planned move, or trade one resource for another. Show the state clearly and define how it ends. Test activation while moving, hit, reset, and interrupted.
Awakening should offer a meaningful temporary shift. Assign roles to its slots just as you did for the base kit. Avoid four full-screen finishers with no readable startup. Test whether opponents can disengage, defend, or punish a miss.
Ensure awakening cleanup restores the base kit correctly after timeout, death, reset, and reload.
Combo and counterplay audit
Build one short confirmed route, one wall route, and one escape-aware route. Then ask a tester to block randomly and use legitimate escape options. If the moveset loops stun without a decision, revise timing, knockback, cooldown, or recovery.
Play against the kit yourself. Note which animation you cannot read and which miss you cannot punish. Creator familiarity can hide unfair signals, so outside testers are essential.
Test against mobility, ranged control, and defensive standard characters. The moveset need not win every matchup, but it should create understandable choices.
Map and performance compatibility
Run the kit in open terrain, near walls, under low ceilings, on slopes, and around breakable objects. Movement skills must not cross intended boundaries. Effects and attached objects should clean up after interruption or reset.
Test several copies of the moveset in one server. A skill that performs well alone may cause severe load when repeated by multiple players. Remove redundant particles, sounds, and timeline events while preserving feedback.
Check touch and controller readability if the interface supports those devices. Do not assume a keyboard-oriented custom flow remains usable everywhere.
Save and share
Save a stable private version before publishing. Record creator name, item identifier, date, target game build, known limits, and whether the awakening is complete. Use the in-game Workshop flow and provide accurate screenshots.
Credit collaborators and permitted assets. If you remix an item, follow the original creator’s terms and link the source where the platform allows. Do not reupload another moveset under a new name.
Never distribute imports through executors, browser scripts, cookies, or password requests. Legitimate sharing remains inside the experience’s supported interface.
Post-update maintenance
After a Jujutsu Shenanigans builder update, load a duplicate of the published item. Check every timeline, condition, property, animation, hitbox, state change, cooldown, special, and awakening cleanup. Run one real match before overwriting the stable upload.
Write a changelog that distinguishes compatibility fixes from balance changes. If a system is broken by the update, mark the item temporarily incompatible instead of leaving users to discover it in a match.
Release checklist
The kit needs a clear identity, four nonredundant base roles, readable special, complete awakening state if advertised, honest hitboxes, counterplay, stable short routes, escape handling, map bounds, cleanup, group performance, reload persistence, metadata, and credit.
If any item remains untested, publish as a clearly labeled work in progress or keep it private. A smaller transparent release is more useful than a polished listing with hidden failure states.