Decision Matrix: Rules vs. MCP vs. Skills vs. Workflows

Capability TypeWhat it isBest For…Trigger
RulesGuardrails & ConstraintsCoding standards, linting rules, naming conventions.Always On (or by file type)
MCP ServersHands & External DataReading a DB, fetching live docs, searching GitHub.On-Demand (as needed)
Agentic SkillsSpecialized MethodologyComplex migrations, boilerplate scaffolding, multi-step validation.Agent-Triggered (Semantic Match)
WorkflowsAutomation Macros/deploy, /test-all, /onboard-project.User-Triggered (Slash command)
  • “I want the agent to NEVER use any in TypeScript.”

    • 👉 Use a Rule. It’s a persistent constraint.
  • “I want the agent to be able to search the latest shadcn documentation online.”

    • 👉 Use an MCP Server. It connects the agent to a live, external data source.
  • “I want the agent to follow a specific 5-step process to generate a New Feature module.”

    • 👉 Use a Agentic Skills. It provides a modular “how-to” that includes templates and scripts.
  • “I want to type /ship and have the agent run tests, lint, and push to main.”

    • 👉 Use a Workflow. It’s a user-initiated macro for a predictable sequence.

Pro-Tip: The “Consultant” Analogy

  • Rules: The corporate policy manual (Must follow).

  • MCP: The library and internet access (Information source).

  • Skills: The specialist training (How to do a specific job).

  • Workflows: The scheduled agenda (What to do right now).