All authors
Claude Skills by Charles5277
github.com/Charles5277109 skills0 installs181 views
- Review Screenshot統一截圖入口。Use when 使用者要求截圖驗證 UI 畫面，或要跑 UI 檢查清單。NOT for 把既有截圖 sweep 進 _archive/（走 screenshots-archive），NOT for Lighthouse 稽核或 performance trace 拆解（走 chrome-devtools-mcp）。Votes: 0GitHub stars: 44
- Rls PerformanceRLS 效能診斷：EXPLAIN ANALYZE、PGRST003 pool timeout、connection pool 耗盡、API 變慢。NOT for RLS policy 的正確性設計（走 supabase-rls）。Votes: 0GitHub stars: 44
- Screenshots ArchiveUse when 使用者要求 sweep 截圖到 _archive/。現行契約已停 rotate；截圖留在 screenshots/<env>/<topic>/。NOT for 產生新截圖（走 review-screenshot）。Votes: 0GitHub stars: 44
- Security EvidenceUse when 要判一則 Codex Security finding 是真漏洞還是假警報（finding mode），或上線前要分清 repo / staging / production 各層還缺哪些安全證據（map mode）。NOT for 修 code、跑掃描、寫 SECURITY.md。Votes: 0GitHub stars: 44
- Supabase MigrationSupabase migration 檔與 schema DDL 規範。觸發：supabase migration new、CREATE FUNCTION / ALTER TABLE / CREATE INDEX。NOT for RLS policy 的內容設計（走 supabase-rls）。Votes: 0GitHub stars: 44
- Supabase Postgres Best PracticesPostgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill BEFORE writing or changing anything that lives in a Postgres database: creating or altering tables and columns (including choosing column types), schema design, migrations and declarative schema files, RLS policies and the tests that verify them, indexes, triggers, database functions, queues and scheduled jobs (pg_cron, pgmq), vector/semantic search (pgvector), and restoring dumps (pg_restore) or im...Votes: 0GitHub stars: 44
- SupabaseUse when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues); client libraries and SSR integrations (supabase-js, @supabase/ssr) in Next.js, React, SvelteKit, Astro, Remix; auth issues (login, logout, sessions, JWT, cookies, getSession, getUser, getClaims, RLS); Supabase CLI or MCP server; schema changes, migrations, declarative schemas, security audits, Postgres extensions (pg_graphql, pg_cron, pg_vector); ...Votes: 0GitHub stars: 44
- Test Driven DevelopmentUse when implementing any feature or bugfix, before writing implementation codeVotes: 0GitHub stars: 44
- Verification CreateUse when user requests verification setup. NOT for maintenance.Votes: 0GitHub stars: 44
- Vite Tunnel建 Cloudflare Named Tunnel 給本機 dev server（跨裝置 OAuth / webhook 測試用）。Votes: 0GitHub stars: 44
- VitepressVitePress static site generator powered by Vite and Vue. Use when building documentation sites, configuring themes, or writing Markdown with Vue components.Votes: 0GitHub stars: 44
- VitestVitest fast unit testing framework powered by Vite with Jest-compatible API. Use when writing tests, mocking, configuring coverage, or working with test filtering and fixtures.Votes: 0GitHub stars: 44
- Vue Best PracticesMUST be used for Vue.js tasks. Strongly recommends Composition API with `<script setup>` and TypeScript as the standard approach. Covers Vue 3, SSR, Volar, vue-tsc. Load for any Vue, .vue files, Vue Router, Pinia, or Vite with Vue work. ALWAYS use Composition API unless the project explicitly requires Options API.Votes: 0GitHub stars: 44
- Vue Testing Best PracticesUse for Vue.js testing. Covers Vitest, Vue Test Utils, component testing, mocking, testing patterns, and Playwright for E2E testing.Votes: 0GitHub stars: 44
- Vueuse FunctionsApply VueUse composables where appropriate to build concise, maintainable Vue.js / Nuxt features.Votes: 0GitHub stars: 44
- Work LoopUse for unattended progression of plan tasks, HANDOFF items, tech debt, or roadmaps. Not for one-time handoff or user decisions.Votes: 0GitHub stars: 44
- Workers Best PracticesReviews and authors Cloudflare Workers code against production best practices. Load when writing new Workers, reviewing Worker code, configuring wrangler.jsonc, or checking for common Workers anti-patterns (streaming, floating promises, global state, secrets, bindings, observability). Biases towards retrieval from Cloudflare docs over pre-trained knowledge.Votes: 0GitHub stars: 44
- WranglerUse before running Wrangler deploy, dev, tail, or types for Cloudflare Workers. Account resources (D1, KV, R2, DNS, secrets) use the cf CLI.Votes: 0GitHub stars: 44
- WtUse when 使用者要開 worktree（隔離環境跑 task 不影響主 working tree），或並行做多條 task（/wt A: ... B: ...）。NOT for 發布散播（走 clade-publish）、提交已完成工作（走 commit），NOT for 只是要切 branch。Votes: 0GitHub stars: 44
- ZodZod schema validation best practices for type safety, parsing, and error handling. This skill should be used when defining z.object schemas, using z.string validations, safeParse, or z.infer. This skill does NOT cover React Hook Form integration patterns (use react-hook-form skill) or OpenAPI client generation (use orval skill).Votes: 0GitHub stars: 44
- Clade Code QualityCode quality, error handling, shell safety, language, and maintainability rules. Use when implementing or refactoring code, scripts, or language-specific components.Votes: 0GitHub stars: 44
- Clade DataDatabase, schema, storage, logging, and data-path rules. Use when changing persistence, migrations, queries, RLS, database environments, or application logging; also before running integration tests, needing a test or dev database, running any supabase CLI command, or deciding where the dev DB lives.Votes: 0GitHub stars: 44
- Clade DeliveryCommit, CI, release, and repository delivery rules. Use when committing, changing CI, preparing delivery, or handling repository state.Votes: 0GitHub stars: 44
- Clade FrontendFrontend, interaction, accessibility, localization, and UX integrity rules. Use when changing UI, forms, display values, interactions, translations, or visual completeness.Votes: 0GitHub stars: 44
- Clade KnowledgeUse for durable documentation, shared knowledge, decisions, onboarding, rule authoring, or technical debt.Votes: 0GitHub stars: 44
- Clade OperationsRuntime, deployment, local service, and infrastructure rules. Use when changing Cloudflare, Nitro, APIs, tunnels, ports, service URLs, or operational configuration.Votes: 0GitHub stars: 44
- Clade SecurityAuthentication, secrets, production access, and security boundary rules. Use when changing identity, authorization, credentials, production MCP access, or user lifecycle behavior.Votes: 0GitHub stars: 44
- Clade Session WorkSession, delegation, handoff, work tracking, and follow-up rules. Use when planning work, delegating, opening worktrees, coordinating agents, or ending a session.Votes: 0GitHub stars: 44
- Clade Spec WorkflowSpecification and requirements workflow rules. Use when work involves SDD, BDD, SpecFormula, decisions, structured plans, or pre-BDD legacy tests.Votes: 0GitHub stars: 44
- Clade VerificationVerification, testing, review, screenshots, and evidence rules. Use when testing, reviewing, debugging, collecting evidence, or claiming completion.Votes: 0GitHub stars: 44
- ClarifyUse when requirements are incomplete, ambiguous, conflicting, or require user decisions before implementation.Votes: 0GitHub stars: 44
- Gh Ci WatchUse immediately after a successful git push when the repo has GitHub Actions and CI / deploy completion must be watched — including slice draft PRs; also use when 查詢某 run 或某 SHA、撈 run log 證據、查 runner 佇列。CI 紅燈修回同一張 PR。NOT for 修 CI 紅燈本身的實作步驟（那是拿到結果後的除錯流程）。Votes: 0GitHub stars: 44
- HandoffSession 交接與 bounded delegation。Use when `/handoff` 要登記進度、在支援的 runtime 交給 successor，或由 Codex upstream 派 native bounded work。NOT for 單純 commit 收尾（走 `/commit`）。Votes: 0GitHub stars: 44
- Implement根據 plan package 的 `tasks.md`，以 don't stop until deliver / One-Shot 執行已解鎖 task。一輪恰好 1 個 task 或 Parallel Hint 批次；驗證後立刻回寫 `[X]` 再繼續，直到交付。不能跳步驟。Votes: 0GitHub stars: 44
- Nuxt Data AuditUse when auditing Nuxt data-fetching, performance, or client-server pagination schema boundaries. NOT for 非 Nuxt 專案，NOT for general code review。Votes: 0GitHub stars: 44
- ReviewUse for review lifecycle work: human-gate checks or UI screenshot evidence. Not for archiving (retired), product code review, or Lighthouse analysis.Votes: 0GitHub stars: 44
- Specify將自然語言功能需求轉成本次迭代的 plan package，產出 `spec.md` 與 `checklists/requirements.md`；package 路徑與 truth delta 的落點依 `rules/Feature目錄命名與輸出定位判準.md` 決定。不得改寫舊 plan package，也不得寫入 `specs/truth/**`。Votes: 0GitHub stars: 44
- System AnalysisUse when producing plan-side plan.md and API, data, or UI analysis from a plan package and truth artifacts.Votes: 0GitHub stars: 44
- VerificationUse for verification setup or maintenance. Not for product implementation or acceptance.Votes: 0GitHub stars: 44
- Version Upgradeconsumer outdated batch、fleet 套件 sweep、skill 上游同步、本機 toolchain 升級。Votes: 0GitHub stars: 44
- Vite Tunnel建 Cloudflare Named Tunnel 給本機 dev server（跨裝置 OAuth / webhook 測試用）。Votes: 0GitHub stars: 44
- WtUse when 使用者要開 worktree（隔離環境跑 task 不影響主 working tree），或並行做多條 task（/wt A: ... B: ...）。NOT for 發布散播（走 clade-publish）、提交已完成工作（走 commit），NOT for 只是要切 branch。Votes: 0GitHub stars: 44
- ReviewUse for review lifecycle work: human-gate checks or UI screenshot evidence. Not for archiving (retired), product code review, or Lighthouse analysis.Votes: 0GitHub stars: 44
- Version Upgradeconsumer outdated batch、fleet 套件 sweep、skill 上游同步、本機 toolchain 升級。Votes: 0GitHub stars: 44
- Notion Hubconsumer 所屬 Notion hub 的唯一入口。Use when 看 board／進度、評估或認領客戶票、在 prod 發現問題要建票、建決策題問客戶拍板、問客戶驗收了沒、或為新客戶／新專案開 hub。NOT for 生命週期狀態同步（由 notion-sync 跟隨 flow 事件推進）、未宣告 notion.hub 的 repo、clade 內部待拍板題（走 flow ask）。Votes: 0GitHub stars: 44
- Work RouteUse when the user wants to start or continue project work (new requirement, bug report, or refactor) without picking workflow skills. NOT for fleet readiness or registry drift queries (clade-onboard).Votes: 0GitHub stars: 44
- .Constitution依使用者需求，以最小、可逐步增量的方式建立或修改模組化憲法。先定位要改的憲法檔，再只對必要的根憲法、共用規則或特定 skill artifact 規則做訪談、收斂與寫入。Use when the user asks to create, split, refine, or extend the modular constitution under `.agents/constitution/`.Votes: 0GitHub stars: 44
- Api PlanTruth owner skill。根據 plan package、system-analysis handoff 與現有 API truth，更新 `specs/truth/contracts/**`，支援 ADD / MODIFY / DELETE / NOOP API 語意單元，並委派 `/truth-delta` 記錄本輪 API truth 改動。Votes: 0GitHub stars: 44
- Bdd承接 /dsl-refine 之後已存在的介面 feature files 與 dsl.md，在使用者指定的單一介面 feature file 或其明確區塊內，以 red、green、refactor 三個入口推進 BDD/TDD 實作。它不負責產 feature files；若規格缺口影響驗收意圖或 DSL 邊界，必須停止並回交上游。Votes: 0GitHub stars: 44
- Clarify Over Specs在 `/specify` 產出 `spec.md` 後，主動掃描整份 spec 的高影響需求缺口；若仍有會影響規格正確性、驗收標準或 readiness 的問題，先委派 `/clarify` 訪談使用者，再把答案回寫到 spec、清理矛盾並回刷 checklist。Use when the user asks for post-spec requirement clarification, wants a generated spec professionally reviewed before `/plan`, or needs a spec-level clarify pass after `/specify`.Votes: 0GitHub stars: 44