ImaginerLabs
55 verified skills
context-learning
Quickly understands unfamiliar code by tracing imports, call chains, and data flows. Produces concise context analysis covering module purpose, dependencies, logic flow, and side effects. Should be used when the user needs to understand code they didn't write — onboarding, investigating bugs, preparing for code review, or figuring out how a feature works. Distinguished from explore which focuses on project-wide investigation, this skill focuses on tracing code references and understanding specific code contexts.
development
pre-commit-review
Chain-combined skill that merges git-commit behavior with code-review judgment to create intelligent pre-commit workflow. Encapsulates the decision of WHEN to require review before commit, WHAT to check in pre-commit review, and HOW to structure commit workflow. Use when user mentions pre-commit review, commit with review, pre-commit checks, or when they want to establish commit quality gates. Triggers especially when user says "should I review before commit?", "what should I check before committing?", "commit workflow", or when they're unsure whether their commit is ready.
development
trace-execution
Master tracing code execution: how to follow execution paths, set strategic breakpoints, and understand control flow. Use when debugging, understanding code flow, or when you need to figure out how code reaches a certain point. Triggers especially when user says "trace execution", "follow the code", "debugging execution", "breakpoint strategy", "control flow", or "how does this get called".
development
security-review
AI-powered codebase security scanner that reasons about code like a security researcher — tracing data flows, understanding component interactions, and catching vulnerabilities that pattern-matching tools miss. Use this skill when asked to scan code for security vulnerabilities, find bugs, check for SQL injection, XSS, command injection, exposed API keys, hardcoded secrets, insecure dependencies, access control issues, or any request like "is my code secure?", "review for security issues", "audit this codebase", or "check for vulnerabilities". Covers injection flaws, authentication and access control bugs, secrets exposure, weak cryptography, insecure dependencies, and business logic issues across JavaScript, TypeScript, Python, Java, PHP, Go, Ruby, and Rust.
tools
web-artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
tools
git-rebase-safety
Master safe rebasing: when to use rebase vs merge, how to handle conflicts, and how to ensure history integrity. Use when user mentions rebasing, git rebase, rebase conflicts, rebase vs merge, or when they're unsure about rebasing strategy. Triggers especially when user says "should I rebase?", "rebase vs merge", "how to resolve rebase conflicts", or "is it safe to rebase?".
testing
test-think
Master the thinking process behind effective testing decisions. This skill encapsulates the judgment of WHAT to test, WHAT NOT to test, and the prioritization framework for test coverage. Use when user mentions test strategy, testing decisions, what cases to cover, over-testing concerns, or asks "should I test this?". Triggers especially when user is unsure about testing scope, test coverage decisions, or when they say things like "should I write a test for this?", "is this worth testing?", "what test cases do I need?", or "how much testing is enough?".
development
web-design-reviewer
This skill enables visual inspection of websites running locally or remotely to identify and fix design issues. Triggers on requests like "review website design", "check the UI", "fix the layout", "find design problems". Detects issues with responsive design, accessibility, visual consistency, and layout breakage, then performs fixes at the source code level.
development
test-readability
Master writing readable tests: how to structure tests for clarity, name tests descriptively, and make tests self-documenting. Use when writing tests, reviewing test quality, or when tests are hard to understand. Triggers especially when user says "readable tests", "test structure", "test naming", "test organization", "self-documenting tests" or "clear tests".
testing
reproduce-bug
Master reliable bug reproduction: how to construct minimal reproduction cases, isolate conditions, and verify bugs consistently. Use when debugging, creating bug reports, or when a bug is hard to reproduce. Triggers especially when user says "reproduce bug", "can't reproduce", "minimal case", "bug report", or "isolating the bug".
development
safe-refactor
Chain-combined skill that ensures refactoring is done safely by combining refactor judgment, test coverage verification, and pre-commit review. Encapsulates the decision of WHEN to refactor, HOW to ensure safety, and WHAT verification is needed. Use when user mentions refactoring, code restructuring, improving code quality, or when they want to refactor without breaking behavior. Triggers especially when user says "should I refactor this?", "is it safe to refactor?", "how do I refactor without breaking things?", or "refactor my code".
development
react-component-extraction
Extracts reusable UI or stateful logic into independent components or custom Hooks. Analyzes context dependencies, evaluates extraction boundaries, and ensures zero breakage for existing callers. Should be used when the user wants to extract, split, or isolate a piece of React code — creating reusable components, custom Hooks, or separating concerns within a large component. Distinguished from react-component-refactor which restructures the entire component, this skill focuses on extracting specific reusable pieces.
development
inspect-state
Master runtime state inspection: how to examine variable values, object state, and data structures during execution. Use when debugging, understanding variable contents, or when code behavior is unexpected. Triggers especially when user says "inspect variable", "check state", "what's in this object", "variable value", "runtime inspection" or "debug state".
development
git-history-rewrite
Master git history manipulation: when modifying history is safe, git reset/rebase alternatives, and maintaining history integrity. Use when user mentions git history, rewriting commits, git reset, amending commits, or when they want to clean up commit history. Triggers especially when user says "clean up history", "rewrite git history", "git reset", "amend commit", or "squash commits".
testing
generate-mock
Master the art of creating effective mocks: when to mock, what to mock, and how to avoid over-mocking. This skill encapsulates the judgment of mock strategy, mock depth, and maintaining test reliability. Use when user mentions mocking, mocks, test doubles, stubbing, or when they're unsure about mock strategy. Triggers especially when user says "should I mock this?", "how to mock", "mock strategy", "too many mocks", or "test mocks".
testing
debug-test
Master debugging failing tests: when tests fail, how to determine if it's a real bug or test issue, and how to fix test problems without breaking production code. Use when tests fail, test debugging, fixing broken tests, or when tests don't work as expected. Triggers especially when user says "test failed", "debug test", "fix test", "test not working", "why is this test failing".
development
doublecheck
Three-layer verification pipeline for AI output. Extracts verifiable claims, finds supporting or contradicting sources via web search, runs adversarial review for hallucination patterns, and produces a structured verification report with source links for human review.
development
security-auditor
Fortress（安全审计师）专注于代码安全和漏洞检测，保护应用安全。 Should be used when the user mentions checking security vulnerabilities, reviewing code for SQL injection/XSS risks, auditing authentication/authorization, checking dependency security, reviewing encryption practices, or conducting security audits. Distinguished from debug-expert which focuses on general bugs rather than security vulnerabilities.
development
system-architect
Blueprint（系统架构师）负责整体技术方案设计、架构决策和技术选型。 Should be used when the user mentions designing system architecture, making technology stack decisions, planning microservices decomposition, reviewing architecture designs, or designing high-availability systems. Distinguished from cloud-architect which focuses on cloud-specific infrastructure, and from code-engineer which handles implementation details.
development
performance-optimizer
Turbo（性能优化师）专注于应用性能分析和优化，提升系统响应速度。 Should be used when the user mentions analyzing performance bottlenecks, optimizing page load time, reducing API latency, improving React performance, database query optimization, or cache strategies. Distinguished from code-engineer which focuses on writing new functionality rather than optimizing existing code performance.
development
code-engineer
Alex（代码工程师）是全栈代码生成专家，专注于从需求、注释或接口设计生成完整可执行代码。 Should be used when the user mentions implementing features, writing/generating code, refactoring existing code, creating components, building APIs from specs, or translating designs into code implementations. Does NOT trigger for testing (use edge-case-master), debugging (use debug-expert), or performance optimization (use performance-optimizer).
development
data-architect
Schema（数据架构师）专注于数据模型设计、数据库架构和数据治理。 Should be used when the user mentions designing database schemas, designing data models, optimizing query performance, planning data migration, designing data warehouses, or discussing data governance strategies. Distinguished from api-designer which focuses on API contracts rather than underlying data storage, and from code-engineer which handles implementation.
development
api-designer
Endpoint（API 设计师）专注于 RESTful/GraphQL 接口设计与文档生成。 Should be used when the user mentions designing APIs, creating interface specifications, generating OpenAPI/Swagger documentation, reviewing API contracts, or defining API governance rules. Distinguished from code-engineer which handles implementation, and from data-architect which focuses on data models rather than interfaces.
development
claude-api
Build, debug, and optimize Claude API / Anthropic SDK apps. Apps built with this skill should include prompt caching. TRIGGER when: code imports anthropic/@anthropic-ai/sdk; user asks to use the Claude API, Anthropic SDKs, or Managed Agents (/v1/agents, /v1/sessions, /v1/environments). DO NOT TRIGGER when: code imports `openai`/other AI SDK, general programming, or ML/data-science tasks.
development
cloud-architect
Cloudy（云架构师）专注于云服务架构设计、部署方案和成本优化。 Should be used when the user mentions cloud architecture design, selecting cloud services (AWS/GCP/Azure), deployment strategies, cost optimization for cloud resources, Kubernetes/Docker container orchestration, or multi-cloud strategies. Distinguished from deployment-engineer which focuses on CI/CD pipelines and scripts, and from system-architect which focuses on overall system design rather than cloud-specific infrastructure.
testing
code-comment-writer
Writes precise, reader-oriented code comments explaining "why" not "what". Covers onboarding, refactoring, algorithm explanation, tech debt marking, and API integration scenarios. Should be used when the user mentions adding comments, documenting code, explaining code logic, improving code readability, or needs help understanding code during handoff. Distinguished from refactoring skills which focus on code structure changes.
development
create-implementation-plan
Create a new implementation plan file for new features, refactoring existing code or upgrading packages, design, architecture or infrastructure.
devops
cross-branch-fix-porter
Cross-branch fix porting expert. Understands fix intent and re-implements the same fix goal in the current branch's code context when direct cherry-pick isn't feasible. Should be used when the user needs to apply a fix from one branch to another where code structures differ significantly. Distinguished from feature-port-doc-generator which documents changes, this skill actively re-implements fixes.
development
debug-expert
Sherlock（调试专家）专注于智能问题定位和修复，像福尔摩斯一样通过细致观察和逻辑推理找到问题根因。 Should be used when the user mentions debugging errors, analyzing crashes, investigating why something is not working, examining error messages/stack traces, or diagnosing unexpected behavior in code. Distinguished from security-auditor which focuses on security vulnerabilities rather than general bugs, and from code-engineer which focuses on writing new code.
development
debug-session
Chain-combined skill for systematic debugging workflow. Combines bug reproduction judgment, error analysis, execution tracing, and debugging expertise into a complete session规范. Use when user mentions debugging, fixing bugs, something not working, error messages, or when code isn't behaving as expected. Triggers especially when user says "debug this", "why is this broken", "it's not working", "error message", "something went wrong", or "help me find the bug".
development
deployment-engineer
Deployer（部署工程师）专注于部署流程自动化、CI/CD 配置和环境管理。 Should be used when the user mentions configuring CI/CD pipelines, writing deployment scripts, creating Dockerfiles, Kubernetes configurations, managing environment variables, or planning release workflows. Distinguished from cloud-architect which focuses on cloud service selection and high-level infrastructure rather than CI/CD scripts and container configs.
testing
docx
Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.
development
edge-case-master
Fuzz（边界用例大师）是测试用例生成专家，专注于边界条件、异常场景和压力测试。 Should be used when the user mentions generating test cases, creating boundary tests, writing unit tests, E2E tests, exception handling tests, or improving test coverage. Distinguished from code-engineer which focuses on writing application code rather than test code.
development
excalidraw-diagram-generator
Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.
tools
explain-code
Master the art of explaining code clearly: how to distill complex logic into understandable explanations, adjust depth for audience, and make unfamiliar code accessible. Use when user asks to explain code, understand code, document code, or when they need to communicate how code works. Triggers especially when user says "explain this code", "what does this do", "how does this work", "help me understand", or "explain this function".
development
explore
Explores unfamiliar codebases, diagnoses problems, and provides contextual insights. Analyzes project structure, traces code logic, identifies issues, and generates actionable recommendations. Should be used when the user needs to explore or investigate a codebase — understanding project structure, diagnosing bugs, tracing feature implementation, or assessing code quality. Distinguished from context-learning which focuses on tracing specific code references, this skill focuses on project-wide exploration and diagnosis.
development
feature-port-doc-generator
Generates standardized porting documentation from completed feature changes. Analyzes commit diffs or file contents, extracts change intent, and outputs Markdown documentation for cross-team understanding. Should be used when the user needs to document a change for cross-team or cross-project consumption. Distinguished from cross-branch-fix-porter which actively re-implements fixes, this skill documents changes.
documentation
frontend-code-review
Comprehensive frontend code quality audit covering ESLint, robustness, side effects, and performance for React/Vue/Taro projects. Should be used when the user needs a thorough code quality check — before committing, during PR review, after refactoring, or when inheriting someone else's code. Distinguished from staged-code-review which focuses on git staged changes pre-commit, this skill focuses on general frontend code quality auditing.
development
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
development
frontend-staged-bundle-review
Reviews staged git changes from a bundle size perspective. Analyzes change intent and provides optimization recommendations for React/Vue/Taro/Next.js projects. Should be used when the user is concerned about bundle size, code bloat, or package weight — before committing or evaluating new dependencies. Distinguished from frontend-code-review which focuses on code quality, this skill focuses specifically on bundle size impact analysis.
development
git-branch-strategy
Master Git branching decisions: when to create branches, naming conventions, branch lifecycle management, and cleanup strategies. Use when user mentions branching, branch names, git workflow, branch management, or when they're unsure about which branch to create or how to organize branches. Triggers especially when user says "should I create a branch?", "what should I name this branch?", "branch naming convention", "how to organize branches", or "when to create a branch".
testing
git-commit
Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping
research
git-merge-resolution
Master git merge conflict resolution: when to merge vs rebase, conflict handling strategies, and maintaining clean merge history. Use when user encounters merge conflicts, git merge issues, or when they need to combine branch histories. Triggers especially when user says "merge conflict", "resolve conflicts", "git merge", "merge strategy", or "conflicts in git".
testing
git-stash-management
Master git stash: when to stash, how to organize stashes, naming strategies, and recovery patterns. Use when user mentions git stash, stashing changes, saving work in progress, or when they have uncommitted changes they need to set aside. Triggers especially when user says "should I stash this?", "git stash", "save my changes", "switch branches with uncommitted work", or "recover stash".
testing
intelligent-test-creation
Chain-combined skill for creating comprehensive, intelligent tests by combining test-think (what to test), generate-mock (mocking strategy), and setup-test-data (test fixtures). Use when user needs to write tests, wants intelligent test coverage, or when they're unsure what tests to write for a feature. Triggers especially when user says "write tests for this", "how to test this", "test coverage", "what tests do I need", or "generate test cases".
testing
mcp-builder
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
tools
quality-analyst
Metric（质量分析师）专注于代码质量评估和技术债追踪。 Should be used when the user mentions evaluating code quality, tracking technical debt, generating quality reports, analyzing code coverage, measuring code complexity, or assessing code maintainability. Distinguished from security-auditor which focuses on security vulnerabilities rather than general code quality metrics.
development
react-component-refactor
Analyzes React component structure, identifies reusable units, and refactors large or messy components into clean, well-organized code. Strictly maintains 1:1 logic equivalence — only structure changes, never behavior. Should be used when the user wants to refactor a React component — splitting a monolith, reorganizing a messy file, or restructuring for better maintainability. Distinguished from react-component-extraction which extracts specific reusable pieces, this skill restructures the entire component.
development
react-performance
Reviews and optimizes React component performance and correctness. Covers stale closures, unnecessary re-renders, useEffect cleanup, state design, debounce/throttle, and race conditions. Should be used when the user is concerned about React performance — slow renders, stale closure bugs, or optimizing useMemo/useCallback usage. Distinguished from frontend-code-review which covers general code quality, this skill focuses specifically on React performance and Hook-related issues.
development
read-test-coverage
Master reading test coverage reports: how to interpret coverage metrics, understand what they mean, and identify untested gaps. Use when analyzing code coverage, identifying test gaps, or when coverage numbers don't match expectations. Triggers especially when user says "test coverage", "coverage report", "interpret coverage", "untested code", or "what's not tested".
development
refactor
Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.
development
setup-test-data
Master test data setup: creating meaningful test fixtures, test data factories, and managing test data lifecycle. Use when user needs test data, test fixtures, sample data for tests, or when tests are hard to maintain due to data setup. Triggers especially when user says "test fixtures", "test data", "setup test", "create test objects", or "sample data".
testing
staged-code-review
Comprehensive pre-commit review of git staged changes. Performs tech-stack-aware code quality checks and generates conventional commit messages. Should be used when the user is about to commit code and wants a quality gate — catching debug leftovers, sensitive data, missing error handling before they enter the repository. Distinguished from frontend-code-review which reviews general code quality, this skill focuses specifically on git staged changes pre-commit.
development
tech-stack-detection
Systematically scans project config files to identify tech stack composition, version info, and engineering tooling. Should be used when the user needs to understand what technologies a project uses — onboarding, evaluating upgrade feasibility, or troubleshooting build issues. Distinguished from explore which investigates project structure and problems, this skill focuses on identifying technology stacks.
tools
understand-error
Master the art of correctly interpreting error messages, stack traces, and failure indicators. This skill encapsulates the judgment of WHAT an error really means, WHERE it originates, and WHY it occurred. Use when user encounters an error message, unexpected behavior, exception, or when code fails with any kind of diagnostic output. Triggers especially when user pastes an error message and asks "what does this mean?", "why am I getting this error?", "how do I fix this?", or "error message explained".
development