Sharkitten has eight recorded level-15 branches. Their elements and passives suggest different team jobs, but the maintained records do not specify the additional requirements for selecting each branch. Use this comparison to decide what you want to investigate in your own game before committing resources.
Editorial reviewed
Understand what Sharkitten already does
Sharkitten is Normal, with Life Force granting 1 SP when it takes skill damage. Its Meow Punch has a recorded cost of 4 and 60 Power, and the written damage benefit grows with the user’s SP up to a stated limit. This suggests a resource-sensitive attack decision. It does not mean you should take every hit willingly; surviving the damage is still necessary to use the gained resource.
Charge Up is its one recorded learnable skill. It spends 4 to increase Power for the next eligible skill by 40, and the preparation expires on departure. A preparation-and-attack plan therefore needs time to stay in and resources for both steps. The original form already offers a specific comparison between immediate action and setup; evolution should be considered against the new team job you want, rather than assumed to improve every aspect at once.
What the level-15 connections establish
The recorded family connects Sharkitten to Rainkat, Psykat, Sharkat, Leafkat, Fierikat, Jolkat, Aerikat and Petrokat at level 15. Every connection also carries an additional-conditions note. That establishes the listed branch relationships and recorded level, but it does not establish which item, menu, material or other action selects a branch.
Before choosing, open the branch’s current detail page and compare its trait and signature. Most branches share the signature name Element Resonance, but a shared name does not prove identical behavior. Sharkat is a useful example of that distinction. Confirm the actual descriptions in your game and the branch-selection requirements there; this guide does not supply an unverified evolution procedure.
Rainkat and Leafkat need different target states
Rainkat is Water. Rain Curtain reduces damage taken by allied Lumi with Wet while Rainkat remains on the team and is not defeated, with an additional Water-team component. The important first question is whether your plan actually keeps the relevant allies Wet. A Water roster alone does not substitute for that condition, and the record should not be turned into unconditional team mitigation.
Leafkat is Grass. Sprout gives allies a critical-rate benefit when attacking Leeched targets, again with a team-element component. Here the dependency is on the enemy’s condition rather than an ally’s Wet state. Consider whether you already have a reliable way to apply Leeched. If not, selecting the branch also creates a setup requirement that must be included in your team plan.
Fierikat and Jolkat support different resource loops
Fierikat is Fire. Fan the Flames connects allied healing to gaining or applying Burn while the passive remains active. That can fit a Burn-oriented lineup, but it does not erase the costs or risks of the skills that create Burn. Some Fire actions also apply Burn to the user, so read both sides of the effect before treating every application as a purely beneficial event.
Jolkat is Electric. Volt Absorption supplies extra SP when allies attack Paralyzed targets while Jolkat remains on the team and is not defeated. The maintained effect records 0.1 extra SP; do not silently round that into a whole point. This branch makes more sense as a conditional resource support option when your lineup can create and keep the relevant target state, rather than as a stand-alone promise of effortless energy.
Petrokat and Aerikat reward different switching plans
Petrokat is Earth. Sacred Earth protects field allies from critical attacks when they have a positive Defense Level, while Petrokat remains on the team and is not defeated. Positive Defense Level is the enabling condition. Consider who supplies it and whether your plan can retain it. The passive does not say that every ally becomes protected simply because Petrokat appears in the roster.
Aerikat is Flying. Tailwind reduces enemy buffs and stat boosts on allied entry and reduces user debuffs on departure while its team condition holds. This suggests a lineup that can use switching events deliberately. Compare that plan with the resources and opportunities needed for the handoff. Do not assume that an unrelated defeat event or every forced transition is identical to a departure rule when the current record does not settle the timing.
Psykat and Sharkat preserve different safety nets
Psykat is Psychic. Dreamy records a limited battle trigger involving an ally falling below half HP, healing and an enemy sleep effect, with a Psychic-team component. It is a conditional safety net, not repeatable healing every time HP changes. Check whether your strategy depends on a once-per-battle resource and what happens after that opportunity has been consumed.
Sharkat stays Normal and retains Life Force. Its Element Resonance description links damage to the user’s SP with a different stated limit from Sharkitten’s Meow Punch. This makes it important to compare behavior rather than only the new form’s element. A branch that preserves a familiar resource dependency may be easier to reason about, but the same survival and expenditure questions remain.
Compare signature rules and ranges together
The elemental branches record Element Resonance at cost 5 and base Power 75, with Power increasing when allied creatures use skills of the relevant type. That introduces a team-history condition. Merely owning several creatures of the same element does not prove that they have taken the skill actions counted by the signature. Track the recorded trigger rather than treating the enhanced Power as its opening value.
Ranges add a different comparison: Leafkat has the higher recorded Attack ceiling than several balanced branches, Fierikat emphasizes HP, and Petrokat emphasizes Defense. These are configuration profiles, not complete battle rankings. Two intervals can overlap even when one ceiling is higher. Use the profile as one consideration alongside the passive condition and skill choices, without inventing a universal best branch.
Write down the dependency you are willing to maintain
A practical shortlist starts with the missing job. If your team already supplies Paralyzed, investigate Jolkat’s resource support; if it maintains positive Defense Levels, investigate Petrokat’s protection condition. If you need something else, compare the relevant branch directly. This is a conditional investigation order, not a guarantee that one branch is optimal or currently available on every server.
Before spending resources, confirm the branch requirements in the current game, compare the exact skill descriptions and decide what your fallback is when the passive condition fails. Keep the existing form if the key requirement remains unclear rather than inventing a procedure from the diagram. A useful evolution decision explains both the benefit you expect and the condition your team must create to obtain it.