ViktorsBaikers
- 104 skills
- 0 followers
- 5 hours ago last updated
- ▌ Devrites Debug Recovery 2 · viktorsbaikers bundleFix application test, build, CI, runtime, browser, or 500 failures from a reproduction. Use for broken behavior; not for DevRites install health.
- ▌ Devrites Frontend Craft 2 · viktorsbaikers bundleBuild accessible production UI and all states during $rite-build. Use for frontend or design-system implementation; not for polish or design exploration.
- ▌ Rite 2 · viktorsbaikers bundleUser-invoked DevRites menu and router; no args renders the menu, a verb invokes the matching `rite-<verb>` skill.
- ▌ Rite 3 · viktorsbaikers bundleUser-invoked DevRites menu and router; no args renders the menu, a verb invokes the matching `rite-<verb>` skill.
- ▌ Rite Vet 2 · viktorsbaikers bundleReview a defined engineering plan before code. Use for plan vetting or lock-in; not for implementation review or final readiness sealing.
- ▌
- ▌ Rite Ship 2 · viktorsbaikers bundleCommit, push, tag, archive, or close a sealed feature after /rite-seal GO. Use for repository mutation; not for GO/NO-GO readiness.
- ▌ Rite Spec 2 · viktorsbaikers bundleSpecify new, vague, or high-risk behavior before code. Use for features, auth, migrations, or public API changes; not for planning an approved spec.
- ▌ Rite Pov 2 · viktorsbaikersProject-grounded verdict for adopting, switching, rejecting, or revisiting a named external technology, library, platform, CVE, or pattern.
- ▌ Rite Vet 3 · viktorsbaikers bundleReview a defined engineering plan before code. Use for plan vetting or lock-in; not for implementation review or final readiness sealing.
- ▌ Rite Build 2 · viktorsbaikers bundleBuild the next approved vertical slice with evidence. HITL one-slice default; AFK may chain serially; opt-in `--parallel N` (2≤N≤10) for path-disjoint worktrees.
- ▌
- ▌
- ▌ Rite Seal 2 · viktorsbaikers bundleDecide GO/NO-GO for an active feature; $rite-ship owns commit, push, tag, and close.
- ▌ Rite Ship 3 · viktorsbaikers bundleCommit, push, tag, archive, or close a sealed feature after $rite-seal GO. Use for repository mutation; not for GO/NO-GO readiness.
- ▌ Rite Spec 3 · viktorsbaikers bundleSpecify new, vague, or high-risk behavior before code. Use for features, auth, migrations, or public API changes; not for planning an approved spec.
- ▌
- ▌ Rite Polish 2 · viktorsbaikers bundlePolish the active feature's code and any touched UI before review. Use for finish or normalization requests; not for repository-wide refactors.
- ▌ Rite Review 2 · viktorsbaikers bundleReview polished feature diff for correctness, readability, architecture, security, tests proving acceptance, Critical/Important findings, and quality dimensions before seal.
- ▌ Rite Temper 2 · viktorsbaikers bundleTemper 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 Adopt 2 · viktorsbaikers bundleAdopt an existing codebase into DevRites by reverse-engineering current behavior and establishing a baseline workspace.
- ▌ Rite Build 3 · viktorsbaikers bundleBuild the next approved vertical slice with evidence. HITL one-slice default; AFK may chain serially; opt-in `--parallel N` (2≤N≤10) for path-disjoint worktrees.
- ▌ Rite Frame 2 · viktorsbaikers bundleFrame 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 Learn 2 · viktorsbaikers bundleReview recurring cross-feature evidence and propose durable project guidance.
- ▌ Rite Prove 2 · viktorsbaikers bundleProve 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 Resolve 2 · viktorsbaikers bundleUser-invoked resume verb for answering, dropping, or batch-resolving open `questions.md` gates.
- ▌
- ▌ Rite Doctor 2 · viktorsbaikersCheck DevRites install, installed pack, or host configuration. Not for application bugs.
- ▌ Rite Polish 3 · viktorsbaikers bundlePolish the active feature's code and any touched UI before review. Use for finish or normalization requests; not for repository-wide refactors.
- ▌ Rite Review 3 · viktorsbaikers bundleReview polished feature diff for correctness, readability, architecture, security, tests proving acceptance, Critical/Important findings, and quality dimensions before seal.
- ▌
- ▌ Rite Temper 3 · viktorsbaikers bundleTemper 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 Converge 2 · viktorsbaikers bundleConverge 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 Watch Pr 2 · viktorsbaikersObserve one GitHub PR and CI state without mutating code, Git, threads, checks, or shared state. Safe for native host schedules and events.
- ▌
- ▌ Rite Clarify 2 · viktorsbaikers bundleAudit a completed spec for missing decisions before strategy or architecture. Use after $rite-spec when coverage is incomplete or stale; not for spec writing.
- ▌ Rite Dogfood 3 · viktorsbaikers bundleExplicit browser dogfood QA for the active feature or branch.
- ▌ Rite Explain 2 · viktorsbaikers bundleUser-invoked explainer that teaches one concept, diff, idea, or recent-work recap with an optional retrieval check-in.
- ▌
- ▌ Rite Resolve 3 · viktorsbaikers bundleUser-invoked resume verb for answering, dropping, or batch-resolving open `questions.md` gates.
- ▌ Rite Upgrade 2 · viktorsbaikers bundleAudit and reconcile an older released DevRites workspace. Proves a current-contract defect, then routes its phase owner while preserving completed work and history.
- ▌ Devrites Audit 2 · viktorsbaikersAudit one feature read-only for security, performance, or simplification risks. Use for one bounded audit axis; not for code changes.
- ▌ Rite Prototype 2 · viktorsbaikersUser-invoked throwaway prototype for one logic or UI design question; delete or absorb after the answer.
- ▌ Rite Converge 3 · viktorsbaikers bundleConverge 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 Watch Pr 3 · viktorsbaikersObserve one GitHub PR and CI state without mutating code, Git, threads, checks, or shared state. Safe for native host schedules and events.
- ▌
- ▌ Devrites Audit 3 · viktorsbaikersAudit one feature read-only for security, performance, or simplification risks. Use for one bounded audit axis; not for code changes.
- ▌ Devrites Doubt 2 · viktorsbaikersStress-test one consequential decision independently. Use for uncertainty around boundaries, data, auth, APIs, or migrations; not trivial choices.
- ▌ Rite Customize 2 · viktorsbaikers bundleCustomize a project instruction, skill, agent, plugin, or legacy import.
- ▌ Rite Prototype 3 · viktorsbaikers bundleUser-invoked throwaway prototype for one logic or UI design question; delete or absorb after the answer.
- ▌ Rite Autocomplete 2 · viktorsbaikers bundleRun 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 Pr Feedback 2 · viktorsbaikers bundleExplicit utility for resolving GitHub PR review feedback.
- ▌ Devrites UX Shape 2 · viktorsbaikers bundleShape UX/UI direction, states, and interactions before code. Use for screens, forms, dashboards, or settings; not for implementation or polish.
- ▌ Rite Autocomplete 3 · viktorsbaikers bundleRun the full DevRites lifecycle unattended; --ship continues to the final Git approval boundary. Use for one-shot autonomous work; not for a single phase.
- ▌
- ▌ Devrites Prose Craft 2 · viktorsbaikers bundleRewrite 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 API Interface 2 · viktorsbaikersShape stable API, type, module, or frontend/backend contracts before implementation. Use when a slice crosses a boundary; not for internal helpers.
- ▌ Devrites Browser Proof 2 · viktorsbaikers bundleObserve 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.
- ▌ Rite · viktorsbaikers bundleUser-invoked DevRites menu and router; no args renders the menu, a verb dispatches to the matching `rite-<verb>` skill.
- ▌ Rite Pov · viktorsbaikersProject-grounded verdict for adopting, switching, rejecting, or revisiting a named external technology, library, platform, CVE, or pattern.
- ▌ Rite Vet · viktorsbaikers bundleReview a defined engineering plan before code. Use for plan vetting or lock-in; not for implementation review or final readiness sealing.
- ▌
- ▌ Rite Seal · viktorsbaikers bundleDecide GO/NO-GO for an active feature; /rite-ship owns commit, push, tag, and close.
- ▌ Rite Ship · viktorsbaikers bundleCommit, push, tag, archive, or close a sealed feature after /rite-seal GO. Use for repository mutation; not for GO/NO-GO readiness.
- ▌ Rite Spec · viktorsbaikers bundleSpecify new, vague, or high-risk behavior before code. Use for features, auth, migrations, or public API changes; not for planning an approved spec.
- ▌ Rite Adopt · viktorsbaikers bundleAdopt an existing codebase into DevRites by reverse-engineering current behavior and establishing a baseline workspace.
- ▌ Rite Build · viktorsbaikers bundleBuild the next approved vertical slice with evidence. HITL one-slice default; AFK may chain serially; opt-in `--parallel N` (2≤N≤10) for path-disjoint worktrees.
- ▌ Rite Frame · viktorsbaikers bundleFrame 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 Learn · viktorsbaikersReview recurring cross-feature evidence and propose durable project guidance.
- ▌ Rite Prove · viktorsbaikers bundleProve 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 Doctor · viktorsbaikersCheck DevRites install, installed pack, or host configuration. Not for application bugs.
- ▌ Rite Polish · viktorsbaikers bundlePolish the active feature's code and any touched UI before review. Use for finish or normalization requests; not for repository-wide refactors.
- ▌ Rite Review · viktorsbaikers bundleReview polished feature diff for correctness, readability, architecture, security, tests proving acceptance, Critical/Important findings, and quality dimensions before seal.
- ▌
- ▌ Rite Temper · viktorsbaikers bundleTemper 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.
- ▌ Devrites Lib · viktorsbaikers bundleInternal shared DevRites helper library. Documents cross-cutting engine commands and references; not a user workflow. Do not invoke directly.
- ▌ Rite Clarify · viktorsbaikers bundleAudit a completed spec for missing decisions before strategy or architecture. Use after /rite-spec when coverage is incomplete or stale; not for spec writing.
- ▌
- ▌ Rite Explain · viktorsbaikers bundleUser-invoked explainer that teaches one concept, diff, idea, or recent-work recap with an optional retrieval check-in.
- ▌
- ▌ Rite Resolve · viktorsbaikers bundleUser-invoked resume verb for answering, dropping, or batch-resolving open `questions.md` gates.
- ▌ Rite Upgrade · viktorsbaikersAudit and reconcile an older released DevRites workspace. Proves a current-contract defect, then routes its phase owner while preserving completed work and history.
- ▌ Rite Converge · viktorsbaikers bundleConverge 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 Watch Pr · viktorsbaikersObserve one GitHub PR and CI state without mutating code, Git, threads, checks, or shared state. Safe for native host schedules and events.
- ▌
- ▌ Devrites Audit · viktorsbaikersAudit one feature read-only for security, performance, or simplification risks. Use for one bounded audit axis; not for code changes.
- ▌ Devrites Doubt · viktorsbaikersStress-test one consequential decision independently. Use for uncertainty around boundaries, data, auth, APIs, or migrations; not trivial choices.
- ▌ Rite Customize · viktorsbaikersCustomize a project instruction, skill, agent, plugin, or legacy import.
- ▌ Rite Prototype · viktorsbaikersUser-invoked throwaway prototype for one logic or UI design question; delete or absorb after the answer.
- ▌
- ▌ Devrites UX Shape · viktorsbaikers bundleShape UX/UI direction, states, and interactions before code. Use for screens, forms, dashboards, or settings; not for implementation or polish.
- ▌ Rite Autocomplete · viktorsbaikers bundleRun the full DevRites lifecycle unattended; --ship continues to the final Git approval boundary. Use for one-shot autonomous work; not for a single phase.
- ▌ Devrites Interview · viktorsbaikersInterview 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 · viktorsbaikers bundleRewrite 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 API Interface · viktorsbaikersShape stable API, type, module, or frontend/backend contracts before implementation. Use when a slice crosses a boundary; not for internal helpers.