Packs

4 packs

Create llms.txt

Generate an llms.txt file for LLM-friendly project documentation following the specification.

4 skills · pack

Create Design System Documentation

Generate component specifications, pattern library entries, and design system documentation for UI consistency.

8 skills · pack

Design REST API from Spec

Create a structured specification, design a consistent REST API, and generate OpenAPI documentation.

6 skills · pack

Reporting and summary skills for the Han suite. Turns feature specifications into plain-language stakeholder summaries (also called executive or business summaries) with diagrams, for sharing with non-technical stakeholders before implementation kicks off.

2 skills · pack

Results for “specification”

25 skills

create-specification

Create a structured specification file for a solution component, optimized for Generative AI consumption.

update-specification

Update an existing specification file for a solution, optimized for Generative AI consumption based on new requirements or code changes.

gen-specs-as-issues

Identify missing features in a project, prioritize them, and create detailed GitHub issues with specifications.

create-github-issue-feature-from-specification

Creates a GitHub issue from a specification file using a feature request template, checking for existing issues first.

create-github-issues-for-unmet-specification-requirements

Creates GitHub Issues for unimplemented requirements from specification files, checking the codebase and existing issues to avoid duplicates.

create-github-action-workflow-specification

Creates a formal, AI-optimized specification for an existing GitHub Actions CI/CD workflow, focusing on behavior and requirements rather than implementation details.

More results

Generate an llms.txt file from repository structure, following the llms.txt specification to help LLMs navigate and understand the project.

Update the llms.txt file in the repository root to reflect changes in documentation, specifications, or repository structure, following the llms.txt specification.

Generate comprehensive Product Requirements Documents (PRDs) for software systems and AI-powered features, including executive summaries, user stories, technical specifications, and risk analysis.

Analyzes a website's current design and user intent to produce a structured redesign specification, including product and design documents, a design system JSON, and a reasoning trace.

conventional-commit

Generate standardized commit messages following the Conventional Commits specification using a structured XML format.

create-implementation-plan

Generate structured, machine-readable implementation plans for features, refactoring, upgrades, or infrastructure changes.

Create standardized, semantic git commits using the Conventional Commits specification by analyzing diffs to determine type, scope, and message.

update-implementation-plan

Update an existing implementation plan file with new or updated requirements for features, refactoring, package upgrades, design, architecture, or infrastructure.

breakdown-epic-arch

Generates a high-level technical architecture specification for an epic from a Product Requirements Document, including system diagrams, component lists, and estimates.

nemotron-customize

Plan, configure, and chain Nemotron model customization steps into single-step or multi-step pipelines for curation, translation, fine-tuning, RL alignment, benchmarking, checkpoint conversion, optimization, and evaluation.

copilot-instructions-blueprint-generator

Generates a comprehensive copilot-instructions.md file that guides GitHub Copilot to produce code consistent with project standards, architecture patterns, and exact technology versions by analyzing existing codebase patterns.

openapi-to-application-code

Generate a complete, production-ready application from an OpenAPI specification using the active framework's conventions and best practices.

ask-questions-if-underspecified

Clarify requirements before implementing by asking targeted questions when a request has multiple plausible interpretations or key details are unclear.

spec-to-code-compliance

Verifies that blockchain code implements exactly what documentation specifies, identifying gaps between specs and implementation for audit engagements.

Generates llms.txt and llms-full.txt files that provide LLM-friendly access to wiki documentation, following the llms.txt specification.

conventional-branch

Create Git branches following the Conventional Branch specification (feature/, bugfix/, hotfix/, release/, chore/). Validates branch names and automates checkout from the correct base branch.

Scaffolds new agent skills conforming to the Agent Skills specification and dotnet/skills repository conventions, generating SKILL.md files with proper frontmatter and directory structures.

Create, synthesize, and iteratively improve agent skills following the Agent Skills specification. Handles source capture, precision passes, authoring, registration, and validation.

Generate an OpenAPI 3.1 specification from a browser-trace capture by analyzing observed HTTP traffic, templating URLs, and inferring JSON schemas from request/response samples.