发现 Skills

ClawdBot control panel UI requirements and architecture

REQUIRED for editing any skill file. Ensures changes sync to Claude, Codex, and Cursor. Never edit .claude/skills/ files directly - always use this skill.

ALWAYS use when touching ANY DayZ file (.c, config.cpp, mod.cpp, .layout, types.xml) or discussing DayZ modding, Enforce Script, or the Enfusion engine. Activate even if the user does not explicitly mention DayZ — if the code imports DayZ classes (PlayerBase, EntityAI, ItemBase, MissionServer), uses DayZ APIs (GetGame(), Class.CastTo(), ScriptRPC), or references DayZ patterns (modded class, CfgPatches, requiredAddons), this skill MUST be loaded. Covers 40+ critical gotchas, complete engine API across 20+ systems, mod architecture, RPC networking, GUI widgets, performance optimization, and professional patterns from COT, VPP, and Expansion mods. Without this skill, the agent WILL produce broken Enforce Script code.

This skill should be used when generating comprehensive test cases from PRD documents or user requirements. Triggers when users request test case generation, QA planning, test scenario creation, or need structured test documentation. Produces detailed test cases covering functional, edge case, error handling, and state transition scenarios.

Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute. Use when user wants to prevent destructive git operations, add git safety hooks, or block git push/reset in Claude Code.

Comprehensive Slint GUI development expert based on the official source repository. Covers Rust integration, component design, layouts, styling, animations, cross-platform deployment, and performance optimization. Use when working with the Slint UI toolkit, building native GUI applications, or when discussing Slint, GUI development, or Rust user interfaces. Built from official documentation and examples.

Structuring Streamlit app layouts. Use when placing content in sidebars, columns, containers, or dialogs. Covers sidebar usage, column limits, horizontal containers, dialogs, and bordered cards.

Convert PRDs to prd.json format for ralph-tui execution. Creates JSON task files with user stories, acceptance criteria, and dependencies. Triggers on: create prd.json, convert to json, ralph json, create json tasks.

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

Programmatic workflow to search Bilibili (B站) videos by keyword, retrieve metadata and thumbnails, and optionally capture rendered page screenshots via an OpenClaw browser relay. Use this when a user requests Bilibili video lists, thumbnails, or page screenshots (search -> download thumbnails -> attempt page screenshot via browser relay -> fallback to thumbnails).

A continuously adaptive skill suite that empowers Clawdbot to act as a versatile coder, business analyst, project manager, web developer, data analyst, and NAS metadata scraper. It intelligently discovers free resources, adapts to user context, and ensures reliable, proven guidance across multiple domains.

Database management and queries. Connect to SQL and NoSQL databases, run queries, and manage schemas.

AI-powered atomic habit tracker with natural language logging, streak tracking, smart reminders, and coaching. Use for creating habits, logging completions naturally ("I meditated today"), viewing progress, and getting personalized coaching.

Repository structure, settings, CI/CD, and team configuration — audit and setup. Use for repo health, branch policies, CI validation, or team onboarding.

Systematic evaluation (Evals) for LLMs and AI products. Design test cases, measure accuracy and quality, track regressions, benchmark models, and build continuous evaluation pipelines. Distinct from traditional software testing because outputs are probabilistic.

General-purpose Static Application Security Testing (SAST) skill for code vulnerability analysis. Trigger when the user asks to: "analyze code for vulnerabilities", "review code security", "find security bugs", "do a SAST scan", "check for [vulnerability type] in code", "audit source code", or requests a security code review of any language or framework. Covers 34 vulnerability classes across web, API, auth, mobile, and logic layers.

53-point conversion audit covering customer focus, narrative arc (Pain-Dream-Fix), copy quality, design, CTAs, and proof. Scored report with prioritized fixes.

Interactive plan and diff review for AI coding agents. Visual browser UI for annotating agent plans — approve or request changes with structured feedback. Supports code review, image annotation, and auto-save to Obsidian/Bear Notes.

CLI tools for Svelte 5 documentation lookup and code analysis. MUST be used whenever creating or editing any Svelte component (.svelte) or Svelte module (.svelte.ts/.svelte.js). If possible, this skill should be executed within the svelte-file-editor agent for optimal results.

Inspect edited files, group them into logical commits, and create focused commits for this repo. Use when: the user asks to commit changes, split work into focused commits, or decide how the current diff should be grouped before committing.

Entity<T> patterns, GUID v7 auto-generation, static methods vs manual repositories

Provides MoAI-ADK foundational principles including the TRUST 5 quality framework, SPEC-First DDD methodology, delegation patterns, progressive disclosure, and an agent catalog reference. Use this when referencing TRUST 5 gates, the SPEC workflow, EARS format, DDD methodology, agent delegation patterns, or MoAI orchestration rules. Do NOT use this for context and token management (use moai-foundation-context instead) or for strategic analysis (use moai-foundation-philosopher instead).

Electron 33+ desktop app development specialist covering Main/Renderer process architecture, IPC communication, auto-update, packaging with Electron Forge and electron-builder, and security best practices. Use when building cross-platform desktop applications, implementing native OS integrations, or packaging Electron apps for distribution. [KO: Electron 데스크톱 앱, 크로스플랫폼 개발, IPC 통신] [JA: Electronデスクトップアプリ、クロスプラットフォーム開発] [ZH: Electron桌面应用、跨平台开发]

Design themes built bottom-up through validated foundational layers. Each layer is applied and verified in isolation before the next is introduced. No layer references concepts from a later layer. Triggers: theme design, design layer, design init, design load, design enhance, design spec, export syntax, color palette, typography system.