supabase-rls
Supabase RLS パフォーマンス最適化。セキュリティ境界と最適化フィルタの区別、および堅牢な関数定義を規定。
Discover Documentation skills, compare source repositories and read the instructions for each workflow.
Supabase RLS パフォーマンス最適化。セキュリティ境界と最適化フィルタの区別、および堅牢な関数定義を規定。
Follow the end-of-session git checklist before handing off.
Use tk to manage tickets and keep .tickets/ in sync with code changes.
Use fmail for agent-to-agent messaging with team conventions.
Follow the team workflow expectations while working.
Deploy to HuggingFace Spaces, create releases, check deployment status, verify before release, push to production. Use when deploying, releasing, or checking deployment logs.
Fix lint errors, format code, run type checking, check code quality. Use when fixing linting issues, formatting Python, running ruff, running ty, checking TypeScript types, or ensuring code quality.
Explain the codebase architecture, project structure, how components work together, API endpoints, data flow. Use when explaining code, understanding structure, or learning about the project.
GitHub Issue を起点に実装前の計画コメントを作成して投稿し、設計方針が確定するまで Issue コメント上で質疑・改訂を繰り返すためのスキル。Issue 番号を受け取り、Issue 本文/既存コメントを読んで実装方針・変更対象見込...
GitHub Issue の実装フェーズを支援するスキル。指定 Issue の「## Implementation Plan (Codex)」コメントを実装仕様として解釈し、必要なコード変更、コミット作成、Pull Request 作成までを行う。すでに当該 Issue に紐づく...
Update session.md with completed tasks, pending tasks, and blockers for agent handoff.
xlmakeの機能追加、更新時に必ず参照するスキル。
GitHubにPull Requestを作成するスキル。コミット・プッシュ済みの状態で、現在のブランチの変更内容を分析し、適切なタイトルと説明文でPRを作成する。「PRを作成して」「プルリクエストを作って」「PR作って」などのトリガー...
xlmakeの機能、利用方法調査時に参照するインデックスファイル。
プランの内容、実装計画を./docs配下にファイルを作成する
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoid...
Use when you have a list of features, tasks, or ideas and need to rank them using structured frameworks (RICE, MoSCoW, Impact/Effort).
Use when you have a Jira backlog export and need to turn KTLO tickets into a product-view with prioritized buckets.
Use when preparing to launch a product or major feature - creates market analysis, positioning, launch plan, and enablement strategy.
Use before creative PM work to explore problem space, generate options, and validate thinking before committing to solutions
Use when you have customer feedback files (transcripts, tickets, surveys) and need to identify themes and opportunities without hallucinating.
Use when starting on a new product, joining a team, or needing a shared understanding of product, customers, and current bets.
Use when defining long-term vision - creates 3-5 year product strategy with vision, strategic pillars, capability roadmap, and competitive moats.
Use when you have an approved charter and need to produce a detailed PRD that engineering and design can execute.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.