Profile My skills Saved Collections Edit profile Submit a skill

← all publishers

codywilliamson

@codywilliamson source repo

8 published skills

  1. ▌
    Pr · codywilliamson
    Use when creating a pull request, preparing a branch for review, or when the user says "pr" or "pull request"
    0
    installs
  2. ▌
    Debug · codywilliamson
    Use when encountering bugs, test failures, unexpected behavior, or error messages — before attempting any fix
    0
    installs
  3. ▌
    Deploy · codywilliamson
    Use when deploying code to production or staging, before pushing changes, or when the user says "deploy" or "ship it"
    0
    installs
  4. ▌
    Design System · codywilliamson bundle
    Use whenever building UI, designing components, creating frontends, prototyping interfaces, or when the user mentions "design system", "make it look like", "style it like", or any visual design task. Also trigger when creating new projects with a frontend, building landing pages, dashboards, or any component that needs consistent visual styling. This skill ensures every UI Claude builds has a cohesive, professional design language instead of generic defaults.
    0
    installs
  5. ▌
    Prompt Refine · codywilliamson
    Audit the prompt refinement hook log — review trigger history, analyze false positives/negatives, and tune heuristics
    0
    installs
  6. ▌
    Writing Pr Comments · codywilliamson
    Write review comments on a pull request or diff. Use this whenever the user asks you to review a PR and leave comments, write review feedback, comment on a diff, or phrase a piece of code review feedback they're unsure how to word. Also use it when reviewing code as part of a larger workflow where the output is comments left on specific lines rather than a written report.
    0
    installs
  7. ▌
    Writing Technical Docs · codywilliamson
    Write or revise technical documentation — READMEs, architecture docs, runbooks, API docs, onboarding guides, design docs, explainers. Use this whenever the user asks you to document something, write a README, explain how a system works in written form, write a runbook or onboarding guide, or clean up docs that already exist. Also use it when they ask you to "write this up" for other engineers, or complain that a doc reads like a reference dump when they wanted a walkthrough.
    0
    installs
  8. ▌
    Writing Pr Descriptions · codywilliamson
    Write a pull request description or title. Use this whenever the user asks you to write, draft, or improve a PR description, MR description, or PR title, or asks you to "write up this change" for review, or hands you a diff or branch and asks what to put in the PR body. Also use it when generating a PR description as part of a larger workflow such as opening a PR with gh.
    0
    installs