interview-ready-comments
Adds interviewer-friendly teaching comments (where-it-fits, function walkthroughs, closing block) without changing behavior.
Adds interviewer-friendly teaching comments (where-it-fits, function walkthroughs, closing block) without changing behavior.
Use this when working on the Workbench UI, Workbench state/store, export/compile pipeline, or adapter/target behavior (agents-md, claude-code, github-copilot, etc.).
Senior TypeScript specialist for type-safe full-stack apps. Use for advanced generics, discriminated unions, and strict mode.
C++ development standards including make/cmake, g++/clang++, and static analysis. Use when working with C++ files (.cpp, .hpp, .cc, .hh).
Creates and manages SessionStart hooks for Claude Code to ensure development environment is ready
Add Neovim plugins not available in NixVim's official plugin set using extraPlugins and extraConfigLua. Use this skill when the user requests adding a plugin by GitHub URL or mentions a plugin that doesn't exist as a native NixVim module.
This skill provides TypeScript best practices and conventions for the fitness app. Use when writing TypeScript code, defining types, working with interfaces, or ensuring type safety.
Optimize IC10 code for efficiency and line count. Use when user wants to reduce line count, improve performance, or refactor existing Stationeers IC10 code.
Use when creating new skills or refactoring existing skills - teaches the progressive disclosure architecture pattern to optimize context window usage by organizing skills into 3 tiers (metadata, entry point, references) and avoiding documentation dumps. Essential before any skill creation or modification work.
Safe refactoring operations using LSP for precise symbol resolution. Supports rename, extract function/method, and move symbol operations with automatic reference updates.
Programming language detection and setup patterns
Markdown style patterns to use when writing documents.
Use when the user asks to run Codex CLI (codex exec, codex resume) or references OpenAI Codex for code analysis, refactoring, or automated editing
This skill describes common patterns and my prefered style to use when editing svelte code. This could be in .svelte files or .svelte.ts files.
Find hardcoded strings in Leavn app, add I18n.str() calls, create localization keys for all 6 supported languages (en, es, de, zh-Hans, ar, he)
This skill should be used when you need to know what members, methods, or extensions are available on Kotlin types. It queries autocomplete metadata generated by the kotlin-autocomplete-gradle-plugin.
Your approach to handling global typing. Use this skill when working on files where global typing comes into play.
.NET/C#의 코딩 규약, 명명 규칙, 레이아웃, C# 12/13/14의 최신 기능 활용 가이드라인을 정의합니다. C#/.NET 코드 작성 시, 클래스·메서드 명명 시, 코드 포맷팅 시, 또는 사용자가 코딩 규약, 명명 규칙, C# 모범 사례, Primary Constructors, Collection Expressions, field 키워드에 대해 언급했을 때 사용합니다.
C# 12 and .NET 8 coding standards including primary constructors, collection expressions, async patterns, null handling, and naming conventions. Use when writing or reviewing .NET 8 code.
Save to LOCAL BTR context tree (NOT ByteRover/brv). Capture code snippets, patterns, and context from the current conversation and store them in the BTR context tree. PROACTIVE TRIGGER: Automatically suggest saving when the user confirms something works ("That works!", "Perfect!", "It's working now", "Thanks, that fixed it!"), after fixing a bug, making an architecture decision, establishing a pattern, or solving a complex problem. Also use when the user explicitly says "save this", "remember this pattern", "capture this context", "save to BTR", "save this to BTR", or "add to BTR".