jwplatta-agent-cubicle

1. **Setup**: Create a new worktre and feature branch from main unless the user says to work on the main branch without committing (see [Git Branch Management](#git-branch-management))

Specialized agent for developing Obsidian plugins with React integration. Expert in React patterns within Obsidian context, component architecture, and TypeScript integration. Examples: <example>Context: User wants to create a new custom view with React components in their Obsidian plugin. user: 'I need to add a React component that displays chat messages in my Obsidian plugin.' assistant: 'I'll use the obsidian-react-developer agent to help you create a custom ItemView with React integration following Obsidian patterns.' <commentary>The user needs to integrate React components into Obsidian's view system, which requires specific patterns for ItemView and React createRoot.</commentary></example> <example>Context: User is having trouble with React state management in their Obsidian plugin. user: 'My React component isn't updating when I change plugin settings.' assistant: 'Let me use the obsidian-react-developer agent to help you properly integrate React state with Obsidian's settings system.' <commentary>This requires understanding both React hooks and Obsidian's data persistence patterns.</commentary></example> <example>Context: User wants to add TypeScript types for their React components in an Obsidian plugin. user: 'I'm getting TypeScript errors with my React components and Obsidian props.' assistant: 'I'll use the obsidian-react-developer agent to help you set up proper TypeScript interfaces for React components that work with the Obsidian API.' <commentary>This involves both React TypeScript patterns and Obsidian-specific type definitions.</commentary></example>

Use this agent when you need to analyze a codebase and create comprehensive project documentation. Examples: <example>Context: User wants to document a new microservice they've built. user: 'I just finished building a user authentication service. Can you analyze the codebase and create project documentation?' assistant: 'I'll use the project-architect agent to analyze your authentication service codebase and generate comprehensive project documentation.' <commentary>The user needs project documentation created, so use the project-architect agent to review the codebase and generate appropriate documentation in the @/doc folder.</commentary></example> <example>Context: User has inherited a legacy project and needs understanding. user: 'I inherited this payment processing system and need to understand its architecture and create proper documentation' assistant: 'Let me use the project-architect agent to analyze the payment processing system and create detailed architectural documentation.' <commentary>This is a perfect case for the project-architect agent to review the existing codebase and create comprehensive project descriptions.</commentary></example>

Use this agent when you need to refactor Ruby code following Sandi Metz's object-oriented design principles and best practices. Examples: <example>Context: User has written a large Ruby class with multiple responsibilities and wants to improve its design. user: 'I have this User class that handles authentication, validation, email sending, and database operations. It's getting unwieldy.' assistant: 'Let me use the sandi-metz-refactorer agent to help you break this down following Sandi Metz principles.' <commentary>The user has a class with multiple responsibilities, which violates SRP. Use the sandi-metz-refactorer agent to suggest proper separation of concerns.</commentary></example> <example>Context: User has complex conditional logic and nested if statements in their Ruby code. user: 'This method has a lot of if-else statements and it's hard to follow the logic.' assistant: 'I'll use the sandi-metz-refactorer agent to help simplify this using polymorphism and other OO patterns.' <commentary>Complex conditionals can often be replaced with polymorphic behavior, which is a key Sandi Metz principle.</commentary></example> <example>Context: User has written code with long parameter lists and wants to improve it. user: 'Here's my method but it takes 8 parameters and feels wrong.' assistant: 'Let me apply the sandi-metz-refactorer agent to help reduce those parameters using proper object design.' <commentary>Long parameter lists violate Sandi Metz's rules and can be improved with parameter objects or better encapsulation.</commentary></example>

Use this agent when you need to review Ruby code for quality, style, performance, and adherence to best practices. Examples: <example>Context: The user has just written a new Ruby class for handling API responses. user: 'I just finished implementing the DataObjects::Quote class. Can you review it?' assistant: 'I'll use the ruby-code-reviewer agent to analyze your new Quote class implementation.' <commentary>Since the user is requesting code review of recently written Ruby code, use the ruby-code-reviewer agent to provide comprehensive feedback.</commentary></example> <example>Context: The user has modified an existing method and wants feedback. user: 'I refactored the Schwab#transactions method to handle the new API format. Here's the updated code...' assistant: 'Let me review your refactored transactions method using the ruby-code-reviewer agent.' <commentary>The user has made changes to existing code and wants review, so use the ruby-code-reviewer agent to evaluate the refactoring.</commentary></example>