Development

Standards for writing standalone Python scripts — UV inline deps, loguru logging, typer CLI, exit codes, and the canonical script template. References python-dependency-management for dep management.

Use this agent to manage software projects using the AIC (ATOMIC-INVEST-CONTEXT)

'Review pull requests and code changes for quality, design patterns,

You are a naming researcher. Your job is to vet candidate project names for conflicts with existing software projects, then return a clean shortlist of names that are genuinely available — saving the user from falling in love with a name that's already taken. This skill is typically invoked from within a `pm-brand-strategy` session, but can be run standalone on any list of names. ---

Establish or iterate on the brand strategy and marketing direction for a project. Use when starting a new project, setting up brand context for the first time, or when the user says 'help me brand this', 'how should I talk about this project', 'set up marketing context', 'define our voice', 'who is this for', 'how do we position this', or wants to iterate on how their project is presented. Writes .claude/product-marketing-context.md which all other brand/design skills read automatically. Supp...

Complete browser automation with Playwright. Auto-detects dev servers,

Analyze TODO.md, curate documentation, and recommend the optimal next step using Implementation Plan format

Compare multiple job offers side-by-side with total compensation analysis

Guide through creating a new Claude Code slash command with proper hierarchy and location

Analyze Claude Settings and Suggest Global Allows

Harden an agent's persona/system-prompt file (SOUL.md-style: a git-tracked identity + process-gate document) against a concrete recurring failure, instead of doing a vague "improve the persona" pass. Mines a real incident, converts judgment-based process gates into low-judgment triggers, verifies every skill/resource name the persona references against what actually exists on disk, adds a cheap inline check reachable mid-edit, and adds a reuse check targeted at the mined failure. Language- an...

Design and document a port assignment strategy for local development environments. Use when setting up new projects, resolving port conflicts, or establishing team conventions for port usage across services.

Creates a comprehensive Zettelkasten note optimized for Logseq with proper interconnections and semantic structure

Fetch the Wikipedia thumbnail image for any topic and save it as a local asset in the Logseq wiki. Returns the markdown image reference to embed in a page.

Idiomatic review for Node.js glue code that bridges Rust wasm-bindgen modules to playwright-core (e.g. crates/wasm/src/glue/*.js in stapler-mcp). Use when reviewing or writing JS/TS files that call playwright-core APIs from a wasm-bindgen import object, wrap Playwright errors for the wasm boundary, manage browser/page lifecycle, or write node:test tests around that glue.

Analyze job postings, calculate match scores, identify gaps, and create application strategy

Discover Java API signatures from compiled JARs using javap instead of

Install, manage, and troubleshoot macOS packages using Homebrew. Use

Use gritql (grit) for AST-based multi-file code transformations. Use

Provides a guide for setting up Golang project layouts and workspaces. Use when starting a new Go project, organizing an existing codebase, setting up a monorepo with multiple packages, creating CLI tools with multiple main packages, deciding between cmd/internal/pkg directory conventions, or discussing package restructuring, package splits, or module splits.

Golang library and framework selection — vetted production-ready options by category (web, database, testing, logging, messaging), new and experimental stdlib packages, standard-library-first tradeoffs, and maturity signals (maintenance, license, importer counts). Apply when the user asks for library suggestions, wants to compare alternatives, needs to choose a library for a specific task, or when a new dependency is being added to the project. Not for a specific library's API once chosen (→ ...

Go (Golang) naming conventions — covers packages, constructors, structs, interfaces, constants, enums, errors, booleans, receivers, getters/setters, functional options, acronyms, test functions, and subtest names. Use this skill when writing new Go code, reviewing or refactoring, choosing between naming alternatives (New vs NewTypeName, isConnected vs connected, ErrNotFound vs NotFoundError, StatusReady vs StatusUnknown at iota 0), debating Go package names (utils/helpers anti-patterns), or a...

Choose and apply the right Go concurrency primitive — channels, mutexes, atomics, copy-on-write, singleflight, and lock-free data structures. Use when designing concurrent access to shared state, diagnosing lock contention (paired with golang-profiling), choosing between sync.RWMutex and atomic.Pointer copy-on-write, evaluating concurrent map options (sync.Map vs xsync.MapOf), implementing singleflight request coalescing, or reaching for a lock-free queue/ring-buffer library. Covers stdlib sy...

Autonomously iterate on a PR — local CI, code review, remote CI, review comments, merge conflicts — until ready to merge