blog-assets
01Command Claude Code needs its repo
Build HTML templates for each visual placeholder in a blog article and batch-export them as 1200x675 PNGs at 2x. Fourth step in the blog production pipeline.
Command Claude Code needs its repo
Build HTML templates for each visual placeholder in a blog article and batch-export them as 1200x675 PNGs at 2x. Fourth step in the blog production pipeline.
Command Claude Code
Write a 1,200-2,000 word blog article as plain semantic HTML from an approved outline. Second step in the blog production pipeline.
Command Claude Code
Reference document showing the full Blog Engine flow with human approval gates. This is not an executable command — it's a map of how blog commands connect.
Command Claude Code
Research canon sources for a blog topic, build a structured outline with visual placeholders, and draft CMS metadata. This is the first step in the blog production pipeline.
Command Claude Code needs its repo
Push a completed blog article to the CMS -- upload images, create CMS item, sync components. Final step in the blog production pipeline.
Command Claude Code
Run the full quality pipeline on a blog draft. Chains /content-qa + /stop-slop + blog-specific checks. Returns READY or NOT READY. Third step in the blog production pipeline.
Command Claude Code
View recent changes to brand/canon-rules.json with grouped diff output. Reads the append-only CHANGELOG.md maintained by the canon-changelog hook.
Command Claude Code
Unified communication triage across email, social mentions, and project management in one pass.
Command Claude Code
Mine community channels (Discord, Slack, Telegram) for recurring questions, pain points, and feature requests. Produces actionable content briefs and documentation gap reports.
Command Claude Code
Jurisdiction-aware content compliance validation. Scans copy for regulatory violations, banned claims, missing disclaimers, and financial promotion language.
Command Claude Code
Reference document showing the full Content Engine flow with human approval gates. This is not an executable command — it's a map of how content commands connect.
Command Claude Code
Weekly content planning for {{COMPANYNAME}}'s Monday-Friday social content. The brain of the content engine.
Command Claude Code
Standardized quality pipeline for all outbound content. Runs 6 checks + Brand Voice Score and returns a READY or NOT READY verdict.
Command Claude Code
Review any copy against your brand canon — flags banned phrases, framing drift, and audience misalignment. Returns a scored audit with fixes.
Command Claude Code
Batch-produce all visual assets for the week's approved content. Builds banners, renders videos, exports PNGs. No manual steps after this — everything comes out ready to post.
Command Claude Code
Produce content for a specific day from the weekly plan. Runs the full pipeline: canon research -> copy -> visual -> brand compliance -> review.
Command Claude Code
Review marketing copy against brand voice, legal guardrails, pillar tone-of-voice rules, and platform rules. Returns a scored audit with fixes.
Command Claude Code
Distribute content across X, LinkedIn, and Threads with platform-native adaptation.
Command Claude Code
The /dashboards command builds all master staging dashboards for EVC in one shot. Each dashboard serves one focused purpose and is rebuilt from source files on demand.
Command Claude Code
Multi-source research with cited reports. Searches the web, synthesizes findings, delivers structured output.
Command Claude Code
Strip internal-only elements (version drawer, review notes) from a staging HTML file to produce a clean export ready for CMS upload or public sharing.
Command Claude Code
End-of-week close-out. Reviews performance, digests team progress, cleans up project management, and saves session state.
Command Claude Code
Print all available commands grouped by use case. When the user runs /help, output the full index below.
Command Claude Code
Weekly intelligence gathering for the {{COMPANYNAME}} content engine. Run on Sunday evening or Monday morning before content planning.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: