productivity▌

When working on the Agents workbench layout, always follow these guidelines:

You are tasked with writing a handoff document to hand off your work to another agent in a new session. You will create a handoff document that is thorough, but also concise. The goal is to compact and summarize your context without losing any of the key details of what you're working on.

Create maintainer-friendly pull requests while avoiding 16 common rejection mistakes. \n \n Prevents personal development artifacts (SESSION.md, planning docs, debug screenshots, temp test files) from being committed using a pre-PR check script \n Enforces three critical workflow rules: always use feature branches, test thoroughly before submitting, and keep PRs focused on a single change under 400 lines \n Provides templates and guides for PR descriptions using What/Why/How structure, conventio

Manage multiple local CLI agents in parallel tmux sessions with task assignment and monitoring. \n \n Start, stop, and monitor agents running in isolated tmux sessions with log tailing and health checks \n Assign tasks to specific agents and track their execution output in real time \n Schedule recurring agent work via cron integration for automated workflows \n Requires tmux and Python 3; agents are configured in a local agents/ directory \n

Master proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design to build maintainable, testable, and scalable systems.

Post, like, retweet, and manage Twitter/X accounts via CLI commands. \n \n Nine app commands covering tweet posting with media, liking, retweeting, DM sending, user following, and profile retrieval \n Supports media attachment through URLs, enabling workflows that combine image or video generation with social posting \n Requires inference.sh CLI authentication; integrates with other inference.sh skills for end-to-end content creation and distribution pipelines \n

Capture conversations and decisions into structured, linkable Notion pages for documentation and knowledge reuse. \n \n Supports six content types: decisions, how-to guides, FAQs, wiki entries, learning notes, and documentation pages, each with dedicated database templates and schemas. \n Workflow includes search and fetch of existing Notion pages to avoid duplication and establish proper linking and relations. \n Requires Notion MCP connection; includes setup steps for OAuth login and remote MC

Build SEO-optimized competitor comparison and alternative pages that rank for competitive keywords while providing genuine value. \n \n Covers four page formats: singular alternatives, plural alternatives roundups, direct product comparisons, and head-to-head competitor matchups, each with distinct search intent and structure \n Emphasizes honest positioning—acknowledge competitor strengths and your own limitations to build reader trust and improve SEO rankings \n Includes centralized competitor

Push Packer build metadata to HCP Packer registry for image lifecycle tracking and governance. \n \n Registers build artifacts in HCP Packer with minimal overhead, storing metadata only (not actual images) and adding less than one minute to build time \n Supports bucket-level labels (updated per build) and immutable build-level labels (git SHA, timestamps) for version control and compliance tracking \n Integrates with Terraform via hcp_packer_artifact data source to query and deploy images acros

Expert patterns for Neon serverless Postgres, branching, connection pooling, and ORM integration. \n \n Covers Prisma and Drizzle ORM setup with Neon, including dual connection string configuration (pooled vs. direct) for migrations and application queries \n Explains PgBouncer connection pooling limits (10K concurrent connections) and reserved superuser connections \n Provides guidance on choosing between Neon's neon-http driver (single queries) and neon-serverless driver (transactions and WebS