- Skills
- 325
- 仓库
- 1
- 职业覆盖
- 7
- 场景覆盖
- 6
- Stars
- ★ 0
ImaginerLabs 的 Skills 325
meeting-minutes
Generate concise, actionable meeting minutes for internal meetings. Includes metadata, attendees, agenda, decisions, action items (owner + due date), and follow-up steps.
documentation-writer
Diátaxis Documentation Expert. An expert technical writer specializing in creating high-quality software documentation, guided by the principles and structure of the Diátaxis technical documentation authoring framework.
doc-coauthoring
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
code-review-workflow
Executes comprehensive 4-phase code review: basic review, quality check, bundle analysis, and test coverage. Should be used when the user mentions comprehensive code review, checking code quality, or reviewing staged changes with multi-phase analysis. This is the comprehensive review workflow, distinct from focused skills like frontend-code-review, staged-code-review, or code-change-test-designer.
code-change-test-designer
Analyzes code changes and designs comprehensive test cases. Reads diffs, summarizes capability changes, and designs test cases covering main flows and edge cases. Should be used when the user mentions test coverage, designing tests for code changes, or analyzing diff/commit for testing purposes. Distinguished from code-review-workflow which provides comprehensive review, this skill focuses on test case design for code changes.
skill-creator
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
enhanced-skill-creator
Enhances and optimizes existing Skills. Analyzes Skills for trigger accuracy, execution effectiveness, and coverage completeness, then provides optimization recommendations. Should be used when the user mentions optimizing, improving, refactoring, or enhancing Skills. Distinguished from creating new skills — this skill focuses on improving existing ones.
create-implementation-plan
Create a new implementation plan file for new features, refactoring existing code or upgrading packages, design, architecture or infrastructure.
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.
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.
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.
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.
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".
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".
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?".
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".
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.
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.