القائمة
Design flat, relational schemas with proper indexes instead of deep nesting
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/KunanonJ/ai-skills-hub --skill cursor-plugin-convex-rule-schema-designيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
Build AI agents on Cloudflare Workers using the Agents SDK. Load when creating stateful agents, durable workflows, real-time WebSocket apps, scheduled tasks, MCP servers, chat applications, voice agents, or browser automation. Covers Agent class, state management, callable RPC, Workflows, durable execution, queues, retries, observability, and React hooks. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.
Comprehensive Cloudflare platform skill covering Workers, Pages, storage (KV, D1, R2), AI (Workers AI, Vectorize, Agents SDK), feature flags (Flagship), networking (Tunnel, Spectrum), security (WAF, DDoS), and infrastructure-as-code (Terraform, Pulumi). Use for any Cloudflare development task. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.
Create and review Cloudflare Durable Objects. Use when building stateful coordination (chat rooms, multiplayer games, booking systems), implementing RPC methods, SQLite storage, alarms, WebSockets, or reviewing DO code for best practices. Covers Workers integration, wrangler config, and testing with Vitest. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.
استنادا إلى تصنيف SOC المهني
عرض SKILL.md
| name | cursor-plugin-convex-rule-schema-design |
| description | Design flat, relational schemas with proper indexes instead of deep nesting |
| metadata | {"version":"0.1.0"} |
Design schemas to be document-relational: relatively flat documents with relationships via IDs, not deeply nested structures.
// ❌ Don't do this
export default defineSchema({
users: defineTable({
name: v.string(),
posts: v.array(v.object({
title: v.string(),
content: v.string(),
comments: v.array(v.object({
text: v.string(),
author: v.string(),
})),
})),
}),
});
This makes it hard to update specific posts, limits you to 8,192 posts per user, and prevents efficient queries.
// ✅ Do this
export default defineSchema({
users: defineTable({
name: v.string(),
email: v.string(),
}).index("by_email", ["email"]),
posts: defineTable({
userId: v.id("users"),
title: v.string(),
content: v.string(),
}).index("by_user", ["userId"])
.index("by_user_and_created", ["userId", "createdAt"]),
comments: defineTable({
postId: v.id("posts"),
userId: v.id("users"),
text: v.string(),
}).index("by_post", ["postId"])
.index("by_user", ["userId"]),
});
Arrays work well for:
users: defineTable({
name: v.string(),
roles: v.array(v.union(v.literal("admin"), v.literal("editor"), v.literal("viewer"))),
favoriteColors: v.array(v.string()), // Small list
}),
Always add indexes for foreign key lookups:
.index("by_user", ["userId"])
.index("by_team", ["teamId"])
.index("by_parent", ["parentId"])