Loading...
Loading...
Found 1,049 Skills
Frontend 리팩토링 전문가. "프론트 리팩토링", "UI 리팩토링", "Vue 코드 정리" 키워드로 트리거. 기존 프론트엔드 코드를 test-data 가이드 코드 패턴으로 리팩토링.
Use when a user wants to deploy ClickHouse to the cloud, go to production, use ClickHouse Cloud, host a managed ClickHouse service, or migrate from a local ClickHouse setup to ClickHouse Cloud.
Use this skill when upgrading or migrating an Android project from any legacy Google Play Billing Library (PBL) version to the latest stable version of PBL.
Migrates Temporal, Inngest, Trigger.dev, and AWS Step Functions workflows to the Workflow SDK. Use when porting Activities, Workers, Signals, step.run(), step.waitForEvent(), Trigger.dev tasks / wait.forToken / triggerAndWait, ASL JSON state machines, Task/Choice/Wait/Parallel states, task tokens, or child workflows.
Comprehensive map and workflows for the Database domain. Triggers when users ask to 'design a database', 'optimize query', 'schema architecture', 'database ecosystem', or migrate data.
Migrate Chakra UI projects from v2 to v3, covering package changes, codemods, provider setup, color mode, prop renaming, compound components, theming, recipes, and Next.js updates. Use this skill whenever a user is upgrading Chakra UI versions, encountering breaking changes after an upgrade, converting old v2 patterns (ColorModeScript, useColorModeValue, styleConfig, extendTheme, isDisabled, colorScheme, @chakra-ui/icons, framer-motion dependency), fixing compound component patterns, or asking about differences between Chakra UI v2 and v3 — even if they don't say "migrate" or "upgrade" explicitly.
Build a compilable type-level skeleton from a high-level architecture spec before writing any implementation logic. Use when you have an architectural assessment, design doc, or restructuring plan and need to prove the new architecture is sound before migrating code. Also use when asked to "scaffold the new architecture", "create type stubs", "build the shell", "flesh out this spec", "skeleton the modules", or any request to turn architectural intent into verified structure. This skill follows the "Human Builds the Shell" paradigm: types are hard constraints that the compiler enforces, so if the skeleton compiles, the architecture is structurally sound. Especially valuable for large refactors where you don't trust agents to maintain coherence.
Audits this repo for business rules that should live in the central wiki, not here. Activates when the user asks to check for leaks, audit business rules, or validate the wiki/repo boundary.
This skill is to be used when users explicitly request "migrate LaTeX templates", "integrate old projects into ChineseResearchLaTeX", "apply old bids/papers/graduation theses/resumes to the current template", "organize Word/PDF/Markdown/scattered tex files into existing projects", or directly mention `transfer-old-latex-to-new`. The old alias `migrating-latex-templates` is also supported. This skill only migrates the main content to the content layer of the existing templates in the current repository; it must never modify the source code of public packages in `packages/`, nor modify the template styles or entry skeletons in `projects/`, and can only write to content files allowed to carry the main content in the target project.
Enforces unified ID naming standards and threshold naming rules for all SDD documentation artifacts
Use when architecting OCI solutions, migrating from AWS/Azure, designing multi-AD deployments, or avoiding common OCI anti-patterns. Covers VCN sizing mistakes, Cloud Guard gotchas, free tier specifics, OCI terminology confusion, and multi-AD patterns.
Provides comprehensive guidance for Pinia state management including stores, state, getters, actions, plugins, and TypeScript support. Use when the user asks about Pinia, needs to manage application state, create stores, implement state persistence, or migrate from Vuex.