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.

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)

Core References (for MCP agents)

These IDs and search hints help MCP agents find context via pacing-docs:

AreaID / ValueSearch hint
Webflow site669e9035529a7f101e149eca"Webflow site ID pacing.agency"
GTM webGTM-PGPK24VR"GTM web container"
GTM serverGTM-NHVBMP3D"GTM server sGTM"
GA4G-TPFS2Z0HNJ"GA4 measurement ID"
Identity_c_pca"GTM _c_pca client ID"
n8nn8n.pacing.agency"n8n pacing agency"
Webflow Services676058e3b03e90853d8d8ceb"Webflow Services collection"
Webflow Case Studies68763c05b86dd4610d8d02b5"Webflow case studies"
Webflow Blog669e9035529a7f101e149f62"Webflow blog post collection"
Webflow Landing Pages6904dcb47ebff962cc495004"Webflow landing pages lp1"

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.