code-review
Reviews code and suggests improvements. Use when asked to review code or propose refactors.
Reviews code and suggests improvements. Use when asked to review code or propose refactors.
Comprehensive TypeScript engineering guidelines based on Google's TypeScript Style Guide. This skill should be used when writing TypeScript code, performing TypeScript code reviews, or answering questions about TypeScript best practices. Applies to .ts and .tsx files, and TypeScript configuration.
Performs AST-based code search and refactoring across codebases. Understands syntax structure, ignores strings and comments. Use when renaming functions, replacing patterns, migrating APIs, finding code structures, or doing mass refactors. Better than grep for code changes.
Code search, analysis, and refactoring using AST patterns. Search code structure, analyze modules, and refactor with precision. KEYWORDS: ast, syntax, parse, surgical, replace, transform, refactor, rename, symbol, class, function, method.
Syntax highlight code blocks with Shiki. Supports server-side rendering in RSC and automatic light/dark theme switching.
Use this skill when the user provides a code snippet and wants a quick quality analysis, statistics, or readability score.
Universal code generator - clones your existing code style exactly
Use when exploring/explaining code, designing/updating architecture, or when asked to visualize structure. Shows annotated file trees inline.
Internationalize and localize applications using ampel-i18n-builder. Use when the user wants to (1) extract translatable strings from source code, (2) refactor code to automatically replace hardcoded strings with i18n calls, (3) add multi-language support to a project, (4) translate an app into multiple languages, (5) generate i18n translation files, (6) check translation coverage or find missing translations, (7) sync translations across locales, or when user types /ampel-i18n:localize. Supports React/TypeScript (JSON), Rust (YAML), and Java/Spring (.properties).
Fast semantic code navigation via LSP. Load FIRST before ANY code task - even 'simple' ones. Trigger scenarios: (1) fixing lint/type/pyright/mypy warnings or errors, (2) fixing reportAny/reportUnknownType/Any type errors, (3) adding type annotations, (4) refactoring or modifying code, (5) finding where a function/class/symbol is defined, (6) finding where a symbol is used/referenced/imported, (7) understanding what a function calls or what calls it, (8) exploring unfamiliar code or understanding architecture, (9) renaming symbols across codebase, (10) finding interface/protocol implementations, (11) ANY task where you'd use ripgrep to find code or read-file to view a function. Use `leta show SYMBOL` instead of read-file, `leta refs SYMBOL` instead of ripgrep for usages, `leta grep PATTERN` instead of ripgrep for definitions, `leta files` instead of list-directory.
Create IDAPython plugins for IDA Pro 9.x with HCLI-compatible packaging. Use when user wants to build IDA plugins with UI (dockable widgets, dialogs, menus, choosers), actions, keybindings, event hooks, or settings. Generates complete plugin code and manifest for installation via hcli.
Apply token optimization when writing docs, changelogs, MCP tasks. Quality
Use when creating Mermaid diagrams - covers flowcharts, sequence diagrams, and AST visualization
Guidelines for adding functionality to the @monque/core package. Use this when implementing new features, fixing bugs, or refactoring code in the core package.
Emacs Lisp package development standards and conventions
Use when designing language features - covers lexer, parser, AST, and interpreter patterns
Comprehensive guide for this Neovim configuration - a modular, performance-optimized Lua-based IDE. Use when configuring plugins, adding keybindings, setting up LSP servers, debugging, or extending the configuration. Covers lazy.nvim, 82+ plugins across 9 categories, DAP debugging, AI integrations, and performance optimization.