I'd start by reading through Microsoft's documentation about_Profiles. I've linked to the 5.1 version of the documentation since that's likely what you have on Windows 10, though I doubt it has changed much from version to version. It includes instructions on how to actually create the file and details about when it runs.
For your use case, you probably want to do the following from your session:
if (!(Test-Path -Path $PROFILE)) {
New-Item -ItemType File -Path $PROFILE -Force
}
which will generate the profile. Then once that is generated you can open it with notepad directly with the same example from there:
notepad $PROFILE
You can substitute your favorite editor for notepad. VSCode for instance would be:
code $PROFILE
You can also just get the path to the your profile by simply typing $PROFILE into the shell and it will output it, and then use that information to navigate to it from your favorite editor.
Per the documentation:
A PowerShell profile is a script that runs when PowerShell starts.
It's more complicated than that since there are multiple profile files as the documentation explains, but for your story it's accurate enough.
You can always also 'dotsource' your profile to make it run manually by executing:
. $Profile
However you should note that objects previously defined by prior invocations of your profile might not be removed. So while developing your profile that's a useful technique, be sure to only trust how it behaves when run by opening a completely new session.