clean-architecture 是做什麼的？
來自 Robert C. Martin 著作的 Clean Architecture 原則與最佳實踐。適用於設計軟體系統、審查程式碼結構或重構應用程式以實現更好的關注點分離。觸發時機包括涉及層級、邊界、依賴方向、實體、使用案例或系統架構的任務。
來自 Robert C. Martin 著作的 Clean Architecture 原則與最佳實踐。適用於設計軟體系統、審查程式碼結構或重構應用程式以實現更好的關注點分離。觸發時機包括涉及層級、邊界、依賴方向、實體、使用案例或系統架構的任務。
此技能基於 Robert C. Martin 的 Clean Architecture 原則，幫助開發者在設計、審查或重構軟體系統時，實現更好的關注點分離與架構清晰度。它適用於任何涉及層級（Layers）、邊界（Boundaries）、依賴方向（Dependency Direction）、實體（Entities）、使用案例（Use Cases）或系統架構的任務。技能支援多種平台（如 Claude Code、Cursor、Codex），透過解析專案結構、程式碼模組與依賴關係，提供具體的架構建議與重構指引。其核心價值在於確保軟體內層（如企業邏輯）不依賴於外層（如框架、資料庫），從而提升系統的可測試性、可維護性與可擴展性。開發者在處理跨層通訊、依賴反轉或領域模型設計時，此技能能自動觸發並提供最佳實踐參考。
npx skills add https://github.com/pproenca/dot-skills/tree/main/skills/clean-architecture來自 Robert C. Martin 著作的 Clean Architecture 原則與最佳實踐。適用於設計軟體系統、審查程式碼結構或重構應用程式以實現更好的關注點分離。觸發時機包括涉及層級、邊界、依賴方向、實體、使用案例或系統架構的任務。
This repo contains 7 individual skills — each has its own dedicated page.
Code simplification skill for improving clarity, consistency, and maintainability while preserving exact behavior. Use when simplifying code, reducing complexity, cleaning up recent changes, applying refactoring patterns, or improving readability. Triggers on tasks involving code cleanup, simplification, refactoring, or readability improvements.
Emil Kowalski's animation best practices for web interfaces. Use when writing, reviewing, or implementing animations in React, CSS, or Framer Motion. Triggers on tasks involving transitions, easing, gestures, toasts, drawers, or motion.
nuqs (type-safe URL query state) best practices for Next.js and other React frameworks. This skill should be used when writing, reviewing, or refactoring code that uses nuqs for URL state management. Triggers on tasks involving useQueryState, useQueryStates, search params, URL state, query parameters, nuqs parsers, limitUrlUpdates, Standard Schema, NuqsAdapter, or Next.js routing with state.
React Hook Form performance optimization for client-side form validation using useForm, useWatch, useController, useFieldArray, and the v7.55+ subscribe() API. This skill should be used when building client-side controlled forms with React Hook Form library. This skill does NOT cover React 19 Server Actions, useActionState, or server-side form handling (use react-19 skill for those).
TypeScript performance, tsconfig, type errors, async patterns — triggered when the user asks to "optimize TypeScript performance", "speed up tsc compilation", "configure tsconfig.json", "fix type errors", "improve async patterns", or encounters TS errors (TS2322, TS2339, "is not assignable to"). Also triggers on .ts, .tsx, .d.ts file work involving type definitions, module organization, or memory management. Does NOT cover TypeScript basics, framework-specific patterns, or testing.
Vitest testing framework patterns for test setup, async testing, mocking with vi.*, snapshots, and test performance (formerly test-vitest). This skill should be used when writing or debugging Vitest tests. This skill does NOT cover TDD methodology (use test-tdd skill), API mocking with MSW (use test-msw skill), or Jest-specific APIs.
Zod schema validation best practices for type safety, parsing, and error handling. This skill should be used when defining z.object schemas, using z.string validations, safeParse, or z.infer. This skill does NOT cover React Hook Form integration patterns (use react-hook-form skill) or OpenAPI client generation (use orval skill).
ElevenLabs text-to-speech with mac-style say UX.
Oracle CLI second-model review/debug/refactor/design with selected files, dry-run token checks, API or browser engine.
Capture and automate macOS UI with the Peekaboo CLI.
Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".
Build a throwaway prototype to flesh out a design — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".