Strangely enough, I found myself enjoying the prologue much more than the first chapter. It wasn't because of the actual events taking place in both chapters (with the prologue obviously being more energetic) but how you structured each one. In the prologue, you described when it was necessary and appropriate; thus the flow of text seemed more natural. In your first chapter, you kept doing stuff like this:
A small blue four-legged Pokémon with a short trunk dashed towards a tall, brown-haired teenager.
and worse off this:
She had raven-black hair that extended down to her waist, and eyes that were normally hazel but seemed to change color every once in a while. Sporting a brown coat and well-kept denim jeans, she walked in on her white shoes with neon green laces.
that slowed down the pacing of your story. It stopped the action of the plot. In general, your prologue used the description as a fluid motion that described as well as pushing the action forward. Your first chapter, on the other hand, was very stop-go-stop-go that it was kind of distracting.
Besides this, the actual sequence of action seemed very listy, like you had planned a list of what you wanted Carson to do
- Carson is training Ellie
- Carson goes home
- Carson gets greeted by Blaze
- Carson finds a note on the fridge
and converted it into prose form without trying to blend the action together. It doesn't really help that you often had one sentence per paragraph either. It made the read rather choppy, unlike your prologue where one piece of action swiftly moved into another one without having an awkward pause to describe something. A lot of your chapter honestly felt like filler:
He went back up and finished the sweet, fruity Oran juice. Then he played foosball by himself just for kicks. It was actually sort of fun, and this way he never need lose to his father, as he did most commonly, or hear his sister whine that she “never got a chance” to beat Carson with her Sentret (She always made him take Aipom).
Again, I point back to your "listy" action sequences. "He drank this. Then he did that. It was fun."
Anyway ... I know you weren't trying to make your chapter long, and perhaps describing this particular scene might have a point, but in its current state, it's just ... well, what's the point of telling me this? Any insertion of personality/thought from Carson is just blunt (again, the entire "describe something then execute it in action" thing I said earlier) and doesn't really indicate that Carson is bored, or Carson is enjoying himself. It's boring in the sense that it's written rather boringly, unfortunately. The description of your prologue seemed to have a point; the description in your first chapter sounded like filler and had no point other than to describe. Description can be used to emphasize emotions, speed up/slow down a scene, and so much more.
I guess my entire point of my repetitive rambling is to take whatever you did in your prologue, which is not worrying about heavily describing things, and focusing more on the sequence of action and the character's emotions. I could tell Lyra was a bit antsy about the ride even if you didn't tell the reader directly. You told me Carson was slightly bored in the first chapter, but it didn't come off as such. Use your action to describe things; don't stop the flow of work to describe what is going to happen before executing what is going to happen.
Likewise, consider merging paragraphs together, especially shorter ones, because that seems to be effecting the fluidity of your fic. You might also want to consider changing up the sentence structure of a few sentences so you're not repeating the same sentence structure one after the other. Ex:
He set it down carefully and found another object. It was a silver badge in the shape of a C, the symbol of a Champion. Carson had realized the first time he had looked through the boxes the purpose of them; to hide the memories of his mother that he and his father shared.
He decided it was best for his sanity that he look no more. He’d seen enough other times his father and sister were somewhere else, and he didn’t need to feel the tears again.
The similar structure here makes the story read as staccato and monotonous. Try combining a few of these sentences into one or changing up the structure entirely.
By the way, you used the semicolon incorrectly here. Try thinking of semicolons as periods; both clauses on each side of the semicolon should be able to function as its own complete sentence. Semicolons are useful when connecting two complete sentence with similar ideas. "To hide the memories of his mother ..." isn't a complete sentence, so you cannot use the semicolon. You're probably better off using a colon instead.
On another note, try not to information dump not unless there's a point to it besides describing a character. To quote the same section from earlier:
She had raven-black hair that extended down to her waist, and eyes that were normally hazel but seemed to change color every once in a while. Sporting a brown coat and well-kept denim jeans, she walked in on her white shoes with neon green laces.
You don't need to dump character description, or even setting description, in one huge go before continuing on. Like I said earlier, it stops the movement of your story. It also makes your work look a tad bit amateur. A lot of beginning writers information dump because they believe they have to describe what someone looks like otherwise the reader won't know what to imagine. Not true. Huge dumps of description, especially of character description, is actually more likely to get skimmed over if not ignored completely because it's just too much information in that is constructed in a completely flat way. Like who really cares about what her shoes are like other than she is, well, wearing them?
Try using character description to your advantage; quite often, people play or fidget around with their hair or their clothing when their conversing with people:
Ex) He pocketed his hands into the dark denim of his jeans and fiddled with a ball of lint.
"I'm a researcher, too!" she whined, tugging at her strands of dark blue hair. "I can help, you know!"
It's not that obvious that you're describing a character since it's worked into interaction with the character. The smaller breaks in description also help keep the fic moving. You did this a few times (description of Ellie and Blaze), but I feel you could have even broken it up even further, or merging in description of the pokemon with the action that they did.
Likewise, I'm not saying information is necessarily bad, but there should be some point to it. It usually works better in the context of another character observing another, like in scrutiny or maybe they have a crush on said character, and it shouldn't be crazily detailed either otherwise your readers might skip over it
Overall, I'm not exactly sure what this story is about but I do like how it started out with something that appeared to be an average day instead of jumping straight into the true plot. I do think the structure of it could use a lot of work so it reads more as a story rather than you listing off a sequence of events that have no effect on any of the characters involved.