stacks-http

Manage HTTP status codes, outbound requests, and reactive fetch operations in Stacks applications.

2|Updated Jul 8, 2026
One-click install
npx skills add https://github.com/bughq/bughq --skill stacks-http-bughq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stacks-http
Source: https://github.com/bughq/bughq/tree/main/.claude/skills/stacks-http
Command: npx skills add https://github.com/bughq/bughq --skill stacks-http-bughq

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @stacksjs/http, @stacksjs/httx, @stacksjs/composables.

What problem does it solve?

This Skill simplifies the complexity of managing HTTP status codes, executing outbound requests, and handling reactive data fetching within Stacks applications, reducing boilerplate and potential errors.

Core Features & Use Cases

  • Standardized Status Codes: Access a comprehensive Response enum for all HTTP status codes to ensure consistency across your application.
  • Robust Outbound Requests: Utilize the HttxClient for reliable HTTP requests featuring built-in retry logic, timeouts, and detailed timing metrics.
  • Reactive Fetching: Leverage useFetch and createFetch composables to easily manage reactive data fetching with a clean, chainable builder pattern.

Quick Start

Use the stacks-http skill to perform a GET request to the specified API endpoint and log the reactive data result.

Frequently Asked Questions about stacks-http

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage HTTP status codes and outbound requests in a Stacks application?

To manage HTTP status codes and outbound requests in a Stacks application, use a unified interface providing a comprehensive Response enum for all status codes to ensure consistency and reduce boilerplate.

How do I make type-safe API calls with built-in retry logic in TypeScript?

To make type-safe API calls with retry logic, utilize the HttxClient for reliable HTTP requests featuring built-in retry mechanisms, timeouts, and detailed timing metrics for complex network communication.

What is the best way to handle reactive data fetching in a Stacks frontend?

The best way to handle reactive data fetching in a Stacks frontend is leveraging the useFetch and createFetch composables to manage reactive data synchronization using native fetch with a clean, chainable builder pattern.

Does the Stacks HTTP client support timeout and error handling for network requests?

Yes, the Stacks HTTP client supports timeout and error handling for network requests by featuring built-in retry logic, timeouts, and detailed timing metrics to satisfy requirements for robust network communication.

Can I use native fetch for reactive API interactions without writing custom state management?

You can use native fetch for reactive API interactions without custom state management by leveraging the useFetch composable to easily manage reactive data fetching and synchronization automatically.

When should I use a chainable builder pattern for HTTP requests in a TypeScript project?

You should use a chainable builder pattern for HTTP requests in a TypeScript project when you need to streamline complex, retry-enabled network communication and require type-safe HTTP status management with reactive fetch operations.