timseriakov

Создаёт и улучшает agent skills с правильной структурой, progressive disclosure, bundled resources и безопасными boundaries. Use when user wants to create, write, build, review, or evolve a skill.

Launch one or more tasks in new git worktrees using workmux.

Analyze a user's Plannotator plan archive to extract denial patterns, feedback taxonomy, evolution over time, and actionable prompt improvements — then produce a polished HTML dashboard report. Falls back to Claude Code ExitPlanMode denial reasons when Plannotator data is unavailable.

Fetch source code for npm, PyPI, or crates.io packages and GitHub/GitLab repos to provide AI agents with implementation context beyond types and docs. Use when needing to understand how a library works internally, debug dependency issues, or explore package implementations.

Write a PR description using conversation context and open PR creation in browser.

Save 60-90% of LLM tokens on shell commands, file reads, and test outputs. Wraps rtk CLI for compressed output.

Reference for the workmux CLI that manages git worktrees and tmux windows as isolated development environments. Use when the user mentions workmux, worktrees, or parallel agent workflows.

Semantic version control workflow: sem (structural truth) -> inspect (review prioritization) -> weave (coordination + merge semantics).

Build and maintain software architecture as code with LikeC4 DSL. Use when tasks mention architecture diagrams, C4/context/container/component views, system landscape, dependency/integration maps, or when the user wants architecture generated/evolved from code. Apply for creating new `.c4`/`.likec4` models, updating existing models, validating with LikeC4 CLI, and preparing preview/build/export outputs.

Design, review, and refactor React Server Component architecture in Next.js App Router apps. Use when a task mentions RSCs, Server Components, Client Components, Suspense loading boundaries, skeletons, async page components, route/page composition, params/searchParams promises, cacheComponents, Server Functions/actions, useOptimistic, or feature-folder organization. Also use when the user wants a route split into a synchronous shell plus async regions, or wants existing client data tooling preserved instead of replaced.