Git & Version Control

Use when building a personal productivity or operating system for a CEO, founder, or executive - when user mentions annual reviews, personal OS, life planning, goal setting systems, executive coaching frameworks, Bill Campbell / Trillion Dollar Coach, startup failure patterns, Good to Great / Level 5 Leadership, Buy Back Your Time, E-Myth / work ON not IN your business, or Customer Development / Steve Blank / get out of the building

Complete Windows file path troubleshooting knowledge for Claude Code on Git Bash and Windows environments. PROACTIVELY activate for: (1) File path errors on Windows, (2) Backslash vs forward slash issues, (3) Edit/Write/Read tool failures, (4) MINGW path resolution, (5) Cross-platform path conversion.

TypeScript best practices. Use when writing TypeScript code for backend services, API handlers, or shared utilities. Applies async/await patterns, typed errors, and strict type safety.

Single source of truth and librarian for ALL Claude official documentation. Manages local documentation storage, scraping, discovery, and resolution. Use when finding, locating, searching, or resolving Claude documentation; discovering docs by keywords, category, tags, or natural language queries; scraping from sitemaps or docs maps; managing index metadata (keywords, tags, aliases); or rebuilding index from filesystem. Run scripts to scrape, find, and resolve documentation. Handles doc_id resolution, keyword search, natural language queries, category/tag filtering, alias resolution, sitemap.xml parsing, docs map processing, markdown subsection extraction for internal use, hash-based drift detection, and comprehensive index maintenance.

Create robust, error-proof Prisma seed scripts with comprehensive error handling and validation.

Prepare and execute an addon release, including version bumping, changelog updates, git tagging, and validation. Use when ready to publish a new version. Triggers: release, version bump, changelog, git tag, publish.

ArkTS Language Specification. ArkTS is a statically-typed programming language developed by Huawei for HarmonyOS, extending TypeScript with features from Java and Kotlin. Use for ArkTS syntax, types, classes, functions, and language features.

Browser automation skill for Lovable deployments. Activates when:- yolo_mode: on in CLAUDE.md- Running /deploy-edge or /apply-migration commands- After git push when auto_deploy: on (automatic detection)- Any mention of "yolo mode", "automate Lovable", "browser automation"Automatically navigates to Lovable.dev and submits deployment prompts.Runs verification tests based on configuration.Auto-deploys after git push when enabled.

Fix session protocol validation failures in GitHub Actions. Use when a PR fails with "Session protocol validation failed", "MUST requirement(s) not met", "NON_COMPLIANT" verdict, or "Aggregate Results" job failure in the Session Protocol Validation workflow. With deterministic validation, failures show exact missing requirements directly in Job Summary - no artifact downloads needed.

Configure issue classification for ADWs to route work to the correct templates. Use when setting up automatic classification of GitHub issues into chores, bugs, and features.

MUST use this skill when user asks to check/review PR comments, address reviewer feedback, fix review issues, or respond to code review. Fetches unresolved review comments from GitHub PR for the current branch.

Manage git worktrees with PR workflow and multi-agent review (Claude + Codex). Use when developing features in isolation with easy rollback.

CSS-first approach - use CSS before JavaScript. Triggers: レイアウト, スタイル, 位置, アニメーション, 表示/非表示, トグル, レスポンシブ, CSS Grid, Flexbox, transforms, transitions, CSSのみ, JavaScript不要, シンプル

GitHub API integration for issues, pull requests, workflows, and repository management. Use when working with GitHub issues, PRs, releases, or CI/CD workflows.

Safely amend commits (HEAD or non-HEAD) with selective staging and safety checks

CLAIM a specific GitHub issue to START working on it. Requires an issue number. Performs validation, atomic claim, posts claim comment, and sets up worktree.USE THIS SKILL WHEN:- User says "claim issue #N" or "claim #N"- User says "start working on issue #N" or "take issue #N"- User says "I'll work on #N" or "pick up #N"- User wants to BEGIN work on a specific issue number- User selected an issue from available work and wants to claim itREQUIRED: An issue number must be specified or identifiable from context.DO NOT USE THIS SKILL WHEN:- User just wants to SEE status (use ghe-status)- User is ALREADY working and wants to post update (use ghe-checkpoint)- User wants to CHANGE phases (use ghe-transition)- User wants reports (use ghe-report)- No specific issue number is mentionedEXAMPLES:<example>Context: User wants to start work on a specific issueuser: "Claim issue #201"assistant: "I'll use ghe-claim to claim issue #201 with the full protocol"</example><example>Context: User picks from

Expert in macOS Accessibility APIs (AXUIElement) for desktop automation. Specializes in secure automation of macOS applications with proper TCC permissions, element discovery, and system interaction. HIGH-RISK skill requiring strict security controls.

GitHub CLI operations

Activate this skill when users need help with scene preset operations including saving, applying, organizing, or managing source visibility configurations. Triggers include requests like "save this layout", "apply my gaming preset", "switch to BRB mode", "create a preset", "list my presets", "rename preset", or managing saved configurations. This skill orchestrates preset tools for efficient scene state management.

General-purpose skill for Mechanic/Fen ecosystem work. Covers ecosystem context, development tools, component overview, and AFD principles. Use for everyday addon work, exploration, or when unsure which specialized skill to use. Triggers: work, build, develop, create, mechanic, fen, fencore, fenui, ecosystem, addon.