MCPInstall

blockmatic

91 skills · 38.9K installs · 2 repositories

  1. 1

    Basilic /w- playbooks packed so install lands at .agents/skills/workflow/w-plan and the rest.

  2. 2

    Review a plan's Goals, Assumptions, Tasks, Risks, and References.

  3. 3

    Audit UI against repository a11y docs and tests; do not invent a WCAG level.

  4. 4

    Refresh API docs from the owning schema source; never edit generated OpenAPI by hand.

  5. 5

    Add API tests that exercise public HTTP behavior against existing harnesses.

  6. 6

    Plan an implementation structure; durable decisions belong in ADRs and architecture docs.

  7. 7

    Implement an agreed task incrementally and verify the result.

  8. 8

    Resolve consequential missing requirements from inspected context.

    647
  9. 9

    Fetch CodeRabbit review comments, apply authorized fixes, and stop at local verification.

  10. 10

    Process reviewer feedback, apply required fixes, and draft replies without unsolicited commits.

    647
  11. 11

    Review and commit the task's intended changes using repository conventions.

  12. 12

    Explore a codebase with parallel agents, then hand off findings.

  13. 13

    Diagnose a failure from evidence and verify the original scenario after a fix.

  14. 14

    Reproduce and resolve an authorized browser issue using runtime evidence.

  15. 15

    Remove AI-generated slop introduced on this branch relative to main.

    647
  16. 16

    Produce a Mermaid diagram of the requested code, architecture, or data flow.

  17. 17

    Document the current code or feature in the owning docs layer.

  18. 18

    Add error handling that matches existing repo error and logging packages.

  19. 19

    Fix reported issues, validate, then commit and push.

  20. 20

    Build a Next.js form using the app's existing mutation path, not a second stack.

  21. 21

    Retrieve GitHub Actions logs with gh, analyze failures, and fix CI errors locally.

  22. 22

    Resolve common Git problems and conflicts with inspected commands.

  23. 23

    Run project linters, apply the smallest fixes, and re-run until the suite is clean.

  24. 24

    Get a new developer from clone to a running local app.

    647
  25. 25

    Measure bottlenecks with repository tools, then recommend or apply evidenced optimizations.

    647
  26. 26

    Write an ordered plan without changing implementation.

  27. 27

    Create or update a reviewable pull request for the intended branch.

  28. 28

    Validate and push the intended branch while preserving unrelated work.

    647
  29. 29

    Refactor selected code while preserving behavior, then verify.

  30. 30

    Advisory review of release impact, changelog, and template contracts.

  31. 31

    After finishing work, answer what you would do better next time.

    647
  32. 32

    Review a change for evidenced defects and risks without editing it.

  33. 33

    Diff the codebase against GitHub issues and matching docs; do not invent a backlog.

  34. 34

    Review the change or tree against repository security docs and existing checks.

  35. 35

    Install shadcn/w-ui primitives in the shared UI package using monorepo import paths.

  36. 36

    Implement the requested change, validate, commit, push, and create its PR.

  37. 37

    Implement a requested increment with red-green-refactor.

  38. 38

    Run the repository test scripts and fix failures until they pass.

  39. 39

    Build or reshape UI with purpose, existing tokens, accessible interactions, and bounded rendered verification.

  40. 40

    Add unit tests for the current change using the repo test skill and colocated files.

  41. 41

    Draft a Next.js and shadcn v0.dev prompt from the current file and wait for OPEN, EDIT, or CANCEL.

  42. 42

    Retrieve Vercel build logs, analyze failures, and fix the local build.

  43. 43

    Fix failing or requested local checks without publishing.

    647
  44. 44

    Relentless design-tree interview until the frontier is empty.

    543
  45. 45

    Chart multi-session fog as a plan-file map of decision tickets.

  46. 46
  47. 47
    243
  48. 48
    242
  49. 49
  50. 50