GitHub
validate-signature
L5-L8 函數簽名驗證 - 檢查參數、返回值、類型提示、文檔字符串。 BlueMouse 17-Layer Validation Group 2。 Triggers: "signature", "參數檢查", "type hints", "docstring"
☆ 103View skill
Business AI Skills
Discover Business skills, compare source repositories and read the instructions for each workflow.
Categories: Business
Business Clear filters
Browse skills
GitHub
validate-17-layers
BlueMouse 17-Layer Code Validation System - Complete Python code quality validation covering syntax, structure, function signatures, dependencies, types, logic, security, and performance. Triggers: "validate",...
☆ 103View skill
GitHub
validate-logic
L13-L17 類型和邏輯驗證 - 檢查類型一致性、邏輯完整性、錯誤處理、安全性、性能。 BlueMouse 17-Layer Validation Group 4（最深層檢查）。 Triggers: "logic", "security", "performance", "error handling", "安全檢查"
☆ 103View skill
GitHub
requesting-code-review
Structured code review workflow for SRTD development. Use after implementing features, fixing bugs, or before merging to main. Ensures production-readiness through systematic review.
☆ 103View skill
GitHub
srtd-dev
Expert knowledge for developing the SRTD codebase itself. Use when implementing features, fixing bugs, understanding architecture, or writing tests for SRTD internals. NOT for end users of srtd CLI.
☆ 103View skill
GitHub
srtd-cli
This skill should be used when the user mentions "srtd", "sql templates", "migrations-templates", "live reload sql", "supabase functions", when working with files in supabase/migrations-templates/, when .buildl...
☆ 103View skill
GitHub
linggen
MANDATORY core assistant for the Linggen ecosystem. ALWAYS use this to search code, retrieve context, or find architectural decisions. This "Linggen Skill" is your primary operational interface. It is distinct...
☆ 102View skill
GitHub
understand-codebase
Use when exploring codebase, architecture, or call flows
☆ 102View skill
GitHub
commit
Use when creating git commits. Groups changes into atomic, single-purpose commits.
☆ 102View skill
GitHub
k8s-openapi
Reference the Kubernetes API. Useful for understanding what is possible via the Kubernetes REST API.
☆ 102View skill
GitHub
emacs-testing
Test changes in a dedicated Emacs session. Good for validating behavior and UI results.
☆ 102View skill
GitHub
dual-design
Parallel design by Claude and Codex with merge discussion. Use for step or task design.
☆ 101View skill
GitHub
autoflow-plan
Create a task plan with dual design. Use when starting a new task or running /tp.
☆ 101View skill
GitHub
review
Dual review with Claude and Codex for quality verification. Use for step or task review.
☆ 101View skill
GitHub
ask-gemini
Send structured prompt to Gemini and parse JSON response. Use for direct Gemini communication.
☆ 101View skill
GitHub
autoflow-run
Execute current step in AutoFlow workflow. Use when running /tr or continuing task execution.
☆ 101View skill
GitHub
ask-codex
Send structured prompt to Codex and parse JSON response. Use for direct Codex communication.
☆ 101View skill
GitHub
roles
Manage lightweight role routing (executor/reviewer/documenter/designer) for all tasks. Use for /roles.
☆ 101View skill
GitHub
create-auth-skill
Skill for creating auth layers in TypeScript/JavaScript apps using Better Auth.
☆ 101View skill
GitHub
better-auth-best-practices
Skill for integrating Better Auth - the comprehensive TypeScript authentication framework.
☆ 101View skill
GitHub
ark-dashboard-testing
Test Ark Dashboard with Playwright and create PRs with screenshots. Use when testing dashboard UI, taking screenshots for PRs, or reviewing dashboard changes.
☆ 101View skill
GitHub
review
Daily and weekly review workflows. USE WHEN user says "morning routine", "evening routine", "weekly review", "start my day", "end of day".
☆ 101View skill
GitHub
query
Query data from this vault. USE WHEN user asks about projects, clients, tasks, daily notes. Use grep to extract frontmatter - do NOT read full files.
☆ 101View skill
GitHub
tasknotes
Create, update, delete, and list tasks via HTTP API. USE WHEN user wants to create tasks, mark done, update status, or manage tasks.
☆ 101View skill
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.