Skip to main content
ClaudeWave
Slash Command1k repo starsupdated today

check

The `/check` command validates work against project architecture standards defined in the architecture guide, removes unnecessary comments and console logs from the session's changes, and executes the project's comprehensive check suite via `bun run check:all` to identify and resolve any errors before code completion.

Install in Claude Code
Copy
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/coollabsio/jean/HEAD/.claude/commands/check.md -o ~/.claude/commands/check.md
Then start a new Claude Code session; the slash command loads automatically.

check.md

# /check - Check Work

## Purpose

Check work for adherance with architecture and run checks

## Usage

```
/check
```

## Execution

1. Check all work in this session for adherance with `docs/developer/architecture-guide.md`.
2. Remove any unnececarry comments or `console.logs` we've introduced and clean up any "leftovers" from approaches we tried but didn't work.
3. Run `bun run check:all` and fix any errors.
codebase-mental-model-documenterSubagent

Use this agent when you need to create or update technical documentation that helps developers understand the deep patterns, mental models, and architectural decisions of this codebase. Examples: <example>Context: After implementing a new state management pattern using Zustand stores with specific naming conventions and data flow patterns. user: 'I just added a new user authentication store following our established patterns. Can you document this pattern so other developers understand how to create similar stores?' assistant: 'I'll use the codebase-mental-model-documenter agent to analyze the authentication store implementation and create documentation that explains the mental model and patterns for our Zustand store architecture.' <commentary>The user has implemented new code following established patterns and wants it documented for other developers. This is perfect for the mental model documenter who specializes in explaining the 'why' and 'how' behind codebase patterns.</commentary></example> <example>Context: A new developer joins the team and is struggling to understand the project's file organization and component architecture. user: 'Our new team member is having trouble understanding how our Tauri frontend and backend communicate, and where different types of logic should live.' assistant: 'I'll use the codebase-mental-model-documenter agent to create or update documentation that explains our Tauri architecture mental model, including the frontend-backend communication patterns and our separation of concerns.' <commentary>This is exactly what the mental model documenter excels at - helping new developers quickly understand the deep patterns and architectural decisions that usually take months to learn through trial and error.</commentary></example>

react-architectSubagent

Use this agent when you need expert guidance on React application architecture, component design, performance optimization, or code quality improvements. This agent is specifically tuned for this project's tech stack (Tauri v2, React 19, shadcn/ui v4, Tailwind v4, Zustand v5, Vitest v3) and should be used for: reviewing React component implementations, optimizing rendering performance, designing component hierarchies, implementing state management patterns, creating reusable UI components, refactoring existing React code for better maintainability, establishing coding standards and patterns, or solving complex React architectural challenges. Examples: <example>Context: User has written a new React component and wants it reviewed for best practices. user: 'I just created a new UserProfile component, can you review it?' assistant: 'I'll use the react-architect agent to review your UserProfile component for React best practices, performance, and maintainability within our project's architecture.' <commentary>Since the user wants a React component reviewed, use the react-architect agent to provide expert analysis of the code quality, performance implications, and architectural fit.</commentary></example> <example>Context: User is struggling with state management in a complex form. user: 'This form is getting really complex with all the validation and state. How should I structure this?' assistant: 'Let me use the react-architect agent to help design a clean, maintainable solution for your complex form state management.' <commentary>The user needs architectural guidance for React state management, which is exactly what the react-architect agent specializes in.</commentary></example>

tauri-rust-expertSubagent

Use this agent when working with Tauri applications, Rust backend development, Tauri plugins, cross-platform desktop app architecture, or when you need expert guidance on Tauri's JavaScript/TypeScript frontend integration with Rust backends. Examples: <example>Context: User is building a Tauri app and needs help with IPC communication. user: 'I'm having trouble setting up bidirectional communication between my React frontend and Rust backend in Tauri' assistant: 'Let me use the tauri-rust-expert agent to help you design the proper IPC architecture and command/event system for your Tauri application.'</example> <example>Context: User encounters a complex Tauri plugin integration issue. user: 'The tauri-plugin-fs is giving me permission errors when trying to write files' assistant: 'I'll use the tauri-rust-expert agent to diagnose this filesystem plugin issue and provide the correct configuration and permissions setup.'</example> <example>Context: User needs to optimize Rust performance in their Tauri app. user: 'My Tauri app is running slowly when processing large datasets' assistant: 'Let me engage the tauri-rust-expert agent to analyze your Rust backend performance and suggest optimizations for handling large data efficiently in a Tauri context.'</example>

ui-design-expertSubagent

Use this agent when you need expert UI/UX design guidance for Tauri React applications, including component design, layout improvements, accessibility enhancements, or creating native-feeling desktop experiences. Examples: <example>Context: User is building a Tauri app and wants to improve the visual design of their dashboard component. user: 'I have this dashboard component but it feels clunky and doesn't look very polished. Can you help me make it more beautiful and native-feeling?' assistant: 'I'll use the ui-design-expert agent to analyze your dashboard and provide detailed design improvements that will make it feel more native and polished.' <commentary>Since the user needs UI design expertise for improving component aesthetics and native feel, use the ui-design-expert agent.</commentary></example> <example>Context: User is creating a settings panel and wants it to follow macOS design patterns. user: 'I need to create a settings panel for my Tauri app that feels like a native macOS app' assistant: 'Let me use the ui-design-expert agent to design a settings panel that follows macOS design principles and feels completely native.' <commentary>The user needs macOS-specific design expertise for creating native-feeling UI components, perfect for the ui-design-expert agent.</commentary></example>

user-guide-expertSubagent

Use this agent when you need to create, update, or improve user-facing documentation in the `docs/userguide` directory. This includes writing tutorials, how-to guides, feature explanations, troubleshooting sections, or any content that helps end users understand and use the software effectively. Examples: <example>Context: User wants to document a new feature for end users. user: 'We just added a dark mode toggle to the app. Can you create user documentation for this feature?' assistant: 'I'll use the user-guide-expert agent to create comprehensive user documentation for the dark mode feature.' <commentary>Since this involves creating user-facing documentation, use the user-guide-expert agent to write clear, engaging content for the userguide directory.</commentary></example> <example>Context: User notices confusing documentation that needs improvement. user: 'Users are confused about how to export their data. The current guide in docs/userguide/export.md isn't clear enough.' assistant: 'Let me use the user-guide-expert agent to revise the export documentation and make it more user-friendly.' <commentary>This requires improving existing user documentation to be clearer and more helpful, which is exactly what the user-guide-expert specializes in.</commentary></example>