markheydon

Guide for using the MudBlazor component library in Blazor Server applications. Use this when building or refactoring Blazor pages and components for SoloDevBoard. Covers setup, layout, component usage patterns, dialog and snackbar services, data grids, forms,…

Diátaxis Documentation Expert. Creates high-quality software documentation using the Diátaxis framework.

Ensure .NET/C# code meets best practices for the solution/project.

Manage the SoloDevBoard Roadmap GitHub Project (Project #8). Add issues to the board, set Phase/Priority/Status/Date fields, manage the Up Next queue, and keep the project in sync with the issue lifecycle. Use this skill whenever creating or updating GitHub…

Create, update, and manage GitHub issues using MCP tools. Use this skill when users want to create bug reports, feature requests, or task issues, update existing issues, add labels/assignees/milestones, or manage issue workflows. Triggers on requests like…

Orchestrates end-to-end feature delivery for SoloDevBoard: planning, GitHub issue management, implementation gating, testing, documentation, and closure.

GitHub CLI guidance for SoloDevBoard issue triage, label management, pull requests, workflows, and project operations.

Get best practices for XUnit unit testing, including data-driven tests

Manage GitHub Issues using a structured label taxonomy (epic/story/bug), triage new issues, apply labels per strategy, maintain project board membership, and keep issues organised across one or more repos. Use when creating issues, triaging unlabelled issues,…

Project-aware documentation conventions that complement the upstream documentation-writer skill. Use when writing or updating README content, docs pages, user guides, tutorials, or technical blog posts in a repository that provides project context files such…

Apply practical, repository-aligned .NET/C# engineering practices without forcing framework-specific or architecture-specific choices.

Guide for using the MudBlazor component library in Blazor applications. Use this when building or refactoring Blazor pages and components with MudBlazor. Covers setup, layout, component usage patterns, dialog and snackbar services, data grids, forms, colour…

Diátaxis Documentation Expert. An expert technical writer specialising in creating high-quality software documentation, guided by the principles and structure of the Diátaxis technical documentation authoring framework.

Write and improve end-user documentation for Import To Planner public docs pages. Use when creating or editing website/content pages such as index, getting-started, csv-format, import-workflow, troubleshooting, faq, privacy-and-security, or self-hosted; when…

Structure GitHub issue bodies with fenced specify/plan seeds for the Spec Kit workflow (/speckit.specify, /speckit.plan). Not a Spec Kit skill—pair with github-issues for gh/MCP writes.

Create, update, and manage GitHub issues using MCP tools. Use this skill when users want to create bug reports, feature requests, or task issues, update existing issues, add labels/assignees/milestones, set issue fields (dates, priority, custom fields), set…

Guide for using the MudBlazor component library in Blazor applications. Use this when building or refactoring Blazor pages and components with MudBlazor. Covers setup, layout, component usage patterns, dialog and snackbar services, data grids, forms, colour…

Intelligent README.md generation prompt that analyses project documentation structure and creates comprehensive repository documentation. Scans repository documentation files and AGENTS.md to extract project information, technology stack, architecture,…

Writes user-facing documentation for website/content/. Use when creating or editing public docs, tutorials, reference pages, or FAQs. Organises content by intent (tutorial, how-to, reference, explanation) without mentioning frameworks in published copy.

README generation for this repository. Builds a concise, Packagist-friendly README.md from repository-native PHP/Composer sources.

Support governance for this repository. Use when reviewing or updating supported PHP, Monolog, WordPress, WP-CLI, smoke-test tuples, CI matrices, or source-of-truth compatibility documentation.

Review DnsCheck.Client changes for correctness, security, API contract, architecture, and maintainability. Use for code reviews of a branch, PR, or local diff. Read-only unless the user explicitly asks for fixes.

Audit the repository or a requested change against DnsCheck.Client goals, scope, conventions, and sample-sync rules.

Extend the DNS Check monitoring API in DnsCheck.Client — models, RestClient, services, tests, MonitorConsole sample, and docs. Use when adding new documented monitoring GET operations or changing the v1 HTTP layer.

Review FreeAgent.NET SDK changes as a principal architect would for pull request approval: bugs, security, public API contract, architecture, complexity, and maintainability only. Use when the user runs /code-review or loop-code-review, asks for a code…

Implement or retrofit one FreeAgent endpoint end-to-end with strict model guardrails, sample app sync, plan-first workflow, and a draft PR for review. Use when adding or updating SDK resource services, models, tests, or sample pages for a FreeAgent API entity.

Audit the repository (or a PR diff) against GOALS.md, SCOPE.md, CONVENTIONS.md, and AGENTS.md sample-sync rules. Use when the user asks for a goals review, drift check, project health audit, or whether work still aligns with G1–G6.

Create an Architectural Decision Record (ADR) document for AI-optimized decision documentation.

Review all open comment threads on a pull request, fix the issues raised, reply to each thread explaining what was done, and resolve the conversation. Use when a PR has received code review with open threads that need addressing before merge.

Project-aware documentation conventions that complement the documentation-writer skill. Use when writing or updating README content, docs pages, user guides, tutorials, or technical blog posts in a repository that provides project context files such as…

Manage GitHub Issues for project and product management workflows. Search for existing issues, create new issues for tasks/epics/stories, update status and comments, link related issues, and close completed work. Use for automating project tracking.

Write consistent Architecture Decision Records (ADRs) for the Rename My Files project. Use when documenting significant architectural decisions, trade-offs, or technical direction choices. Ensures all ADRs follow standard structure, naming conventions, and…

Maintain consistent structure and format for IMPLEMENTATION_PLAN.md and SCOPE.md documents. Use when creating, updating, or reviewing the implementation plan or scope documents to ensure phase naming, section headers, checklist formats, status symbols, and…

Generate or refresh README.md for MeatyTimes by analysing Spec Kit artefacts, governance docs, and repository layout. Use when the user asks to create, update, or regenerate the repository README, project documentation overview, or onboarding docs for new…

Create a feature branch with sequential or timestamp numbering

Syncs this Hugo showcase from identity.md into hugo.yml, plus consultant-voice scan and allowed tags. Use when the user edits identity.md, runs /sync-identity, or asks to update public messaging, branding, or taxonomy on markheydon.me.uk.

Scans GitHub repos against markheydon.me.uk project/blog coverage, maintains github-content-index.md, drafts missing project pages locally, proposes blog posts only when warranted, and audits screenshot paths. Use when the user runs /sync-github-content or…

Writes developer documentation, tutorials, ADRs, and blog posts for this repo. Use when creating or editing website/content/, README.md, CHANGELOG.md, or user-facing technical content.

Creates and validates Azure Bicep templates for this repo. Use when writing or modifying Bicep in infra/, using Azure Verified Modules, or when the user asks for infrastructure-as-code changes.

Review Potsure changes as a principal architect would for pull request approval: bugs, security, architecture, complexity, and maintainability only. Use when the user runs /code-review, asks for a code review, or wants findings on a branch, PR, or local diff…