All authors
Claude Skills by YuDefine
github.com/YuDefine27 skills0 installs39 views
- 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. Also use when: 使用者描述 prod／staging 的 runtime 症狀（5xx、錯誤 toast、變慢、間歇、特定 user 異常）、要開始查原因時，在 grep code／查 codebase／派 Explore 之前.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 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
- GuideHub skill 地圖：本 repo 實際裝到的 skill 的使用場景、邊界與銜接流程（router，零 context 成本；依 consumer manifest 的 modules 分層）。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
- Project BootstrapUse when creating or onboarding a Clade consumer from nuxt-supabase-starter. Not for existing-consumer feature work.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
- Specformula Api Spec當要導入 SpecFormula、規劃新的 API、或調整 API Spec Schema 時載入此規格Votes: 0GitHub stars: 44
- Specformula Config當要配置 SpecFormula 框架到專案內、修改 API Spec 存放路徑、或修改 Data Source 設定時載入此規格Votes: 0GitHub stars: 44
- Specformula Entity Spec當要導入 SpecFormula、新增資料表或實體、或修改 Entity Mapping / DDL 時載入此規格Votes: 0GitHub stars: 44
- Specformula Feature當要撰寫或修改 .feature 檔案時載入此規格Votes: 0GitHub stars: 44
- ClarifyUse when requirements are incomplete, ambiguous, conflicting, or require user decisions before implementation.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
- 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
- .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
- Data PlanTruth owner skill。根據 plan package、system-analysis handoff 與現有 data truth，更新 `specs/truth/data/**`，支援 ADD / MODIFY / DELETE / NOOP 資料語意單元，並委派 `/truth-delta` 記錄本輪 data truth 改動。Votes: 0GitHub stars: 44
- Dsl RefineTruth owner skill。承接 plan package 的 acceptance Gherkin 與 system-analysis 產物，將業務 Journey 拆成 interface-level executable feature files 與 DSL，並更新 `specs/truth/features/backend/**`、`specs/truth/features/frontend/**`。完成後委派 `/truth-delta` 記錄 feature/dsl truth 改動。Votes: 0GitHub stars: 44
- Gherkin And DslEvaluate and refactor Gherkin feature files and DSL vocabularies so they can be implemented as test code with minimal inference. Use when converting test plans into Gherkin, reviewing or tightening Given/When/Then sentences, deciding Rule/Background/Scenario Outline/DataTable structure, or checking whether Gherkin and DSL fully cover the intended test cases.Votes: 0GitHub stars: 44
- Spec By Example承接新的 plan package 中的 `spec.md`，把需求收斂成 plan-side `features/acceptance/*.feature`。此 skill 只寫入本次 plan package（`specs/plans/NNN-*/`，clade lifecycle repo 為 `specs/plans/<work-id>/`）的 `features/acceptance/**`，不修改 `specs/truth/**`，也不更新 `truth-delta.md`。Votes: 0GitHub stars: 44
- Tasks根據 plan package 的 `spec.md`、`plan.md`、`research.md`、`ui/**`，以及 `truth-delta.md` 與 `specs/truth/**` 產出可直接執行的 `tasks.md`。先寫 Setup 與 Foundational，測試層集中在 Phase 3 `Test Alignment & Implementation`；Feature phase 只留 Green / Refactor 或 CODE-REMOVE / REGRESSION。Votes: 0GitHub stars: 44
- Technical Research承接 plan package 的 `spec.md`，產出 plan-side `research.md`，並作為 truth owner 更新 `specs/truth/techstack.md`。每次執行都必須盤點 techstack truth 的 ADD / MODIFY / DELETE / NOOP，完成後委派 `/truth-delta` 更新本 plan 的 `truth-delta.md`。Votes: 0GitHub stars: 44
- Truth Delta維護每次 plan package 內的 `truth-delta.md`，讓 truth owner skill 以共同格式記錄本輪對 `specs/truth/**` 的 ADD / MODIFY / DELETE / NOOP 語意單元變更。Use when a truth owner skill has inspected or changed truth specs and must initialize, append, update, or validate the current plan package truth delta handoff.Votes: 0GitHub stars: 44
- Ui Plan根據 plan package、system-analysis handoff、truth-delta 與現有 truth，產出 plan-side `ui/**` 設計與靜態雛形。`ui-plan` 不是 truth owner，不寫入 `specs/truth/**`，但必須讀 truth-delta 以對齊本輪 API/data/feature truth 變更。Votes: 0GitHub stars: 44