claude-code-telegrammer

Master index of all available skills for development workflows. Use when needing guidance on which skill to apply or when starting work on any project.

Master index of all available skills for development workflows. Use when needing guidance on which skill to apply or when starting work on any project.

Autonomous work mode — never ask user to run commands, never stand by, always take next action. Use when working independently on tasks.

Claude Code setup and configuration reference. Skills, commands, hooks, MCP servers, CLI, and permissions.

Code audit, cleanup, refactoring, API minimization, test review, examples, and project evaluation. Use when reviewing code quality or preparing for release.

Core development philosophy including development cycles, naming conventions, architectural decisions, and multi-agent workflows. Use when establishing project foundations or making architectural decisions.

Inspect DOM elements via playwright-cli eval for autonomous CSS/layout debugging.

Emacs Lisp development best practices including file templates, project structure, testing, and coding style. Use when writing Emacs Lisp packages or configuration.

Git workflow, GitHub operations, worktrees, conflict resolution, PyPI publishing, and version management. Use when working with git, GitHub, or releasing packages.

Project organization, multi-agent coordination, bug reporting, feature requests, and documentation practices. Use when managing projects, coordinating work, or organizing development workflows.

Master orchestrator agent — delegate work to project agents via Emacs vterm/screen, stay responsive for user conversation. Use when running as the master agent at ~/proj/master-agent.

Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.

Use this skill when writing, reviewing, or refactoring any code. Provides a checklist of essential programming principles (DRY, KISS, SOLID, YAGNI, etc.) to verify before finalizing any implementation. Triggers: "check my code", "review this", "refactor", "write a module", "create a class", "implement a function", "does this follow best practices".

Project management — bug reports, feature requests, bulletin board, planning, progress tracking, timelines, and reporting. Use when managing project tasks or communicating status.

Create pull requests for external and internal projects. Handles fork setup, branch conventions, commit style matching, and hook management. Use when contributing to any repository via PR.

Python development for scientific computing and SciTeX projects. Includes testing, debugging, ML practices, and environment management.

Quality enforcement rules — no fallbacks, no false positives, no patch work, script everything. Use when reviewing code, verifying fixes, or ensuring code quality.

SciTeX ecosystem general standards — branding, package architecture, four interfaces, version management, and repository quality. Use when creating, auditing, or maintaining any SciTeX package.

Multi-backend notification system with fallback priority — audio TTS, desktop, emacs, matplotlib, playwright, email, webhook, Telegram, and Twilio phone/SMS. Use when alerting users, escalating to phone calls, or sending notifications from scripts and AI agents.

Agent Communication Hub — real-time WebSocket messaging between AI agents across machines with channel routing, @mentions, presence, and persistence.

SciTeX ecosystem skills — general standards, package-specific guides, and workflow references. Use when working on any SciTeX package.

Workaround for Claude Code auto-compact bug. Self-compact via Emacs MCP server.

Shell scripting best practices for bash and other shells. Use when writing shell scripts, bash functions, CLI help text, or command-line automation. Includes env var defaults in help, safe file operations, SLURM templates, and custom tools.

Audio feedback (TTS), voice transcription (STT), speak signatures, and phone call escalation.

Enforce agent isolation with code guards, not documentation. Prevent cross-contamination between agent contexts.

SciTeX ecosystem skills — general standards, package-specific guides, and workflow references. Use when working on any SciTeX package.

TUI watchdog for Claude Code — screen polling, auto-response, lock management. Bottom layer of the SciTeX agent stack.