Skill UI

Implements federated sign-in using Amazon Cognito as the central user pool. This skill allows developers to integrate various external Identity Providers (IdPs) such as Google, Facebook, Apple, and Microsoft (OIDC/Entra ID) for Single Sign-On (SSO). It automates the setup of Cognito User Pool Domains, OAuth configurations, and handles the complex identity synchronization process, ensuring seamless user experience while maintaining centralized user management.

This skill guides developers through configuring Microsoft Entra ID (Azure AD) as a federated identity provider for Webiny projects. It enables Single Sign-On (SSO) by allowing users to authenticate using their corporate Microsoft 365 accounts. The setup involves registering an application in the Entra ID portal and integrating the credentials into the Cognito Federation structure, allowing Cognito to remain the core user pool while utilizing Microsoft identities for login.

This skill provides a custom "New Entry Wizard" component for integrating into a Headless CMS workflow. It intercepts the standard entry creation process, allowing developers to collect essential initial fields (like title, slug, or category) via a dedicated, guided UI. Once data is collected, the wizard automatically pre-fills the main entry form, ensuring a smooth, structured user experience while maintaining the integrity of the CMS content creation flow.

This guide details how to implement real-time notifications from a backend API to the Admin UI using WebSockets. It covers emitting messages from server-side logic (e.g., background tasks) and receiving/handling them within the Admin's WebSocket handler, allowing for immediate UI feedback like toasts or cache updates.

The SuperDoc CLI is a powerful command-line interface designed for programmatically editing, querying, and transforming Word documents (.docx). It handles complex document operations such as batch find-and-replace, content extraction, advanced formatting, and mandatory tracked changes. Ideal for automated workflows in legal, academic, or technical fields where rigorous document version control and modification history are critical.

This utility facilitates the formal closeout of a launched AI agent. It performs three critical functions: 1) inventories all built primitives (memory, environment, deployment); 2) regenerates a clean, single-file overview page for sharing; and 3) suggests the next 1-2 most impactful upgrades or hardening steps, providing a clear roadmap for the founder.

This skill provides a comprehensive workflow for creating professional and standardized pull requests (PRs). It enforces critical rules, including mandatory issue linkage to approved items, strict branch naming conventions (e.g., feat/description), adherence to Conventional Commits, and the completion of detailed PR body templates. Use this guide when submitting any code changes to ensure high quality, traceability, and seamless code review.

This skill automatically analyzes overly large Pull Requests (over 400 lines) and intelligently splits them into a series of smaller, manageable, and logically chained PRs (Stacked or Feature Branch Chain). It ensures that each review slice remains focused, actionable, and can be reviewed within a reasonable time frame (≤60 minutes), significantly improving code review efficiency and maintainability.

This skill guides the creation of technical documentation (such as RFCs, READMEs, PR descriptions, and architecture guides) that minimizes the mental effort required for the reader. It emphasizes structural patterns like 'Lead with the answer,' 'Chunking,' and 'Progressive disclosure' to ensure content is scannable, actionable, and easy to review, significantly reducing cognitive load for maintainers and contributors.

A comprehensive guide and set of rules for writing effective, warm, and actionable comments across various development platforms. It helps users structure feedback for GitHub PRs, issue trackers, or Slack messages, ensuring the tone is consistently thoughtful, direct, and focused on clear next steps, rather than simply listing observations.

This guide outlines the rigid contract and best practices for maintaining journey-based automated testing within a product development lifecycle. It dictates how to run reproducible, robust tests against core product semantics, ensuring that changes in behavior do not introduce regressions. Use this when integrating new journeys, diagnosing CI failures, or managing semantic shifts.

A comprehensive guide detailing the mandatory steps, naming conventions, and automated checks required for creating branches and opening Pull Requests. This skill ensures all code submissions are linked to approved issues, adhere to conventional commits, and pass rigorous CI requirements before merging, maintaining high code quality and stability.