Token导航 LogoToken导航

Agent Skill · 前端设计

grey-haven-api-design(grey haven API 设计)

用于辅助 API 设计、接口文档、请求响应结构和服务集成说明。它适合让 Agent 梳理 endpoint、生成 OpenAPI 草稿、检查字段命名、整理错误码或辅助前后端联调。使用时需要确认真实业务语义、鉴权方式、分页和错误处理规则;涉及生成接口文档时,应避免凭空补字段,最好从现有代码、schema 或接口样例中提取事实。

grey-haven-api-design 是前端设计类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描已通过,按安装量在前端设计类的 10,216 个 Skill 里排第 8,327。

总安装 294周安装 12GitHub Stars 24下载 94核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:grey-haven-api-design(grey haven API 设计)
来源仓库:https://github.com/greyhaven-ai/claude-code-config
仓库路径:skills/grey-haven-api-design
安装命令:
npx skills add https://github.com/greyhaven-ai/claude-code-config --skill grey-haven-api-design
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/greyhaven-ai/claude-code-config --skill grey-haven-api-design

这个 Skill 是做什么的

前端设计类 Skill 关注页面结构、视觉规范和组件写法,输出通常是可运行的界面代码。

用于辅助 API 设计、接口文档和错误码整理,支持 OpenAPI 草稿生成。它适合梳理 endpoint、检查字段命名和鉴权规则,辅助前后端联调。使用时需确认真实业务语义和分页逻辑,避免凭空补字段或接口定义。

安装命令:npx skills add https://github.com/greyhaven-ai/claude-code-config --skill grey-haven-api-design。建议从现有代码或样例中提取事实,不要虚构请求响应结构。

来源仓库内路径:skills/grey-haven-api-design

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/greyhaven-ai/claude-code-config --skill grey-h…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

grey-haven-api-design 怎么安装?

在终端执行 npx skills add https://github.com/greyhaven-ai/claude-code-config --skill grey-haven-api-d…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

grey-haven-api-design 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

grey-haven-api-design 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

grey-haven-api-design 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

grey-haven-api-design 用的人多吗?

公开数据是累计安装 294 次,近一周安装 12 次,下载 94 次,GitHub 24 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

grey-haven-api-design 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理前端设计类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

前端设计类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
frontend-design

前端设计 · Codex、Claude

8,823,360126,072只读MIT通过
vercel-composition-patterns

Vercel 组合模式 · Codex、Claude

3,858,81625,893需要联网MIT通过
vercel-react-native-skills

Vercel React native skills 前端 · Codex、Claude

2,468,66425,878只读MIT通过
adapt

adapt 搜索 · Codex、Claude

2,027,04023,125操作浏览器未明确通过
bolder

bolder 分析 · Codex、Claude

2,004,28823,130只读未明确通过
grey-haven-api-design

grey haven API 设计 · 本页

29424需要联网未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Grey Haven API Design Standards

RESTful API design for FastAPI backends and TanStack Start server functions.

Follow these standards when creating API endpoints, defining schemas, and handling errors in Grey Haven projects.

Supporting Documentation

  • examples/ - Complete endpoint examples (all files <500 lines)

- fastapi-crud.md - CRUD endpoints with repository pattern - pydantic-schemas.md - Request/response schemas - tanstack-start.md - Server functions - pagination.md - Pagination patterns - testing.md - API testing

  • reference/ - Configuration references (all files <500 lines)

- fastapi-setup.md - Main app configuration - openapi.md - OpenAPI customization - error-handlers.md - Exception handlers - authentication.md - JWT configuration - cors-rate-limiting.md - CORS and rate limiting

Quick Reference

RESTful Resource Design

URL Patterns:

  • ✅ /api/v1/users (plural nouns, lowercase with hyphens)
  • ✅ /api/v1/organizations/{org_id}/teams (hierarchical)
  • ❌ /api/v1/getUsers (no verbs in URLs)
  • ❌ /api/v1/user_profiles (no underscores)

HTTP Verbs:

  • GET - Retrieve resources
  • POST - Create new resources
  • PUT - Update entire resource
  • PATCH - Update partial resource
  • DELETE - Remove resource

HTTP Status Codes

Success:

  • 200 OK - GET, PUT, PATCH requests
  • 201 Created - POST request (resource created)
  • 204 No Content - DELETE request

Client Errors:

  • 400 Bad Request - Invalid request data
  • 401 Unauthorized - Missing/invalid authentication
  • 403 Forbidden - Insufficient permissions
  • 404 Not Found - Resource doesn't exist
  • 409 Conflict - Duplicate resource, concurrent update
  • 422 Unprocessable Entity - Validation errors

Server Errors:

  • 500 Internal Server Error - Unhandled exception
  • 503 Service Unavailable - Database/service down

Multi-Tenant Isolation

Always enforce tenant isolation:

# Extract tenant_id from JWT
repository = UserRepository(db, tenant_id=current_user.tenant_id)

# All queries automatically filtered by tenant_id
users = await repository.list()  # Only returns users in this tenant

FastAPI Route Pattern

from fastapi import APIRouter, Depends, HTTPException, status

router = APIRouter(prefix="/api/v1/users", tags=["users"])

@router.post("", response_model=UserRead, status_code=status.HTTP_201_CREATED)
async def create_user(
    user_data: UserCreate,
    db: Session = Depends(get_db),
    current_user: User = Depends(get_current_user),
) -> UserRead:
    """Create a new user in the current tenant."""
    repository = UserRepository(db, tenant_id=current_user.tenant_id)
    user = await repository.create(user_data)
    return user

See examples/fastapi-crud.md for complete CRUD endpoints.

Pydantic Schema Pattern

from pydantic import BaseModel, EmailStr, Field, ConfigDict

class UserCreate(BaseModel):
    """Schema for creating a new user."""
    email: EmailStr
    full_name: str = Field(..., min_length=1, max_length=255)
    password: str = Field(..., min_length=8)

class UserRead(BaseModel):
    """Schema for reading user data (public fields only)."""
    id: str
    tenant_id: str
    email: EmailStr
    full_name: str
    created_at: datetime

    model_config = ConfigDict(from_attributes=True)

See examples/pydantic-schemas.md for validation patterns.

TanStack Start Server Functions

// app/routes/api/users.ts
import { createServerFn } from "@tanstack/start";
import { z } from "zod";

const createUserSchema = z.object({
  email: z.string().email(),
  fullName: z.string().min(1).max(255),
});

export const createUser = createServerFn({ method: "POST" })
  .validator(createUserSchema)
  .handler(async ({ data, context }) => {
    const authUser = await getAuthUser(context);
    // Create user with tenant isolation
  });

See examples/tanstack-start.md for complete examples.

Error Response Format

{
  "error": "User with ID abc123 not found",
  "status_code": 404
}

Validation errors:

{
  "error": "Validation error",
  "detail": [
    {
      "field": "email",
      "message": "value is not a valid email address",
      "code": "value_error.email"
    }
  ],
  "status_code": 422
}

See reference/error-handlers.md for exception handlers.

Pagination

Offset-based (simple):

@router.get("", response_model=PaginatedResponse[UserRead])
async def list_users(skip: int = 0, limit: int = 100):
    users = await repository.list(skip=skip, limit=limit)
    total = await repository.count()
    return PaginatedResponse(items=users, total=total, skip=skip, limit=limit)

Cursor-based (recommended for large datasets):

@router.get("")
async def list_users(cursor: Optional[str] = None, limit: int = 100):
    users = await repository.list_cursor(cursor=cursor, limit=limit)
    next_cursor = users[-1].id if len(users) == limit else None
    return {"items": users, "next_cursor": next_cursor}

See examples/pagination.md for complete implementations.

Core Principles

1. Repository Pattern

Always use tenant-aware repositories:

  • Extract tenant_id from JWT claims
  • Pass to repository constructor
  • All queries automatically filtered
  • Prevents cross-tenant data leaks

2. Pydantic Validation

Define schemas for all requests/responses:

  • {Model}Create - Fields for creation
  • {Model}Read - Public fields for responses
  • {Model}Update - Optional fields for updates
  • Never return password hashes or sensitive data

3. OpenAPI Documentation

FastAPI auto-generates docs:

  • Add docstrings to all endpoints
  • Use summary, description, response_description
  • Document all parameters and responses
  • Available at /docs (Swagger UI) and /redoc (ReDoc)

See reference/openapi.md for customization.

4. Rate Limiting

Protect public endpoints:

from app.core.rate_limit import rate_limit

@router.get("", dependencies=[Depends(rate_limit)])
async def list_users():
    """List users (rate limited to 100 req/min)."""
    pass

See templates/rate-limiter.py for Upstash Redis implementation.

5. CORS Configuration

Use Doppler for allowed origins:

# NEVER hardcode origins in production!
allowed_origins = os.getenv("CORS_ALLOWED_ORIGINS", "").split(",")

app.add_middleware(
    CORSMiddleware,
    allow_origins=allowed_origins,
    allow_credentials=True,
)

See reference/cors-rate-limiting.md for complete setup.

When to Apply This Skill

Use this skill when:

  • ✅ Creating new FastAPI endpoints or TanStack Start server functions
  • ✅ Designing RESTful resource hierarchies
  • ✅ Writing Pydantic schemas for validation
  • ✅ Implementing pagination, filtering, or sorting
  • ✅ Configuring error response formats
  • ✅ Setting up OpenAPI documentation
  • ✅ Implementing rate limiting or CORS
  • ✅ Designing multi-tenant API isolation
  • ✅ Testing API endpoints with pytest
  • ✅ Reviewing API design in pull requests
  • ✅ User mentions: "API", "endpoint", "REST", "FastAPI", "Pydantic", "server function", "OpenAPI", "pagination", "validation"

Template References

These API design patterns come from Grey Haven's actual templates:

  • Backend: cvi-backend-template (FastAPI + SQLModel + Repository Pattern)
  • Frontend: cvi-template (TanStack Start server functions)

Critical Reminders

  1. Repository pattern - Always use tenant-aware repositories for multi-tenant isolation
  2. Pydantic schemas - Never return password hashes or sensitive fields in responses
  3. HTTP status codes - 201 for create, 204 for delete, 404 for not found, 422 for validation errors
  4. Pagination - Use cursor-based for large datasets (better performance than offset)
  5. Error format - Consistent error structure with error, detail, and status_code fields
  6. OpenAPI docs - Document all parameters, responses, and errors with docstrings
  7. Rate limiting - Protect public endpoints with Upstash Redis (100 req/min default)
  8. CORS - Use Doppler for allowed origins, never hardcode in production
  9. JWT authentication - Extract tenant_id from JWT claims for multi-tenant isolation
  10. Testing - Use FastAPI TestClient with doppler run --config test -- pytest

Next Steps

  • Need endpoint examples? See examples/ for FastAPI CRUD and TanStack Start
  • Need configurations? See reference/ for OpenAPI, CORS, error handlers
  • Need templates? See templates/ for copy-paste ready endpoint code
  • Need checklists? Use checklists/ for systematic API design reviews

平台分布

Codex

37.82%
按下载量换算36

Claude

29.5%
按下载量换算28

Cursor

17.65%
按下载量换算17

Gemini CLI

8.76%
按下载量换算8

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills