all publishers

jwiegley

@jwiegley source repo

49 published skills

  1. ▌
    Nixos 3 · jwiegley
    Resolve NixOS issues using research and sequential thinking. Use when diagnosing or fixing problems on a NixOS host -- failed builds or switches, broken services or modules, configuration errors -- or whenever the user mentions NixOS, nixos-rebuild, or /etc/nixos.
    6 repo stars
  2. ▌
    Persian 3 · jwiegley bundle
    Translate English language text into high quality, accurate Persian (Farsi) text using a team of specialist reviewers
    6 repo stars
  3. ▌
    Node Red 3 · jwiegley bundle
    Build, edit, and debug Node-RED flows on John's NixOS host (vulcan). Tuned to his actual plugin set, wiring conventions, naming style, and to the nodered_events PostgreSQL log + Grafana dashboard for chain tracing. Use whenever the user mentions Node-RED, flows.json, a flow tab name (Office, Schedule, Schedules, Pool Time, Away, Bedroom, TV Room, Institute Night, Debug), a Node-RED plugin or node type (chronos, api-call-service, api-current-state, server-state-changed, join-wait, actionflows, etc.), the Node-RED Events Grafana dashboard, or asks why a flow fired or didn't fire.
    6 repo stars
  4. ▌
    Skill Creator 3 · jwiegley bundle
    Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
    6 repo stars
  5. ▌
    Forge 2 · jwiegley
    Multi-phase, multi-model deep analysis workflow for complex problems. This skill should be used when the user wants rigorous, multi-model collaborative analysis: deep research with Fable/Opus and PAL MCP consensus (GPT-5.5-Pro + Gemini 3 Pro), strategic planning, Fable/Opus execution with tests, comprehensive review, and adversarial devil's advocate critique. Invoke explicitly with /forge.
    6 repo stars
  6. ▌
    Johnw 2 · jwiegley bundle
    Write in John Wiegley's authentic voice. Use when drafting technical articles, blog posts, essays, or any written material that should read as if John wrote it himself. Captures patterns from 1,100+ posts spanning 1992-2026 across both technical (newartisans) and personal (johnwiegley) blogs. Focuses on technical writing but incorporates cross-cutting voice patterns from the full corpus.
    6 repo stars
  7. ▌
    Nixos 2 · jwiegley
    Resolve NixOS issues using research and sequential thinking. Use when diagnosing or fixing problems on a NixOS host -- failed builds or switches, broken services or modules, configuration errors -- or whenever the user mentions NixOS, nixos-rebuild, or /etc/nixos.
    6 repo stars
  8. ▌
    Retest 2 · jwiegley bundle
    Full model-support battery on any branch -- rebuild, unit tests, FPGA correctness vs the HuggingFace transformers source of truth, code review, comment-check, and a perf pass. Derives the target model set from the branch diff. Use when retesting a stack of PRs that adds or fixes support for one model or arch family on the FPGA pipeline.
    6 repo stars
  9. ▌
    Wiggum 2 · jwiegley bundle
    Methodology for the user-triggered /wiggum command (do not self-invoke). An autonomous-continuation loop for long-running work -- run, checkpoint, and verify until a defined Definition of Done holds or a stop-and-escalate condition fires. Covers durable handoff state, baseline re-verification after context compaction, per-commit self-audit, work-unit commit and restack cadence, subagent fan-out limits, host-conditional anvil (live Emacs) tooling, and escalation.
    6 repo stars
  10. ▌
    Caveman 2 · jwiegley
    Compress and simplify prompts to preserve meaning while reducing use of context. Use when asked to compress, shorten, or "caveman" a prompt or other text, or when text must fit a smaller context budget without losing meaning.
    6 repo stars
  11. ▌
    Fix All 2 · jwiegley bundle
    Fix all issues — no exceptions, no excuses. Fix every finding uncovered during the work, here and now. "Out of scope," "pre-existing," and "follow-up ticket" are not acceptable framings. Fixes go upstream, everything changed gets a real test, and no reward hacking.
    6 repo stars
  12. ▌
    Persian 2 · jwiegley bundle
    Translate English language text into high quality, accurate Persian (Farsi) text using a team of specialist reviewers
    6 repo stars
  13. ▌
    Swiftui 2 · jwiegley bundle
    Write, review, or improve SwiftUI code following best practices for state management, view composition, performance, modern APIs, Swift concurrency, and iOS 26+ Liquid Glass adoption. Use when building new SwiftUI features, refactoring existing views, reviewing code quality, or adopting modern SwiftUI patterns.
    6 repo stars
  14. ▌
    Toolkit 2 · jwiegley
    The standard tooling and working discipline for planning and executing a coding task -- GitHub CLI, codebase search, the language -pro agents, web research, sequential thinking, context7, and lint/type-check gating. The /medium and /heavy effort-tier commands build on it; load it when told to apply the standard toolkit.
    6 repo stars
  15. ▌
    It Voice 2 · jwiegley
    Guides writing and editing of technical documentation in an elevated, sedate, institutionally grounded register — measured, authoritative, and formal rather than casual or promotional. Applies when drafting or revising manuals, plans, runbooks, specifications, or policy documents, or when lifting an existing flat draft into this register.
    6 repo stars
  16. ▌
    Node Red 2 · jwiegley bundle
    Build, edit, and debug Node-RED flows on John's NixOS host (vulcan). Tuned to his actual plugin set, wiring conventions, naming style, and to the nodered_events PostgreSQL log + Grafana dashboard for chain tracing. Use whenever the user mentions Node-RED, flows.json, a flow tab name (Office, Schedule, Schedules, Pool Time, Away, Bedroom, TV Room, Institute Night, Debug), a Node-RED plugin or node type (chronos, api-call-service, api-current-state, server-state-changed, join-wait, actionflows, etc.), the Node-RED Events Grafana dashboard, or asks why a flow fired or didn't fire.
    6 repo stars
  17. ▌
    Parallelize 2 · jwiegley bundle
    Offload safe, independent subtasks to concurrent subagents while continuing your own work as the coordinator, then integrate what they return. Use when mid-task and some work could run in parallel without conflicting -- research, generating a standalone new file, tests for a stable interface, docs, or isolated analysis -- to accelerate without races. The coordinator alone runs git and mutates shared state; subagents read freely but write only to isolated namespaces and hand back artifacts. Triggers include "parallelize this", "spin up subagents to help", "do these in parallel", "fan this out".
    6 repo stars
  18. ▌
    Comment Audit 2 · jwiegley bundle
    Exhaustively verify code comments against the current state of a project. Use when asked to audit, fact-check, or validate comments/docstrings -- to confirm that every claim a comment makes is true, that any code shown in a comment actually works, and that everything a comment references still exists. Supports auditing an entire project or only the changes in a PR or stack of PRs. Triggers: "check the comments", "are these comments still accurate", "audit comments in this PR", "verify the docstrings".
    6 repo stars
  19. ▌
    Skill Creator 2 · jwiegley bundle
    Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
    6 repo stars
  20. ▌
    Fix Transcript 2 · jwiegley bundle
    Methodology for cleaning up a transcript file in place -- paragraphs, punctuation, capitalization -- without changing wording or meaning. Use when asked to clean, format, or fix a speech-to-text transcript, correcting technical vocabulary and spoken punctuation while preserving the speaker's words. The `/fix-transcript` command turns it on with the target file as its argument.
    6 repo stars
  21. ▌
    Eliminate Dead Code 2 · jwiegley bundle
    Methodology for finding and removing dead code and stale documentation with evidence-based safety, using a mark / debate / act / verify workflow. Use when asked to remove dead code, unused symbols, unreachable branches, stale docs, unused imports, or dead feature flags -- gathering independent evidence before each removal and re-verifying build and tests after. The `/eliminate-dead-code` command turns it on.
    6 repo stars
  22. ▌
    Translate En · jwiegley bundle
    Translate Arabic/Persian Baha'i sacred texts into English using a team of specialist reviewers, producing translations in the elevated register of Shoghi Effendi
    6 repo stars
  23. ▌
    Anvil · jwiegley bundle
    Use the available Anvil MCP backend — interactive Emacs, dedicated headless Emacs, or NeLisp — for structured file, Org, Git, data, and Elisp work. Detect the advertised capabilities, prefer typed and token-efficient operations, and apply live-session safety only where the backend actually reaches the user's interactive Emacs.
    6 repo stars
  24. ▌
    Forge · jwiegley
    Multi-phase, multi-model deep analysis workflow for complex problems. This skill should be used when the user wants rigorous, multi-model collaborative analysis: deep research with a native orchestrator and PAL MCP consensus, strategic planning, execution with tests, comprehensive review, and adversarial devil's advocate critique. Invoke explicitly with /forge.
    6 repo stars
  25. ▌
    Johnw · jwiegley bundle
    Write in John Wiegley's authentic voice. Use when drafting technical articles, blog posts, essays, or any written material that should read as if John wrote it himself. Captures patterns from 1,100+ posts spanning 1992-2026 across both technical (newartisans) and personal (johnwiegley) blogs. Focuses on technical writing but incorporates cross-cutting voice patterns from the full corpus.
    6 repo stars
  26. ▌
    Retest · jwiegley bundle
    Full model-support battery on any branch -- rebuild, unit tests, FPGA correctness vs the HuggingFace transformers source of truth, code review, comment-check, and a perf pass. Derives the target model set from the branch diff. Use when retesting a stack of PRs that adds or fixes support for one model or arch family on the FPGA pipeline.
    6 repo stars
  27. ▌
    Wiggum · jwiegley bundle
    Methodology for the user-triggered /wiggum command (do not self-invoke). An autonomous-continuation loop for long-running work -- run, checkpoint, and verify until a defined Definition of Done holds or a stop-and-escalate condition fires. Covers durable handoff state, baseline re-verification after context compaction, per-commit self-audit, work-unit commit and restack cadence, subagent fan-out limits, and escalation.
    6 repo stars
  28. ▌
    Caveman · jwiegley
    Compress and simplify prompts to preserve meaning while reducing use of context. Use when asked to compress, shorten, or "caveman" a prompt or other text, or when text must fit a smaller context budget without losing meaning.
    6 repo stars
  29. ▌
    Fix All · jwiegley bundle
    Fix all issues — no exceptions, no excuses. Fix every finding uncovered during the work, here and now. "Out of scope," "pre-existing," and "follow-up ticket" are not acceptable framings. Fixes go upstream, everything changed gets a real test, and no reward hacking.
    6 repo stars
  30. ▌
    Refocus · jwiegley
    Reassess scope creep against the user's goal at least hourly during active work, then refocus on timely completion. Use when asked to refocus or whenever Wiggum is active.
    6 repo stars
  31. ▌
    Swiftui · jwiegley bundle
    Write, review, or improve SwiftUI code following best practices for state management, view composition, performance, modern APIs, Swift concurrency, and iOS 26+ Liquid Glass adoption. Use when building new SwiftUI features, refactoring existing views, reviewing code quality, or adopting modern SwiftUI patterns.
    6 repo stars
  32. ▌
    Toolkit · jwiegley
    The standard tooling and working discipline for planning and executing a coding task -- GitHub CLI, codebase search, the language -pro agents, web research, sequential thinking, and lint/type-check gating. The /medium and /heavy effort-tier commands build on it; load it when told to apply the standard toolkit.
    6 repo stars
  33. ▌
    It Voice · jwiegley
    Guides writing and editing of technical documentation in an elevated, sedate, institutionally grounded register — measured, authoritative, and formal rather than casual or promotional. Applies when drafting or revising manuals, plans, runbooks, specifications, or policy documents, or when lifting an existing flat draft into this register.
    6 repo stars
  34. ▌
    Docstring · jwiegley
    Write docstrings for PyTorch functions and methods following PyTorch conventions. Use when writing or updating docstrings in PyTorch code.
    6 repo stars
  35. ▌
    Parallelize · jwiegley bundle
    Offload safe, independent subtasks to concurrent subagents while continuing your own work as the coordinator, then integrate what they return. Use when mid-task and some work could run in parallel without conflicting -- research, generating a standalone new file, tests for a stable interface, docs, or isolated analysis -- to accelerate without races. The coordinator alone runs git and mutates shared state; subagents read freely but write only to isolated namespaces and hand back artifacts. Triggers include "parallelize this", "spin up subagents to help", "do these in parallel", "fan this out".
    6 repo stars
  36. ▌
    Alexey Review · jwiegley bundle
    Review a pull request (or any Haskell/C++/compiler or other change) with very close fidelity to the review judgment, severity calibration, and communication mechanics of Alexey. Use when the user invokes /alexey or asks for an Alexey-fidelity review. Applies his engineering discipline; explicitly not an impersonation.
    6 repo stars
  37. ▌
    Comment Audit · jwiegley bundle
    Exhaustively verify code comments against the current state of a project. Use when asked to audit, fact-check, or validate comments/docstrings -- to confirm that every claim a comment makes is true, that any code shown in a comment actually works, and that everything a comment references still exists. Supports auditing an entire project or only the changes in a PR or stack of PRs. Triggers: "check the comments", "are these comments still accurate", "audit comments in this PR", "verify the docstrings".
    6 repo stars
  38. ▌
    Skill Creator · jwiegley bundle
    Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
    6 repo stars
  39. ▌
    At Dispatch V2 · jwiegley
    Convert PyTorch AT_DISPATCH macros to AT_DISPATCH_V2 format in ATen C++ code. Use when porting AT_DISPATCH_ALL_TYPES_AND*, AT_DISPATCH_FLOATING_TYPES*, or other dispatch macros to the new v2 API. For ATen kernel files, CUDA kernels, and native operator implementations.
    6 repo stars
  40. ▌
    Fix Transcript · jwiegley bundle
    Methodology for cleaning up a transcript file in place -- paragraphs, punctuation, capitalization -- without changing wording or meaning. Use when asked to clean, format, or fix a speech-to-text transcript, correcting technical vocabulary and spoken punctuation while preserving the speaker's words. The `/fix-transcript` command turns it on with the target file as its argument.
    6 repo stars
  41. ▌
    Add Uint Support · jwiegley
    Add unsigned integer (uint) type support to PyTorch operators by updating AT_DISPATCH macros. Use when adding support for uint16, uint32, uint64 types to operators, kernels, or when user mentions enabling unsigned types, barebones unsigned types, or uint support.
    6 repo stars
  42. ▌
    Abstraction Review · jwiegley bundle
    Architecture-alignment code review that detects when a change evades the codebase's existing abstractions instead of extending or correcting them: parallel implementations built beside existing ones, special-case dispatch on identity, semantics carried by naming conventions, runtime rediscovery of statically known facts, workarounds contorted around a guard, contracts shoehorned onto handy mechanisms, and mocks or tests that validate the workaround instead of the requirement. Judges architectural fit only, not correctness or implementation quality. Use when reviewing agent-authored or large-scale changes, or when asked whether a change routes around an abstraction, "eats the vegetables", or aligns with the existing architecture.
    6 repo stars
  43. ▌
    Denotational Design · jwiegley bundle
    This skill should be used when applying denotational design (Conal Elliott's method) to a project — designing a library, compiler, runtime, or system around a precise mathematical meaning. It guides a structured dialog to choose the principal mathematical object, its operations and theorems, a tower of representation objects with denotations between them, per-representation operation definitions solved from homomorphism (commuting) equations, machine-checked proofs in Lean/Rocq/Agda, empirical realization testing, and cross-language bisimulation (e.g., a Rust realization against its proof-assistant oracle). Triggers include "denotational design", "meaning function", "what does this type mean", "semantic domain", "type class morphism", "commuting theorems", "representation tower", "design this denotationally", or a request to give an existing codebase a formal semantic basis.
    6 repo stars
  44. ▌
    Eliminate Dead Code · jwiegley bundle
    Methodology for finding and removing dead code and stale documentation with evidence-based safety, using a mark / debate / act / verify workflow. Use when asked to remove dead code, unused symbols, unreachable branches, stale docs, unused imports, or dead feature flags -- gathering independent evidence before each removal and re-verifying build and tests after. The `/eliminate-dead-code` command turns it on.
    6 repo stars
  45. ▌
    Validated Code Review · jwiegley bundle
    Use when the user requests a thorough pre-PR code review of the current branch — e.g. "run a validated code review". "validated" is a key word
    6 repo stars
  46. ▌
    Swiftui Expert Skill · jwiegley bundle
    Write, review, or improve SwiftUI code following best practices for state management, view composition, performance, modern APIs, Swift concurrency, and iOS 26+ Liquid Glass adoption. Use when building new SwiftUI features, refactoring existing views, reviewing code quality, or adopting modern SwiftUI patterns.
    6 repo stars
  47. ▌
    Node Red · jwiegley bundle
    Edit, analyze, and create Node-RED flows by working with flows.json files, understanding node types, and applying Node-RED best practices. Use when the user mentions Node-RED, flows.json, flow development, or needs to modify Node-RED configurations.
    6 repo stars
  48. ▌
    Persian · jwiegley bundle
    Translate English language text into high quality, accurate Persian (Farsi) text using a team of specialist reviewers
    6 repo stars
  49. ▌
    Nixos · jwiegley
    Resolve NixOS issues using research and sequential thinking
    6 repo stars