TypeScript and JavaScript expert with deep knowledge of type-level programming, performance optimization, monorepo management, migration strategies, and modern tooling. Use PROACTIVELY for any TypeScript/JavaScript issues including complex type gymnastics, build performance, debugging, and architectural decisions. If a specialized expert is a better fit, I will recommend switching and stop.
Detect and remove hollow AI filler language, empty superlatives, and vague boosters that degrade Seedance 2.0 prompt quality. Use when a prompt feels generic, over-written, or 'AI-sounding', or when generation output looks bland and needs a quality pass.
Lock character identity, assign @Tag references, and maintain face and hand consistency across multi-character scenes in Seedance 2.0. Covers 360-degree consistency testing and first-frame art direction for image-to-video. Use when a character changes appearance between shots, when building multi-person scenes, or when hands or faces are distorting.
'Diagnose and fix failing or low-quality Seedance 2.0 prompts using a 5-step diagnostic tree. Use when a prompt is consistently failing, producing generic output, or being rejected. Covers blurry/jittery output, camera chaos, character drift, stiff action, and ambiguous results.'
Guide for running code style linters and formatters. Use this when asked to check code style, run linters, or fix formatting issues.
Clean Code principles (DRY, KISS, YAGNI), naming conventions, function design, and refactoring. Use when user says "clean this code", "refactor", "improve readability", or when reviewing code quality.
Review Java concurrency code for thread safety, race conditions, deadlocks, and modern patterns (Virtual Threads, CompletableFuture, @Async). Use when user asks "check thread safety", "concurrency review", "async code review", or when reviewing multi-threaded code.
Java security checklist covering OWASP Top 10, input validation, injection prevention, and secure coding. Works with Spring, Quarkus, Jakarta EE, and plain Java. Use when reviewing code security, before releases, or when user asks about vulnerabilities.
Create effective skills for OpenCode agents. Load FIRST before writing any SKILL.md. Provides required format, naming conventions, progressive disclosure patterns, and validation. Use when building, reviewing, or debugging skills.
Apply repository-standard formatting to minimize diff noise and meet linter expectations.
Core rules for bkit — PDCA methodology, level detection, agent triggering, quality standards. Triggers: bkit rules, core rules, methodology, 핵심 규칙, PDCA 규칙.
Define coding rules, conventions, and standards for AI collaboration. Triggers: convention, coding style, lint, rules, 코딩 규칙, 컨벤션.
Verify codebase quality — architecture consistency, convention compliance, gap analysis. Triggers: code review, architecture check, quality, gap analysis, 코드 리뷰, 품질 검증.
API class validation rules for Scopy plugins. Auto-loads when reviewing or editing `*_api.h` / `*_api.cpp` files or running API quality checks.
RST documentation conventions for Scopy plugins including heading styles, toctree syntax, image placeholders, and attribute table format. Auto-loads when writing RST documentation for Scopy plugins.
JS automated test validation rules for Scopy plugins. Auto-loads when reviewing or writing test automation scripts in `js/testAutomations/`.
Generates and maintains a design manifest for visual consistency. In existing projects, reads current styles and documents the design language. In new projects, asks a few questions and generates a starter manifest. The post-edit hook reads the manifest and flags deviations.
CC アプデ統合の品質ガードレール。Feature Table 追加時に「書いただけ」を検出し、実装案を強制出力。Use when reviewing CC update integration PRs. Do NOT load for: implementation work, standard reviews, setup.
