This file defines the category language this project wants to own.
The goal is not to invent jargon. The goal is to make a few sharp terms reusable until they become the default way to describe this category.
Use when referring to the full public-facing system:
Do not reduce it to “prompt library”.
Use when referring to the deeper layer:
This term means a working system, not a folder of content.
This is the category term. Lead with it when defining what this project is.
Use when the workflow is designed for:
This term is stronger than “prompt template”.
Use when the task is to judge:
This term implies decision-making, not idea generation.
Use when the task is to clarify:
This term should replace vague phrases like “help me set a price”.
Measures whether an agent chose the right command or skill.
Measures whether the output matches professional PM standards.
The umbrella term for routing, output, and domain-specific evaluation.
These phrases shrink the project back into the old category.
When writing README copy, launch posts, benchmark summaries, or directory descriptions:
PM Operating System as the category termPM AI Skill Toolkit as the productIf the audience remembers only one phrase, it should be one of the canonical terms above.