viktorbezdek

@viktorbezdek source repo

116 skills
0 followers
4 hours ago last updated

▌
PDF · viktorbezdek bundle
Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms.

0
installs
▌
DOCX · viktorbezdek bundle
Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction.

0
installs
▌
XLSX · viktorbezdek bundle
Comprehensive spreadsheet creation, editing, and analysis with support for formulas, formatting, data analysis, and visualization.

0
installs
▌
Osint · viktorbezdek bundle
Conduct deep OSINT research on individuals — from name or handle to a scored dossier with psychoprofile (MBTI/Big Five), career map, and confidence-graded facts. Phased pipeline (0→6): tooling check, seed collection, internal intelligence, platform extraction, cross-reference, psychoprofile, completeness evaluation, dossier output. Swarm mode: 3-5 parallel Sonnet sub-agents. 55+ Apify actors. 7 search APIs. Trigger phrases: "osint", "research person", "find everything about", "due diligence", "background check", "digital footprint", "build dossier", "profile someone", "пробей", "досье", "разведка", "найди всё про", "профиль человека", "кто это". NOT for: company/product research without a named person, competitive analysis, market research, content generation, or general web scraping without an individual target.

0
installs
▌
Gws CLI · viktorbezdek bundle
Google Workspace CLI (gws) for managing all 18 Workspace APIs from the terminal. Use when running gws commands, listing Drive files, sending Gmail, reading Sheets, creating Calendar events, managing Tasks, querying Chat, pushing Apps Script, building cross-service automations, or when user mentions gws or Google Workspace CLI. NOT for building MCP servers (use mcp-server), NOT for general API design (use api-design), NOT for GCP infrastructure (use cicd-pipelines).

0
installs
▌
Deslop UI · viktorbezdek bundle
Audit and rewrite UI copy to remove AI slop — overlong button labels, hedging error messages, corporate filler, and passive voice in interface text. Use when asked to clean up UI text, deslop interface copy, fix AI-sounding buttons or error messages, audit microcopy for AI patterns, or humanize product UI. Trigger phrases: "deslop", "anti-slop", "remove AI slop from UI", "clean up button labels", "fix error messages", "humanize interface text", "UI copy review". NOT for writing new UI copy from scratch (use ux-writing). NOT for marketing or editorial prose (use deslop-copy). NOT for code quality cleanup (use ai-slop-cleaner).

0
installs
▌
Deslop Copy · viktorbezdek bundle
Remove AI slop from marketing copy, blog posts, product descriptions, emails, and editorial content — and humanize the result. Use when asked to deslop, humanize, or anti-slop marketing copy, landing pages, product descriptions, email campaigns, blog posts, or any AI-generated prose. Trigger phrases: "deslop", "anti-slop", "remove AI slop", "humanize this copy", "this sounds AI-generated", "make this sound human", "clean up marketing copy", "remove AI clichés". NOT for UI microcopy or interface text (use deslop-ui). NOT for code cleanup (use ai-slop-cleaner). NOT for creating brand-new copy from scratch (use storytelling or prompt-engineering). NOT for preventing AI detector flags specifically (use deslop-detect).

0
installs
▌
Debugging · viktorbezdek bundle
Finds and fixes bugs through systematic root cause analysis, stack trace interpretation, browser DevTools automation, CI/CD pipeline debugging, performance profiling, test pollution detection, and AI-powered error analysis. Use when the user asks to debug, fix a bug, investigate an error, analyze a stack trace, find root cause of a failure, profile performance, diagnose test failures (unit/integration/E2E), troubleshoot CI/CD pipelines, debug flaky tests, use Chrome DevTools, or trace data flow to source. NOT for writing new tests or setting up test frameworks (use testing-framework), NOT for TDD methodology or writing tests before code (use test-driven-development), NOT for reviewing code quality or PRs (use code-review), NOT for designing CI/CD pipelines (use cicd-pipelines), NOT for feature development or refactoring (use language-specific plugins).

0
installs
▌
Deslop Detect · viktorbezdek bundle
Rewrite AI-generated content to evade AI content detectors by increasing perplexity, burstiness, and lexical entropy. Use when asked to make content pass GPTZero, Originality.ai, Turnitin AI detection, Copyleaks, or any AI content detector; when asked to make writing "undetectable"; or when existing deslop passes fail detection checks. Trigger phrases: "pass AI detector", "evade AI detection", "make this undetectable", "GPTZero", "Originality.ai", "Turnitin", "AI detection score", "reduce AI score", "beat the detector", "bypass AI checker". NOT for general copy quality improvement (use deslop-copy). NOT for UI copy cleanup (use deslop-ui). NOT for code (use ai-slop-cleaner). NOT for academic fraud — this skill is for legitimate content creators reclaiming work that was partially AI-assisted.

0
installs
▌
API Design · viktorbezdek bundle
Design production-grade REST, GraphQL, gRPC, and Python library APIs with correct schemas, error contracts, auth, and versioning. Use when the user asks to design an API, define endpoints, create an OpenAPI/Swagger spec, design a GraphQL schema, build a gRPC service, model request/response with Pydantic, add pagination, or review API contracts. NOT for building MCP server tools (use mcp-server). NOT for Node.js/Express API routes or backend patterns (use backend-patterns or typescript-development).

0
installs
▌
MCP Server · viktorbezdek bundle
MCP (Model Context Protocol) server development — use when the user mentions MCP, Model Context Protocol, FastMCP, MCP server, MCP tool, Claude Code plugin, or building agent tools with MCP. Covers server implementation in Python or TypeScript, evaluation testing, production deployment, and plugin packaging. NOT for designing tool interfaces or tool consolidation patterns for agents (use tool-design), NOT for prompt engineering or prompt optimization (use prompt-engineering).

0
installs
▌
UX Writing · viktorbezdek bundle
Write effective microcopy, error messages, button labels, and interface text using UX writing principles. Use when crafting microcopy, UX copy, interface text, error messages, button labels, empty states, or conversational UI text. NOT for generating documentation (use documentation-generator). NOT for writing marketing copy or brand voice guidelines (use storytelling for narrative, not UI microcopy). NOT for designing the UI itself (use frontend-design or navigation-design). NOT for content strategy or information architecture (use content-modelling).

0
installs
▌
Code Review · viktorbezdek bundle
Reviews existing code and pull requests using multi-agent swarm analysis covering security, performance, style, test coverage, and documentation quality. Extracts and prioritizes PR comments, performs security audits, and generates actionable fix plans with file:line references. Use when the user asks to review code, review a PR, audit code for security, assess code quality, analyze pull request comments, get feedback on existing code, or perform a code audit. NOT for writing new code or implementing features (use other development skills), NOT for finding and fixing runtime bugs or errors (use debugging), NOT for writing tests or setting up test infrastructure (use testing-framework), NOT for TDD methodology (use test-driven-development).

0
installs
▌
Elicitation · viktorbezdek bundle
Psychological elicitation and deep-interview design using narrative identity (McAdams), self-defining memories (Singer), Motivational Interviewing (Miller & Rollnick OARS), values elicitation (Schwartz), schema detection (Young), and life review (Haight/Birren). Use when designing user interviews that need to reveal motivations rather than stated preferences, writing conversation flows for personal discovery, auditing interview scripts for interrogation anti-patterns, building conversational AI that understands users over time, drafting life story or personal history products, or critiquing a conversation transcript for missed depth. NOT for clinical diagnosis, therapy, or treatment planning. NOT for structured data capture or survey design (use standard survey tools). NOT for persona creation from scratch (use persona-definition). NOT for stakeholder mapping (use persona-mapping).

0
installs
▌
Plugin Hooks · viktorbezdek bundle
Authoritative guide to Claude Code hooks — event-driven scripts that execute before or after tool calls, session events, file changes, and more. Use when writing a PreToolUse hook to block dangerous commands, a PostToolUse hook to auto-format after edits, a SessionStart hook to inject context, a Stop hook for session loops, a Notification hook for desktop alerts, a FileChanged hook for reactive environments, a WorktreeCreate hook for custom worktree provisioning, or current documented hook events. Covers handler types (command, http, mcp_tool, prompt, agent), matcher syntax (exact/OR-list/regex), exit code semantics, and JSON output schema. NOT for designing hook script content for a specific domain (use the domain skill) — this skill covers hook mechanics and authoring only.

0
installs
▌
Tool Design · viktorbezdek bundle
This skill should be used when the user asks to "design agent tools", "create tool descriptions", "reduce tool complexity", "implement MCP tools", or mentions tool consolidation, architectural reduction, tool naming conventions, or agent-tool interfaces. NOT for building MCP servers or MCP protocol implementation (use mcp-server), NOT for multi-agent coordination or agent handoffs (use multi-agent-patterns), NOT for agent memory or persistence (use memory-systems).

0
installs
▌
Cloud Finops · viktorbezdek bundle
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 (OpenCost, Kubecost), serverless FinOps (Lambda, Functions, Cloud Run), data platforms (Kafka/MSK, Elasticsearch/OpenSearch, Redis/Valkey), multi-cloud normalization (FOCUS specification), tagging governance, SaaS management (SAM, licence optimisation, SMPs, shadow IT), AI coding tools (Cursor, Claude Code, Copilot, Windsurf, Codex), ITAM, Databricks, Snowflake, OCI, and GreenOps. Use for any query about technology cost, commitment portfolio management, rightsizing, cost allocation, SaaS sprawl, AI dev tool spend, container cost attribution, serverless optimization, multi-cloud strategy, or connecting spend to business va

0
installs
▌
Git Workflow · viktorbezdek bundle
Git workflow management — use when the user mentions git, conventional commits, commit quality, branch management, worktree operations, GitFlow, changelog generation, semantic versioning, release notes, backlog management, or issue tracking integration. NOT for CI/CD pipelines or pipeline YAML (use cicd-pipelines), NOT for non-git workflow orchestration (use skillstack-workflows or multi-agent-patterns), NOT for code review content or PR quality assessment (use code-review).

0
installs
▌
Storytelling · viktorbezdek bundle
Expert guidance for writing, editing, and teaching stories across fiction, business, data, speech, UX, and interactive narrative. Covers canonical story structures (3-act, Hero's Journey, Story Circle, Save the Cat, Kishōtenketsu, Freytag, Fichtean), business narrative frameworks (StoryBrand, Pixar Spine, Before-After-Bridge), data storytelling (Knaflic, situation-complication-resolution), speech writing (Duarte SparkLines, TED, Monroe's Motivated Sequence), narrative craft (character, scene, dialogue, POV), interactive narrative, and anti-pattern diagnostics. Use when writing or editing stories, designing pitches or presentations, structuring case studies, drafting speeches, planning interactive narratives, critiquing narrative work, or teaching storytelling. NOT for technical documentation (use documentation-generator). NOT for UX microcopy like button labels and error messages (use ux-writing). NOT for persona creation (use persona-definition).

0
installs
▌
Hindsight Memory · viktorbezdek bundle
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", "retain this", "save to my memory bank", "hindsight memory", "check my long-term memory", "is memory working". NOT for short-term session context (Claude already has the transcript), NOT for code/structural search (use CodeGraph/Semble/grep), NOT for building a memory framework from scratch (use the memory-systems skill).

0
installs
▌
Plugin Ideation · viktorbezdek bundle
Turns a vague "I want to build a Claude plugin" into a concrete, problem-first plugin idea — or tells you to not build it. Use when you want to build a Claude plugin, have an idea for a plugin and don't know if it's worth pursuing, are asking "should I build this as a plugin or is there already one", are exploring plugin ideas for your team, or are mining your workflow for repeatable pain points that could become plugins. Covers pain-point mining (what workflow pains become plugins), the problem-worthy checklist (seven criteria a plugin idea must pass), the "build for a problem, not for yourself" discipline, and ideation anti-patterns (scope creep, engineering-exercise plugins, one-off tasks, already-solved). NOT for validating an idea against existing plugins — use plugin-research for marketplace surveys.

0
installs
▌
Plugin Research · viktorbezdek bundle
Validates a plugin idea by surveying the marketplace, reading authoritative Anthropic sources, and deciding build-vs-fork-vs-skip before writing any code. Use when you want to research existing Claude Code plugins, check whether there is already a plugin for X, decide whether to build a new plugin or fork an existing one, run a marketplace survey before starting work, find authoritative documentation on a Claude Code feature, or gather primary sources for a plugin design. Covers the marketplace survey methodology, the canonical list of authoritative Anthropic URLs (code.claude.com, docs.claude.com, platform.claude.com, github.com/anthropics/claude-code, github.com/anthropics/skills, the Complete Guide PDF), community pattern discovery, and the build-vs-fork-vs-skip decision gate. NOT for deciding whether an idea is worth pursuing (use plugin-ideation) or for designing component layout (use plugin-architecture).

0
installs
▌
Hosted Agents · viktorbezdek bundle
Build and deploy hosted background coding agents with sandboxed VM execution, multiplayer sessions, and multi-client interfaces. Use when the user asks to "build background agent", "create hosted coding agent", "set up sandboxed execution", "implement multiplayer agent", or mentions background agents, sandboxed VMs, agent infrastructure, Modal sandboxes, self-spawning agents, or remote coding environments. NOT for agent coordination patterns or multi-agent design (use multi-agent-patterns), NOT for agent memory or persistence (use memory-systems), NOT for tool design or tool interfaces (use tool-design).

0
installs
▌
Skill Foundry · viktorbezdek bundle
Author high-quality Claude Code SKILL.md files using philosophy-first design, evidence-based prompting, progressive disclosure, and anti-pattern prevention. Use when the user asks to write a skill file, create a new Claude Code skill, design a SKILL.md, review whether a skill's description will trigger correctly, or convert a workflow into a reusable skill. NOT for optimizing standalone prompts or system prompts (use prompt-engineering). NOT for full plugin development with hooks and MCP (use plugin-architecture). NOT for generating code documentation (use documentation-generator).

0
installs
▌
Plugin Documenter · viktorbezdek bundle
Generates comprehensive documentation for any Claude Code plugin by fetching and analyzing all source files. Use when you need to document a Claude plugin, write a plugin README, explain how a plugin works, generate plugin usage guides, create plugin tutorials, analyze a plugin architecture for documentation, or produce installation and setup instructions. Takes a GitHub URL or local path, fetches all plugin files, maps the component architecture, identifies real use-case scenarios from skill descriptions and reference content, and produces a complete documentation package with problem statement, architecture overview, component-by-component guide, realistic usage scenarios, installation instructions, and cross-reference map. NOT for building plugins (use plugin-architecture), NOT for validating plugin structure (use plugin-validation), NOT for evaluating plugin activation (use plugin-evaluation).

0
installs
▌
Plugin Evaluation · viktorbezdek bundle
Measures whether a Claude Code plugin actually works by running triggering evals (does the model pick the skill?) and output evals (does it produce correct results?). Use when you need to evaluate a plugin, run skill activation testing, set up an eval harness, measure plugin quality, write trigger rate tests, check output quality, compare plugin iterations, or iterate on a SKILL description based on eval results. Covers the two eval file formats (trigger-evals.json and evals.json), the grader/analyzer/comparator pattern from Anthropic's skill-creator, quality criteria for eval queries (realistic, varied, near-miss negatives), and the iteration methodology for fixing a skill that fails activation. NOT for writing the plugin's code itself — use plugin-architecture, plugin-hooks, or plugin-validation.

0
installs
▌
Plugin Validation · viktorbezdek bundle
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 plugin for issues. NOT for functional evaluation (whether skills activate or produce correct output — use plugin-evaluation for that). NOT for single-skill SKILL.md quality review (use skill-foundry for that).

0
installs
▌
Cicd Pipelines · viktorbezdek bundle
CI/CD pipeline design and DevOps automation — use when the user mentions GitHub Actions, GitLab CI, Jenkins, Terraform, infrastructure as code, DevSecOps, ArgoCD, Kubernetes deployment automation, or pipeline configuration YAML. NOT for release orchestration or semantic-release workflows (use git-workflow), NOT for Docker containers or Dockerfiles (use docker-containerization), NOT for git branching or commits (use git-workflow).

0
installs
▌
Clarity Editing · viktorbezdek bundle
Edit written text for clarity and conciseness — active voice, hedge and weasel-word removal, jargon strip, sentence compression, nominalization fixes, and readability. Use when the user asks to tighten, shorten, edit, or clarify a paragraph or doc, remove hedges and weasel words, convert to active voice, cut jargon, kill passive voice, fix nominalizations, or improve readability. NOT for structuring the overall doc (use structured-writing). NOT for UI microcopy (use ux-writing). NOT for auto-generating docs from code (use documentation-generator). NOT for design-system content/tone (use consistency-standards).

0
installs
▌
Example Design · viktorbezdek bundle
Design pedagogically effective code examples, tutorials, and runnable samples using progressive complexity and deliberate scaffolding. Use when the user asks to write a code example that teaches a concept, design a quickstart tutorial, create sample code for a library or API, build a runnable demo, or structure examples from simple to advanced. NOT for generating full repo documentation or READMEs (use documentation-generator). NOT for writing examples inside a skill file (use skill-foundry). NOT for API endpoint design (use api-design).

0
installs
▌
Memory Systems · viktorbezdek bundle
Guides implementation of agent memory systems, compares production frameworks (Mem0, Zep/Graphiti, Letta, LangMem, Cognee), and designs persistence architectures for cross-session knowledge retention. Use when the user asks to "implement agent memory", "persist state across sessions", "build knowledge graph for agents", "track entities over time", "add long-term memory", "choose a memory framework", or mentions temporal knowledge graphs, vector stores, entity memory, adaptive memory, dynamic memory, or memory benchmarks (LoCoMo, LongMemEval). NOT for multi-agent coordination or agent handoffs (use multi-agent-patterns), NOT for tool design or tool interfaces (use tool-design), NOT for hosted agent infrastructure or sandboxed VMs (use hosted-agents).

0
installs
▌
Plugin Composition · viktorbezdek bundle
Integrates multiple components inside a single Claude Code plugin — skills, hooks, MCPs, subagents, and commands — using the canonical directory layout and path substitution variables. Use when building a multi-component plugin, combining skills and hooks, laying out the plugin directory structure, working with CLAUDE_PLUGIN_ROOT or CLAUDE_PLUGIN_DATA, choosing where to put shared scripts inside a plugin, or debugging why a path reference is not resolving at runtime. Covers the canonical directory tree, path substitution variables (CLAUDE_PLUGIN_ROOT vs CLAUDE_PLUGIN_DATA vs CLAUDE_PROJECT_DIR vs CLAUDE_ENV_FILE), the bin/ shared-scripts pattern, namespacing rules, hook merge semantics, and MCP auto-start lifecycle. NOT for choosing WHICH component type to use (that's plugin-architecture) or writing an individual component's content.

0
installs
▌
Prioritization · viktorbezdek bundle
Apply RICE, MoSCoW, ICE, and effort-impact frameworks to rank options and decide what to work on next. Use when the user asks to prioritize a backlog, rank features, decide what to build first, apply RICE or MoSCoW scoring, cut scope, or compare items by effort vs impact. NOT for defining success metrics or OKRs (use outcome-orientation). NOT for making a strategic bet under uncertainty (use strategic-decision workflow).

0
installs
▌
Plugin Architecture · viktorbezdek bundle
Decides which Claude Code extension type to use for a given capability — skill, hook, MCP server, subagent, or slash command — and designs the plugin.json manifest around that decision. Use when designing a plugin, planning plugin structure, choosing between skill vs hook vs mcp, setting up plugin composition, laying out plugin components, or refactoring an existing plugin whose decomposition feels wrong. Covers the five extension types, the decision matrix (when each fits), plugin.json schema reference, directory layout, namespacing conventions, and worked examples from real plugins. NOT for the content of a single component — use skill-foundry, plugin-hooks, mcp-server, or plugin-composition for deep dives.

0
installs
▌
Swarm Protocol · viktorbezdek bundle
Orchestration logic for running a parallel persona-swarm brainstorm — when to invoke, which subset of the 12 canonical personas to spawn (PM, Engineer, Designer, Skeptic, User Advocate, Pre-Mortem Specialist, Junior, Veteran, First-Principles Thinker, Constraint-Setter, Optimist, Operator), how to spawn them in parallel via the Task() tool with persona-specific subagent types, how to handle their outputs, and when to do a second round. Use when the user asks to brainstorm with multiple perspectives, run a persona swarm, get a virtual roundtable, workshop an idea from PM/engineer/designer/skeptic angles, pre-mortem a decision, or invoke the brainstorm-swarm. NOT for code review (use code-review). NOT for single-perspective interviews (use elicitation or deep-interview). NOT for executing or building things (use team or autopilot). NOT for designing custom personas — that's the custom-personas skill. NOT for the synthesis output formatting — that's the swarm-synthesis skill.

0
installs
▌
Database Design · viktorbezdek bundle
Database design and schema engineering for relational databases. Use for SQL schema design, ORM model authoring, migration strategies (Alembic, Liquibase, Flyway, Drizzle), query optimisation, indexing decisions, normalisation vs denormalisation trade-offs, and data-integrity constraints. Trigger phrases: "design this schema", "write a migration", "optimise this query", "model these entities", "add an index". NOT for NoSQL/document stores — use a dedicated NoSQL skill for those. NOT for ETL pipelines or data warehousing at scale — those involve different trade-offs. NOT for ORM configuration (framework setup) — this skill is about DATA SHAPE, not connection pooling or ORM bootstrap.

0
installs
▌
Email Marketing · viktorbezdek bundle
Email content writing for newsletters, drip sequences, onboarding flows, and transactional emails. Use for newsletter drafting, automated drip sequence copy, welcome email series, subject line and preview text optimisation, re-engagement emails, and plain-language transactional email (receipts, confirmations, alerts). Trigger phrases: "write a newsletter", "draft an onboarding email sequence", "write a subject line", "write a drip campaign", "create a welcome email". NOT for email infrastructure setup (ESP config, sending domains, DKIM/DMARC) — that is a technical ops concern. NOT for social media content — use the social-media-content skill for LinkedIn or Twitter. NOT for cold outreach / sales prospecting emails — those have compliance and conversion constraints beyond marketing content.

0
installs
▌
Frontend Design · viktorbezdek bundle
Visual design systems, UI/UX styling, Tailwind CSS, CSS variables, component libraries (shadcn/ui, Radix UI), design tokens, accessibility (WCAG), responsive layout, dark mode, and Figma-to-code workflows. NOT for React component logic, hooks, or state management (use react-development). NOT for Next.js routing, SSR, or server components (use nextjs-development).

0
installs
▌
Ontology Design · viktorbezdek bundle
Design formal knowledge models — classes, properties, relationships, hierarchies, and semantic graphs — for knowledge representation and reasoning. Use when the user asks to build an ontology, design a knowledge graph, model entity relationships formally, define class hierarchies, create a taxonomy for semantic reasoning, or structure data for RDF/OWL. NOT for CMS content types, editorial workflows, or publishing structures (use content-modelling). NOT for naming conventions or terminology standards across docs (use consistency-standards).

0
installs
▌
Persona Mapping · viktorbezdek bundle
Map stakeholders across organizations using Power-Interest matrices, RACI charts, influence analysis, and salience models to understand who has authority, who is affected, and how to engage each group. Use when the user asks to map stakeholders, create a RACI matrix, analyze organizational influence, identify decision-makers, prioritize who to involve, or plan stakeholder communication. NOT for individual user personas or empathy maps for product design (use persona-definition). NOT for designing the product's target audience (use persona-definition).

0
installs
▌
Risk Management · viktorbezdek bundle
Systematically assess and mitigate risks using risk registers, probability-impact matrices, mitigation strategies, and contingency plans. Use when the user asks to assess risks, build a risk register, plan for failure modes, evaluate downside scenarios, prepare contingency plans, or quantify uncertainty before a decision or launch. NOT for finding conceptual flaws or blind spots in ideas (use critical-intuition). NOT for security vulnerability auditing in code (use code-review). NOT for identifying boundary conditions in code (use edge-case-coverage).

0
installs
▌
Custom Personas · viktorbezdek bundle
Design ad-hoc personas for niche domains when the canonical 12 brainstorm- swarm personas don't fit. Covers: when a custom persona is justified (vs forcing canonical to fit), the persona-design template (voice, contribution shape, output format), anti-patterns (too-narrow personas, redundant personas, sock-puppet personas), and how to invoke a custom persona inline via Task() with a tailored prompt rather than a saved subagent definition. Use when running a brainstorm-swarm and the topic calls for a CFO, Security Engineer, Lawyer, Marketing, Customer Success, or other domain- specific perspective not in the canonical 12. NOT for the canonical personas (use swarm-protocol). NOT for the orchestration mechanics (use swarm-protocol). NOT for the synthesis output (use swarm-synthesis). NOT for product personas as artifacts (use persona-definition).

0
installs
▌
Swarm Synthesis · viktorbezdek bundle
Combine a parallel persona-swarm's outputs into an actionable artifact — consensus matrix (what every persona agreed on), dissent log (where personas disagreed and why), open questions (what nobody could answer), recommended next move (synthesized decision). Preserves dissent rather than forcing consensus. Use when running a brainstorm-swarm and the swarm-protocol skill has collected the persona outputs — this skill produces the synthesis artifact. NOT for orchestrating the spawn (use swarm-protocol). NOT for designing the interview arc (use interview-facilitation). NOT for designing custom personas (use custom-personas). NOT for short-form structured writing like BLUF or Pyramid (use communication/structured-writing).

0
installs
▌
Structured Writing · viktorbezdek bundle
Structure a written piece using BLUF (Bottom Line Up Front), the Minto Pyramid Principle, inverted pyramid, or SPQR (Situation-Problem-Question- Resolution). Use when the user asks to write BLUF-style, apply the Pyramid Principle, structure a memo/email/doc, lead with the conclusion, outline a long message so it is skim-readable, or reorganize buried-lede writing. NOT for line-level clarity and concision editing (use clarity-editing). NOT for UI microcopy (use ux-writing). NOT for narrative or story arcs (use storytelling). NOT for slide decks (use frontend-slides).

0
installs
▌
Agent Evaluation · viktorbezdek bundle
This skill should be used when the user asks to "evaluate agent performance", "build test framework", "measure agent quality", "create evaluation rubrics", "implement LLM-as-judge", "compare model outputs", "mitigate evaluation bias", or mentions multi-dimensional evaluation, agent testing, quality gates, direct scoring, pairwise comparison, position bias, evaluation pipelines, or automated quality assessment for LLM agent systems. NOT for testing code or applications (use testing-framework), NOT for agent coordination or multi-agent design (use multi-agent-patterns).

0
installs
▌
Pitch Sprint · viktorbezdek bundle
Parallel-merge workflow for producing a pitch (investor deck, board proposal, internal funding request, customer sales narrative) in roughly a week. Runs three parallel streams (deep interviews via elicitation, market dynamics via systems-thinking, audience sharpening via persona-definition), merges them into a single storytelling spine, audits via critical-intuition, and polishes every line with ux-writing. Use when you have one week to produce a pitch that must actually land with a specific, named audience and every claim must be grounded in something real. NOT for internal status updates, factual reports, or quick sales emails — use plain writing for those.

0
installs
▌
Systems Thinking · viktorbezdek bundle
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 creative solutions (use creative-problem-solving). NOT for stress-testing specific assumptions (use critical-intuition). NOT for structured risk registers or mitigation plans (use risk-management).

0
installs
▌
Visual Communication · viktorbezdek bundle
Communicate systems and flows visually using Mermaid (flowchart, sequence, state, ER, class), the C4 model, and diagram-as-code. Use when the user asks to draw a flow, sequence diagram, state machine, ER diagram, C4 model, architecture diagram, or wants Mermaid code for a system, wants to pick a diagram type, or wants to visualize a process as a flowchart. NOT for UI/UX mockups or visual design (use frontend-design). NOT for slide graphics or presentations (use frontend-slides). NOT for wireframes or design systems (use frontend-design).

0
installs
▌
Legacy Rescue · viktorbezdek bundle
Loop workflow for making real progress on a legacy codebase without breaking production. Starts by generating a codemap so you actually understand what exists (documentation-generator), identifies feedback-center modules (systems-thinking), gets a second perspective on areas you'll touch (code-review), builds a test safety net before any changes (test-driven-development), plans changes with rollback options (risk-management), makes small atomic commits (git-workflow), and loops through debugging as issues surface. Use when inheriting a codebase that's hard to change safely, when a production system needs modernization, or when you've been told "just don't break anything" but also need to ship features. NOT for greenfield work or isolated script changes.

0
installs
▌
Bdi Mental States · viktorbezdek bundle
This skill should be used when the user asks to "model agent mental states", "implement BDI architecture", "create belief-desire-intention models", "transform RDF to beliefs", "build cognitive agent", or mentions BDI ontology, mental state modeling, rational agency, or neuro-symbolic AI integration. NOT for multi-agent coordination or agent handoffs (use multi-agent-patterns), NOT for agent memory frameworks or persistence (use memory-systems).

0
installs
▌
Coding Discipline · viktorbezdek bundle
Research-grounded 5-principle behavioral contract for production LLM coding agents — Think Before Coding, Simplicity First, Surgical Changes, Goal-Driven Execution, and Calibrated Communication. Each principle names its anti-patterns and failure modes with empirical backing (SWE-bench, FeatBench, DELEGATE-52, SE literature). Apply when implementing features, fixing bugs, refactoring, or any coding task where production engineering discipline must be enforced. Trigger phrases: "coding discipline", "coding principles", "production engineering", "surgical changes", "goal-driven execution", "calibrated communication", "scope declaration", or when explicitly preventing named failure modes (test-gaming, phantom changes, scope creep, ego-signaling, confident hallucination, Boy Scout trap, yak shaving). NOT for code review of human-written code (use code-review), NOT for CI/CD setup (use cicd-pipelines), NOT for API design (use api-design), NOT for test framework setup without discipline framing (use testing-framewor

0
installs
▌
Stakeholder Alignment · viktorbezdek bundle
Align stakeholders in writing using RFCs, design docs, proposals, pre-reads, and decision docs with explicit role assignments (DACI, RAPID). Use when the user asks to write an RFC, design doc, proposal, pre-read, or decision doc, wants to align async stakeholders on a decision, needs to assign deciders vs consulted vs informed, wants to structure a cross-team proposal, or is preparing a pre-read for a decision meeting. NOT for structuring a generic memo (use structured-writing). NOT for stakeholder power maps (use persona-mapping). NOT for storytelling pitches or investor decks (use storytelling-for-stakeholders).

0
installs
▌
Content Modelling · viktorbezdek bundle
Design CMS content models — content types, fields, editorial workflows, governance rules, and COPE (Create Once, Publish Everywhere) patterns — for structured, multi-channel publishing. Use when the user asks to design a content model, define content types in a CMS, structure fields for editorial content, plan a headless CMS architecture, or design content reuse across channels. NOT for formal knowledge graphs, OWL/RDF ontologies, or semantic modeling (use ontology-design). NOT for naming conventions or taxonomy standards across code (use consistency-standards).

0
installs
▌
Navigation Design · viktorbezdek bundle
Design information architecture, wayfinding systems, and navigation structures for documentation sites and applications. Use when the user asks to design navigation, plan a sitemap, structure a sidebar or menu, define content hierarchy, design breadcrumbs, or organize how users move through content. NOT for user journey maps or touchpoint flows across time (use user-journey-design). NOT for microcopy, labels, or button text in navigation (use ux-writing). NOT for Next.js routing, layouts, or parallel routes (use nextjs-development).

0
installs
▌
Problem Definition · viktorbezdek bundle
Frame the real user or business problem (not a code/test bug) using Jobs-To-Be-Done, the 5-whys ladder, and problem-vs-symptom separation. Use when the user asks "are we solving the right problem", wants to write a problem statement, needs to separate problems from symptoms, wants to apply 5-whys to a product or organizational issue, suspects a brief conflates a feature with a problem, or wants to surface assumptions about what problem is actually being solved. NOT for ideating or brainstorming candidate solutions (use creative-problem-solving). NOT for diagnosing code, test, or CI bugs (use debugging). NOT for ranking problems by priority (use prioritization).

0
installs
▌
Trade Off Analysis · viktorbezdek bundle
Analyze trade-offs between competing product options using cost-benefit, opportunity cost, reversibility (one-way vs two-way doors), and second-order effects. Use when the user faces a product choice with non-trivial trade-offs, asks "what are we giving up", weighs short-term vs long-term impact, or needs to frame a decision before committing. NOT for scored prioritization of a backlog (use prioritization). NOT for quantified risk assessment (use risk-management). NOT for strategic go/no-go (use strategic-decision).

0
installs
▌
React Development · viktorbezdek bundle
React-specific development patterns including hooks (useState, useEffect, useReducer, useContext), component architecture, state management, shadcn/ui integration, JSX/TSX, React testing, and Bulletproof React auditing. NOT for Next.js routing, SSR, or server components (use nextjs-development). NOT for CSS design systems, Tailwind utilities, or accessibility patterns (use frontend-design).

0
installs
▌
Build A Plugin · viktorbezdek bundle
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 validation (plugin-validation), and trigger plus output evaluation with iteration loop (plugin-evaluation). Use when building a full Claude Code plugin with multiple components, hooks, MCP servers, or composed skills. Use when converting a working prototype into a shippable plugin. NOT for writing a single SKILL.md file — use the write-your-own-skill workflow for that. NOT for one-off prompt engineering — use prompt-engineering directly.

0
installs
▌
Build AI Agent · viktorbezdek bundle
Funnel workflow for going from "I want an agent that does X" to a deployed, evaluated, cost-monitored agent. Runs through nine phases starting with the is-this-task-agent-appropriate check (agent-project-development), then prompt design with eval criteria first (prompt-engineering), tool design and consolidation (tool-design), architecture selection for multi-step work (multi-agent-patterns), persistence decisions (memory-systems), context-window management (context-optimization), evaluation pipeline construction (agent-evaluation), deployment (hosted-agents), and ongoing cost and quality monitoring (cloud-finops + agent-evaluation). Use when you're starting a new agent project and want to avoid the common failure modes. NOT for one-shot prompts — use prompt-engineering directly for those.

0
installs
▌
Testing Framework · viktorbezdek bundle
Test framework router and infrastructure setup across multiple languages and platforms. Use when the user asks to choose a test framework, scaffold test infrastructure, add focused unit/integration/E2E/accessibility coverage, or integrate tests into CI/CD. Covers Rust, TypeScript/React, PHP/TYPO3, Shell, Playwright, accessibility, mutation, and fuzz testing as selectable modules. NOT for TDD methodology or red-green-refactor workflow (use test-driven-development), NOT for diagnosing and fixing bugs or analyzing errors (use debugging), NOT for reviewing existing code or PRs (use code-review).

0
installs
▌
Update A Plugin · viktorbezdek bundle
Update a Plugin

0
installs
▌
Engaging Craft · viktorbezdek bundle
Apply proven copywriting techniques to long-form technical content so it holds attention from sentence to sentence — and humanize prose that reads AI-generated. Covers AIDA, PAS, Before-After-Bridge, Bencivenga's pyramid, Sugarman's slippery slide, Schwartz's awareness levels, hook engineering, voice and tonality calibration, the concrete-over-abstract discipline, and the AI-prose-tell catalog (banned high-frequency AI words like delve / underscore / pivotal / leverage; AI transitions like "that being said" / "at its core"; reflex hedges; academic filler verbs; buzzwords like revolutionize / cutting-edge / seamless integration; the six structural fingerprints; the sniff test). Use when the user asks to make an article more engaging, write a hook, calibrate voice, humanize AI-generated prose, remove AI tells, fix robotic or generic copy, replace abstract claims with concrete examples, or apply a copywriting formula. NOT for outlining or section structure (use long-form-structure). NOT for line-level clarity ed

0
installs
▌
Critical Intuition · viktorbezdek bundle
Stress-test, critique, and challenge existing ideas through pattern recognition, bias detection, Bayesian reasoning, blind-spot exposure, and red-flag identification. Use when the user asks to stress-test a plan, challenge assumptions, find flaws, identify risks in an idea, expose hidden biases, audit a proposal for blind spots, or "poke holes in this". NOT for generating new ideas or solutions (use creative-problem-solving), NOT for structured risk registers or mitigation plans (use risk-management), NOT for brainstorming or divergent thinking (use creative-problem-solving).

0
installs
▌
Edge Case Coverage · viktorbezdek bundle
Identify and document boundary conditions, corner cases, error scenarios, and validation requirements that implementations must handle. Use when the user asks to find edge cases, identify corner cases, specify validation rules, enumerate error scenarios, harden a function against bad inputs, or think through what can go wrong at the boundaries of a system. NOT for writing the actual tests (use testing-framework or test-driven-development). NOT for structured risk registers around project-level risks (use risk-management). NOT for security vulnerability scanning (use code-review).

0
installs
▌
Filesystem Context · viktorbezdek bundle
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-context optimization like KV-cache or observation masking (use context-optimization), NOT for summarization or compression techniques (use context-compression), NOT for understanding context theory or fundamentals (use context-fundamentals).

0
installs
▌
Skill Template · viktorbezdek bundle
Template for creating Claude Code skills. Replace this description with a clear explanation of what this skill does and when it should be used.

0
installs
▌
Nextjs Development · viktorbezdek bundle
Next.js framework development including App Router, Server Components, Server Actions, SSR, SSG, ISR, caching, data fetching, middleware, layouts, parallel routes, and module architecture for Next.js 13+/15/16. NOT for generic React patterns, hooks, or component logic (use react-development). NOT for UI/CSS design systems or visual styling (use frontend-design).

0
installs
▌
Persona Definition · viktorbezdek bundle
Create individual user personas and customer archetypes — with demographics, goals, pain points, behaviors, and empathy maps — to represent the humans a product or system is built for. Use when the user asks to define personas, create user archetypes, describe target users, build empathy maps, or characterize the audience for a product or design decision. NOT for mapping stakeholders across an organization, RACI charts, or influence analysis (use persona-mapping). NOT for designing research interview flows (use elicitation).

0
installs
▌
Prompt Engineering · viktorbezdek bundle
Design, evaluate, and iteratively improve prompts for LLMs — system prompts, few-shot examples, reasoning structures, and instruction templates. Use when the user asks to improve a prompt, write a system prompt, optimize LLM instructions, reduce hallucinations through prompt structure, test prompt variants, or apply prompting techniques (structured reasoning, ReAct, few-shot, structured output). NOT for building MCP tools or server implementation (use mcp-server). NOT for creating Claude Code SKILL.md files (use skill-foundry). NOT for building a full agent (use build-ai-agent workflow).

0
installs
▌
Python Development · viktorbezdek bundle
Python development — use when the user works with .py files, pyproject.toml, uv, ruff, mypy, pytest, async/await, MicroPython, CLI tools, or PyPI publishing. Covers modern tooling, best practices, library architecture, functional patterns, and production workflows. NOT for TypeScript or JavaScript development (use typescript-development), NOT for React component patterns (use react-development).

0
installs
▌
Research Synthesis · viktorbezdek bundle
Structured research and evidence synthesis for knowledge-intensive tasks. Use for multi-source research coordination, evidence triangulation across conflicting sources, competing-hypothesis analysis, literature/documentation sweeps, claim verification, and synthesis reports. Trigger phrases: "research this topic", "synthesise findings from", "compare sources on", "what does the evidence say about", "triangulate these claims". NOT for primary data collection (interviews, surveys) — this skill synthesises existing sources. NOT for code research or codebase exploration — use CodeGraph and Semble for that. NOT for creative content generation — synthesis produces structured analysis, not narrative content.

0
installs
▌
Documentation Discipline · viktorbezdek bundle
Decide what and when to write down, and produce Architecture Decision Records (ADRs), one-pagers, runbooks, and decision logs. Use when the user asks whether something should be documented, wants to write an ADR, needs a runbook or operational playbook, wants to keep a decision log, or is trying to decide between a one-pager and an RFC. NOT for auto-generating docs from code (use documentation-generator). NOT for end-user tutorials or how-tos (use example-design). NOT for docs-site information architecture (use navigation-design). NOT for cross-team alignment via RFCs (use stakeholder-alignment).

0
installs
▌
API To Production · viktorbezdek bundle
End-to-end workflow for taking an API from design through TDD, code review, CI/CD, and containerized deployment. Composes five phases — REST/GraphQL/gRPC design with schemas and error contracts (api-design), red-green-refactor on every endpoint (test-driven-development), multi-perspective code review (code-review), pipeline wiring with automated testing (cicd-pipelines), and Docker containerization with multi-stage builds and optimization (docker-containerization). Use when building a new API endpoint or service that needs to ship to production. Use when converting a prototype API into production-grade infrastructure. NOT for frontend-only work — use frontend-design or react-development. NOT for existing API maintenance without deployment changes — use code-review directly.

0
installs
▌
Long Form Polish · viktorbezdek bundle
Polish a long-form technical draft for pacing, scan-ability, and tightness. Cover paragraph and sentence rhythm, the scan reader's experience (headings, callouts, pull quotes, white space, lists, tables), the 30% cut discipline for removing filler, and the read-aloud test for finding bumps. Distinct from short-form line-level editing — this skill works at the paragraph and section level for pieces of 1500-5000+ words. Use when the user asks to polish a long article, fix pacing, improve scan-ability, run a cut pass, do a read-aloud test, tighten a draft, fix uneven sections, or prepare a draft for publication. NOT for short-form clarity editing of memos / RFCs / emails (use communication/clarity-editing). NOT for sentence-level craft techniques like AIDA / PAS (use engaging-craft). NOT for outlining or structural changes (use long-form-structure). NOT for code documentation cleanup (use documentation-generator).

0
installs
▌
Interview Facilitation · viktorbezdek bundle
Structure the interview arc when a brainstorm-swarm interviews the user. Covers the divergent-then-convergent arc (open with breadth, close with depth), question design (open vs probing, leading vs neutral, what-vs-why- vs-how), depth-vs-breadth tradeoffs, and when to send a second round of follow-up questions to specific personas. Use when running a brainstorm swarm and the swarm-protocol skill has spawned the persona subagents — this skill teaches how those personas interact with the user during the interview phase. NOT for the persona swarm orchestration itself (use swarm-protocol). NOT for synthesizing the swarm output (use swarm-synthesis). NOT for designing custom personas (use custom-personas). NOT for one-on-one Socratic interviews (use deep-interview from skillstack).

0
installs
▌
Context Compression · viktorbezdek bundle
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 context failures or degradation patterns (use context-degradation), NOT for KV-cache optimization or context partitioning (use context-optimization), NOT for learning context theory or basics (use context-fundamentals), NOT for file-based offloading or scratch pads (use filesystem-context).

0
installs
▌
Context Degradation · viktorbezdek bundle
Diagnosing context FAILURES — lost-in-middle, poisoning, distraction, confusion, and clash patterns with model-agnostic measurement workflows. Use when the user asks to "diagnose context problems", "fix lost-in-middle issues", "debug agent failures", "understand context poisoning", or mentions context degradation, context clash, or agent performance degradation. NOT for learning context basics or theory (use context-fundamentals), NOT for compressing or summarizing context (use context-compression), NOT for KV-cache optimization or partitioning (use context-optimization), NOT for building isolated multi-agent architectures (use multi-agent-patterns).

0
installs
▌
Outcome Orientation · viktorbezdek bundle
Reframe work around measurable outcomes using OKRs, KPIs, and the outcome-vs-output distinction. Use when the user asks to define success criteria, write OKRs, set KPIs, clarify what "done" means in terms of impact, distinguish outputs from outcomes, or make a goal statement measurable and time-bound. NOT for ranking or scoring features by priority (use prioritization). NOT for systemic feedback-loop analysis (use systems-thinking).

0
installs
▌
Strategic Decision · viktorbezdek bundle
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 downside per option (risk-management), ranks using the original criteria (prioritization), and uses outcome-orientation as an end gate — does the top-ranked option actually achieve the outcome we defined? Use for irreversible bets, resource allocation across competing priorities, pivot/persevere decisions, hire-for-speed vs hire-for-quality choices. NOT for reversible decisions with cheap experimentation — just experiment.

0
installs
▌
User Journey Design · viktorbezdek bundle
Map user journeys with touchpoints, emotional states, pain points, and opportunities across the full arc of a user's experience over time. Use when the user asks to map a user journey, create a customer journey map, design a service blueprint, document touchpoints and friction points, or visualize the end-to-end experience of a user across multiple interactions. NOT for static navigation structure or sitemaps (use navigation-design). NOT for creating user personas or archetypes (use persona-definition). NOT for designing research interview flows (use elicitation). NOT for writing microcopy at specific touchpoints (use ux-writing).

0
installs
▌
Debug Complex Issue · viktorbezdek bundle
Loop workflow for debugging a complex issue you've been stuck on for more than 30 minutes. Runs systematic hypothesis formation (debugging skill), feedback-loop mapping when the bug looks like a dynamic problem (systems-thinking), context-pathology check when it's an LLM/agent bug (context-degradation), blast-radius assessment before any fix attempt (risk-management), and uses test-driven-development as the debugging oracle — write a failing test that reproduces the bug, then iterate fix → test until green. Use when a bug has defeated a first-pass attempt, when symptoms seem to shift under investigation, when an LLM-based system is misbehaving in ways simple prompt fixes don't resolve, or when you need to fix safely under production constraints. NOT for obvious bugs where the fix is visible — just fix those directly.

0
installs
▌
Onboard To Codebase · viktorbezdek bundle
Ramp-up workflow for understanding a new codebase fast — onboard to codebase, understand a repo, grok a project, ramp up on code. Generates a codemap so the structure is visible before you read any implementation (documentation-generator), then builds a system model of dependencies, feedback loops, and critical paths so you know which parts matter (systems-thinking), then traces key flows end-to-end through the code so you see how the pieces connect in practice (debugging), and finally builds a context strategy so you know what to keep in working memory and what to look up on demand (context-fundamentals). Use when joining a new team, inheriting a codebase, onboarding an AI agent to a repo, or switching projects and needing productive orientation in hours instead of weeks. NOT for codebases you already know well — skip straight to the relevant skill instead.

0
installs
▌
Distribution Craft · viktorbezdek bundle
Engineer the distribution layer of a long-form technical article — title, dek (subtitle), meta description, social pull-quotes, and channel-specific framing. Most technical articles die at the title; this skill covers the craft of titles that earn the click without clickbait, deks that confirm the promise, social pull-quotes for X / LinkedIn / Hacker News / Reddit, open-graph metadata, and the practice of reframing the same article differently per channel. Use when the user asks to write a title for an article, suggest titles, write a dek or subtitle, write a meta description, pull social quotes, prepare a launch, write a tweet thread for an article, reframe for LinkedIn / HN / Reddit, or audit existing distribution copy. NOT for the article body itself (use long-form-structure / engaging-craft / long-form-polish). NOT for SEO keyword research and on-page optimization beyond titles and meta (general SEO is out of scope). NOT for content marketing strategy. NOT for short-form business writing like email subjec

0
installs
▌
Technical Research · viktorbezdek bundle
Research before craft for long-form technical content. Profile the audience (knowledge level, jobs-to-be-done, prior beliefs), tier sources (primary > peer-reviewed > authoritative > popular > vendor), triangulate every load- bearing claim across three sources, manage evidence types (data, expert quotes, demonstrations, case studies, source code), and apply citation discipline (when, how, link-rot mitigation, footnote vs inline). Use when the user asks to research a technical article, profile an audience, find sources for a deep-dive, fact-check a draft, build a claim-evidence map, or audit citations. NOT for code documentation research (use documentation- generator). NOT for line-level editing (use long-form-polish or communication/clarity-editing). NOT for the article structure itself (use long-form-structure). NOT for UX research or persona definition for product (use persona-definition).

0
installs
▌
Cloud Infrastructure · viktorbezdek bundle
Cloud infrastructure design and infrastructure-as-code (IaC) authoring. Use for Terraform module authoring, AWS CDK constructs, cloud architecture design (VPCs, load balancers, managed services, serverless), multi-region and disaster-recovery patterns, cost-optimisation analysis, and IaC code review. Trigger phrases: "write Terraform for", "design the AWS architecture", "set up a VPC", "convert this to CDK", "optimise our cloud costs". NOT for application-layer code — this skill models infrastructure, not the code running on it. NOT for Kubernetes application manifests (Deployments, Services, Ingress) — those belong in a k8s-specific skill. NOT for CI/CD pipeline configuration — that is a deployment concern separate from infrastructure provisioning.

0
installs
▌
Context Fundamentals · viktorbezdek bundle
Foundational theory of context engineering — what context IS, how attention works, progressive disclosure principles, and context budgeting basics. Use when the user asks to "understand context", "explain context windows", "learn context engineering", or discusses context components, attention mechanics, or context budgets. NOT for fixing broken context or diagnosing failures (use context-degradation), NOT for compressing or summarizing context (use context-compression), NOT for KV-cache or partitioning performance optimization (use context-optimization), NOT for file-based context patterns or scratch pads (use filesystem-context).

0
installs
▌
Context Optimization · viktorbezdek bundle
EXTENDING effective context capacity — KV-cache optimization, observation masking, context partitioning, and retrieval strategies. Use when the user asks to "optimize context", "implement KV-cache", "partition context", "mask observations", or mentions extending context capacity or cache-friendly prompt design. NOT for reducing or compressing content via summarization (use context-compression), NOT for diagnosing context failures or degradation patterns (use context-degradation), NOT for file-based context patterns or scratch pads (use filesystem-context), NOT for learning context basics (use context-fundamentals).

0
installs
▌
Multi Agent Patterns · viktorbezdek bundle
This skill should be used when the user asks to "design multi-agent system", "implement supervisor pattern", "create swarm architecture", "coordinate multiple agents", or mentions multi-agent patterns, context isolation, agent handoffs, sub-agents, or parallel agent execution. NOT for agent memory or persistence (use memory-systems), NOT for tool design or tool interfaces (use tool-design), NOT for hosted agent infrastructure or sandboxed VMs (use hosted-agents), NOT for BDI cognitive models or mental state modeling (use bdi-mental-states).

0
installs
▌
Value Proposition Design · viktorbezdek bundle
Design a product value proposition using the Value Proposition Canvas (jobs, pains, gains, pain relievers, gain creators) and the Kano model. Use when the user asks to write a value proposition, map pains and gains to product features, apply VPC, distinguish basic/performance/delighter features (Kano), or articulate why a product matters to a specific customer. NOT for marketing copy or microcopy (use ux-writing). NOT for pitching the value prop to stakeholders (use storytelling-for-stakeholders). NOT for generic slogans.

0
installs
▌
Security Engineering · viktorbezdek bundle
Application security design and threat-informed engineering. Use for authentication and authorisation architecture (OAuth2, JWT, RBAC, ABAC), OWASP Top 10 vulnerability analysis, secrets management (Vault, AWS Secrets Manager, environment isolation), input validation patterns, secure API design, SQL injection and XSS prevention, and security-aware code review. Trigger phrases: "secure this endpoint", "design an auth system", "review this for security vulnerabilities", "how do I store secrets", "implement RBAC". NOT for network/infrastructure security (firewalls, VPNs, WAF config) — those belong in cloud-infrastructure. NOT for compliance auditing (SOC2, GDPR gap assessments) — that requires a compliance specialist. NOT for penetration testing or red-teaming — this skill is for defensive engineering, not offensive exercises.

0
installs
▌
Design Review Sprint · viktorbezdek bundle
Sequential-audit workflow for running a full UX review pass across an application or product. Walks through five phases — visual audit of design system adherence (frontend-design), navigation and information architecture review (navigation-design), microcopy and error-message audit (ux-writing), end-to-end journey validation (user-journey-design), and cross-product consistency check (consistency-standards). Use when launching a new product version, onboarding a design system, preparing for an accessibility audit, or when user feedback signals "something feels off" but nobody can pinpoint what. NOT for single-component fixes — use frontend-design directly. NOT for greenfield design — design the system first, then audit it.

0
installs
▌
Write Your Own Skill · viktorbezdek bundle
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 (consistency-standards), writes structural validation tests before the content (test-driven-development), audits the draft against anti-patterns (critical-intuition), and generates the README with scenario tables (documentation-generator). Use when creating any new Claude Code skill that you want to be activation-reliable, well-scoped, and maintainable. NOT for quick-and-dirty prompts — use prompt-engineering directly.

0
installs
▌
Social Media Content · viktorbezdek bundle
Short-form social media content for LinkedIn, Twitter/X, and similar platforms. Use for LinkedIn post drafting, Twitter/X thread writing, hook-first content structures, platform-native tone calibration, hashtag strategy, and engagement-optimised formatting. Trigger phrases: "write a LinkedIn post", "draft a Twitter thread", "turn this into a thread", "write a social post about", "make this shareable". NOT for long-form blog articles or newsletters — use the storytelling or email-marketing skill for those. NOT for ad copy or paid social — those have conversion-optimisation constraints beyond organic content. NOT for content calendars or scheduling strategy — this skill writes the content, not the plan.

0
installs
▌
Long Form Structure · viktorbezdek bundle
Structure long-form technical articles around the hook → promise → setup → development → payoff contract. Pick from canonical templates (deep-dive, tutorial, opinion, case study, whitepaper, technical narrative). Engineer section transitions and signposting. Match length to ambition (when 800 vs 1500 vs 3000 vs 5000+ words is right). Use when the user asks to outline a technical article, structure a deep-dive, plan a tutorial, organize a whitepaper, pick an article template, fix pacing across sections, or audit the structure of an existing draft. NOT for short-form work writing like RFCs or memos (use communication/structured-writing — BLUF, Pyramid). NOT for line-level editing or pacing within paragraphs (use long-form-polish). NOT for fiction or character-driven story arcs (use storytelling). NOT for research, sourcing, or citation (use technical-research).

0
installs
▌
Outcome Oriented Thinking · viktorbezdek bundle
Apply outcome-over-output product thinking — separating what gets built from what actually changes for the user, running the "so what" test to climb from output to outcome to impact, choosing leading vs lagging metrics, and identifying a North Star metric. Use when the user asks whether something is an outcome or an output in a product context, wants to run the "so what" test on a deliverable, wants a North Star metric, needs to choose leading indicators for a product bet, or is debating whether shipping a feature equals success. NOT for generic OKR authoring (use outcome-orientation). NOT for feedback-loop analysis (use systems-thinking). NOT for metric scoring or ranking (use prioritization).

0
installs
▌
User Needs Identification · viktorbezdek bundle
Identify what users actually need using functional/emotional/social jobs, needs-vs-wants laddering, latent-need surfacing, and job statements. Use when the user asks what users truly need, wants to write a job statement (When/I-want-to/So-I-can), wants to move past stated wants to underlying needs, needs to separate functional jobs from emotional or social ones, or wants to spot latent needs the user cannot articulate. NOT for persona demographics (use persona-definition). NOT for stakeholder power maps (use persona-mapping). NOT for interview scripting (use elicitation).

0
installs
▌
LLM Cost Optimization · viktorbezdek bundle
Funnel-with-gate workflow for reducing LLM costs without degrading quality. Starts with diagnosing the cost surface using cloud-finops (specifically the finops-for-ai and finops-anthropic references), then applies context-optimization to reduce context per call, context-compression to compress what can't be reduced, prompt-engineering for shorter prompts and better model selection, and uses agent-evaluation as a mandatory gate — if any optimization degrades quality, roll it back. Finishes with prioritization of remaining opportunities and risk-management guardrails for future auto-scaling. Use when LLM costs are growing faster than usage, when leadership is asking why the bill doubled, when unit economics are turning negative, or when a new feature is about to ship and cost containment is part of the launch plan. NOT for cost reductions that don't involve LLMs — use cloud-finops directly.

0
installs
▌
Product Story To Ship · viktorbezdek bundle
PM funnel workflow for turning user research into prioritized engineering stories — product story, user research to backlog, user needs to stories, PM workflow. Chains elicitation (deep interviews that surface real needs), user-journey-design (touchpoints, pain points, emotions), persona-definition (who we're building for), outcome-orientation (measurable success criteria), and prioritization (RICE/MoSCoW/ICE scoring). Use when translating user research into engineering work, when the backlog is unranked feature requests, when launching a new product from interviews to sprint-ready stories, or when the team builds features nobody asked for. NOT for technical architecture — use strategic-decision. NOT for backlog grooming without new research — use prioritization directly.

0
installs
▌
Consistency Standards · viktorbezdek bundle
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 for CMS content types or editorial workflows (use content-modelling). NOT for language-specific code conventions (use typescript-development or python-development).

0
installs
▌
Content Platform Build · viktorbezdek bundle
Layering workflow for building a knowledge base, CMS, documentation site, or structured content platform from scratch. Builds the data model first (content-modelling), adds a formal knowledge-graph layer if needed (ontology-design), establishes naming and taxonomy conventions (consistency-standards), designs information architecture (navigation-design), fine-tunes voice and microcopy (ux-writing), fills the structure with examples (example-design), and adds tooling for scale (documentation-generator). Use when starting a content or docs system from scratch, migrating one to a structured model, or rescuing one that has drifted into inconsistency. NOT for small single-page docs — use documentation-generator alone.

0
installs

116 published skills · page 1 of 2