viktorbezdek

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 microc

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 (ba

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 t

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 co

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 (u

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-degradat

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-

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 desi

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),

[TODO: Write comprehensive description in third-person. Start with "This skill provides..." or "This skill should be used when..."] [TODO: Add "Use when" scenarios - specific situations where Claude should use this skill] [TODO: Add keywords - technologies, use cases, error messages that should trigger this skill]

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

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 promp