klen/dotfiles

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

원문 언어: 영어

coverage

Evaluate test coverage and fill real gaps with high-value tests.

원문 언어: 영어

github-cli

Use the `gh` CLI for all GitHub interactions — issues, PRs, discussions, releases, repos, Actions, and API calls. Prefer `gh` over direct web browsing, web search, or raw git/HTTPS API calls whenever the target is on GitHub. Avoid cloning repos to read files;…

원문 언어: 영어

browser

Browser automation CLI for AI agents. Use for website interaction tasks such as navigating pages, filling forms, clicking buttons, screenshots, scraping, testing web apps, logins, or other programmatic browser actions.

원문 언어: 영어

build

Implement one task or scoped change: make the change, add valuable tests, and verify it works.

원문 언어: 영어

debug

Debug systematically: observe, hypothesize, test, fix, verify.

원문 언어: 영어

plan

Break a spec into small, implementation-ready tasks. Use when a spec exists and the work needs execution order, acceptance criteria, and verification.

원문 언어: 영어

refactor

Refactor code to simplify it without changing behavior.

원문 언어: 영어

review

Review concrete changes and report evidence-backed bugs, regressions, and risks.

원문 언어: 영어

spec

Write a short implementation spec before coding. Use when starting new work, when requirements are unclear, or when a change needs explicit boundaries.

원문 언어: 영어

tdd

Use test-first development for behavioral changes. Write a failing test, make it pass, then simplify.

원문 언어: 영어

code-architecture-tailwind-v4-best-practices

Guides Tailwind CSS v4 patterns for buttons and components. Use this skill when creating components with variants, choosing between CVA/tailwind-variants, or configuring Tailwind v4's CSS-first approach.

원문 언어: 영어

code-architecture-wrong-abstraction

Guides when to abstract vs duplicate code. Use this skill when creating shared utilities, deciding between DRY/WET approaches, or refactoring existing abstractions.

원문 언어: 영어

conventional-commit

Structure commit messages following the Conventional Commits specification. Use when drafting commit messages before coding or reviewing commit message quality.

원문 언어: 영어

css-container-queries

Apply CSS container queries for component-based responsive design. Use when implementing responsive components that adapt to their container size rather than viewport size.

원문 언어: 영어

five-whys

Conduct root cause analysis using the Five Whys technique. Use when investigating problems, debugging issues, understanding failures, analyzing churn, or finding the underlying cause of any issue.

원문 언어: 영어

graph-thinking

Apply graph-based thinking to visualize complex relationships and solve problems non-linearly. Use when mapping dependencies, analyzing systems, exploring interconnected concepts, or designing architectures.

원문 언어: 영어

hypothesis-tree

Structure complex questions into testable hypotheses. Use when validating product ideas, debugging problems, planning experiments, or breaking down ambiguous challenges into actionable research.

원문 언어: 영어

jobs-to-be-done

Understand customer motivations through job theory. Use when defining product strategy, conducting user research, identifying competitors, writing user stories, or reframing features around customer progress.

원문 언어: 영어

karpathy-guidelines

Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.

원문 언어: 영어

naming-cheatsheet

Apply language-agnostic naming conventions using the A/HC/LC pattern. Use when naming variables, functions, or reviewing code for naming consistency.

원문 언어: 영어

pest-analysis

Guides PEST (Political, Economic, Social, Technological) analysis for strategic planning. Use when analyzing external macro-environmental factors or evaluating business decisions.

원문 언어: 영어

react-key-prop

Guides proper usage of the key prop in React lists. Use this skill when rendering lists, mapping arrays to components, or troubleshooting list-related state bugs.

원문 언어: 영어

react-use-callback

Guides proper usage of the useCallback hook in React. Use this skill when optimizing function references, passing callbacks to memoized components, or preventing unnecessary re-renders.

원문 언어: 영어

react-use-client-boundary

Guides proper usage of "use client" directive in React/Next.js. Use this skill when adding client components, troubleshooting Server Component errors, or deciding where to place the client boundary.

원문 언어: 영어

react-use-state

Guides proper usage of React useState hook. Use this skill when adding state to components, deciding between useState vs alternatives, or troubleshooting state update issues.

원문 언어: 영어

react-useeffect-avoid

Guides when NOT to use useEffect and suggests better alternatives. Use when reviewing React code, troubleshooting performance, or considering useEffect for derived state or form resets.

원문 언어: 영어

typescript-advanced-types

Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications. Use when implementing complex type logic, creating reusable type utilities, or ensuring…

원문 언어: 영어

typescript-best-practices

Guides TypeScript best practices for type safety, code organization, and maintainability. Use this skill when configuring TypeScript projects, deciding on typing strategies, writing async code, or reviewing TypeScript code quality.

원문 언어: 영어

typescript-interface-vs-type

Guides when to use interface vs type in TypeScript. Use this skill when defining object types, extending types, or choosing between interface and type aliases.

원문 언어: 영어

typescript-satisfies-operator

Guides proper usage of TypeScript's satisfies operator vs type annotations. Use this skill when deciding between type annotations (colon) and satisfies, validating object shapes while preserving literal types, or troubleshooting type inference issues.

원문 언어: 영어

what-not-to-do-as-product-manager

Anti-patterns and mistakes to avoid as a product manager. Use when evaluating leadership behaviors, improving team dynamics, reflecting on management practices, or onboarding new product managers.

원문 언어: 영어