Profile My skills Saved Collections Edit profile Submit a skill

← all publishers

jv-vogler

@jv-vogler source repo

5 published skills

  1. ▌
    Implement · jv-vogler
    Implement
    0
    installs
  2. ▌
    Local Review · jv-vogler
    Use when reviewing a pull request or branch locally without posting to GitHub — the user says "review PR #N", "review this PR locally", "check this branch's changes", "review my diff", asks whether a PR matches its ticket or does what the task asked, or wants review comments written to a file to read, filter, and copy before publishing anything.
    0
    installs
  3. ▌
    Humanize · jv-vogler
    Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, passive voice, negative parallelisms, and filler phrases.
    0
    installs
  4. ▌
    Write Description · jv-vogler
    Use when opening or updating a pull request, writing or fixing a PR description or body, running `gh pr create` or `gh pr edit`, when asked to "write the PR description", or when an existing PR body is stale, a wall of text, or narrates the diff file-by-file.
    0
    installs
  5. ▌
    Architecture · jv-vogler bundle
    The four-layer frontend architecture — infrastructure → domain → view → routes — with its dependency rules, file layout, naming conventions, and the recurring patterns that hold it together (serialization boundary, initial-data hook ladder, flow state machines, typed domain errors). Use whenever adding or changing a feature, page, API call, hook, form, or component in a React app laid out as src/infrastructure + src/domain + src/view + src/pages; whenever deciding which layer a piece of code belongs in; whenever reviewing a diff for layering violations; and whenever structuring a greenfield React frontend that wants a proven shape. Reach for it even when a request sounds purely local — "add a field to this form", "call this new endpoint", "show a spinner here" — because those are precisely the changes that quietly leak business rules into components.
    0
    installs