MichaelvanLaar

Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.

Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.

Archive multiple completed changes at once. Use when archiving several parallel changes.

Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.

Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.

Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.

Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.

Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.

Use this skill when the owner wants content ideas, angles, or directions for a piece of content — not a finished text. Invoke when the user says "give me content ideas", "brainstorm angles for this article", "what could we post about this", "develop some directions from this briefing", "I need angles for a LinkedIn post / blog / newsletter", or pastes an article or notes and asks how the company could pick up the topic. This is the idea-generation step that precedes writing — it produces distinct strategic angles the owner can then hand to a writing skill. Do NOT use it to write the finished text itself.

Use this skill to draft a finished marketing or PR text for an output format that does NOT have its own dedicated skill — for example a press release, newsletter, whitepaper, landing-page copy, product description, email, webinar abstract, or ad copy. Invoke when the user says "write a press release", "draft a newsletter", "write the copy for this landing page", "turn this idea into a <format>", or names any text deliverable without a dedicated skill. This is the general-purpose writer for the long tail of formats. It deliberately defers: if a dedicated skill exists for the requested format (such as a blog article or LinkedIn post, or a project-specific skill), it points the owner there first. Do NOT use it for formats that already have a dedicated skill.

Use this skill when the owner wants to write, draft, or generate a blog article. Invoke when the user says "write a blog article", "draft a blog post", "create a blog article", "generate a blog post", "write a how-to article", "draft a thought leadership piece", "write a pillar page", or similar requests for long-form web content.

Use this skill when the owner wants to write, draft, or generate a LinkedIn post. Invoke when the user says "write a LinkedIn post", "draft a post for LinkedIn", "create a LinkedIn update", "generate a LinkedIn post", or "post on LinkedIn".

Use this skill when setting up a new marketing project with Claude Code, registering context files, or extending the context of an existing project. Invoke when the user asks to "onboard a new client", "set up context files", "initialize marketing project", "register context", "add context", or "set up project context". Also use when context files are missing and the user wants to set up through a guided interview.

Use this skill to register an existing file as context in CLAUDE.md so content skills can discover and load it for future work. Invoke when the user says "register this as context", "promote to context", "add this to context", "add this file to the context table", "reference this in CLAUDE.md", or "make this a context file".

Use this skill at the end of a content creation session to review deliverables, collect feedback, detect recurring correction patterns, and create a git commit. Invoke when the user says "wrap up", "end session", "session wrap", "wrap session", "commit session work", or "close out this session".

Use this skill when building a new content-production skill for a specific output format. Invoke when the user says "create a new content skill", "build a skill for [format]", "new content skill", "synthesize research into a skill", or "create a [format] skill".

Audit and optimize an existing Claude Code configuration against current best practices. Use this skill when a user asks to review, improve, clean up, or optimize their Claude Code setup, CLAUDE.md, settings, hooks, MCP servers, or skills. Also use when the user says things like "check my config", "is my CLAUDE.md too long", "reduce token costs", "tighten permissions", or "my Claude Code setup feels bloated". This skill assumes the project has code, and possibly documentation or OpenSpec specs, that inform the optimization.

Bootstrap a best-practice Claude Code configuration for a new or unconfigured project. Use this skill when a user asks to set up Claude Code, initialize a project, create a CLAUDE.md, or configure permissions/hooks/settings for the first time. Also use when the user says things like "set up this project", "configure Claude Code", "bootstrap config", or "better /init". This skill replaces the built-in /init with a leaner, more opinionated setup grounded in current best practices.

Bootstrap a best-practice GitHub Copilot Coding Agent configuration for a new or unconfigured project. Use when a user asks to set up GitHub Copilot, create copilot-instructions.md, or configure GitHub Copilot for the first time. Also use when the user says things like "set up my Copilot config", "bootstrap Copilot", or "initialize GitHub Copilot". Grounded in official GitHub Copilot Coding Agent best practices.

Audit and improve an existing GitHub Copilot Coding Agent configuration. Checks the 8,000-character limit, anti-patterns, missing sections, invalid applyTo globs, missing dependency caching, hooks configuration, and accumulated learnings. Use when a user asks to optimize, audit, or improve their Copilot configuration.

Run accessibility, security, and performance audits on the built site. Use after build or before deploy.

Pre-deploy checklist. Run before pushing to production.

Pull n8n documentation for context

Cut a new mpv-photo-frame release — bumps VERSION, updates CHANGELOG.md, tags, and (after confirmation) pushes. Use when the user asks to cut/create/publish a release or new version, or runs /release.

ALWAYS use this skill when the user wants to publish, release, or version bump the npm package. Covers the complete release workflow: pre-checks, changelog, version bump, npm publish, GitHub release, and verification.