Skip to main content

Workspace Agents

This workspace defines Cursor agents (custom subagents) organised by tool or theme. Agents complement Project Rules in .cursor/rules/ and provide repeatable workflows for specific tasks.

Sync: Every agent in .cursor/agents/ must have a doc page here. Run npm run verify-agents-sync (in docusaurus/) to check. See .cursor/plans/README.md → "When you create a new agent".

Agent Types​

TypeWorkspaceContext sourceMCP required
Full-workspaceTechStackMain (this repo)Local files, rules, docsVaries by agent
MCP onlyMinimal (client projects)pacing-docs searchpacing-docs; Webflow for Webflow agents

MCP-only agents run in workspaces with only pacing-docs MCP (and Webflow MCP for Webflow agents). They search for context instead of reading local files. Copy .cursor/agents/mcp-*.md into the client workspace.

Adapting agents for clients​

Agents are designed to work across client projects. Do not hardcode Pacing-specific IDs (site IDs, collection IDs, GTM container IDs, n8n host URLs) in agent definitions or documentation. Instead:

  • Obtain from user: Ask for site ID, collection IDs, container IDs, or n8n host at runtime. Agents should prompt for these when missing.
  • Use MCP tools: Webflow sites_list, collections_list; GTM exports; n8n API — to discover client-specific values.
  • Search hints only: In MCP agents, use search hints (e.g. "Webflow CMS collections structure") to find documentation patterns, not client IDs.
  • Client-specific docs: When working in a client workspace, the client may have their own architecture.md, tools/*.md, or CMS documentation with their IDs. Prefer those over Pacing defaults.

Pacing's own IDs (e.g. pacing.agency Webflow site, GTM containers, n8n.pacing.agency) appear only in internal docs (architecture, tools, guides) as examples. Agent prompts and agent documentation should remain client-agnostic.

Categories​

Agents are organised by the tool they use or their main theme:

CategoryOverviewAgents
DocumentationAuditing and fixing markdown docsDocs Page Auditor, Docs Page Fixer
WebflowContent, keywords, SEO metadataKeyword Content Page, SEO Metadata Auditor (+ MCP versions)
n8nWorkflow design and reviewn8n Workflow Designer (+ MCP version)
GTMTracking implementation auditsGTM Tracking Auditor (+ MCP version)
StrategyTech stack proposalsClient Tech Stack Proposal (+ MCP version)

Each category has an overview page listing all agents with Workspace (Full vs MCP only) and MCP required.

MCP Requirements Summary​

MCPUsed by
pacing-docsAll MCP-only agents (search for context)
WebflowWebflow Keyword Content Page, Webflow SEO Metadata Auditor (full and MCP)

Search hints (for MCP agents)​

MCP agents use pacing-docs search to find context. Use these search hints (not client IDs) in agent definitions:

AreaSearch hint
Webflow"Webflow CMS collections structure", "Webflow content guidelines", "Webflow MCP keyword optimizer"
GTM"GTM event specification lead_form_submit", "GTM _c_pca identity", "Pacing GTM template"
GA4"GA4 measurement ID sGTM"
n8n"n8n new workflow prompt", "n8n webhook URL", "n8n workflow documentation"
Identity"GTM _c_pca client ID"
Consent"Termly consent GTM userPrefUpdate"

Client-specific values (site ID, collection IDs, container IDs, n8n host) must be obtained from the user or discovered via MCP tools at runtime. Do not hardcode them in agents.

Core Design Pattern (Audit → Approve → Apply)​

For docs automation that could change source files:

  1. Audit agent reads the target, loads context, checks against standards, and writes an audit + proposed draft.
  2. Human review happens in the queue folder.
  3. Fixer agent applies only approved drafts, creates backups, and verifies parity.

Setup Patterns (How to Create New Agents)​

  • Agent files live in .cursor/agents/ (lowercase, hyphenated names).
  • Make outputs explicit (e.g. queue under .cursor/plans/).
  • For MCP agents: include core references and a mandatory search step.
  • Enforce source-of-truth mapping for any agent that touches docs.