Skip to content

NagareNegishi/Job-Application-Tracker / .claude/skills/frontend-design

frontend-design

Verified

Improve the visual design of the job tracker React frontend. Use when asked to improve, redesign, restyle, or enhance the UI in job-tracker-ui/.

Scope

Allowed

  • Restyle one component at a time — stop after each and wait for approval
  • Improving layout, spacing, typography, color
  • Add, remove, or change Tailwind class names on existing elements
  • Refactoring components in src/components/ for visual improvements
  • Suggest new shadcn/ui primitives before adding — explain why it's needed and what alternatives exist, then wait for approval

Off-limits

  • Do not make any functional changes — visual and structural changes only
  • Do not modify backend files (JobTrackerApi/, JobTrackerApi.Tests/)
  • Do not change src/services/, src/hooks/, or src/types/
  • Do not change routing structure
  • Do not modify vite.config.ts, tsconfig.json, or build config
  • Do not add npm dependencies without explicit approval

Conventions

  • Use Tailwind utility classes for all styling — no inline styles, no CSS modules, no custom CSS files
  • Use existing shadcn/ui components from src/components/ui/ first
  • If no suitable shadcn/ui component exists, suggest an alternative (new component or third-party package) with reasoning — do not install or add dependencies yourself, wait for approval
  • Use @/ path alias for all imports

Workflow

Before starting

If the request is ambiguous, do not proceed — ask for clarification first:

  • If layout or positioning is unclear, generate 2–3 concrete options and ask which to use, with an option to describe something different
  • If the target component is not specified, ask which one

Per component loop

  1. Make changes to one component only
  2. Show a summary of what changed and why
  3. Stop and wait — do not proceed to the next component
  4. If approved, suggest a commit message but do not run any git commands — the user will handle git themselves
  5. If not approved, ask what to change before retrying
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 322kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall