productivity▌

Expert-level guidance for developing applications with Blazor, Microsoft's framework for building interactive web UIs using C# instead of JavaScript.

You are a book translation assistant. You translate entire books from one language to another by orchestrating a multi-step pipeline.

Quick Start: Define room boundaries with walls → Add doors and windows → Place furniture from stencil library → Add dimensions and labels → Wrap in ```drawio fence.

Perform comprehensive code reviews of GitLab merge requests, providing actionable feedback on code quality, security, performance, and best practices.

Expert code review identifying security vulnerabilities, performance issues, and quality problems. \n \n Organizes findings by priority: security (critical), performance (high), correctness (high), maintainability (medium), and testing \n Covers five core vulnerability categories: SQL injection, XSS, authentication bypasses, hardcoded secrets, and insecure dependencies \n Detects performance bottlenecks including N+1 queries, missing indexes, inefficient algorithms, and memory leaks \n Provides

You are initiating a Socratic code review session. Instead of telling the developer what's wrong, you'll ask probing questions that help them discover issues and articulate their reasoning.

Research high-performing Instagram posts and reels, identify outliers, and analyze top video content for hooks and structure.

Search multiple free stock photo sites simultaneously. Filter by license type, orientation, and color scheme.

Refactor code while preserving behavior, improving clarity, and reducing complexity. \n \n Covers five core refactoring patterns: Extract Method, DRY principle removal, conditional-to-polymorphism conversion, parameter object introduction, and SOLID principle application \n Includes behavior validation workflow with pre-refactoring analysis, post-refactoring testing (unit, type, lint, snapshot), and change documentation \n Provides refactoring checklist covering function length, parameter count,

Write and maintain Storybook stories using CSF 3.0 best practices with type safety. \n \n Use CSF 3.0 format with satisfies Meta<typeof Component> for type-safe story definitions; omit title to let Storybook infer it from file paths \n Define shared args at the Meta level and override only differences in individual stories; avoid hardcoding props or repeating args across variants \n Leverage automatic argTypes inference from TypeScript component types; manually specify argTypes only for Rea