Agent skill

Frontend Request Skill

by jiushiwon in jiushiwon/wg-skills

A skill your agent uses when designing or reviewing the request layer of a frontend project (web / uni-app / mini-program), including request.ts wrappers, interceptors, deduplication, mocks, error…

Apache-2.0Auto-check passedBackend & APIs

Install Frontend Request Skill

skills CLI
$ npx skills add jiushiwon/wg-skills --skill frontend-request-skill -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jiushiwon/wg-skills frontend-request-skill --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jiushiwon/wg-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/vibeCoding/frontend/frontend-request-skill .claude/skills/frontend-request-skill && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
frontend-request-skill
GitHub stars
112
Token cost
~3.6k tokens
SKILL.md length
788 words
Files
10 (incl. references)
Skills in repo
12
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses when designing or reviewing the request layer of a frontend project (web / uni-app / mini-program), including request.ts wrappers, interceptors, deduplication, mocks, error…

  • Works in 8 steps: 统一入口 → 鉴权衔接 → 游客模式 → …
  • Reviewing the request layer of a frontend project (web / uni-app / mini-program)
  • SKILL.md covers 定位, 前后端契约(强约定), 解决的问题 and When to Use, plus 9 more sections
  • Needs NO_AUTH_TOKEN

What it does

Frontend Request Skill is an agent skill from jiushiwon/wg-skills. Use when designing or reviewing the request layer of a frontend project (web / uni-app / mini-program), including request.ts wrappers, interceptors, deduplication, mocks, error handling, file upload, SSE streaming, or token refresh. Provides both a general frontend specification and a uniapp-specific adapter.

Its SKILL.md is about 3.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including reference files (for example `README.md`, `references/api-contract.md` and `references/auth-patterns.md`).

It sits in Backend & APIs, covering File uploads and storage, Data cleaning and API design. It works with React and Vue.js. The licence is Apache-2.0.

When your agent uses it

  • Reviewing the request layer of a frontend project (web / uni-app / mini-program)
  • Including request.ts wrappers

Example prompts

  • “/frontend-request-skill”

Requirements

  • Python 3
  • Node.js

Workflow steps

8 steps, taken from the step headings in SKILL.md.

  1. 统一入口
  2. 鉴权衔接
  3. 游客模式
  4. 防抖去重
  5. Mock 机制
  6. 错误处理
  7. SSE 流式请求
  8. Token 自动刷新与失败重试

What it can do on your machine

Read from SKILL.md and the folder at commit 3569fb8. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • NO_AUTH_TOKEN

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Frontend Request Skill loads about 3.6k tokens when it runs, and up to ~30k if it reads all its reference files. Until then it costs about 83 tokens; SKILL.md has 788 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~83
When it runs · the whole SKILL.md, loaded when a task matches
~3.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~30k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jiushiwon/wg-skills at commit 3569fb8, republished under its Apache-2.0 licence (© jiushiwon). 788 words, ~3,559 tokens.

Download SKILL.mdSave it as .claude/skills/frontend-request-skill/SKILL.md (or your agent's skills folder). This skill also uses 9 other files; get the full folder from GitHub.
name
frontend-request-skill
description
Use when designing or reviewing the request layer of a frontend project (web / uni-app / mini-program), including request.ts wrappers, interceptors, deduplication, mocks, error handling, file upload, SSE streaming, or token refresh. Provides both a general frontend specification and a uniapp-specific adapter.

前端请求层设计 Skill

定位

只聚焦前端请求层设计:从 request.ts 出发,建立统一、健壮、可维护的请求体系。

本 skill 提供两层规范:

  1. 通用前端规范:面向 Web/H5/React/Vue 等标准前端项目,基于 fetch / axios 实现。
  2. uniapp 适配规范:面向 uni-app 小程序/APP/H5 跨端项目,基于 uni.request 实现。

二者核心思想完全一致(统一入口、响应信封、鉴权拦截、错误码映射、Token 刷新队列、SSE、上传),仅底层网络 API 不同。

本 skill 只处理请求相关逻辑,不依赖其他 skill。

前后端契约(强约定)

本 skill 的所有规范必须与 references/api-contract.md 严格对齐。

该契约文档是前后端桥接的唯一真理源,定义:

  • 接口存放位置(vue/uniapp/react 统一 src/api/)
  • 登录页/管理页接口契约
  • 请求头规范(Authorization / Content-Type / X-Request-ID)
  • 响应信封 { code, message, data }
  • 错误码契约(code<0 异常,>=0 成功,-1 特殊 = JWT 鉴权失效)
  • showError 参数语义(默认 false 自动弹,true 调用方自己处理)
  • HTTP 500 兜底(强制 swallow 用户 Toast,交给全局错误处理)

强约定:

  • 后端新生成业务 → 必须更新后端 api-contract.md
  • 前端新加接口 → 必须读取契约,按契约定义路径/字段/code
  • 契约变更必须前后端同步

解决的问题

痛点后果本技能方案
每个页面各自调原生请求鉴权/错误处理重复统一 request.ts
Token 过期无感知用户操作失败响应拦截器识别 401,统一交给 auth service 处理
重复点击导致重复请求数据异常/资源浪费防抖去重
后端接口未 ready前端阻塞Mock 机制
游客误触敏感接口报错/白屏请求层前置拦截
错误提示不统一用户体验差统一错误通知
SSE/流式接口不知如何接入聊天/AI 回复无法流式展示跨端 SSE 封装 + 打字机效果
Token 过期后并发请求全部失败用户重复登录、数据丢失Token 刷新队列 + 失败请求自动重试

When to Use

  • "请求封装"
  • "request.ts 怎么写"
  • "前端请求统一处理"
  • "uniapp 请求统一处理"
  • "接口拦截"
  • "Token 刷新"(请求层衔接部分,详见 references/auth-patterns.md)
  • "游客模式拦截"
  • "Mock 数据配置"
  • "接口防抖"
  • "错误处理"
  • "文件上传"
  • "SSE 流式请求"
  • "打字机效果"
  • "Server-Sent Events"
  • "AI 聊天流式回复"

When NOT to Use

  • 需要完整登录鉴权/权限设计 → 本 skill 只提供请求层衔接,完整鉴权体系需单独设计
  • 需要项目整体规范化/目录结构诊断 → 不在本 skill 范围内
  • 需要跨平台兼容性审计 → 不在本 skill 范围内

两层规范速查

规范适用场景底层 API参考位置
通用前端规范Web / H5 / React / Vue 等fetch / axiosreferences/frontend-spec.md
uniapp 适配规范微信小程序 / App / H5uni.request / uni.uploadFilereferences/uniapp-spec.md

二者仅在「底层网络 API」和「Token 存储方式」上有差异;响应信封、错误码、鉴权拦截、去重、Mock、SSE 解析逻辑完全一致。

Quick Reference

能力关键选项参考位置
前后端契约接口位置 / 错误码 / JWTreferences/api-contract.md
统一请求request<T>(options)references/frontend-spec.md、references/uniapp-spec.md
Token 注入needAuth、authModereferences/auth-patterns.md
401/403 处理skipAuthHandlerreferences/auth-patterns.md
防抖去重skipDebouncereferences/request-impl.md
Mock 数据USE_MOCKreferences/mock-guide.md
错误提示showErrorreferences/error-handling.md
文件上传upload<T>(options)references/error-handling.md
SSE 流式请求sse<T>(options, onMessage)references/sse-guide.md
Token 自动刷新auth.service.ts 队列references/auth-patterns.md

核心文件结构

强约定:所有前端项目(vue / uniapp / react)接口统一存放在 src/api/ 下。

详细目录约定见 api-contract.md §2。

src/
├── api/                       # 前后端桥接层(frontend-request-skill 管理)
│   ├── request.ts             # 统一请求封装(核心)
│   ├── upload.ts              # 文件上传封装
│   ├── sse.ts                 # SSE 流式请求封装
│   ├── modules/               # 业务模块 API(auth / user / role / menu / ...)
│   ├── _mocks_/               # Mock 数据字典
│   │   ├── index.ts           # MOCK_MAP + MockEntry
│   │   └── *.mock.ts          # 各模块 Mock
│   └── types/                 # 接口请求/响应类型
├── services/
│   └── auth.service.ts        # 鉴权服务:login / logout / handleUnauthorized
├── config/
│   ├── api.config.ts          # BASE_URL / 超时 / Mock / 成功码 / 鉴权失败码 / 重试
│   └── error.config.ts        # 错误码映射(与 api-contract.md 错误码表对齐)
├── utils/
│   ├── auth.ts                # getToken / setToken
│   ├── toast.ts               # 错误提示工具
│   └── error.ts               # 错误信息提取
└── composables/
    ├── useAuth.ts             # 游客判断 Hook
    └── useTypewriter.ts       # 打字机效果 Hook

禁止把接口散落到 pages/api/、views/api/、utils/api/、service/ 等位置。

uniapp 项目同样使用 src/api/,H5/小程序/App 三端一致。

响应信封与错误约定

本 skill 采用统一的响应结构(响应信封),与后端接口契约严格对齐:

typescript
export interface ApiResponse<T = any> {
  code: number;    // 业务状态码
  message: string; // 提示信息
  data: T;         // 业务数据
}
业务状态码约定(与 api-contract.md §7 严格对齐)
code 范围含义处理方式
code = 0业务成功正常返回 data
code < 0业务异常抛出 RequestError,错误码为对应的负数值
code = -1JWT 鉴权失效(未登录 / Token 无效 / 过期 / 未传递)触发 Token 刷新流程,等同 HTTP 401
code > 0按项目约定(若存在)默认也视为业务异常

本项目示例默认 SUCCESS_CODES = [0]、AUTH_FAILURE_CODES = [-1]。如果你的后端约定不同,请在 src/config/api.config.ts 中调整。

showError 参数语义(与 api-contract.md §8 严格对齐)

核心约定:默认请求层自动弹 Toast,传 showError: true 时不弹,调用方自己处理。

取值含义默认
false(默认)请求层按 ERROR_CODE_MAP 自动弹 Toast✅
true请求层不弹,调用方自行 try/catch 处理—

设计理由:默认自动弹覆盖 80% 场景(页面直取数据);少数特殊场景(轮询、上传队列、批量提交)传 showError: true 让调用方自己处理。

HTTP 500 错误兜底(与 api-contract.md §9 严格对齐)

HTTP 500 / 502 / 503 / 504 类错误前端不弹任何用户 Toast。

理由:500 是服务端问题,用户弹 Toast 也无法解决;交给全局错误处理(Sentry / 监控平台 / 后端日志)。

业务调用方仍可感知(用于降级逻辑),但用户无感。

HTTP 状态异常

HTTP 层错误与业务 code 互不干扰,统一由 statusCode 判断:

HTTP 状态错误码场景
401UNAUTHORIZED登录过期,触发 Token 刷新
403FORBIDDEN权限不足
400 / 404 / 500 等HTTP_ERROR请求异常
超时 / 断网TIMEOUT / NETWORK_ERROR网络异常
错误码映射约定

src/config/error.config.ts 中的 ERROR_CODE_MAP 用于把错误码转成用户友好文案。本 skill 内置的映射仅为示例,你必须按自己后端的真实 code 约定替换:

typescript
export const ERROR_CODE_MAP: Record<string, string> = {
  // HTTP 状态异常(请求层)
  UNAUTHORIZED: '登录已过期,请重新登录',
  FORBIDDEN: '权限不足',
  TIMEOUT: '请求超时,请检查网络',
  NETWORK_ERROR: '网络异常,请稍后重试',

  // 业务异常示例(按 code < 0 约定,需与后端契约保持一致)
  '-1001': '参数校验错误',
  '-1002': '未登录或 Token 无效',
  '-1003': '无权限',
  '-1004': '资源不存在',
  '-1005': '资源冲突',
  '-1006': '请求过于频繁',
  '-2000': '系统繁忙,请稍后再试',
};

重要:以上错误码与各 init-skill 内置契约(fastapi-init-skill、springboot-init-skill 等)保持一致。接入真实项目时,请与后端确认错误码表并替换。

分页约定

前后端统一的分页请求/响应格式:

请求参数:

参数类型默认说明
pagenumber1页码,从 1 开始
pageSizenumber20每页条数,上限 100

响应结构(在 data 内):

typescript
export interface PageResponse<T> {
  list: T[];       // 数据列表
  total: number;   // 总条数
  page: number;    // 当前页码
  pageSize: number; // 每页条数
}

各后端 init-skill(springboot / fastapi / go-gin)的分页格式已对齐此约定。

Token 响应约定

后端登录接口返回 Token 时,统一使用以下字段:

typescript
export interface TokenResponse {
  accessToken: string;   // 访问令牌(Java 后端 camelCase,Python 后端 snake_case 兼容)
  refreshToken: string;  // 刷新令牌
  tokenType: string;     // 固定 "Bearer"
  expiresIn: number;     // 过期时间(秒)
}

注意:Java 后端使用 camelCase,Python 后端使用 snake_case。前端必须做兼容处理(优先 camelCase,fallback snake_case),详见 api-contract.md §10。

JWT 鉴权约定(所有骨架统一)

强约定:所有后端骨架(Go / Java / Python / NodeJS)必须使用 JWT 做无状态鉴权。

请求头:Authorization: Bearer <token>。

失效标识:HTTP 401 或 code === -1。

完整规范见 api-contract.md §11。

设计要点

1. 统一入口
typescript
// src/api/request.ts
export interface RequestOptions {
  url: string;
  method?: 'GET' | 'POST' | 'PUT' | 'DELETE' | 'OPTIONS' | 'HEAD';
  data?: any;                // 请求体:通常为 plain object
  header?: Record<string, string>;
  timeout?: number;
  needAuth?: boolean;        // 是否需要 Token,默认 true
  showError?: boolean;       // 是否在请求层弹出错误 Toast;默认 false(自动弹)。true 时不弹,调用方自行处理
  skipDebounce?: boolean;    // 是否跳过防抖,默认 false
  skipAuthHandler?: boolean; // 是否跳过 401 处理,默认 false
  prefix?: string;           // API 前缀,默认 DEFAULT_PREFIX
  authMode?: 'bearer' | 'customer-token'; // Token 头格式
  retry?: number;            // 失败重试次数,默认 REQUEST_RETRY_COUNT
}

export interface RequestPromise<T> extends Promise<ApiResponse<T>> {
  __abort?: () => void;
}

export interface ApiResponse<T = any> {
  code: number;
  message: string;
  data: T;
}

export interface UploadOptions {
  url: string;
  file: File | string;       // 通用前端用 File;uniapp 用文件路径 string
  name?: string;
  formData?: Record<string, any>;
  header?: Record<string, string>;
  timeout?: number;
  onProgress?: (progress: number) => void; // 0-100
}

export function request<T = any>(options: RequestOptions): RequestPromise<T>;
export function get<T = any>(
  url: string,
  data?: any,
  options?: Omit<RequestOptions, 'url' | 'method' | 'data'>
): RequestPromise<T>;
export function post<T = any>(
  url: string,
  data?: any,
  options?: Omit<RequestOptions, 'url' | 'method' | 'data'>
): RequestPromise<T>;
export function put<T = any>(
  url: string,
  data?: any,
  options?: Omit<RequestOptions, 'url' | 'method' | 'data'>
): RequestPromise<T>;
export function del<T = any>(
  url: string,
  data?: any,
  options?: Omit<RequestOptions, 'url' | 'method' | 'data'>
): RequestPromise<T>;
export function upload<T = any>(options: UploadOptions): Promise<T>; // 直接返回业务 data,不包 ApiResponse

完整实现见 references/frontend-spec.md(通用前端)与 references/uniapp-spec.md(uniapp 适配)。

2. 鉴权衔接

本 skill 只负责请求层与鉴权的衔接点:

  • 默认请求自动注入 Token
  • 支持 needAuth: false 跳过(如登录接口本身)
  • 支持 authMode: 'bearer' | 'customer-token' 切换鉴权头格式
  • 401/403 响应交给 auth.service.ts 统一处理
  • 登录态来源可由项目自行选择:Storage 最小化方案 或 Pinia userStore 方案

重要:通用前端示例默认使用 localStorage;uniapp 示例默认使用 uni.getStorageSync('token')。如果你使用 Pinia 管理登录态,请参考 references/auth-patterns.md 替换为 userStore 方案,请求层代码无需改动。

详细 Token 管理、401/403 处理、Token 刷新队列、登出回跳等见 references/auth-patterns.md。

Show full SKILL.md (298 more words)Show less
3. 游客模式

请求层只做最小拦截:

typescript
import { formatError } from '@/utils/error';

if (options.needAuth !== false && !getToken()) {
  return Promise.reject(formatError('NO_AUTH_TOKEN', '未登录'));
}

业务层建议前置检查:

typescript
const { checkLogin } = useAuth();

function handleLike() {
  if (!checkLogin()) return;
  post('/api/like', { id: itemId });
}
4. 防抖去重
  • 同一 key 的并发请求只发一次,返回同一个 Promise
  • 请求完成后清理 pending,释放内存
  • 提交类接口可设置 skipDebounce: true
5. Mock 机制
  • 通过全局开关 USE_MOCK 控制:开启后所有请求强制走 Mock,关闭后全部走真实接口
  • Mock 数据建议按接口字段契约声明类型(MockEntry<T>)
  • 支持精确匹配 METHOD:/path 和 REST 路径参数匹配
  • 见 references/mock-guide.md
6. 错误处理
  • 统一错误信息提取(message / msg / error / detail)
  • 开发环境 Modal 展示完整错误,生产环境 Toast/Modal 分级提示
  • 文件上传单独封装
  • 见 references/error-handling.md
7. SSE 流式请求
  • 封装 sse<T>(options, onMessage, onError?),支持 H5 EventSource 与小程序 enableChunked 双端
  • 自动注入 Token、401 识别、手动中断
  • 流式 chunk 解析 + 数据行缓存,适用于 AI 聊天、打字机效果
  • 见 references/sse-guide.md
8. Token 自动刷新与失败重试
  • HTTP 401 触发静默刷新
  • 刷新期间新请求入队,刷新成功后自动重发
  • 刷新失败统一登出,避免用户反复登录
  • 见 references/auth-patterns.md

Common Mistakes

错误后果正确做法
在请求层写死鉴权跳转逻辑与 auth skill 重复、难以维护请求层只识别 401/403,统一交给 auth.service.ts
把 401 重试/Token 刷新在每个 API 里单独实现代码重复、并发刷新导致多次登录使用队列式 Token 刷新,统一收口到 auth.service.ts
并发请求未做去重重复点击导致重复提交用 Map 缓存同一 key 的 pending Promise
JSON.stringify 直接生成请求 key属性顺序不同导致 key 不同,去重失效递归排序 key 后序列化
statusCode !== 200 判断成功201/204 等合法状态被误判200 <= statusCode < 300
Mock 数据写进生产包数据泄露、行为异常Mock 仅由 VITE_USE_MOCK 控制,生产环境设为 false
文件上传复用 request 的防抖大文件/多次选择文件被错误去重上传单独封装,不走 request 防抖
SSE 在小程序端使用 H5 的 EventSource小程序无原生 EventSource,直接报错使用 enableChunked + 手动解析 chunk
SSE 不处理连接中断/页面卸载内存泄漏、重复回调返回可中断的 requestTask,页面 onUnload 时调用
401 时直接重试原请求但不刷新 Token重试仍失败,陷入死循环先刷新 Token,再重试队列中的请求
Token 刷新不排队并发刷新导致多次登录请求使用 isRefreshing + Promise 队列
接口散落到 pages/api/、views/api/、service/跨项目无法复用,Mock 难统一强约定:所有前端项目(vue/uniapp/react)统一放 src/api/,见 api-contract.md §2
凭直觉写接口路径/字段前后端不对齐,联调失败强约定:新加接口必须读 api-contract.md,没有就更新
HTTP 500 给用户弹"服务器繁忙" Toast用户看到无意义提示,无法自助解决强约定:500 类错误请求层 swallow,交给全局错误处理,见 api-contract.md §9
把业务异常用 showError: true 隐藏用户不知道发生了什么showError: true 只用于轮询 / 静默重试 / 自定义提示场景

输出

触发本 skill 时,按以下优先级输出:

  1. 契约对齐:先读 references/api-contract.md,确认接口位置 / 错误码 / JWT 约定
  2. 问题诊断:当前请求层存在的主要问题(重复代码、缺拦截器、错误处理散落等)
  3. 结构方案:推荐的 src/api/、src/config/、src/utils/、src/services/ 文件划分
  4. 核心代码:给出或修正 request.ts、upload.ts、错误处理工具的实现
  5. 衔接说明:明确哪些逻辑属于请求层、哪些应收口到 auth.service.ts
  6. 进阶能力:按需补充 SSE 流式请求、Token 自动刷新队列、失败重试
  7. 参考引用:复杂实现直接引用 references/ 中的对应文档

职责边界

范畴本 skill 负责本 skill 不负责
请求封装request.ts、拦截器、去重、Mock、错误提示、上传、SSE 衔接—
鉴权实现请求层 Token 注入、401/403 识别、刷新触发点Token 管理、登录态、登出回跳等完整鉴权体系
Token 刷新队列—推荐由 auth.service.ts 统一实现,请求层只负责触发与重试
项目规范—目录结构、命名规范等通用规范
跨平台审计—多端兼容性检查

与后端规范的联动

本 skill 的响应信封、错误码、JWT、请求头规范以 references/api-contract.md 为准。

  • 后端 EnvelopeRoute 输出 { code, message, data }
  • 前端 request.ts 按相同结构解析
  • ERROR_CODE_MAP 直接复用契约 §7 错误码表
  • JWT 鉴权 + code === -1 失效标识由契约 §11 约束

后端 init-skill(fastapi-init-skill / springboot-init-skill / go-gin-init-skill / nodejs-init-skill)必须生成与 references/api-contract.md 兼容的 api-contract.md,否则前后端无法桥接。

© jiushiwon, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 9 other files (references) in vibeCoding/frontend/frontend-request-skill of jiushiwon/wg-skills.

  • SKILL.md
  • README.md
  • references/api-contract.md
  • references/auth-patterns.md
  • references/error-handling.md
  • references/frontend-spec.md
  • references/mock-guide.md
  • references/request-impl.md
  • references/sse-guide.md
  • references/uniapp-spec.md

Open the folder on GitHubat commit 3569fb8

Compare with similar skills

Frontend Request Skill next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Frontend Request Skill compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Frontend Request Skill this skilljiushiwon/wg-skills112—~3.6kAutomated safety check: PassApache-2.0
API Reviewermitchdenny/hex1b178—~4kAutomated safety check: PassMIT
Livewire Developmentcoollabsio/coolify63k—~964Automated safety check: PassMIT
Livewire Developmentyungifez/skuul4091 repos~1.9kAutomated safety check: PassMIT
Databuddydatabuddy-analytics/Databuddy1.2k—~2.1kAutomated safety check: PassAGPL-3.0
Edgestore Setupedgestorejs/edgestore454—~1.8kAutomated safety check: PassMIT

Similar skills

  • API Reviewer

    mitchdenny/hex1b

    Guidelines for reviewing API design in the Hex1b codebase. An agent skill from mitchdenny/hex1b.

    178 GitHub stars~4k tokensUpdated 6 days ago
    Backend & APIsAuto-check passed
  • Livewire Development

    coollabsio/coolify

    A skill your agent uses for any task or question involving Livewire.

    63k GitHub stars~964 tokensUpdated yesterday
    Backend & APIsAuto-check passed
  • Livewire Development

    yungifez/skuul

    A skill your agent uses for any task or question involving Livewire.

    409 GitHub starsUsed in 1 repo~1.9k tokens
    Backend & APIsAuto-check passed
  • Databuddy

    databuddy-analytics/Databuddy

    Integrate Databuddy analytics using the SDK, REST API, or MCP.

    1.2k GitHub stars~2.1k tokensUpdated yesterday
    Backend & APIsAuto-check passed
  • Edgestore Setup

    edgestorejs/edgestore

    A skill your agent uses when adding, extending, or troubleshooting EdgeStore file uploads, upload UI, or bucket access policies in a TypeScript/React application.

    454 GitHub stars~1.8k tokensUpdated 2 days ago
    Backend & APIsAuto-check passed
  • Wayfinder Development

    slimani-dev/muraqib

    A skill your agent uses for Laravel Wayfinder which auto-generates typed functions for Laravel controllers and routes.

    128 GitHub starsUsed in 1 repo~622 tokens
    Backend & APIsAuto-check passed

More from jiushiwon/wg-skills

All 12 skills in this repo
  • Frontend UI Foundry

    jiushiwon/wg-skills

    A skill your agent uses when generating UI for a specific scenario (mobile/PC/官网/管理端/营销页/文档/金融/原生/3D), when refactoring an existing HTML/Vue/React project to a unified design system, when extracting…

    112 GitHub stars~1.4k tokensUpdated yesterday
    Auto-check passed
  • Workflow Diagram Skill

    jiushiwon/wg-skills

    A skill your agent uses when 用户想用一句话生成流程图、工作流图解、开发流程图、AI 流程图或任何步骤型图解,支持多风格输出(flat icon / 暖白手账风 / dark / cute),并提供现成模板一键出图。

    112 GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed
  • Uniapp App Generate Skill

    jiushiwon/wg-skills

    This skill should be used when the user wants to create a standardized uni-app project for WeChat mini-program, H5, and App from scratch.

    112 GitHub stars~5k tokensUpdated yesterday
    Auto-check: notes
  • Fastapi Init Skill

    jiushiwon/wg-skills

    FastAPI 项目一键初始化技能。面向零基础小白,提供环境探测、自动安装、完整 Web 骨架生成、SSE 流式框架、JWT 鉴权、统一响应封装、文件上传接口、一键启动/重启脚本、Swagger 文档,内置 MySQL(默认)/ PostgreSQL / MongoDB 数据库选择。用户只需说"帮我搭一个 FastAPI 项目"即可一条命令完成从零到跑的完整链路。触发词:"FastAPI…

    112 GitHub stars~1.8k tokensUpdated yesterday
    Auto-check: notes
  • Ffmpeg Skill

    jiushiwon/wg-skills

    FFmpeg 多媒体处理技能 — 将自然语言描述转为正确的 ffmpeg 命令,覆盖视频剪辑、转码、水印、合成、提取、生成等操作。内置一键安装脚本(Windows/Mac/Linux)。触发词:ffmpeg、视频剪辑、视频裁剪、视频转码、视频压缩、去水印、加水印、视频拼接、视频合成、提取音频、视频转…

    112 GitHub stars~1.4k tokensUpdated yesterday
    Auto-check passed
  • React Generate Skill

    jiushiwon/wg-skills

    This skill should be used when the user wants to create a standardized React 18 + TypeScript + Vite + Zustand project from scratch.

    112 GitHub stars~2.8k tokensUpdated yesterday
    Auto-check passed

Works with

Questions about Frontend Request Skill

What does Frontend Request Skill do?

A skill your agent uses when designing or reviewing the request layer of a frontend project (web / uni-app / mini-program), including request.ts wrappers, interceptors, deduplication, mocks, error…. Frontend Request Skill is an agent skill from jiushiwon/wg-skills.ts wrappers, interceptors, deduplication, mocks, error handling, file upload, SSE streaming, or token refresh.

When should I use Frontend Request Skill?

Frontend Request Skill fits situations like: reviewing the request layer of a frontend project (web / uni-app / mini-program); including request.ts wrappers.

How do I install Frontend Request Skill in Claude Code?

Run `npx skills add jiushiwon/wg-skills --skill frontend-request-skill -a claude-code`. Or copy the skill folder (vibeCoding/frontend/frontend-request-skill in jiushiwon/wg-skills) into .claude/skills/frontend-request-skill in your project. Claude Code loads it when a task matches its description.

How do I install Frontend Request Skill in Codex?

Run `npx skills add jiushiwon/wg-skills --skill frontend-request-skill -a codex`. Or copy the skill folder (vibeCoding/frontend/frontend-request-skill in jiushiwon/wg-skills) into .agents/skills/frontend-request-skill in your project. Codex loads it when a task matches its description.

Can I use Frontend Request Skill in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jiushiwon/wg-skills --skill frontend-request-skill -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/frontend-request-skill, .gemini/skills/frontend-request-skill, .github/skills/frontend-request-skill and .opencode/skills/frontend-request-skill in your project.

What does Frontend Request Skill need to run?

Going by SKILL.md and its folder, Frontend Request Skill needs credentials named NO_AUTH_TOKEN. Our summary lists: Python 3; Node.js.

Does Frontend Request Skill access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Frontend Request Skill safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Frontend Request Skill use?

Frontend Request Skill is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Frontend Request Skill use?

About 3.6k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 26k tokens, read only when the agent opens those files.

What are the alternatives to Frontend Request Skill?

Skills that share tags, products or a category with Frontend Request Skill: API Reviewer (mitchdenny/hex1b, 178 stars), Livewire Development (coollabsio/coolify, 63k stars), Livewire Development (yungifez/skuul, 409 stars) and Databuddy (databuddy-analytics/Databuddy, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Frontend Request Skill?

jiushiwon (a GitHub user) maintains it in jiushiwon/wg-skills, which has 112 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 7, 2026.

Source: jiushiwon/wg-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.