claudefiles

'Use this when the users says: "review existing feature","make this change"

Use when the user says: "extract learnings", "save this for next time", "remember this pattern", "consolidate memories", "dream", "clean up memories".

Use when the user asks about Claude token usage, wants to see how much they are spending on Claude, understand cache hit rates, review Claude Code workflow patterns, or get cost optimization recommendations.

Use when the user asks to recall, search, or continue past conversations. Triggers on "what did we discuss", "continue where we left off", "remember when", "as I mentioned", "you suggested", "we decided", "search my conversations", "find the conversation where", "what did we work on". Also triggers on implicit signals like past-tense references ("the bug we fixed"), possessives without context ("my project"), or assumptive questions ("do you remember").

Generate a commit message

Manage conversations and task context

Use when the user says: "responsive design", "make it mobile-friendly", "adapt for mobile". Make interfaces work across screen sizes with responsive design.

Use when the user says: "add animations", "motion design", "transitions". Add meaningful animations and transitions to interfaces.

Use when the user says: "fix the layout", "arrange this", "visual hierarchy". Improve layout, spatial design, structure, and alignment.

Use when the user says: "audit this UI", "frontend quality", "full UI audit", "design audit". Comprehensive audit of interface quality across accessibility, performance, theming, and responsive design.

Use when the user says: "make it bolder", "more distinctive", "too generic". Make designs more distinctive and visually striking.

Use when the user says: "improve the copy", "error messages are confusing", "UX writing". Improve UX clarity, reduce confusion, and improve information hierarchy.

Use when the user says: "fix the colors", "color system", "palette needs work". Improve color palettes, contrast, and theming.

Use when the user says: "critique this UI", "design critique", "review this interface", "does this look AI-generated". Evaluate design effectiveness with actionable feedback.

Use when the user says: "add delight", "make it more fun", "moments of joy". Add micro-interactions and moments of delight to interfaces.

Use when the user says: "too complex", "simplify this UI", "strip it down". Simplify complex interfaces without losing function.

Use when the user says: "extract components", "consolidate patterns", "build a design system". Extract reusable components from existing UI.

Use when building frontend components or pages. Core design skill for creating distinctive, production-grade interfaces that avoid generic AI aesthetics.

Use when the user says: "production hardening", "handle edge cases in UI", "make it resilient". Improve interface resilience, error states, and edge cases.

Use when the user says: "normalize the design", "make it consistent", "align with design system". Normalize design consistency across the interface.

Use when the user says: "improve onboarding", "empty states", "first-run experience". Design or improve onboarding flows and first-run experiences.

Use when the user says: "optimize frontend performance", "improve load time", "fix rendering". Improve frontend performance and rendering efficiency.

Use when the user says: "polish this UI", "final pass", "pixel-perfect". Final quality pass for alignment, spacing, and consistency details.

Use when the user says: "too busy", "too noisy", "reduce visual clutter". Reduce visual noise and clutter in interfaces.

Use when the user says: "setup impeccable", "design context setup", "teach impeccable", "design this UI", "look and feel", "establish design tokens", "plan the look and feel", "UI planning", "design system for this project", "craft the interface". Gathers design context and concrete tokens, saves to design/context.md.

Use when the user says: "fix the typography", "improve the type", "font choices". Improve typography, font choices, hierarchy, sizing, and readability.

Use when the user says: "address PR comments", "fix review feedback", "fix failing CI", or "resolve merge conflicts". Triages and resolves PR blockers on GitHub or Azure DevOps.

Use when the user says: "brainstorm options", "generate ideas", "explore ideas", "what are our options", or wants divergent thinking before committing to an approach. Four parallel thinkers generate ideas, rank by user-chosen criteria.

Use when the user says: "challenge this", "poke holes in this", or "what's wrong with this approach". Adversarial review using parallel critics (3 generics + 0-2 domain specialists). Assumes the target is wrong, finds out why, and argues for a better approach.

Use when the user says: "commit and push". Commits and pushes changes to the current branch.

Use when the user says: "create PR" or "open pull request". Reviews branch changes and creates a PR on GitHub or Azure DevOps.

Use when the user says: "grill me on this", "poke holes in my idea", "help me think this through", "what am I not thinking about", or wants multi-angle questioning before committing to building something. Pre-pipeline exploration that sharpens thinking.

Use when the user says: "prior art", "how do others do this", "what patterns exist", "industry standards for X", or wants to survey external approaches.

Use when the user says: "research adding X", "feasibility study", "evaluate approach", or wants a focused investigation before committing. Dispatches the researcher agent for codebase investigation and presents a structured brief.

Use when the user says: "ship it" or "commit push and PR". Commits, pushes, and creates a PR in one step.

Use when the user says: "create a skill", "write a skill", "new skill", or wants to author a new SKILL.md. Guided skill creation following Claudefiles conventions.

Generate a PR summary