FWIW, I’m assuming you’re speaking of the last 18 entries to your Dribbble page.
I want to start off by saying that I think your designs are insanely eye-catching. Definite kudos there, that’s very hard to do.
The thing to keep in-mind about UX is that it is, as @HAWK pointed out, a very process-driven, problem-solving discipline. Your designs are striking, to be sure, but without knowing what problems you’re attempting to solve or business use cases for each product, it’d be hard to say that any of them are “good” designs.
This is part of what makes a UX portfolio so hard to evaluate: most people are not good at describing the process, challenges, and compromises that go into creating any design. Visuals simply aren’t enough to get the job done. Timothy Jaeger makes an excellent point of this in his article on UX portfolio content, and recommends focusing on the following questions for each project:
What were the business challenges?
This could be something as simple as a sentence or two that indicates what problem you were solving.
What was your approach?
Surely you evaluated / tried things and settled on a solution…Note these down as well as the decision-making that went into how you came to your conclusions.
What was that process like?
What were the lessons learned? What compromises were made and how did these effect the final product?
What was the result?
When did you say ‘finished’? Was it when you handed the work off to the client or is it every two weeks when you track user engagement with your new app or game?
How did you measure success / failure?
Surely not everything you work on is a smashing success. What did you use to evaluate the results of your labor? How does your boss, or bosses’ boss, know that what you worked on turned out to be a success for the company? How is it measured? Is there a percentage increase that is important to the business?
I’d think your portfolio could be improved by seeking to answer these questions for your designs.
As far as general UX “sins” in the designs, a couple of things jump out to me offhand:
Using placeholder text in form fields. Empty form fields are easier to spot without placeholder text, which actually has a negative effect on form filling and task completion. Best practice is labeling above help text above input. Placeholders in Form Fields Are Harmful
ALL CAPS EVERYWHERE. I get that, from a visual perspective, writing in all caps makes everything nice and blocky, which helps with overall contrast and placeholding. The problem is that humans recognize words by their shapes, not necessarily their spelling. All caps (and Title Casing, for that matter) throw this off. I know it’s a hard change, but in most cases it’s more UX-friendly to use sentence casing. Word recognition - Wikipedia
Accessibility Issues. Your designs are colors are very striking, but put yourself in the shoes of someone who’s colorblind. It would be hard for a user to pick out the color used for interactivity, for instance, in many of your designs. There are also concerns about text sizing, visual focus on text fields, and contrast that are hard to tell for certain with this level of prototyping. 7 Things Every Designer Needs to Know about Accessibility | by Jesse Hausler | Salesforce Design | Medium
I hope this all helps-- let me know if I can answer any questions!