← all publishers

jonfazzaro

@jonfazzaro source repo

Report this profile Claim this profile

• 10 skills
• 0 followers
• 1 day ago last updated

1. ▌
   Debuzz · jonfazzaro

   Translate Claude's previous response (or any pasted text) into plain, direct English by using the local Pi CLI through OpenRouter, with audience modes (colleague/manager/director) controlling how detailed versus high-level the result is. Use whenever the user invokes /debuzz, asks to "de-buzzfeed" a reply, says "say that in normal english" / "translate that to regular person english", asks for a manager- or exec-friendly version of a reply, or complains that a response sounds hypey, dramatic, listicle-like, or "like buzzfeed".
   0
   installs
2. ▌
   Nullables · jonfazzaro bundle

   Specifies behavior without mocks using Nullables. Use when writing specifications, especially specifying code with external I/O (HTTP, files, databases, clocks, random numbers), designing infrastructure wrappers or replacing mocking libraries.
   0
   installs
3. ▌
   Refactoring · jonfazzaro bundle

   Use when refactoring code, or when an in-scope readability or design problem obstructs requested work. Improve code form without changing behavior.
   0
   installs
4. ▌
   Micro Commits · jonfazzaro bundle

   Micro-commits process for committing early and often as code is written. Use whenever writing or changing code, especially alongside Continuous Specification or TDD — each green spec run is a commit opportunity.
   0
   installs
5. ▌
   Discovery Trees · jonfazzaro bundle

   Render a concise, color-coded text Discovery Tree whenever communicating a coding plan, specification, plan adjustment, newly discovered work, or completion of a planned task. Use it proactively during implementation to make the current state, dependencies, and viable next tasks easy for a human to assess and choose between. Do not use it for a simple isolated answer or task with no meaningful plan.
   0
   installs
6. ▌
   Ensemble Review · jonfazzaro bundle

   Use when the user asks for an ensemble, panel, cross-model, or independent multi-model review of a document, plan, proposal, runbook, or source file.
   0
   installs
7. ▌
   Ensemble Working · jonfazzaro bundle

   Facilitate a human-and-agent ensemble through one collaborative AI pattern while working on a shared task. Use when a team wants to think together, compare approaches, or maintain shared ownership instead of having one person prompt alone.
   0
   installs
8. ▌
   Describe Structure · jonfazzaro

   Required whenever adding, editing, or restructuring tests or specifications, including *.test.* and *.spec.* files. Use for unit-test coverage, regression tests, TDD, mutation testing, bug fixes, and refactoring—even when the user does not name test structure. Invoke before writing test code. In suites that already use describe, structure every new or changed test as component → when [action] → given [condition] → outcome-focused it; preserve flat suites without describe.
   0
   installs
9. ▌
   Continuous Specification · jonfazzaro bundle

   Use whenever a production-code change alters executable behavior—features, fixes, integrations, migrations, scripts, performance work, or behavior-changing refactors. Establish behavior through small executable expectations and green checkpoints.
   0
   installs
10. ▌
    Targeted Mutation Testing · jonfazzaro

    Use when a changed production class or component has branching, lifecycle or asynchronous behavior, guards, error recovery, authentication, serialization, or an external-integration seam and needs file-scoped mutation testing before completion.
    0
    installs