Use loom ticket for ticket creation, status updates, deps, and notes.

Maintain custom Clash rule lists in rules/*.list for this repo. Use when adding or removing domain/IP rules, adjusting list contents, or wiring rule lists into mihomo.yaml/mihomo.js.

Manage implementation tasks with sequential sub-steps within a plan

Use this skill when working with dotfiles managed by yadm. This includes pulling remote changes, committing and pushing dotfile changes, modifying configuration files (shell, editor, terminal, git, etc.), viewing tracked files, resolving merge conflicts, and maintaining the dotfiles repository.

Manages WPF Application lifecycle including Startup, Exit, SessionEnding events and single instance detection. Use when handling app initialization, shutdown, or preventing multiple instances.

The slogan unpacked — seven readings of 'Manufacturing Intelligence'

makepad-2.0-dsl

makepad-2.0-shaders

>

Detect sandbox evasion techniques in malware samples by analyzing timing checks, VM artifact queries, user interaction

Detect process injection techniques (T1055) including CreateRemoteThread, process hollowing, and DLL injection

Run the `trackmedaddy` command (available on PATH) with the appropriate subcommand based on $ARGUMENTS. Important: invoke it as a plain shell command, do NOT prefix it with the skill directory path.

Diagnose and resolve common Algorand development errors.

Evaluate whether users will *want* a product—not just use it. The complement to friction analysis.

Manages version control with Jujutsu (jj), including rebasing, conflict resolution, and Git interop. Use when tracking changes, navigating history, squashing/splitting commits, or pushing to Git remotes.

>

>

本系统为**任何长期与AI协作的用户**建立认知状态追踪机制。通过分析你的日常输入（工作日志、日记、复盘等），构建持续更新的十维人格特征空间，使AI能够：

A complete marketing system captured on a single page. Instead of a 50-page marketing plan that never gets executed, the 1-Page Marketing Plan distills everything into a 3x3 grid of nine squares — eac

Governance patterns for orgs where Apex triggers and record-triggered Flows both run on the same object. Covers field-write conflict prevention, single-entry-point consolidation, recursion guards across automation types, and automation inventory documentation. Use when inheriting a mixed-automation org, adding a Flow to an object that already has triggers, or resolving silent field-overwrite bugs. NOT for order-of-execution mechanics (use order-of-execution-deep-dive). NOT for trigger handler framework design (use trigger-framework). NOT for Flow-only design patterns (use record-triggered-flow-patterns).