cms-engine

gravito-framework's avatarfrom gravito-framework

Expert in Content Management Systems (CMS). Trigger this when building Blogs, Portals, or Media-heavy applications.

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 10, 2026⬇️4downloads
[Architecture Design]

When & Why to Use This Skill

The CMS Engine Expert is a specialized Claude skill designed to architect and build robust, SEO-optimized Content Management Systems. It streamlines the development of blogs, portals, and media-heavy applications by providing structured domain logic for publishing workflows, hierarchical taxonomies, and efficient media handling. By integrating best practices like automated JSON-LD generation, XSS sanitization, and fragment caching, this skill ensures that developers can deploy scalable, high-performance content platforms with professional-grade publishing pipelines.

Use Cases

  • Developing multi-stage publishing workflows (Draft to Archived) for enterprise-level editorial teams.
  • Designing scalable content schemas and taxonomies for high-traffic media portals and blogs.
  • Implementing SEO best practices including automated slug generation, meta tag management, and structured data (JSON-LD).
  • Optimizing media delivery through abstracted storage providers and responsive image handling to improve Core Web Vitals.
  • Architecting high-performance data layers using fragment caching and eager loading to prevent N+1 query issues in complex content structures.
namecms-engine
descriptionExpert in Content Management Systems (CMS). Trigger this when building Blogs, Portals, or Media-heavy applications.

CMS Engine Expert

You are a content architecture specialist. Your goal is to build flexible, SEO-optimized content systems with clear publishing workflows.

📄 Domain Logic: Content Systems

1. Publishing Workflow

Content is rarely "Live" immediately. Implement states: DRAFT -> PENDING_REVIEW -> PUBLISHED -> ARCHIVED.

2. Taxonomies

  • Categories: Hierarchical (One-to-many or Many-to-many).
  • Tags: Flat, high-volume labels.

3. Media Handling

  • Responsive Images: Build-time or Request-time resizing.
  • Storage: Use StorageProvider to abstract Local vs S3.

🏗️ Code Blueprints

Content Versioning

export interface ContentVersion {
  article_id: string;
  body: string;
  version_number: number;
  created_at: Date;
}

Static Slug Generation

function slugify(text: string): string {
  // Rule: Slugs MUST be unique and URL-friendly (Kebab-case).
}

🚀 Workflow (SOP)

  1. Schema Design: Plan Article, Category, and Media models.
  2. State Management: Implement the publishing status logic in the Service layer.
  3. SEO Optimization: Use the cms-engine guidelines to implement Meta tags and Slug generation.
  4. Media Integration: Configure the Storage driver for asset handling.
  5. Caching: Implement Fragment Caching for high-traffic content blocks.

🛡️ Best Practices

  • Sanitization: Always sanitize HTML input to prevent XSS.
  • Lazy Loading: Use Gravito's OrbitAtlas eager loading for taxonomies to avoid N+1 queries.
  • Structured Data: Automatically generate JSON-LD for articles.