Browse Skills

Guides the creation of pull requests for the Fluid Framework project, ensuring branch safety, composing titles and descriptions per convention, and opening PRs after user confirmation.

Provides title style options (Conventional Commits or plain imperative), body template based on the repository's pull request template, and CI requirements for composing, drafting, or reviewing PRs in the Fluid Framework repository.

Run a CI readiness check before pushing branches to catch formatting issues, stale API reports, missing changesets, and policy violations. Uses a bundled script to auto-fix and verify changed packages.

Guides developers through reviewing public API changes in the Fluid Framework, including release tag assignment, breaking change classification, API Council requirements, deprecation process, and changeset guidance.

Creates comprehensive implementation plans with exact file paths, code examples, and verification steps for engineers with minimal domain knowledge. Use when design is complete and detailed tasks are needed.

Automates browser interaction to test and debug web applications using Playwright scripts. Ideal for building features or troubleshooting front-end issues with real browser testing.

A meta-protocol that instructs AI agents on how to read and follow skills: always re-read the skill file, announce usage, and create checklists with TodoWrite. Use before any task to ensure disciplined execution.

Captures screenshots using platform-specific command-line tools and loads them for visual analysis. Ideal when you need to see what's on screen to debug UI issues or review designs.

Automates setting up isolated git worktree environments for safe experimentation, with auto-detection of project setup and test verification.

Updates Noridoc documentation files across the codebase after code changes, using a subagent to ensure architectural and system-level documentation stays accurate.

Prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies. Use when writing or changing tests, adding mocks, or tempted to add test-only methods to production code.

Guides test-driven development by writing failing tests first, then implementing minimal code to pass them, and refactoring. Ensures tests verify actual behavior by enforcing the red-green-refactor cycle.