vkc-admin-ops-workflow

LEE-SANG-BOK's avatarfrom LEE-SANG-BOK

Standardize admin operations workflow (Draft -> Review -> Scheduled publish -> Published) using DB states + admin API routes + scheduled visibility. Use when implementing admin-controlled publishing systems.

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

When & Why to Use This Skill

This Claude skill provides a standardized framework for implementing robust admin-controlled publishing workflows. It streamlines the lifecycle of content—from Draft and Review to Scheduled and Published states—by defining canonical database schemas, API route structures, and visibility logic. By using this skill, developers can ensure consistent state management, secure administrative operations, and automated content scheduling across their applications.

Use Cases

  • Content Management Systems: Implementing news, blog, or announcement features with built-in review cycles and scheduled visibility.
  • Regulatory & Policy Updates: Managing the lifecycle of official documents or compliance rules that require approval before going live.
  • Marketing & Promotions: Automating the activation and expiration of promotional banners or campaign rules using start/end timestamps.
  • Internal Tooling: Standardizing CRUD operations for administrative dashboards to maintain data integrity and clear state transitions.
namevkc-admin-ops-workflow
descriptionStandardize admin operations workflow (Draft -> Review -> Scheduled publish -> Published) using DB states + admin API routes + scheduled visibility. Use when implementing admin-controlled publishing systems.
short-descriptionAdmin ops workflow standard

VKC Admin Ops Workflow

When to use

  • Adding any “admin-controlled publishing” feature (content drafts, policy updates, regulation updates, templates/rulesets activation)

Canonical implementation in this repo

  • Scheduled visibility model (start/end): news table in src/lib/db/schema.ts
  • Admin CRUD: src/app/api/admin/news/route.ts
  • Public read with schedule filtering: src/app/api/news/route.ts

Standard workflow

  • Draft → Review → Scheduled (optional) → Published
  • The “published view” is derived from:
    • isActive
    • startAt/endAt (optional schedule window)

What to standardize each time

  • DB states and timestamps (createdAt, updatedAt, optional startAt, endAt)
  • Admin endpoints (/api/admin/**) for CRUD + activation
  • Public endpoints with schedule filtering + caching headers when appropriate

Reference

  • .codex/skills/vkc-admin-ops-workflow/references/workflow-spec.md