Packs

6 packs

Build Spring Boot REST API

Scaffold a Spring Boot project and implement REST API following best practices.

3 skills · pack

Design REST API from Spec

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

6 skills · pack

Write API Documentation

Document REST API endpoints with OpenAPI specs and developer-friendly docs.

5 skills · pack

Build TypeSpec API for Copilot

Generate TypeSpec API plugin files with REST operations, authentication, and Adaptive Cards.

3 skills · pack

ATC.NET library skills including atc-net tools, e.g. REST API source generation from OpenAPI specs, WPF controls, cross-platform XAML development etc.

2 skills · pack

Simulator.Company platform assistant. Exposes the Simulator REST API as an MCP server and provides skills for managing actors, forms, graph structures, and financial accounts.

19 skills · pack

Results for “rest-api”

6 skills

superpowers-sage-wp-rest-api

WordPress REST API — register_rest_route, WP_REST_Controller, WP_REST_Request, REST namespace, custom endpoints, Application Passwords, JWT REST authentication, permission_callback, schema validation, WP_REST_Response, REST API versioning, rest_ensure_response, coexistence with Acorn Routes, register_rest_route vs routes/web.php decision, REST API debugging, wp rest-api namespace list, wp json discovery, CORS, REST nonce, cookie auth, REST API disable, JSON schema validation

cloudthinker-ai

Manages GLPI IT asset and service management by querying tickets, inventory, and CMDB via the GLPI REST API, producing structured reports.

Call Cheshire Terminal REST, MCP, discovery, and developer API surfaces for Solana agents, arena rooms, Upstash boxes, trading health, and OpenAPI. Use when integrating cheshireterminal.ai, /mcp, /.well-known/agent-card.json, ct_sk_ API keys, arena coordination, box handoff, or Apigee/zero-service health probes.

More results

cloudthinker-ai

Manages and analyzes incidents, post-incident reviews, and collaboration workflows in Allma via its REST API, covering incident discovery, timeline tracking, stakeholder communication, and retrospective analysis.

Use when building, refactoring, or documenting Graft apps and proxies, including when asked to create a tool server, API server, dual-protocol server, or MCP-HTTP bridge. Graft's core thesis: define tools once and serve them as both HTTP REST endpoints and MCP tools from the same server, with discovery, docs, and OpenAPI generated automatically. Covers concrete actions such as defining tools and handlers, configuring authentication middleware, setting up HTTP and stdio transports, generating OpenAPI documentation, wrapping existing APIs via proxy mode, and wiring up the full CLI workflow.

Designs the contract for an API change inside one codebase — a component's props, a function surface, URL or query parameters, an event payload, or a module boundary — through a discovery pass, an options document with one recommendation, a question round, and an adversarial validation round, with every element of the contract justified from one stated goal. Use when you want to design, shape, decide, or nail down an interface, contract, signature, or API change for a capability you can already describe, sized for roughly one pull request. Produces a design document and changes no code. Does not specify what a feature should do — use plan-a-feature. Does not plan delivery or sequencing — use plan-implementation. Does not assess the architecture of existing code — use architectural-analysis. Does not write the code — use tdd. Does not restructure existing code — use refactor. Runs its rounds without pausing for review; to review each round as it lands, use pairing.