all publishers

ViktorsBaikers

@viktorsbaikers source repo

323 published skills · page 2 of 4

  1. ▌
    Rite Clarify 4 · viktorsbaikers bundle
    Audit a completed spec for missing decisions before strategy or architecture. Use after /rite-spec when coverage is incomplete or stale; not for spec writing.
    2 repo stars
  2. ▌
    Rite Dogfood 5 · viktorsbaikers
    Explicit browser dogfood QA for the active feature or branch.
    2 repo stars
  3. ▌
    Rite Explain 4 · viktorsbaikers bundle
    User-invoked explainer that teaches one concept, diff, idea, or recent-work recap with an optional retrieval check-in.
    2 repo stars
  4. ▌
    Rite Handoff 4 · viktorsbaikers bundle
    User-invoked handoff writer: sync chat-only context into `.devrites/` and write a fresh-agent handoff.
    2 repo stars
  5. ▌
    Rite Harness 2 · viktorsbaikers bundle
    Generate or maintain a project-local verify skill that launches, drives, and proves the real app with a user-POV feature map.
    2 repo stars
  6. ▌
    Rite Resolve 5 · viktorsbaikers bundle
    User-invoked resume verb for answering, dropping, or batch-resolving open `questions.md` gates.
    2 repo stars
  7. ▌
    Rite Upgrade 4 · viktorsbaikers
    Audit and reconcile an older released DevRites workspace. Proves a current-contract defect, then routes its phase owner while preserving completed work and history.
    2 repo stars
  8. ▌
    Rite Adopt 7 · viktorsbaikers bundle
    Adopt an existing codebase into DevRites by reverse-engineering current behavior and establishing a baseline workspace.
    2 repo stars
  9. ▌
    Rite Build 7 · viktorsbaikers bundle
    Build the next approved vertical slice with evidence. HITL one-slice default; AFK/autocomplete refill eligible isolated work under --parallel N, one global writer cap under Autocomplete.
    2 repo stars
  10. ▌
    Rite Frame 7 · viktorsbaikers bundle
    Frame an ad-hoc ask before coding, then audit the diff. Use for underspecified imperative asks, raw-diff self-audits, or `/rite-quick` setup. Not a lifecycle gate.
    2 repo stars
  11. ▌
    Rite Learn 7 · viktorsbaikers
    Review recurring cross-feature evidence and propose durable project guidance.
    2 repo stars
  12. ▌
    Rite Prove 7 · viktorsbaikers bundle
    Prove a completed feature with tests and the full test suite, build/typecheck/lint, end-to-end/browser evidence, screenshots, commands, and outputs for seal. Not for single-slice proof.
    2 repo stars
  13. ▌
    Rite Quick 7 · viktorsbaikers
    Express lane for a small reversible change: typo/copy/config, rate-limit constant, error message, local variable rename, feature flag, README link, one-file/function fix.
    2 repo stars
  14. ▌
    Rite Review 5 · viktorsbaikers bundle
    Review polished feature diff for correctness, readability, architecture, security, tests proving acceptance, Critical/Important findings, and quality dimensions before seal.
    2 repo stars
  15. ▌
    Rite Status 4 · viktorsbaikers
    User-invoked read-only active-feature report: phase, active slice, next action, evidence, open questions, drift, risks, and handoff readiness.
    2 repo stars
  16. ▌
    Rite Temper 5 · viktorsbaikers bundle
    Temper a readied spec before planning. Use when the user says "temper this", "strategy review", "pre-mortem the spec", or asks if we are over/under-building. Not for code review or final seal.
    2 repo stars
  17. ▌
    Rite Fast 5 · viktorsbaikers bundle
    Fast lane for mid-size work: one spec-and-plan step with clarifying questions, up to ten slices built without per-slice gates, one completeness check with gap fixes, review, polish, proof.
    2 repo stars
  18. ▌
    Rite Fast 6 · viktorsbaikers bundle
    Fast lane for mid-size work: one spec-and-plan step with clarifying questions, up to ten slices built without per-slice gates, one completeness check with gap fixes, review, polish, proof.
    2 repo stars
  19. ▌
    Rite Plan 7 · viktorsbaikers bundle
    Re-plan existing work when reality invalidates the plan: reslice a slice that is too big, repair drift, reorder dependencies, split boundaries, or unblock work. Not first-pass decomposition.
    2 repo stars
  20. ▌
    Rite Seal 7 · viktorsbaikers bundle
    Decide GO/NO-GO for an active feature; /rite-ship owns commit, push, tag, and close.
    2 repo stars
  21. ▌
    Rite Ship 7 · viktorsbaikers bundle
    Commit, push, tag, archive, or close a sealed feature after /rite-seal GO. Use for repository mutation; not for GO/NO-GO readiness.
    2 repo stars
  22. ▌
    Rite Spec 7 · viktorsbaikers bundle
    Specify new, vague, or high-risk behavior before code. Use for features, auth, migrations, or public API changes; not for planning an approved spec.
    2 repo stars
  23. ▌
    Rite Define 6 · viktorsbaikers bundle
    Define the first build plan from an approved spec: architecture, task slices, traceability, and state. Use when turning approved intent into its initial plan.
    2 repo stars
  24. ▌
    Rite Doctor 5 · viktorsbaikers
    Check DevRites install, installed pack, or host configuration. Not for application bugs.
    2 repo stars
  25. ▌
    Rite Polish 6 · viktorsbaikers bundle
    Polish the active feature's code and any touched UI before review. Use for finish or normalization requests; not for repository-wide refactors.
    2 repo stars
  26. ▌
    Rite Review 6 · viktorsbaikers bundle
    Review polished feature diff for correctness, readability, architecture, security, tests proving acceptance, Critical/Important findings, and quality dimensions before seal.
    2 repo stars
  27. ▌
    Rite Pov 7 · viktorsbaikers
    Project-grounded verdict for adopting, switching, rejecting, or revisiting a named external technology, library, platform, CVE, or pattern.
    2 repo stars
  28. ▌
    Rite Vet 7 · viktorsbaikers bundle
    Review a defined engineering plan before code. Use for plan vetting or lock-in; not for implementation review or final readiness sealing.
    2 repo stars
  29. ▌
    Rite Adopt 5 · viktorsbaikers bundle
    Adopt an existing codebase into DevRites by reverse-engineering current behavior and establishing a baseline workspace.
    2 repo stars
  30. ▌
    Rite Build 6 · viktorsbaikers bundle
    Build the next approved vertical slice with evidence. HITL one-slice default; AFK/autocomplete refill eligible isolated work under --parallel N, one global writer cap under Autocomplete.
    2 repo stars
  31. ▌
    Rite Frame 5 · viktorsbaikers bundle
    Frame an ad-hoc ask before coding, then audit the diff. Use for underspecified imperative asks, raw-diff self-audits, or `/rite-quick` setup. Not a lifecycle gate.
    2 repo stars
  32. ▌
    Rite Learn 5 · viktorsbaikers
    Review recurring cross-feature evidence and propose durable project guidance.
    2 repo stars
  33. ▌
    Rite Prove 5 · viktorsbaikers bundle
    Prove a completed feature with tests and the full test suite, build/typecheck/lint, end-to-end/browser evidence, screenshots, commands, and outputs for seal. Not for single-slice proof.
    2 repo stars
  34. ▌
    Rite Quick 6 · viktorsbaikers
    Express lane for a small reversible change: typo/copy/config, rate-limit constant, error message, local variable rename, feature flag, README link, one-file/function fix.
    2 repo stars
  35. ▌
    Rite Adopt 6 · viktorsbaikers bundle
    Adopt an existing codebase into DevRites by reverse-engineering current behavior and establishing a baseline workspace.
    2 repo stars
  36. ▌
    Rite Frame 6 · viktorsbaikers bundle
    Frame an ad-hoc ask before coding, then audit the diff. Use for underspecified imperative asks, raw-diff self-audits, or `/rite-quick` setup. Not a lifecycle gate.
    2 repo stars
  37. ▌
    Rite Learn 6 · viktorsbaikers
    Review recurring cross-feature evidence and propose durable project guidance.
    2 repo stars
  38. ▌
    Rite Prove 6 · viktorsbaikers bundle
    Prove a completed feature with tests and the full test suite, build/typecheck/lint, end-to-end/browser evidence, screenshots, commands, and outputs for seal. Not for single-slice proof.
    2 repo stars
  39. ▌
    Rite Define 5 · viktorsbaikers bundle
    Define the first build plan from an approved spec: architecture, task slices, traceability, and state. Use when turning approved intent into its initial plan.
    2 repo stars
  40. ▌
    Rite Doctor 4 · viktorsbaikers
    Check DevRites install, installed pack, or host configuration. Not for application bugs.
    2 repo stars
  41. ▌
    Rite Polish 5 · viktorsbaikers bundle
    Polish the active feature's code and any touched UI before review. Use for finish or normalization requests; not for repository-wide refactors.
    2 repo stars
  42. ▌
    Rite Plan 6 · viktorsbaikers bundle
    Re-plan existing work when reality invalidates the plan: reslice a slice that is too big, repair drift, reorder dependencies, split boundaries, or unblock work. Not first-pass decomposition.
    2 repo stars
  43. ▌
    Rite Seal 5 · viktorsbaikers bundle
    Decide GO/NO-GO for an active feature; /rite-ship owns commit, push, tag, and close.
    2 repo stars
  44. ▌
    Rite Ship 6 · viktorsbaikers bundle
    Commit, push, tag, archive, or close a sealed feature after /rite-seal GO. Use for repository mutation; not for GO/NO-GO readiness.
    2 repo stars
  45. ▌
    Rite Spec 6 · viktorsbaikers bundle
    Specify new, vague, or high-risk behavior before code. Use for features, auth, migrations, or public API changes; not for planning an approved spec.
    2 repo stars
  46. ▌
    Rite Fast 4 · viktorsbaikers bundle
    Fast lane for mid-size work: one spec-and-plan step with clarifying questions, up to ten slices built without per-slice gates, one completeness check with gap fixes, review, polish, proof.
    2 repo stars
  47. ▌
    Rite Seal 6 · viktorsbaikers bundle
    Decide GO/NO-GO for an active feature; /rite-ship owns commit, push, tag, and close.
    2 repo stars
  48. ▌
    Rite Adopt 4 · viktorsbaikers bundle
    Adopt an existing codebase into DevRites by reverse-engineering current behavior and establishing a baseline workspace.
    2 repo stars
  49. ▌
    Rite Build 5 · viktorsbaikers bundle
    Build the next approved vertical slice with evidence. HITL one-slice default; AFK/autocomplete refill eligible isolated work under --parallel N, one global writer cap under Autocomplete.
    2 repo stars
  50. ▌
    Rite Frame 4 · viktorsbaikers bundle
    Frame an ad-hoc ask before coding, then audit the diff. Use for underspecified imperative asks, raw-diff self-audits, or `/rite-quick` setup. Not a lifecycle gate.
    2 repo stars
  51. ▌
    Rite Learn 4 · viktorsbaikers
    Review recurring cross-feature evidence and propose durable project guidance.
    2 repo stars
  52. ▌
    Rite Prove 4 · viktorsbaikers bundle
    Prove a completed feature with tests and the full test suite, build/typecheck/lint, end-to-end/browser evidence, screenshots, commands, and outputs for seal. Not for single-slice proof.
    2 repo stars
  53. ▌
    Rite Quick 5 · viktorsbaikers
    Express lane for a small reversible change: typo/copy/config, rate-limit constant, error message, local variable rename, feature flag, README link, one-file/function fix.
    2 repo stars
  54. ▌
    Overhaul 5 · viktorsbaikers bundle
    Approval-gated overhaul of a project, PR, or branch: concurrent frontend and backend review, one approved repair plan, test-driven fixes, independent verification, evidence-backed scores.
    2 repo stars
  55. ▌
    Overhaul 6 · viktorsbaikers bundle
    Approval-gated overhaul of a project, PR, or branch: concurrent frontend and backend review, one approved repair plan, test-driven fixes, independent verification, evidence-backed scores.
    2 repo stars
  56. ▌
    Rite Pov 4 · viktorsbaikers
    Project-grounded verdict for adopting, switching, rejecting, or revisiting a named external technology, library, platform, CVE, or pattern.
    2 repo stars
  57. ▌
    Rite Vet 5 · viktorsbaikers bundle
    Review a defined engineering plan before code. Use for plan vetting or lock-in; not for implementation review or final readiness sealing.
    2 repo stars
  58. ▌
    Overhaul 3 · viktorsbaikers bundle
    Approval-gated overhaul of a project, PR, or branch: concurrent frontend and backend review, one approved repair plan, test-driven fixes, independent verification, evidence-backed scores.
    2 repo stars
  59. ▌
    Rite Pov 5 · viktorsbaikers
    Project-grounded verdict for adopting, switching, rejecting, or revisiting a named external technology, library, platform, CVE, or pattern.
    2 repo stars
  60. ▌
    Rite Vet 6 · viktorsbaikers bundle
    Review a defined engineering plan before code. Use for plan vetting or lock-in; not for implementation review or final readiness sealing.
    2 repo stars
  61. ▌
    Overhaul 4 · viktorsbaikers bundle
    Approval-gated overhaul of a project, PR, or branch: concurrent frontend and backend review, one approved repair plan, test-driven fixes, independent verification, evidence-backed scores.
    2 repo stars
  62. ▌
    Rite Pov 6 · viktorsbaikers
    Project-grounded verdict for adopting, switching, rejecting, or revisiting a named external technology, library, platform, CVE, or pattern.
    2 repo stars
  63. ▌
    Rite Fast 2 · viktorsbaikers bundle
    Fast lane for mid-size work: one spec-and-plan step with clarifying questions, up to ten slices built without per-slice gates, one completeness check with gap fixes, review, polish, proof.
    2 repo stars
  64. ▌
    Rite Plan 5 · viktorsbaikers bundle
    Re-plan existing work when reality invalidates the plan: reslice a slice that is too big, repair drift, reorder dependencies, split boundaries, or unblock work. Not first-pass decomposition.
    2 repo stars
  65. ▌
    Rite Seal 4 · viktorsbaikers bundle
    Decide GO/NO-GO for an active feature; /rite-ship owns commit, push, tag, and close.
    2 repo stars
  66. ▌
    Rite Ship 5 · viktorsbaikers bundle
    Commit, push, tag, archive, or close a sealed feature after /rite-seal GO. Use for repository mutation; not for GO/NO-GO readiness.
    2 repo stars
  67. ▌
    Rite Spec 5 · viktorsbaikers bundle
    Specify new, vague, or high-risk behavior before code. Use for features, auth, migrations, or public API changes; not for planning an approved spec.
    2 repo stars
  68. ▌
    Rite Fast 3 · viktorsbaikers bundle
    Fast lane for mid-size work: one spec-and-plan step with clarifying questions, up to ten slices built without per-slice gates, one completeness check with gap fixes, review, polish, proof.
    2 repo stars
  69. ▌
    Overhaul · viktorsbaikers bundle
    Approval-gated overhaul of a project, PR, or branch: concurrent frontend and backend review, one approved repair plan, test-driven fixes, independent verification, evidence-backed scores.
    2 repo stars
  70. ▌
    Rite Fast · viktorsbaikers bundle
    Fast lane for mid-size work: one spec-and-plan step with clarifying questions, up to ten slices built without per-slice gates, one completeness check with gap fixes, review, polish, proof.
    2 repo stars
  71. ▌
    Rite 5 · viktorsbaikers bundle
    User-invoked DevRites menu and router; no args renders the menu, a verb invokes the matching `rite-<verb>` skill.
    2 repo stars
  72. ▌
    Rite 6 · viktorsbaikers bundle
    User-invoked DevRites menu and router; no args renders the menu, a verb dispatches to the matching `rite-<verb>` skill.
    2 repo stars
  73. ▌
    Rite Harness · viktorsbaikers bundle
    Generate or maintain a project-local verify skill that launches, drives, and proves the real app with a user-POV feature map.
    2 repo stars
  74. ▌
    Rite 7 · viktorsbaikers bundle
    User-invoked DevRites menu and router; no args renders the menu, a verb invokes the matching `rite-<verb>` skill.
    2 repo stars
  75. ▌
    Overhaul 2 · viktorsbaikers bundle
    Approval-gated overhaul of a project, PR, or branch: concurrent frontend and backend review, one approved repair plan, test-driven fixes, independent verification, evidence-backed scores.
    2 repo stars
  76. ▌
    Rite Upgrade 3 · viktorsbaikers
    Audit and reconcile an older released DevRites workspace. Proves a current-contract defect, then routes its phase owner while preserving completed work and history.
    2 repo stars
  77. ▌
    Rite Converge 4 · viktorsbaikers bundle
    Converge intent and live code. Use when resuming a half-built feature, after `/rite-adopt` drift, or the user asks "what's left to build". Not for initial planning.
    2 repo stars
  78. ▌
    Rite Watch Pr 4 · viktorsbaikers
    Observe one GitHub PR and CI state without mutating code, Git, threads, checks, or shared state. Safe for native host schedules and events.
    2 repo stars
  79. ▌
    Rite Zoom Out 4 · viktorsbaikers
    Rite Zoom Out
    2 repo stars
  80. ▌
    Devrites Audit 4 · viktorsbaikers
    Audit one feature read-only for security, performance, or simplification risks. Use for one bounded audit axis; not for code changes.
    2 repo stars
  81. ▌
    Devrites Doubt 3 · viktorsbaikers
    Stress-test one consequential decision independently. Use for uncertainty around boundaries, data, auth, APIs, or migrations; not trivial choices.
    2 repo stars
  82. ▌
    Rite Customize 3 · viktorsbaikers
    Customize a project instruction, skill, agent, plugin, or legacy import.
    2 repo stars
  83. ▌
    Rite Prototype 4 · viktorsbaikers
    User-invoked throwaway prototype for one logic or UI design question; delete or absorb after the answer.
    2 repo stars
  84. ▌
    Rite Pr Feedback 3 · viktorsbaikers
    Explicit utility for resolving GitHub PR review feedback.
    2 repo stars
  85. ▌
    Devrites UX Shape 3 · viktorsbaikers bundle
    Shape UX/UI direction, states, and interactions before code. Use for screens, forms, dashboards, or settings; not for implementation or polish.
    2 repo stars
  86. ▌
    Rite Autocomplete 4 · viktorsbaikers bundle
    Run the full DevRites lifecycle unattended; --ship continues to the final Git approval boundary. Use for one-shot autonomous work; not for a single phase.
    2 repo stars
  87. ▌
    Devrites Interview 2 · viktorsbaikers
    Interview the user one question at a time to extract intent. Use when the user says "interview me", "I am not sure what I want", or the ask is underspecified. Not for casual clarification.
    2 repo stars
  88. ▌
    Rite Pressure Test 3 · viktorsbaikers
    Rite Pressure Test
    2 repo stars
  89. ▌
    Devrites Prose Craft 3 · viktorsbaikers bundle
    Rewrite prose to remove AI tells while preserving meaning and voice. Use for artifacts, replies, commits, or PR copy; not code comments or UI craft.
    2 repo stars
  90. ▌
    Devrites API Interface 3 · viktorsbaikers
    Shape stable API, type, module, or frontend/backend contracts before implementation. Use when a slice crosses a boundary; not for internal helpers.
    2 repo stars
  91. ▌
    Devrites Browser Proof 3 · viktorsbaikers bundle
    Observe and prove working UI behavior in a real browser with screenshots, interactions, network evidence, and Core Web Vitals. Use for browser proof or performance after the page works.
    2 repo stars
  92. ▌
    Devrites Source Driven 2 · viktorsbaikers
    Verify uncertain framework or library behavior in installed source or official docs. Use for unfamiliar APIs; not internal code.
    2 repo stars
  93. ▌
    Devrites Debug Recovery 3 · viktorsbaikers bundle
    Fix application test, build, CI, runtime, browser, or 500 failures from a reproduction. Use for broken behavior; not for DevRites install health.
    2 repo stars
  94. ▌
    Devrites Frontend Craft 3 · viktorsbaikers bundle
    Build accessible production UI and all states during /rite-build. Use for frontend or design-system implementation; not for polish or design exploration.
    2 repo stars
  95. ▌
    Rite 4 · viktorsbaikers bundle
    User-invoked DevRites menu and router; no args renders the menu, a verb dispatches to the matching `rite-<verb>` skill.
    2 repo stars
  96. ▌
    Rite Pov 3 · viktorsbaikers
    Project-grounded verdict for adopting, switching, rejecting, or revisiting a named external technology, library, platform, CVE, or pattern.
    2 repo stars
  97. ▌
    Rite Vet 4 · viktorsbaikers bundle
    Review a defined engineering plan before code. Use for plan vetting or lock-in; not for implementation review or final readiness sealing.
    2 repo stars
  98. ▌
    Rite Plan 4 · viktorsbaikers bundle
    Rite Plan
    2 repo stars
  99. ▌
    Rite Seal 3 · viktorsbaikers bundle
    Decide GO/NO-GO for an active feature; /rite-ship owns commit, push, tag, and close.
    2 repo stars
  100. ▌
    Rite Ship 4 · viktorsbaikers bundle
    Commit, push, tag, archive, or close a sealed feature after /rite-seal GO. Use for repository mutation; not for GO/NO-GO readiness.
    2 repo stars