← all publishers

blauwtje

@blauwtje source repo

Report this profile Claim this profile

• 19 skills
• 0 followers
• 5 hours ago last updated

1. ▌
   Implementing Test First · blauwtje

   Use when a change to behavior will be written test-first: a bug with a reproduction, a rule with named inputs and outputs, or a request that says test-driven, red-green, or write the test first. Fires on the thought that the tests come after the code. Not for a change with no observable behavior, an unproven failure, which debug owns, or a whole plan, which implementing runs.
   0 installs
2. ▌
   Research · blauwtje bundle

   Use when a code decision hinges on how a pinned external library, framework, API or service behaves and a wrong recalled answer would still compile or type-check yet fail at runtime or at the provider boundary. Not for questions the repository's own code answers, a version bump alone, or a concept explanation.
   0 installs
3. ▌
   Settings · blauwtje bundle

   Use when the user asks to see or change an exo setting, for every project, for one repository or for this machine only, such as where shaping stores specs (docs/specs files, GitHub issues or both). Not for the harness's own settings.json, permissions or hooks, and not for the savings switch, which savings owns.
   0 installs
4. ▌
   Designing · blauwtje bundle

   Use when a page, component, or visual axis changes: typography, color, spacing, motion, copy. Fires on a new visual surface, a redesign, or a surface called empty, boring, or generic. When a new visual surface does not name its displayed data, settings, or behavior, shaping decides those first; designing follows for presentation. Not for typo-only copy fixes or behavior with no visual effect.
   0 installs
5. ▌
   Merge Prs · blauwtje

   Review and merge the open pull requests of this repository one at a time behind hard gates read from the GitHub API. Use when the user asks to merge open or listed PRs. Not for reviewing code, for a PR the user did not name or list, or for anything that deletes a branch.
   0 installs
6. ▌
   Using Exo · blauwtje

   Use when a session starts, after a clear and after a compaction, before any other action, to know how the exo skills are named, found and ordered. Not for a turn that already holds its rules in context.
   0 installs
7. ▌
   Prototyping · blauwtje

   Use when a decision about logic, state or data flow needs running code before it is made: a state model, an algorithm choice, or an untried integration. Fires on words like prototype, throwaway or proof of concept, or on the thought of building the real thing to find out. Not for a decided change, which implementing-batch builds, or a look, which designing owns.
   0 installs
8. ▌
   Skills Tool · blauwtje bundle

   Use when creating, editing or sizing a skill or agent, before the edit and before it is called done. Not for CLAUDE.md, a rule or an output style.
   0 installs
9. ▌
   Implementing · blauwtje bundle

   Use when a session opens on a plan file to run, after a clear, or when the user says to run or resume a plan. Not for authoring or repairing a plan, a decided change with no plan file, or a task that must build in this session, which `implementing-batch` owns.
   0 installs
10. ▌
    Implementing Batch · blauwtje bundle

    Use when a decided change builds in this session and inspection shows it modifies more than two source/test/config files, adds a dependency, changes a public signature, crosses a persisted format or security boundary, or reaches an uninspected file; also a whole plan run here. Not for a change reaching at most two files, a version bump, a git-only operation, or an unproven failure.
    0 installs
11. ▌
    Debug · blauwtje

    Use when existing behavior is reported wrong as a bug, error, crash, regression, broken output, or slowdown, and evidence does not yet identify one causal line or boundary plus a mechanism that predicts the symptom. Not when a diagnostic names the exact file, line, and symbol and matches the source; when the user-stated cause checks out; or for a feature complaint.
    0 installs
12. ▌
    Setup · blauwtje bundle

    Use when the user runs /exo:setup or asks to set up, personalize or configure exo as a whole, walking through every setting at once. Not for one setting, which settings owns, and not for the savings figures, which savings reports.
    0 installs
13. ▌
    Deepen · blauwtje

    Use when the user asks where or how to improve architecture without naming one exact change: tech debt, coupling, shallow modules, refactor candidates across a codebase or subsystem. In a read-only planning mode it owns the turn and writes the plan for its findings. Not for a single named refactor or rename, failing existing behavior, or a security or dependency audit.
    0 installs
14. ▌
    Memory · blauwtje bundle

    Record what this repository taught exo: book a correction the user just made, propose a claim two separate sessions have booked, write it once the user approves, and drop a line whose files are gone. Use when the user invokes it. Not for a plan another session runs, and not for a build or test command, which debug appends to AGENTS.md or CLAUDE.md.
    0 installs
15. ▌
    Handoff · blauwtje

    Save an unfinished session's live state to a file a fresh session reads after a clear: goal, current state, decisions and who made them, what is proven, the single next step. Use when the user invokes it. Not for a plan another executor runs, which planning owns, and not for finished work, which the commit and the pull request record.
    0 installs
16. ▌
    Issuing · blauwtje bundle

    Write and create GitHub issues for this repository as specs, with the labels, type, relations, milestone and project fields the repository actually defines. Use when the user asks to file, open, write or split issues. Not for closing or editing an existing issue, for a plan, or for issues in a repository the working directory does not point at.
    0 installs
17. ▌
    Savings · blauwtje bundle

    Use when the user asks what exo cost, what exo or the read guard has saved or refused, for the savings counter, report, panel or totals, asks to switch exo savings, the ladder or the read guard off or on, or to change the guard's big-file limit. Not for the size of one diff, which git shows; not for the live figure, which the status line segment prints.
    0 installs
18. ▌
    Shaping · blauwtje bundle

    Use when a request, or new wishes for an existing brief, issue or plan, leaves a product decision open: what counts as done, data, architecture, or a trade-off. When a new visual surface does not name its displayed data, settings, or behavior, shaping decides those first; designing follows for presentation. Not for a clear goal, a named change, a failure, visual-only work, or a two-file edit.
    0 installs
19. ▌
    Planning · blauwtje bundle

    Use when a read-only planning mode is active, the user asks for a plan, another session will run the work, or inspection finds two or more edit-order dependencies. Not for same-session work with at most one dependency edge; one-file, typo, rename, or version-bump edits; git-only operations; an unproven failure outside a planning turn; or an architecture audit, which deepen owns.
    0 installs