Remove redundant `RESHAPR_` prefix from artifact type identifiers

[yada]

In the reshapr artifact list command output, the TYPE column displays the system types associated with each artifact. Currently, many entries are prefixed with RESHAPR_ (for example: RESHAPR_CUSTOM_TOOLS, RESHAPR_PROMPTS, RESHAPR_RESOURCES).

Because this data is entirely contextual to the reshapr CLI ecosystem itself, repeating the RESHAPR_ prefix on every row:

• Adds unnecessary visual noise
• Increases terminal table width usage
• Reduces readability
• Provides no additional value to the end user

Proposed Improvement

Standardize and streamline type names by removing the redundant namespace prefix.

Current Type	Proposed Type
RESHAPR_CUSTOM_TOOLS	CUSTOM_TOOLS
RESHAPR_PROMPTS	PROMPTS
RESHAPR_RESOURCES	RESOURCES

Example Comparison

Current Output

ID             NAME                             TYPE                 MAIN
0Q9JHRYRBB6SZ  GitHub GraphQL-20260410.graphql  GRAPHQL_SCHEMA       Yes
0Q9JJ14WBB73V  file                             RESHAPR_CUSTOM_TOOLS No
0QBG4EFQFB6G1  file                             RESHAPR_PROMPTS      No
0QBGBHY43B5QB  file                             RESHAPR_RESOURCES    No

Proposed Streamlined Output

ID             NAME                             TYPE                 MAIN
0Q9JHRYRBB6SZ  GitHub GraphQL-20260410.graphql  GRAPHQL_SCHEMA       Yes
0Q9JJ14WBB73V  file                             CUSTOM_TOOLS         No
0QBG4EFQFB6G1  file                             PROMPTS              No
0QBGBHY43B5QB  file                             RESOURCES            No

Where the idea is comingfrom -> reshaprio/reshapr.io@107928d

[Abdul-Moiz31]

Hi @yada , can I work on this or any other issue which is currently opened .

Also, after the Reshaper website, I cloned this repository as well.
If there’s any guidance or specific areas you’d like me to explore to better understand the internals of the repo, please let me know.

I’d love to dig deeper, learn more about it, and come back with solid solutions and a better understanding.

Looking forward to your guidance!

Thanks in advance.

[lbroudoux]

I think there are 2 things to consider here:

• The internal naming of artifact type - and here we must absolutely keep the RESHAPR_ prefix to avoid collision of names with other specs, formats or standards. This naming is also used within the API and must stay in place.
• The displayed naming of artifact type in Web UI, Terminal UI or simple CLI - and here we might bring some "conversion" to make things prettier.

However, my honest opinion on this topic is that this is purely cosmetic and very fragile at the moment. We may integrate some other "prompts" or "resources" specification formats at some point, and we'll be forced to go backward and re-adapt conversion layers.

This issue can be kept open, but it has close-to-0 priority for me.

[yada]

Agree with @lbroudoux on the fact that this is clearly cosmetic and not urgent...
I have created it to track it and use it as a reminder, so we can make a decision later on.