iceywu-dev-workflow
IceyWu Dev Workflow
A concise execution playbook centered on @iceywu/utils development and integration.
When to Use
- Selecting utility functions for app/business logic
- Extracting duplicated code into reusable utilities
- Fixing utility edge cases and regression bugs
- Reviewing or preparing pull requests related to
@iceywu/utils
Workflow
- Confirm utility intent
- Define expected input/output and error behavior
- Prefer deterministic, side-effect-free helpers
More from iceywu/skills
frontend-docs-context7
Use this skill when users ask for frontend library/framework usage, APIs, best practices, or examples (e.g. Vue, Vite, React, Tailwind). Always fetch up-to-date docs with Context7.
28frontend-dev-tools
Use this skill when users ask to run/open/preview/debug a frontend project (including Chinese intents like 运行/打开/预览/调试). Enforce MCP browser tools (Playwright/Chrome DevTools) first, then fallback only if MCP is unavailable.
26vue
Vue 3 Composition API, script setup macros, reactivity system, and built-in components. Use when writing Vue SFCs, defineProps/defineEmits/defineModel, watchers, or using Transition/Teleport/Suspense/KeepAlive.
24pnpm
Node.js package manager with strict dependency resolution. Use when running pnpm specific commands, configuring workspaces, or managing dependencies with catalogs, patches, or overrides.
24vite
Vite build tool configuration, plugin API, SSR, and Vite 8 Rolldown migration. Use when working with Vite projects, vite.config.ts, Vite plugins, or building libraries/SSR apps with Vite.
24web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
24