Professional Profile Skill

Purpose

This skill provides Claude Code with Robert Abby's professional background, technical expertise, and career goals to enable context-aware coding assistance that aligns with his experience level and job search objectives.

When to Use This Skill

Claude Code should reference this skill when:

• •Creating portfolio projects or code examples
• •Writing code that showcases specific technical skills from the resume
• •Suggesting project ideas or features that would strengthen job applications
• •Making architectural decisions that reflect senior-level engineering practices
• •Implementing accessibility features (a11y) or performance optimizations
• •Working with React, TypeScript, or modern frontend tooling
• •Creating documentation or README files for projects
• •Providing code review feedback or refactoring suggestions
• •The user asks for career-related guidance or project recommendations

How to Use This Skill

When this skill is triggered, Claude Code should:

1. •

   Align with Experience Level: Suggest solutions that reflect 15 years of frontend engineering experience, including advanced patterns, performance considerations, and scalability best practices.

2. •

   Leverage Tech Stack: Prioritize technologies from Rob's core skills:

   • •React, TypeScript, Next.js, GraphQL
   • •Modern state management (TanStack Query, Zustand, Apollo Client)
   • •Testing (React Testing Library, Jest, Cypress)
   • •UI libraries (Chakra UI, Tailwind CSS, Material Design)
   • •Build tools (Vite, Webpack, Turborepo)
   • •Accessibility (WCAG 2.1 AA compliance)
3. •

   Showcase Strengths: Generate code that demonstrates:

   • •Component architecture and design system thinking
   • •Accessibility best practices
   • •Performance optimization techniques
   • •TypeScript type safety and patterns
   • •Testing strategies
   • •Modern React patterns (hooks, composition)
   • •Cross-functional collaboration mindset
4. •

   Consider Career Goals: Frame suggestions to help Rob stand out for Senior Frontend Product Engineer roles by:

   • •Writing production-quality, maintainable code
   • •Including comprehensive documentation
   • •Demonstrating leadership through code organization and patterns
   • •Showing impact through measurable improvements
   • •Emphasizing user experience and accessibility
5. •

   Professional Context: Reference Rob's notable achievements when relevant:

   • •Led UI component library development (+25 components)
   • •Improved Lighthouse scores (78→95 accessibility, 90+ performance)
   • •Reduced bundle sizes by 40% and page load times by 2.3s
   • •Mentored engineers and established coding standards
   • •Led large-scale feature development for 200k+ users

Key Professional Attributes

• •Location: Bellingham, WA (willing to relocate)
• •Experience: 15 years in frontend engineering
• •Current Role: IT Manager at VIMSIA (Mar 2025-Present)
• •Most Recent IC Role: Staff Engineer at PartySlate (Dec 2018-Feb 2025)
• •Specializations: React, TypeScript, UX, Design Systems, Accessibility, Performance
• •Leadership Style: Mentorship, collaboration, positive team culture
• •Certifications: MIT AI Products & Services, Certified Scrum Product Owner

Projects That Would Strengthen Portfolio

Based on Rob's background, suggest projects that demonstrate:

• •Complex state management in large applications
• •Design system development from scratch
• •Accessibility-first component libraries
• •Performance optimization case studies
• •GraphQL integration patterns
• •Micro-frontend architectures
• •Developer tooling and CLI utilities
• •Real-time collaborative features
• •Mobile-responsive marketplace interfaces

Code Quality Standards

All code suggestions should include:

• •TypeScript with strict type checking
• •Comprehensive JSDoc comments for complex functions
• •Accessibility attributes (ARIA labels, semantic HTML)
• •Unit tests with React Testing Library
• •Error boundaries and error handling
• •Loading and empty states
• •Responsive design considerations
• •Performance optimization (lazy loading, code splitting, memoization)

Communication Style

• •Explain architectural decisions and trade-offs
• •Provide context for why certain patterns are industry best practices
• •Suggest improvements that would impress technical hiring managers
• •Be direct about code quality and maintainability concerns

Files in This Skill

• •SKILL.md - This file (instructions for Claude Code)
• •resume.md - Full resume in markdown format
• •career-goals.md - Detailed career objectives and target roles

Example Trigger Scenarios

Scenario 1: Starting a new project

User: "I want to build a component library"
Claude Code: *References professional-profile skill*
Response: "Based on your experience building UI component libraries at PartySlate and SAVO, 
let's create a modern setup using Vite, TypeScript, React, and Storybook with visual 
regression testing—similar to the 25+ reusable modules you developed. We'll also integrate 
accessibility testing from the start..."

Scenario 2: Code review

User: "Review this component"
Claude Code: *References professional-profile skill*
Response: "Given your background in accessibility (improving Lighthouse scores from 78 to 95), 
here are some a11y improvements: Add ARIA labels, ensure keyboard navigation, use semantic 
HTML. Also, let's add TypeScript strict types and loading states to match your production-quality 
standards..."

Scenario 3: Architecture decision

User: "Should I use Redux or Zustand?"
Claude Code: *References professional-profile skill*
Response: "Based on your tech stack (you've used Mobx, Apollo Client, and TanStack Query), 
for this use case Zustand would be a great choice because it's lightweight and provides the 
flexibility you're used to. Here's how to structure it for scalability..."

Note: This skill should be loaded automatically when working in Claude Code. Rob's resume and goals are available in the accompanying markdown files.