Iterative deep planning with critiques and alternatives. Use when facing complex design decisions, architecture choices, or implementation strategies that require thorough analysis. Trigger for any request involving "how should I design", "what's the best approach", "help me plan", "architecture decision", "trade-offs between", or when a user is choosing between multiple technical approaches. Also trigger when a proposed plan needs critique or when the stakes of a wrong decision are high. Prefer this skill over a one-shot answer whenever the problem has meaningful complexity, multiple valid approaches, or non-obvious failure modes.

2026-03-221

no-use-effect

gokulkrishh/skills

Enforce the no-useEffect rule when writing or reviewing React code. ACTIVATE when writing React components, refactoring existing useEffect calls, reviewing PRs with useEffect, or when an agent adds useEffect "just in case." Provides the five replacement patterns and the useMountEffect escape hatch.

2026-03-181

motion-base-ui

gokulkrishh/skills

Animating Base UI components with Motion for React. Use this skill when implementing animations on Base UI components (Menu, Dialog, Popover, Tooltip, Switch, etc.) with the Motion library. Triggers on: motion animation, base-ui animate, animate dropdown, animate dialog, animate popover, exit animation, spring animation, render prop animation, AnimatePresence base-ui.

2026-03-141

ux-writing

gokulkrishh/skills

Write, review, and improve UX copy -- error messages, button labels, empty states, tooltips, onboarding flows, and all interface microcopy. Use when writing or fixing user-facing text in a product. Outputs production-ready copy with rationale.

2026-03-081

code-review

gokulkrishh/skills

Reviews code for security (OWASP), performance, accessibility, and quality. Outputs findings by severity (Critical, Warning, Suggestion, Good) with a verdict. Use when reviewing code, diffs, or PRs.

2026-03-081

name	commit
description	Generates a conventional commit (feat/fix/refactor/docs/chore) with a clear, lowercase message based on staged or unstaged changes.
argument-hint	[optional: commit scope or message hint]
model	haiku
effort	low
user-invocable	true

Instructions

Run git diff --staged to see staged changes. If nothing is staged, run git diff to see unstaged changes and stage them with git add (specific files, not -A).
Analyze the diff and determine the commit type:
- feat: — new feature or functionality
- fix: — bug fix or correction
- refactor: — code restructuring without behavior change
- docs: — documentation only
- chore: — tooling, deps, config changes
Write a concise, lowercase conventional commit message (no period at end). Focus on the "what" in a single line.
Commit using:

git commit -m "$(cat <<'EOF'
type: message here

EOF
)"

Do NOT push unless explicitly asked.
Show the commit hash and message after committing.

Style Rules

Always lowercase after the type prefix
No trailing period
Keep under 72 characters
Single line — no multi-line body unless the change is complex
Examples from this repo:
- fix: simplify user authentication fallback rendering and improve loading skeleton styles
- feat: add motion-plus dependency and remove setup script for auth token injection
- refactor: remove unused SignIn import from DemoState component