Concept: Prompt-Centric Design
Prime Style MCP is built on a philosophy called Prompt-Centric Design — distinct from conventional APIs and toolsets.
This page explains why MCP treats prompts as the hero, and the benefits of this approach.
Prompts Are "Thinking Frameworks"
In MCP, a prompt is not merely a command to a large language model (LLM). It is a systematized thinking framework — the kind that outstanding specialists (business analysts, software architects, QA engineers) carry in their heads.
The requirements_analyzer prompt doesn't just convert ideas into requirements. It encapsulates the process itself — how a business analyst analyzes inputs, resolves ambiguities, and identifies goals.
Using an MCP prompt means borrowing an expert's thinking process to accomplish your own task.
Why Aren't APIs and Tools the Hero?
Typical developer platforms offer independent APIs and tools for each capability — a "user creation API," a "file analysis tool," etc. These are useful, but users must figure out which tools to use and in what order to achieve their goal.
MCP reverses this approach:
- Prompts (Prompts) are the hero: Provide a thinking framework (workflow) aligned with the user's goal (e.g., "I want to launch a new project").
- Tools (Tools) are supplementary: Provide concrete processing (e.g., code complexity calculation, document parsing) that the prompt needs to execute its thinking process.
- Resources (Resources) are reference: Provide knowledge (e.g., design patterns, checklists) that prompts reference.
Users don't need to assemble a workflow themselves. Just choose the right prompt for their goal and immediately put expert thinking into practice.
Benefits of Prompt-Centric Design
1. Democratizing Expertise
Since expert thinking processes are codified as prompts, even less-experienced engineers can work like specialists.
2. Enforcing Best Practices
By embedding team best practices (ADR creation, security review perspectives) into prompts, you naturally maintain and improve quality standards across the organization.
3. Flexibility and Extensibility
Prompts are implemented as TypeScript functions. Modifying existing prompts or combining multiple prompts to create new thinking frameworks is straightforward. Evolve MCP alongside your team's growth.
Prompts in MCP are not just "features" — they are "educational tools" for raising a team's development capabilities and quality of thinking.