bendrucker

Raycast extension development. Use when working with @raycast/api imports, Raycast commands/tools, or building extensions.

Triage and prioritize the Things Today list. Use when the user wants to review, prioritize, or reorder their Today list.

Fix type errors instead of ignoring them. Use when cleaning up type ignores across files or batch-fixing type errors.

Watch GitLab CI and investigate pipeline failures. Use when a pipeline or job is failing or red, when watching MR CI, branch builds, or a specific pipeline, when waiting for CI to go green, or when authoring or validating .gitlab-ci.yml.

Read and query Things 3 data (lists, todos, projects, tags, logbook). Not for writes. Use things:url to create, update, or capture to the inbox.

My personal plugin marketplace and settings for Claude Code

Find deepening opportunities in a codebase. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.

Configure, create, or troubleshoot Claude Code hooks (PreToolUse, PostToolUse, UserPromptSubmit), debug hook failures, or set up any automation within Claude Code. Examples include "I want to run tests before every file edit", "My hook isn't firing", "1 out of 2 hooks ran", or "How do I create a hook that formats JSON output with jq?"

Query Claude Code session history via a DuckDB index over `~/.claude/projects/`. Use when asked about Claude Code activity ("how many tokens today?", "what did I work on this week?") or instead of reading, grepping, or jq-ing session transcripts. Not for codebase search, git log queries, or arbitrary databases.

Curate the writing plugin's trope ruleset by auditing wordlist entries against session history and surfacing candidate phrases. Use when refreshing trope detection, reviewing wordlist health, or mining sessions for new AI-writing patterns to add or stale rules to remove.

Reading and managing Apple Mail via JXA. Use when working with email, archiving messages, or processing the inbox.

Research existing solutions when exploring a new problem space. Use when the user mentions "prior art", "existing solutions", "what libraries exist for", or wants to understand the landscape before building.