all publishers

existencialistaP

@existencialistap source repo

10 published skills

  1. ▌
    Skill Authoring · existencialistap
    Use when creating, editing, renaming, deleting, or adding a skill; when a skill stops firing or its description changes; when auditing skill health, routing, or token cost. Runs the catalog checks itself — never asks the user to run scripts.
    0 installs
  2. ▌
    Systematic Debugging · existencialistap bundle
    Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes. Use when asked what broke or why something throws, or when something stopped working and returns the wrong result after a change — even when the cause looks obvious from reading the pasted code, diff, or stack trace; name the cause, make the minimal fix, and say how to confirm it.
    0 installs
  3. ▌
    Verification Planning · existencialistap
    Use before implementing a feature, bug fix, refactor, or cross-system change to plan a credible project-specific verification path.
    0 installs
  4. ▌
    Test Driven Development · existencialistap bundle
    Use when implementing any feature or bugfix, before writing implementation code. Use when asked to add tests, fix a bug, or change behavior — even when the fix looks obvious from the code or the code is pasted inline; write the failing test first and change the function second, never the change alone.
    0 installs
  5. ▌
    Context · existencialistap bundle
    Use when starting work in a project before broad codebase exploration to check the project context map at ~/.local/share/ai-agent-config/contexts/<slug>.md, or when asked to create/update/refresh that map with this skill
    0 installs
  6. ▌
    Council · existencialistap
    Use when the user asks for a council, consensus, second opinion, multi-model review, or a high-stakes decision that benefits from independent judgments.
    0 installs
  7. ▌
    Ponytail · existencialistap
    Lazy senior dev mode: the smallest change that fully solves the task (YAGNI ladder, root-cause fixes, never cut validation or security), and a reply that names what was skipped. Use on any coding task (writing, fixing, refactoring, reviewing, choosing dependencies) and when the user says "ponytail", "be lazy", "simplest solution", "yagni", or complains about over-engineering or bloat. Use when the user asks whether a dependency is needed or the standard library already covers it. Use even when the ask looks like a one-line answer — the ladder and the skipped-work note still apply.
    0 installs
  8. ▌
    Step Back · existencialistap
    Momentum is a poor architect. Each patch on top of existing code feels like
    0 installs
  9. ▌
    Flow Guide · existencialistap bundle
    Use whenever anyone asks how to use the N0/worker/queue/Herdr flow, when to plan interactively versus with --direct, how to read or pick up from queue.md, or how to hand work to a worker — and load it before explaining or starting any step of that flow, even when the question sounds like a one-liner.
    0 installs
  10. ▌
    Orchestrate · existencialistap bundle
    Use when routing or supervising work - pick direct, task batch, Herdr, or handoff, then run the N0 supervision loop native-first
    0 installs