busirocket-supabase

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Supabase Boundaries

Supabase 服务边界

Service boundary patterns for Supabase projects.

适用于Supabase项目的服务边界模式。

When to Use

适用场景

Use this skill only when:

Working in a project that uses Supabase
Creating or refactoring Supabase access code
Enforcing a clear boundary between Supabase and the rest of the app

仅在以下情况使用此技能：

处理使用Supabase的项目
创建或重构Supabase访问代码
强制在Supabase与应用其余部分之间建立清晰的边界

Non-Negotiables (MUST)

不可协商的规则（必须遵守）

Single boundary: All Supabase access lives in a dedicated layer (service wrappers). No direct Supabase calls from outside that layer.
Single client: The Supabase client is created in one module; all Supabase usage goes through that client and your service wrappers.
Focused wrappers: Keep wrappers small, focused, and typed.

单一边界：所有Supabase访问都应置于专用层（服务包装器）中。禁止从该层外部直接调用Supabase。
单一客户端：Supabase客户端在一个模块中创建；所有Supabase使用都必须通过该客户端和你的服务包装器进行。
聚焦的包装器：保持包装器体积小、职责单一且类型化。

Rules

规则

Supabase Access

Supabase 访问规则

```
supabase-access-rule
```
- Isolate Supabase access in service wrappers
```
supabase-services-usage
```
- Callers outside the service layer must not use Supabase directly

```
supabase-access-rule
```
- 将Supabase访问隔离在服务包装器中
```
supabase-services-usage
```
- 服务层外部的调用者不得直接使用Supabase

Related Skills

How to Use

使用方法

Read individual rule files for detailed explanations and code examples:

rules/supabase-access-rule.md
rules/supabase-services-usage.md

Each rule file contains:

Brief explanation of why it matters
Code examples (correct and incorrect patterns)
Additional context and best practices

阅读各个规则文件以获取详细说明和代码示例：

rules/supabase-access-rule.md
rules/supabase-services-usage.md

每个规则文件包含：

简要说明规则的重要性
代码示例（正确与错误模式）
额外背景信息与最佳实践