Generate a feature request issue for the FAST repository using the provided template.
npx skills add https://github.com/microsoft/fast --skill fast-feature-request
This prompt only applies to generating Feature Request issues for the FAST repository.
Do not create or modify any existing Github issues. This skill is only for
generating the markdown content for a new issue based on the provided template.
Based on the conversation context, generate a feature request as a markdown code
block using the template located at
../../ISSUE_TEMPLATE/feature-request.md.
The summary should clearly state what the feature is and why it matters, focusing
on user value rather than implementation details.
Expected Behavior should describe how the feature would work from an end-user or
developer perspective. Be specific about the desired outcome.
Current Behavior should explain the gap — what exists today and how the absence of
this feature affects users. If there is a workaround, mention it briefly.
Possible Solution is optional. Include it only if there is a concrete implementation
idea worth capturing. Prefer high-level direction over prescriptive code.
Context should explain the motivation — what the user is trying to accomplish
and why this feature would help. Mention alternatives that were considered, if any.
Examples is optional. Include it when code snippets, screenshots, or usage
scenarios would clarify the request.
Search for existing open or closed issues that overlap with this feature request.
If duplicates or related issues exist, mention them in the Context section.
Suggest a concise issue title in the format feat: add [what] to/in [where].
Provide the markdown code block only, without any additional commentary or explanation.
Any comments in the template can be removed since they're only meant to provide
guidance on how to fill out the template, and are not intended to be part of the
final issue body.
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
Take microsoft/fast-feature-request from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.