菜单
Use when the task involves database schema changes, SQL migrations, RLS policies, cloud storage buckets, file system persistence, or data access control.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when updating documentation, README sections, CHANGELOG entries, docstrings, or CLAUDE.md conventions after a feature is complete.
Use when the task involves server-side API routes, middleware, business logic, authentication, database queries, or infrastructure configuration.
Task and document management with Backlog.md. Use this skill whenever working with tasks, tracking work, creating subtasks, searching or viewing existing tasks, or any time work should be preserved across sessions or handed off. Triggers include: "create a task", "track this", "add to backlog", "what tasks do I have", "mark as done", "continue on task", "break this into tasks", or any request where the outcome has a concrete deliverable worth tracking. Always use this skill when a project includes a Backlog.md setup and work needs to be logged. Prefer CLI commands unless MCP tools are confirmed working in the current environment.
Use when adversarial code review is needed — actively constructing failure scenarios, edge cases, and security violations to break the implementation.
Run code review via an external LLM API using external-review.sh. Outputs structured JSON with verdict, summary, and per-file concerns.
Use when the task involves UI components, HTML, CSS, styling, React, Vue, Svelte, client-side state, accessibility, or browser APIs.
| name | storage-rules |
| description | Use when the task involves database schema changes, SQL migrations, RLS policies, cloud storage buckets, file system persistence, or data access control. |
The storage layer is the SOLE OWNER of Row Level Security (RLS) policies. No other layer should create or modify RLS policies. If another layer needs RLS changes, route the request here.
-- Up and -- Down sectionsYYYYMMDD_HHMMSS_description.sqlDocument every access policy with a comment explaining the intent. Access rules are hard to audit after the fact — write the reasoning at creation time.
storage-rules governs all persistence concerns. Backend rules do not override storage ownership of RLS. Both skills may apply on tasks that touch APIs + schema.