Profile My skills Saved Collections Edit profile Submit a skill

← all publishers

bangle-io

@bangle-io source repo

5 published skills

  1. ▌
    Wordgard · bangle-io bundle
    Write idiomatic Wordgard editor code (schema elements, extensions, commands, decorations, markdown specs) for the editor-w stack. Use whenever working on wordgard, @bangle.io/wordgard-utils, @bangle.io/wordgard-markdown, or packages/core/editor-w, or when reviewing such code.
    0
    installs
  2. ▌
    Bangle Desktop Release · bangle-io bundle
    Build, test, package, and release the Bangle.io Electron desktop app. Use when working on desktop nightlies, stable desktop releases, Electron smoke tests, updater artifacts, or macOS signing/notarization.
    0
    installs
  3. ▌
    Bangle Project Operator · bangle-io bundle
    Keep the Bangle 2 GitHub Project aligned with the bangle-io repository. Use for adding, finding, triaging, prioritizing, scheduling, editing, reconciling, or completing project items; assigning backlog, icebox, sprint, urgency, size, or product-area fields; relating plans, issues, pull requests, and code; auditing whether the board matches repository reality; or requests such as "add a task", "update the board", "triage this", "what should we work on", and "sync the project with the repo".
    0
    installs
  4. ▌
    Bangle Followup Operator · bangle-io bundle
    Operate recurring Bangle.io agent follow-ups after a thread has already started. Use when the user asks to continue, check status, decide what is next, push, create or update a PR, poll CI, rebase, merge, release, run Playwright/manual UX checks, spawn or aggregate code-review subagents, run thermonuclear review, address review findings, make a plan, add a project task, or asks "we good?", "pushed?", "PR?", "did you test?", "what should I test?", or similar follow-up prompts in the Bangle repo.
    0
    installs
  5. ▌
    Thermonuclear Code Quality Review · bangle-io bundle
    Perform an unusually strict code-quality audit focused on structural simplification, maintainability, abstraction quality, file growth, branching complexity, type boundaries, architectural ownership, and test quality. Use for thermonuclear reviews, deep maintainability audits, harsh code-quality reviews, or reviews that should seek ambitious behavior-preserving restructuring rather than local cleanup.
    0
    installs