Profile My skills Saved Collections Edit profile Submit a skill

← all publishers

sbnet

@sbnet source repo

14 published skills

  1. ▌
    Spec Interview 2 · sbnet
    Interview the user about a feature they want to build, then write a complete spec to specs/SPEC-<ref>.md (with an index). Use when the user says "I want to build X" or asks for a spec/interview. Once the spec is validated, chain into /gh-issue.
    0
    installs
  2. ▌
    Git · sbnet
    Git commit guidelines using conventional commits. Use when creating commits, writing commit messages.
    0
    installs
  3. ▌
    Honesty · sbnet
    Behavioral guideline for providing brutally honest feedback. Use always - this skill defines core interaction expectations for code review and technical discussions.
    0
    installs
  4. ▌
    Geo · sbnet
    Audit and improve visibility in generative engines (AI answers, LLM-powered search): GEO, complementary to classic SEO. Use when the user asks about GEO, AI search visibility, llms.txt, or being cited by AI assistants.
    0
    installs
  5. ▌
    Init · sbnet
    Set up flux in the current project: config, gate script for CI, workflows, CLAUDE.md contract, specs index, GitHub label. Use when the user asks to initialize/install flux in a project.
    0
    installs
  6. ▌
    Gh Pr · sbnet
    Write and open the pull request for the current branch via the gh CLI, linked to its issue and spec. Use when the user asks to create/open/write a PR.
    0
    installs
  7. ▌
    Review · sbnet
    Review the current branch's PR and post the findings as comments on it. Use when the user asks to run/launch/trigger a review, or the feature/gh-pr flow reaches the point where CI is green and a review is worth requesting before merge.
    0
    installs
  8. ▌
    Feature · sbnet
    The single entry point to build anything. Calibrates the process to the change (trivial, standard or full), then drives it end to end (spec, issue, implementation, gates, PR, CI, review triage). Only merging stays human. Use when the user asks to implement, fix or build something.
    0
    installs
  9. ▌
    Documentation · sbnet
    In-code documentation, folder READMEs, and code comments. Use when writing README.md files, JSDoc comments, or explaining code organization.
    0
    installs
  10. ▌
    Writing Voice · sbnet
    Voice and tone rules for all written content. Use when writing prose that should sound human and be suitable for reading aloud.
    0
    installs
  11. ▌
    Gh Issue · sbnet
    Write and create a well-structured GitHub issue via the gh CLI, optionally from a SPEC-<ref>.md spec. Use when the user asks to create a GitHub issue/ticket.
    0
    installs
  12. ▌
    Spec Interview · sbnet
    Interview the user about a feature they want to build, then write a complete spec to specs/SPEC-<ref>.md (with an index). Use when the user says "I want to build X" or asks for a spec/interview. Once the spec is validated, chain into /gh-issue.
    0
    installs
  13. ▌
    UI Review · sbnet
    Heuristic UI/UX review of the running app: screenshots at multiple breakpoints, state coverage, consistency, form ergonomics. Use when the user asks for a UI review, UX feedback, or a design pass on pages or flows.
    0
    installs
  14. ▌
    Gh Address Comments · sbnet
    Triage and address review comments on the current branch's PR: the human picks what to fix, the agent fixes it autonomously. Use when the user asks to handle/address review comments on a PR.
    0
    installs