viktorbezdek

End-to-end workflow for authoring a Claude Code plugin from idea to validated, evaluated artifact. Composes six phases — ideation with a 7-criteria kill gate (plugin-ideation), marketplace survey and build-vs-fork decision (plugin-research), skill/hook/MCP/subagent/command decomposition (plugin-architecture), component implementation (plugin-hooks + plugin-composition + skill-creator), structural

Validates the structural correctness of Claude Code plugins — plugin.json manifest fields, SKILL.md YAML frontmatter, reference cross-references, skill name-to-directory consistency, and plugin structure conventions. Use when checking whether a plugin is well-formed before shipping, when debugging "plugin won't load" errors, when setting up CI for a plugin repo, or when reviewing a third-party plu

Meta-workflow for creating your own Claude Code skill that actually activates when needed and delivers genuine value. Starts with skill-creator as the canonical starting point, adds elicitation frameworks when the skill is for a human/domain area (interviewing, research, therapy-adjacent), designs the examples that will illustrate the skill (example-design), aligns with repo conventions (consisten

Using the FILE SYSTEM for context — scratch pads, plan persistence, dynamic skill loading, sub-agent file workspaces, and terminal log persistence. Use when the user asks to "offload context to files", "implement scratch pads", "persist agent plans", "use filesystem for agent memory", or mentions file-based context management, tool output persistence, or just-in-time context loading. NOT for in-co

Expert FinOps guidance covering cloud, AI, SaaS, and adjacent technology spend. Includes AI cost management, GenAI capacity planning, AI-powered FinOps automation, Anthropic billing, AWS (EC2, Bedrock, Savings Plans, CUR, commitment strategy), Azure (reservations, Savings Plans, AHB, OpenAI PTUs, portfolio liquidity), GCP (Vertex AI, Compute Engine, BigQuery), Kubernetes and container FinOps (Open

Interact with and integrate Hindsight long-term AI memory in Claude Code via the `hindsight` CLI. Use for recalling past context, reflecting over a memory bank, retaining facts/decisions, managing banks/entities/mental-models, and understanding the auto-recall/auto-retain hooks this plugin installs. Trigger phrases: "what do I remember about", "recall from my memory", "reflect on my past work", "r

REDUCING context size — summarization strategies, anchored iterative summarization, tokens-per-task optimization, compaction triggers, and probe-based evaluation. Use when the user asks to "compress context", "summarize conversation history", "implement compaction", "reduce token usage", or mentions structured summarization or long-running sessions exceeding context limits. NOT for diagnosing cont

Analyze complex problems through feedback loops, system dynamics, causal relationships, and leverage points to understand WHY a system behaves the way it does. Use when the user asks to map feedback loops, trace causal chains, identify why a problem keeps recurring, find leverage points for change, analyze emergent behavior, or understand a complex system before intervening. NOT for generating cre

This skill should be used when the user asks to "start an LLM project", "design batch pipeline", "evaluate task-model fit", "structure agent project", or mentions pipeline architecture, agent-assisted development, cost estimation, or choosing between LLM and traditional approaches. NOT for evaluating agent quality or building evaluation rubrics (use agent-evaluation), NOT for multi-agent coordinat

Establish and enforce uniform naming conventions, taxonomy standards, style guides, and content reuse patterns across a project. Use when the user asks to audit for consistency, standardize naming, create a style guide, align terminology across docs, eliminate drift, or define reuse patterns across content or code. NOT for formal knowledge graphs or semantic ontologies (use ontology-design). NOT f

Docker and container development — use when the user mentions Dockerfiles, multi-stage builds, Docker Compose, container optimization, image size reduction, DDEV, containerization, or dev environment setup with containers. NOT for CI/CD pipeline YAML or pipeline configuration (use cicd-pipelines), NOT for workflow orchestration or release automation (use workflow-automation), NOT for Kubernetes or

Gate workflow for making a strategic decision under uncertainty when multiple options have merit and the stakes are high. Defines the success criteria first (outcome-orientation), maps what actually drives the outcome (systems-thinking), generates options including uncomfortable ones (creative-problem-solving), stress-tests each for blind spots and hidden assumptions (critical-intuition), assesses