jurislm
OrganizationClaude Code 外掛市集 — MCP 伺服器、Skills 與跨專案開發經驗模式
Categories
Indexed Skills (44)
openspec-apply-change
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
openspec-archive-change
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
openspec-bulk-archive-change
Archive multiple completed changes at once. Use when archiving several parallel changes.
openspec-continue-change
Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.
openspec-explore
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
openspec-ff-change
Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.
openspec-new-change
Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.
openspec-onboard
Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.
openspec-sync-specs
Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.
openspec-verify-change
Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
spectra-audit
Audit changed code for security sharp edges — dangerous defaults, type confusion, and silent failures
spectra-debug
Systematically debug a problem using a four-phase workflow
spectra-discuss
Have a focused discussion about a topic and reach a conclusion
spectra-drift
Detect drift between a Spectra change and the current codebase state
spectra-ingest
Update an existing Spectra change from external context
spectra-propose
Create a change proposal with all required artifacts
higgsfield-game-generation
Build and iterate playable browser games, or create game-specific sprites, textures, animated 3D assets, music, SFX, and voice with Higgsfield CLI. Use when: "make a game", "build a browser game", "create game assets", "make a spritesheet", "generate a tileable texture", "animate a 3D game character", or "deploy/publish my game". Supports solo, local multiplayer, and online multiplayer games. NOT for: ordinary image/video generation, game trailers, native mobile/desktop builds, or editing a game without its source files.
higgsfield-generate
Generate images/videos/3D assets/audio via Higgsfield AI. Defaults: GPT Image 2 for image/design/text, Seedance 2.0 for video, Nano Banana 2/Lite/Pro for character/reference images, Marketing Studio for ads, Seed Audio 1.0 for audio. Use when: "generate an image", "make a video", "animate this photo", "image-to-video", "edit/stylize/remix this image", "reframe this video", "edit this video from a sketch", "create a 3D model/GLB", "create a sound effect", "make music", "text-to-audio", "create an ad", "make a UGC video", "unboxing", "presenter video", "import product from URL", or "analyze video virality". Supports image-to-3D (`multi_image_to_3d`), text-to-audio/music (`seed_audio`), workflow generation (`draw_to_video`, `reframe`), Marketing Studio, and Virality Predictor (`brain_activity`). Chain with higgsfield-soul-id for face/identity consistency. NOT for: Soul training, photoshoots, cards, explainers (use higgsfield-video-explainer), playable games/assets (use higgsfield-game-generation), or TTS.
higgsfield-marketplace-cards
Generate marketplace product image cards through Higgsfield: compliant main image, secondary product images, and A+ style content modules. Use when the user asks for marketplace listing images, product detail cards, secondary product images, product infographics, lifestyle listing shots, A+ style content, marketplace image sets, or sales-ready product visuals. Backend owns marketplace compliance references and prompt templates; this skill only routes user intent to the CLI. NOT for generic brand product photography without marketplace/listing context (use higgsfield-product-photoshoot), video generation or UGC ads (use higgsfield-generate), or Soul Character training (use higgsfield-soul-id).
higgsfield-product-photoshoot
Generate brand-quality product images through Higgsfield product-photoshoot prompt enhancement on GPT Image 2 / gpt_image_2. Entry point for professional brand/product visuals. Use when: "product photo", "studio shot", "lifestyle image", "Pinterest pin", "hero/banner", "carousel", "ad creative", "Meta ads", "virtual try-on", "model wearing", "person holding product", "closeup with hands", "levitating/floating/splash product", "CGI/surreal product", "restyle", "seasonal/aesthetic variation", or any product, brand, or paid-social creative. Modes: product_shot, lifestyle_scene, closeup_product_with_person, moodboard_pin, hero_banner, social_carousel, ad_creative_pack, virtual_model_tryout, conceptual_product, restyle. Backend assembles the final prompt; never freehand it. NOT for: no-product text-to-image (use higgsfield-generate), branded avatar video (use higgsfield-generate Marketing Studio), marketplace listing cards (use higgsfield-marketplace-cards), Soul Character training (use higgsfield-soul-id).
higgsfield-soul-id
Train a Soul Character — a personalized model on a person's face that Higgsfield uses for identity-faithful image and video generation. Use when: "create my Soul", "train my face", "make my digital twin", "build me an avatar", "learn my appearance", "create a character of me", "set up identity for video", "I want my face in generated images". Chain: train Soul (one-time, returns reference_id) → use in higgsfield-generate via `--soul-id <id>` with models like `text2image_soul_v2` or `soul_cinema_studio`. NOT for: one-shot face swaps (use higgsfield-generate with --image), named-character / non-photo avatars (use higgsfield-generate with prompt).
higgsfield-video-explainer
Build a complete non-photoreal narrated explainer or story video from ordered 10-second blocks: one narrator, one universal style key, one Seed Audio take and one Gemini Omni clip per block, then server-side assembly with explainer_video. Use when: "make an explainer video", "explain this in a video", "turn this topic or document into a narrated video", "tell this story as an animated video", "make a faceless narrated video", or "show me explainer styles". Supports live CMS presets, custom style references, mascot/faceless modes, two aspects, and optional burned subtitles. NOT for: photoreal films, ads/UGC, talking heads, podcasts, motion typography reels, one-off clips without narration, or editing a finished video.
higgsfield-websites
Build, edit, and deploy full-stack websites via the Higgsfield CLI (`higgsfield website …`). Each site is a React 19 + TanStack Start SSR app in one Cloudflare Worker (D1/R2/KV/DO/Containers). TWO product types, picked via `--type` on create: `website` (standalone, NO Higgsfield integration, independent brand, custom CSS — the image-grounded pipeline in references/website-flow.md) vs `app` (Sign in with Higgsfield + fnf SDK, Quanta + app layouts per references/app-flow.md). This file routes to the right flow; each flow carries its own workflow, references, hard rules, and deploy/publish gates. Use when: "build me a website", "make a landing page", "create a web app", "build a SaaS dashboard / tool / portfolio", "deploy this site", "edit my site", "publish", "ship to production". NOT for: single image/video/audio generation (higgsfield-generate), product photos (higgsfield-product-photoshoot), marketplace cards (higgsfield-marketplace-cards).
spectra-analyze
Analyze artifact consistency for a change
spectra-apply
Implement or resume tasks from a Spectra change
spectra-archive
Archive a completed change
spectra-ask
Query openspec/documents and answer questions
spectra-commit
Commit files related to a specific Spectra change
spectra-verify
Verify implementation matches artifacts
codebase-sync
This skill should be used when the user says "更新 README", "更新 CLAUDE.md", "同步文件", "移除過時內容", "codebase 文件已過時", "文件跟不上代碼", "CLAUDE.md 要更新", "重構完需要更新文件", "update README", "sync documentation", "docs are outdated", "documentation is stale", "docs don't match the code", "update my docs after refactor", or wants to audit and refresh README.md and CLAUDE.md to match the current codebase state.
coolify
This skill should be used when the user asks to "deploy to Coolify", "manage Coolify applications", "check Coolify status", "create database on Coolify", "manage Coolify servers", "diagnose Coolify issues", "update environment variables on Coolify", "部署到 Coolify", "查看 Coolify 狀態", "建立 Coolify 資料庫", "診斷 Coolify 問題", "更新環境變數", or mentions Coolify deployment, infrastructure management, or self-hosted PaaS operations.
hetzner
This skill should be used when the user asks to "create a Hetzner server", "manage Hetzner Cloud infrastructure", "list Hetzner servers", "add SSH key to Hetzner", "check Hetzner server types", "provision a VPS", "Volume mount 失敗", "reboot 後 container 掛掉", "fstab 設定", "Storage Box 連線", "建立 Hetzner 伺服器", "列出 VPS", "管理 SSH 金鑰", "查看伺服器規格", "Hetzner Volume", "備份到 Storage Box", "Storage Box 空間用量", "Storage Box 剩餘容量", "備份前檢查空間", "備份前空間預檢查", or mentions Hetzner Cloud server management, infrastructure provisioning, or cloud resource operations.
langfuse
This skill should be used when the user asks to "manage Langfuse prompts", "view traces", "check LLM observations", "query Langfuse", "list prompts", "get trace details", "create scores", "analyze LLM performance", "查看 LLM 追蹤記錄", "列出 Langfuse prompts", "分析 LLM 用量", "查 traces", "查 Langfuse", or mentions Langfuse, prompt management, LLM observability, or trace analysis.
learn-eval
This skill should be used when the user wants to save or extract learnings from the current session. Trigger phrases: "extract reusable patterns", "save this pattern", "learn from this session", "save what we just figured out", "remember this for next time", "don't want to forget this", "this is a library quirk", "記錄這次的 pattern", "把這次學到的存起來", "萃取 session pattern", "學習紀錄", "記下來", "下次別忘了", "這個 API 很奇怪，記一下", "記錄這個 workaround". Applies a quality gate and dedup check before writing any skill file.
podcast-to-blog
This skill should be used when the user says "podcast 轉文章", "幫我把這集 podcast 寫成文章", "podcast 逐字稿", "轉錄 podcast", "podcast to blog", "聽這集幫我寫筆記", "transcribe audio", "音檔轉文字", "mp3 轉文章", "convert audio to blog post", "RSS feed 轉文章", or provides an Apple Podcasts URL, audio file path, or RSS feed URL and wants a blog post or transcript generated from it.
repo-standards
This skill should be used when the user asks "如何設定新 repo", "release workflow 怎麼寫", "release-please 怎麼用", "lint 怎麼設定", "eslint config 怎麼寫", "新增 repo 要怎麼設定", "git worktree 怎麼設定", "設定 code review workflow", "設定 Drone CI", "drone.yml 怎麼寫", "CI 怎麼設定", "部署怎麼設定", "避免重複部署", "deploy gating", "Coolify 部署 pipeline", "set up new repo", "configure ESLint", "set up release workflow", "set up Drone CI", "set up git worktree", "add a .drone.yml pipeline", "avoid duplicate deploy", "configure CD / deploy", "設定 Vitest", "設定 Bun", "設定測試框架", "upgrade to ESLint 9", "migrate to flat config", "audit CI setup", "check release workflow", "檢查 repo 設定", "更新 AGENTS.md", "AGENTS.md 讀 CLAUDE.md", "同步 AGENTS.md", "sync AGENTS.md with CLAUDE.md", or needs to set up Drone CI/CD, release automation, deploy gating, ESLint configuration, git worktree, AGENTS.md handoff, or code review workflows for a repository.
jt-flow-one
以 Linear issue 為需求來源，用 Superpowers skill 集完成一個需求的端到端交付： 釐清 → worktree → TDD 實作 → PR → review → merge → 部署驗收 → Linear readback。 GitHub Flow 單段式（無 develop 分支，feature 直接對預設分支開 PR）。 Linear issue 本身即授權，不另設提案核准關卡。 Use when the user asks to "做完這個 Linear issue", "把這個需求做完", "deliver this issue end to end", or points at a Linear issue and asks for implementation.
hook-standards
Claude Code hook 的規格：什麼行為該用 hook 強制、什麼該留在 CLAUDE.md 判斷層、 deny 與 ask 怎麼選、匹配與失敗紀律、輸出格式、註解義務，以及安裝與更新步驟。 另附三支現行守衛（git-guard、destructive-guard、worktree-hookspath-fix）的逐支規格。 Use when 新增或修改 Claude Code hook、編輯 settings.json 的 hooks 區塊、 審查一支 hook 是否合格，或需要知道目前環境有哪些守衛、它們會擋下什麼。
engineering-delivery
一件工程案件的端到端交付 coordinator：以 Linear issue 為需求來源，走完 N0 前提 → 需求分析 → 設計 → worktree → TDD 實作 → 本地審查 → PR → 外部審查 → 合併 → 驗收 → 結案。指向一個 Linear issue 並要求交付即為完整授權。 Use when the user asks to 做完這個 Linear issue、把這個需求做完、 deliver this issue end to end.
external-review-gate
由 `engineering-delivery` 調用：把外部審查的結果映射為 gate 終態。審查的取得歸 `coderabbit:code-review` 擁有，本 Skill 不描述任何管道呼叫細節。
merge-gate
由 `engineering-delivery` 調用：判定這個 PR 可不可以合併。gate 清單以目標 repo 的 CLAUDE.md 為準，未宣告時採本 Skill 的預設值。
acceptance-readback
由 `engineering-delivery` 調用：監看部署或合併後 CI 到終態，取得驗收證據，並在 失敗時判定根因是否可由改碼解除。
delivery-preflight
由 `engineering-delivery` 調用：單次查證本次交付的環境前提（版本控制、GitHub 託管、remote 解析、案件管理管道），回傳 internal result。
using-jt-workflow
jt-flow 的紀律與 Skill 選用：產品團隊心智模型、可替換工具與具名依賴的判別、 案件記錄紀律，以及會讓人偷懶的紅旗清單。接觸任何交付工作前先讀。
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.