ViktorsBaikers
UserStop your AI from shipping half-baked code. A disciplined senior-engineer workflow for Claude Code (spec, vet, build, prove, review, seal, ship) that keeps each feature's state on disk, catches spec drift mid-build, gates every phase on your project's principles, and refuses to claim "done" without proof.
Categories
Indexed Skills (37)
rite-dogfood
Explicit browser dogfood QA for the active feature or branch.
rite-explain
User-invoked explainer that teaches one concept, diff, idea, or recent-work recap with an optional retrieval check-in.
rite-learn
Review recurring cross-feature evidence and propose durable project guidance.
rite-pr-feedback
Explicit utility for resolving GitHub PR review feedback.
rite-prototype
User-invoked throwaway prototype for one logic or UI design question; delete or absorb after the answer.
rite-resolve
User-invoked resume verb for answering, dropping, or batch-resolving open `questions.md` gates.
rite
User-invoked DevRites menu and router; no args renders the menu, a verb dispatches to the matching `rite-<verb>` skill.
rite-upgrade
Audit and reconcile an older released DevRites workspace. Proves a current-contract defect, then routes its phase owner while preserving completed work and history.
rite-customize
Customize a project instruction, skill, agent, plugin, or legacy import.
devrites-lib
Internal shared DevRites helper library. Documents cross-cutting engine commands and references; not a user workflow. Do not invoke directly.
rite-autocomplete
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.
rite-build
Build the next approved vertical slice with evidence. HITL stops after one; explicit AFK may chain bounded green slices.
rite-converge
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.
rite-doctor
Check DevRites install, installed pack, or host configuration. Not for application bugs.
rite-frame
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.
rite-prove
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.
rite-review
Review polished feature diff for correctness, readability, architecture, security, tests proving acceptance, Critical/Important findings, and quality dimensions before seal.
rite-seal
Decide GO/NO-GO for an active feature; /rite-ship owns commit, push, tag, and close.
rite-spec
Specify new, vague, or high-risk behavior before code. Use for features, auth, migrations, or public API changes; not for planning an approved spec.
rite-temper
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.
rite-vet
Review a defined engineering plan before code. Use for plan vetting or lock-in; not for implementation review or final readiness sealing.
rite-clarify
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.
devrites-browser-proof
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.
devrites-doubt
Stress-test one consequential decision independently. Use for uncertainty around boundaries, data, auth, APIs, or migrations; not trivial choices.
devrites-interview
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.
devrites-prose-craft
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.
devrites-refresh-indexes
Refresh stale optional indexes. Use when structural lookup disagrees with live code or rite-doctor requests a synchronous reindex.
devrites-source-driven
Verify uncertain framework or library behavior in installed source or official docs. Use for unfamiliar APIs; not internal code.
devrites-frontend-craft
Build accessible production UI and all states during /rite-build. Use for frontend or design-system implementation; not for polish or design exploration.
devrites-api-interface
Shape stable API, type, module, or frontend/backend contracts before implementation. Use when a slice crosses a boundary; not for internal helpers.
devrites-debug-recovery
Fix application test, build, CI, runtime, browser, or 500 failures from a reproduction. Use for broken behavior; not for DevRites install health.
devrites-ux-shape
Shape UX/UI direction, states, and interactions before code. Use for screens, forms, dashboards, or settings; not for implementation or polish.
rite-polish
Polish the active feature's code and any touched UI before review. Use for finish or normalization requests; not for repository-wide refactors.
rite-ship
Commit, push, tag, archive, or close a sealed feature after /rite-seal GO. Use for repository mutation; not for GO/NO-GO readiness.
rite-adopt
Adopt an existing codebase into DevRites by reverse-engineering current behavior and establishing a baseline workspace.
rite-pov
Project-grounded verdict for adopting, switching, rejecting, or revisiting a named external technology, library, platform, CVE, or pattern.
devrites-audit
Audit one feature read-only for security, performance, or simplification risks. Use for one bounded audit axis; not for code changes.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.