the-main-thread

Inspect large or complex XLSX workbooks with this repository's JBang and Apache POI analyzer before answering. Use for workbook structure, formulas, bounded cell evidence, the UCI Online Retail II audit, or embedded images when the binary must stay outside the agent context.

Generate Quarkus test data for NebulaTrack satellite events using Instancio models, Datafaker, and domain-specific formats instead of hardcoded literals

Build systems, CI/CD, Kubernetes, deploy pipelines, feature flags in delivery infrastructure, and service runtime operations owned by platform — not customer ticket queues and not accounts payable.

Billing, refunds, invoices, payment processors, revenue recognition, and anything where money or invoices move — including when a broken API blocks checkout or invoicing.

Customer-facing support desk — ticket intake, severity classification, and routing incidents that affect end users (not money movement and not build pipelines).

Review, critique, and give publication-readiness feedback on technical articles, tutorials, blog posts, outlines, and individual sections, especially for Java, Quarkus, and The Main Thread audiences. Use when a user asks "review this", "tear this apart", "give me feedback", "check this tutorial", "is this good enough to publish?", "what's wrong with this?", or provides a draft and asks for editorial or technical critique. Covers technical accuracy, code samples, narrative/pedagogy, and voice calibration. Pair with main-thread-tutorial-structure and authentic-voice when those skills are available.

Apply The Main Thread voice to tutorials, articles, explanations, and technical marketing copy: first-person personal technical narration, direct peer-to-peer engineering prose, fluent German/non-native rhythm, smaller plain vocabulary, concrete stakes, occasional dry humor, and no generic AI polish. Use when drafting, rewriting, or reviewing prose for tone; when a user asks for "my voice", "make this sound less AI", "make it sound like The Main Thread", or "run a voice pass"; and when a draft needs less documentation smell, less repetition, or a negation-budget pass. This skill controls wording only. Pair with main-thread-tutorial-structure for invisible story scaffolding, verification, and code standards, and with article-reviewer for critique.

Create publishing assets for finished The Main Thread articles after structure and voice are done. Use when preparing a Substack/blog publishing package, rendering Mermaid diagrams to copy-pasteable PNGs, writing alt text for diagrams, researching and generating SEO title/subtitle/url slug/tags, creating persona-based Substack title/subtitle variants for A/B testing, drafting social posts for Mastodon, X, Bluesky, and LinkedIn, or creating a 1200x630 hero image prompt aligned to the article. Do not rewrite article prose unless explicitly asked.

Define invisible story scaffolding for The Main Thread hands-on tutorials: why the problem matters, what gets built, what readers need, how the code works, how it fails, how to configure it, how to prove it, and how to close the loop. Use when planning, drafting, rewriting, or reviewing a full tutorial, quick guide, architecture article, or code-heavy explanation that needs production framing, complete code, verification commands, and a contained narrative. Use O'Reilly mechanics for cleanup only, not as the prose voice. Pair with authentic-voice for personal technical narration and article-reviewer for structured critique. Verify version-sensitive facts with current docs or tools rather than memory.