tylerbutler

Add a new OCLIF command to a CLI package with proper base class, flags, args, and post-creation steps

Create changesets for pending changes by analyzing git diff and commit history

Audit workspace dependencies for version mismatches, unused packages, and sync issues across all packages

Fix all repository policy violations

Run Nx affected commands for the current changes

Reference for Nx task architecture, orchestration patterns, and how to add or modify build tasks

Reference for OCLIF command patterns, base classes, and conventions used in CLI packages

Monorepo coding conventions to follow when writing or editing code in this repository

Use this skill when a user wants to add generated API/reference docs to a Gleam project from Gleam's package-interface.json metadata. Trigger for requests about Gleam docs JSON, package-interface.json, reference docs, Starlight or Astro docs sites, HexDocs-like pages, just recipes, pnpm/node scripts, or replicating the Gluegun docs recipe. This skill helps wire the generator script, package scripts, just tasks, sidebar entries, tests, and validation so the workflow is repeatable.

Use this skill for any Kusto query or telemetry investigation specifically related to Fluid Framework or its partners. Triggers include: writing or running a Kusto query against the Office Fluid database, investigating Fluid Framework telemetry or error rates, querying Office_Fluid_FluidRuntime_* tables, looking up a Fluid session by Session_Id or docId, investigating a Fluid-related error in Loop or Whiteboard telemetry, monitoring an FF bump or partner ring deployment, checking Fluid render reliability or Scriptor errors, or when the user mentions Fluid-specific tables (Office_Fluid_FluidRuntime_*, OwhLoads, HostTracker, Scriptor) or Fluid-specific error types (dataCorruptionError, dataProcessingError, DeltaConnectionFailureToConnect, ICE, ACE). Do NOT trigger for general Kusto questions that are not related to Fluid Framework.

Trigger ADO pipelines for a Copilot-created PR by posting /azp run comments. Use when the user asks to trigger CI pipelines for a specific PR.

Guide the Fluid Framework client release group through minor releases, patch releases, and post-release type test updates. Use when performing a release, preparing for a release, creating release branches, bumping versions, generating changelogs/release notes, or updating type test baselines after a release. Triggers on mentions of release, releasing, release branch, version bump, release notes, changelog generation, patch release, minor release, or release engineering.

Create new packages in the Fluid Framework monorepo following all conventions. Use when creating a new package, adding a new DDS, or scaffolding a new library. Triggers on mentions of new package, scaffold, create package, add package, or package template.

Quick reference for flub and fluid-build CLI commands in the Fluid Framework monorepo. Use when you need to find the right flub command, understand its flags, or figure out how to run a specific build/check/generate task. Triggers on mentions of flub, fluid-build, build CLI, or specific flub subcommands.

Manage type compatibility tests in the Fluid Framework monorepo. Use when type tests fail, when acknowledging breaking changes, or when preparing type test baselines. Triggers on mentions of type tests, typetests, type validation, type compatibility, backward/forward compat, or validate*Previous.generated.ts.

Manage API Extractor reports and release tag entry points in the Fluid Framework monorepo. Use when regenerating API reports, adding new exports, changing release tags, or debugging API Extractor errors. Triggers on mentions of API reports, api-extractor, release tags, entry points, public/beta/alpha/legacy/internal exports.

Rebuild Gleam protocol and reload Elixir modules

Debug WebSocket channel issues

Create a new REST API endpoint with authentication

Generate OpenAPI documentation from Phoenix router

Create a changie changelog entry for the current changes. Use when asked to create a changelog entry, changie entry, or change log.

Guide through release preparation

Run the repoverlay test suite

Project conventions and architecture for this Astro site (tylerbutler.com)

Scaffold a new blog article with correct frontmatter and file placement

Add a new shell alias to dot_aliae.yaml with proper cross-platform templating

Guide for working with chezmoi dotfiles - file naming, templates, and apply workflow. Use when editing files in this dotfiles repository.

Use when you've made code changes and need to add a changelog entry. Analyzes git diffs to create changie fragment YAML files in the correct format for this project.

Use after completing code changes to create a changie changelog entry in .changes/unreleased/. Infers the change kind and body from the current session's work, confirms with the user, then writes the YAML file directly.

Create a changie changelog entry for a code change. Use when asked to add a changelog entry, record a change, or after completing a feature/fix/refactor.

Create a changie changelog fragment for this repo. Use whenever a code change needs a changelog entry — after finishing a feature or bugfix, when the user asks to add a changelog entry, or when a PR is missing one. Also use this if the finishing-a-development-branch workflow needs a changelog entry added.

Validate all vestibule packages are ready for hex.pm publishing

Create changie changelog fragments for the lattice monorepo. Use this skill whenever the user mentions changelogs, changelog entries, changelog fragments, changie, "add a changelog", "add a change entry", or wants to document changes for a release. Also use proactively after completing user-facing code changes to any package, even if the user doesn't explicitly ask for a changelog entry.