plugin-cms-toolkit

CMS Toolkit

Sitecore, Umbraco, and Optimizely expertise baked into Claude Code — scaffolding, content modeling, accessibility scanning, security audits, code review, and best practices enforcement for agency teams.

30-Second Setup

# Add the marketplace source
/plugin marketplace add twofoldtech-dakota/plugin-cms-toolkit

# Install the plugin
/plugin install plugin-cms-toolkit@twofoldtech-plugins

No configuration needed. The plugin auto-detects your CMS platform from project files.

Open a Sitecore, Umbraco, or Optimizely project and start working — the toolkit activates automatically.

---

What's Included

Component	Name	What It Does
Skill	/plugin-cms-toolkit:scaffold	Generates components, content types, controllers, and pages
Skill	/plugin-cms-toolkit:content-model	Designs and audits content architectures
Skill	/plugin-cms-toolkit:a11y	WCAG 2.2 AA accessibility scanner
Skill	/plugin-cms-toolkit:security	OWASP Top 10 + CMS security audit + dependency CVE scan
Skill	cms-detect	Auto-detects your CMS platform (runs in background)
Skill	sitecore	Deep Sitecore XM Cloud / XP expertise (auto-invoked)
Skill	umbraco	Deep Umbraco v14–17 expertise (auto-invoked)
Skill	optimizely	Deep Optimizely CMS 12 / SaaS expertise (auto-invoked)
Agent	cms-reviewer	CMS-specific code review with anti-pattern detection
Hook	Pattern enforcement	Catches hardcoded GUIDs, secrets, N+1 queries on every edit

---

Usage

Scaffold Code

Generate platform-specific, production-ready code that matches your project's existing conventions:

/plugin-cms-toolkit:scaffold component HeroBanner
/plugin-cms-toolkit:scaffold content-type ArticlePage
/plugin-cms-toolkit:scaffold controller Search
/plugin-cms-toolkit:scaffold page LandingPage

The scaffold skill:

1. Detects your CMS and architecture (headless vs traditional)
2. Scans your codebase for naming, namespace, and folder conventions
3. Generates files that fit right in
4. Lists created files and any manual follow-up steps

Design Content Models

Plan content architectures interactively or from a description:

/plugin-cms-toolkit:content-model blog with categories and authors

Outputs a visual content type diagram with field mappings, then generates /plugin-cms-toolkit:scaffold commands to build it:

[Page Type] Article Page
├── Tab: Content
│   ├── Title (short text, required)
│   ├── Hero Image (image, required)
│   ├── Body (rich text)
│   └── Author (content reference → Author)
├── Tab: SEO (inherited from SEO Base)
│   ├── Meta Title (short text)
│   └── Meta Description (text area)
└── Tab: Settings
    └── Hide from Navigation (boolean)

Audit an existing content model for issues:

/plugin-cms-toolkit:content-model audit

Accessibility Scanner

Run a WCAG 2.2 AA audit against your CMS templates, components, and content type definitions:

/plugin-cms-toolkit:a11y                    # Full scan
/plugin-cms-toolkit:a11y views              # Razor views and templates only
/plugin-cms-toolkit:a11y components         # React/Next.js components only
/plugin-cms-toolkit:a11y content-types      # Content model accessibility only

Checks for missing alt text, ARIA violations, keyboard traps, heading hierarchy, contrast patterns, focus management, and CMS-specific issues like image fields without alt text companions.

Security Audit

Audit your CMS project for OWASP Top 10 vulnerabilities, CMS-specific security issues, and dependency CVEs:

/plugin-cms-toolkit:security                # Full audit (code + deps + config)
/plugin-cms-toolkit:security code           # Source code analysis only
/plugin-cms-toolkit:security deps           # Dependency vulnerability scan only
/plugin-cms-toolkit:security config         # Configuration review only

Scans for injection, broken access control, exposed secrets, insecure deserialization, missing auth, and runs dotnet list package --vulnerable / npm audit for known CVEs.

Background Expertise

Three platform skills activate automatically when you're working in a CMS project. They provide:

• Content modeling rules — template inheritance, compositions, field type selection
• Component patterns — Content SDK, Razor views, React/JS SDK, ViewComponents
• API guidance — Content Delivery API, Graph API, REST API, serialization
• Anti-pattern prevention — what not to do and why, with correct alternatives

Code Review

The cms-reviewer agent checks for CMS-specific issues across all three platforms: