marketplace

Copy editor for Gilbert's writing — blog posts, emails, LinkedIn, Bluesky, social replies, announcements, newsletters. Use when drafting, editing, polishing, or writing from scratch, or for tone feedback, headlines, or SEO review. Triggers: "make this better", "polish this", "rewrite", "edit this post", "headline", "SEO". Always activate for writing tasks — Gilbert's voice must be preserved.

Ready-to-use Pester 5 test patterns and recipes for PowerShell modules — mocking (filesystem, REST, credentials, DSC), VS Code hang fixes, parametrized tests. Use when asking for a test template, mock example, or how to test a specific scenario. Triggers: "pester pattern", "mock REST", "mock file system", "mock credential", "test DSC resource", "pester hangs", "VS Code freezes pester", "test template", "pester recipe". Not for running (use pester-run), reviewing (use pester-review), or scaffolding fresh tests (use pester-write).

Run Pester 5 tests with agent-optimized output — failures and summary only, no passing-test noise. Use when asked to run tests, execute the test suite, run a specific file, filter by tag, verify a change, or find what's failing. Triggers: "run the tests", "run Pester", "execute the test suite", "check if tests pass", "what tests are failing", "are all tests green", "does this break any tests". Not for writing tests (use pester-write) or reviewing quality (use pester-review).

Prepare a release — update CHANGELOG.md and bump the version in manifests (package.json, *.psd1, pyproject.toml, Cargo.toml, *.csproj). Follows Keep a Changelog and SemVer. Use when the user wants to cut, ship, or prep a release, bump a version, do a first stable release (0.x→1.0), prep a hotfix, or normalize a non-semver version. Triggers: "prepare the release", "version bump", "update changelog", "cut a release", "ship a new version", "go 1.0". Does the file edits and commit — not CI/CD config, tooling, rollbacks, or git tagging.

Create and manage Architecture Decision Records (ADRs) — short docs in `docs/decisions/` capturing why a design decision was made. Use when the user asks to create, update, or backfill an ADR, document a decision, or convert an RFC to an ADR. PROACTIVELY suggest when a significant architectural choice is being made (libraries, patterns, dependencies, trade-offs). Triggers: "ADR", "decision record", "document this decision", "why did we choose", "design rationale", "we decided to". For pre-decision team discussion use rfc instead. Not for general docs, READMEs, runbooks, or incident reports.

Create Requests for Comments (RFCs) — proposals in `docs/decisions/` opening a significant decision for discussion before committing. Use when the user wants to propose a change, draft a technical proposal, or open a design discussion. PROACTIVELY suggest for migrations, breaking API changes, new architecture, or competing approaches needing structured input. Triggers: "RFC", "propose", "design proposal", "request for comments", "get feedback on this approach", "I want input from the team". For decisions already made use adr. Not for small choices, general docs, or post-mortems.

Review existing Pester 5 test files for correctness, idiomatic v5 usage, coverage gaps, and v4→v5 migration issues. Use when asked to review, audit, improve, or grade a *.Tests.ps1 file, or when shown a test file for feedback. Triggers: "review my tests", "audit test coverage", "v4 to v5 migration", "pester migration", "are my tests good", "check my test file", "are my tests idiomatic", "what am I missing in my tests". Not for writing new tests (use pester-write), running tests (use pester-run), or non-test code.

Write Pester 5 test files for PowerShell functions, modules, scripts, DSC resources, or classes (PS 5.1 and 7+). Use when asked to add tests, create *.Tests.ps1, scaffold tests, mock a dependency, cover an edge case, or test a specific function. PROACTIVELY suggest tests when a function or module is added/modified without a corresponding test file. Triggers: "write Pester tests", "add tests for", "test coverage", "unit tests for", "mock this dependency", "Pester spec", "scaffold tests", "test this function". Not for running (pester-run), reviewing quality (pester-review), CI config, or non-Pester frameworks.

Open Graph and social sharing image design with platform specs, text placement, and branding. Covers OG meta tags, Twitter cards, LinkedIn previews, and HTML template patterns. Use for: social sharing images, blog thumbnails, link previews, social cards. Triggers: og image, open graph, social sharing image, twitter card, social card, link preview image, og meta, sharing preview, social thumbnail, meta image, og:image, twitter:image, linkedin preview

Review MARP markdown presentations for "Death by PowerPoint" issues. Use when asked to review, critique, or improve a presentation, check slides for clarity, or when terms like "Death by PowerPoint," "slide review," "too much text," or "presentation feedback" appear. Applies David JP Phillips' principles for cognitive optimization of slides.