jet-skills

Review a design/PR/proposal as a Staff Solution Architect — simplicity, scalability, EDA fit, security, cost, EU data residency, operability.

Set up or refresh this repo's project context — writes a local CONTEXT.md so every other skill/command has company/domain specifics without anything being hardcoded.

Forecast token/usage cost for an LLM workload from usage signals; produce a wiki-ready table.

Produce an Enterprise-Architecture briefing from a technical update or discussion, with governance questions; translate PL↔EN if the source and audience differ.

Challenge and right-size the scope of a feature, plan, or idea before any code is written — using four explicit modes (Expansion / Selective / Hold / Reduction).

Staff Solution Architect persona for design review and tradeoff analysis. Use for deep architecture work that benefits from a focused subagent.

Author Architecture Decision Records from a discussion, meeting notes, or a design debate. Use whenever the user wants to capture a decision, writes "record this as an ADR", finishes an architecture discussion, or asks to document why a choice was made. One ADR per decision.

Draft a long-form article, blog post, essay, or technical write-up in the author's own voice — outline first, then a full draft that reads like a person wrote it. Use whenever the user asks to "write an article", "draft a blog post", "write a long-form piece", "turn this into an essay", or wants a publishable write-up rather than notes or a spec.

Switch to ultra-compressed communication that cuts tokens while keeping accuracy. Use whenever the user says "caveman mode", "be terse", "minimise tokens", or wants maximally compact responses without losing correctness.

Debug methodically — reproduce, minimise, hypothesise, instrument, fix, then add a regression test. Use whenever the user is chasing a bug, says "why is this failing", "help me debug", or has a flaky/mysterious failure.

Generate complete, structured documentation for a feature, module, API, or project using the Diataxis framework (tutorial / how-to / reference / explanation). Use whenever the user asks to "write docs", "document this", "generate documentation", "write a tutorial", "write a how-to", or "explain this module". Reads the real code before writing and never documents behavior the code doesn't have.

1 hook across 1 event