ViktorsBaikers
- 323 skills
- 0 followers
- 2 repo stars
- 4 days ago last updated
- ▌ Rite Clarify 4 · 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 4 · viktorsbaikers bundleUser-invoked explainer that teaches one concept, diff, idea, or recent-work recap with an optional retrieval check-in.
- ▌ Rite Handoff 4 · viktorsbaikers bundleUser-invoked handoff writer: sync chat-only context into `.devrites/` and write a fresh-agent handoff.
- ▌ Rite Harness 2 · viktorsbaikers bundleGenerate or maintain a project-local verify skill that launches, drives, and proves the real app with a user-POV feature map.
- ▌ Rite Resolve 5 · viktorsbaikers bundleUser-invoked resume verb for answering, dropping, or batch-resolving open `questions.md` gates.
- ▌ Rite Upgrade 4 · 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 Adopt 7 · viktorsbaikers bundleAdopt an existing codebase into DevRites by reverse-engineering current behavior and establishing a baseline workspace.
- ▌ Rite Build 7 · viktorsbaikers bundleBuild 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.
- ▌ Rite Frame 7 · 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 7 · viktorsbaikersReview recurring cross-feature evidence and propose durable project guidance.
- ▌ Rite Prove 7 · 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 Quick 7 · viktorsbaikersExpress 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.
- ▌ Rite Review 5 · viktorsbaikers bundleReview polished feature diff for correctness, readability, architecture, security, tests proving acceptance, Critical/Important findings, and quality dimensions before seal.
- ▌ Rite Status 4 · viktorsbaikersUser-invoked read-only active-feature report: phase, active slice, next action, evidence, open questions, drift, risks, and handoff readiness.
- ▌ Rite Temper 5 · 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 Fast 5 · viktorsbaikers bundleFast 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.
- ▌ Rite Fast 6 · viktorsbaikers bundleFast 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.
- ▌ Rite Plan 7 · viktorsbaikers bundleRe-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.
- ▌ Rite Seal 7 · viktorsbaikers bundleDecide GO/NO-GO for an active feature; /rite-ship owns commit, push, tag, and close.
- ▌ Rite Ship 7 · 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 7 · 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 Define 6 · viktorsbaikers bundleDefine the first build plan from an approved spec: architecture, task slices, traceability, and state. Use when turning approved intent into its initial plan.
- ▌ Rite Doctor 5 · viktorsbaikersCheck DevRites install, installed pack, or host configuration. Not for application bugs.
- ▌ Rite Polish 6 · 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 6 · viktorsbaikers bundleReview polished feature diff for correctness, readability, architecture, security, tests proving acceptance, Critical/Important findings, and quality dimensions before seal.
- ▌ Rite Pov 7 · viktorsbaikersProject-grounded verdict for adopting, switching, rejecting, or revisiting a named external technology, library, platform, CVE, or pattern.
- ▌ Rite Vet 7 · viktorsbaikers bundleReview a defined engineering plan before code. Use for plan vetting or lock-in; not for implementation review or final readiness sealing.
- ▌ Rite Adopt 5 · viktorsbaikers bundleAdopt an existing codebase into DevRites by reverse-engineering current behavior and establishing a baseline workspace.
- ▌ Rite Build 6 · viktorsbaikers bundleBuild 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.
- ▌ Rite Frame 5 · 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 5 · viktorsbaikersReview recurring cross-feature evidence and propose durable project guidance.
- ▌ Rite Prove 5 · 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 Quick 6 · viktorsbaikersExpress 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.
- ▌ Rite Adopt 6 · viktorsbaikers bundleAdopt an existing codebase into DevRites by reverse-engineering current behavior and establishing a baseline workspace.
- ▌ Rite Frame 6 · 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 6 · viktorsbaikersReview recurring cross-feature evidence and propose durable project guidance.
- ▌ Rite Prove 6 · 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 Define 5 · viktorsbaikers bundleDefine the first build plan from an approved spec: architecture, task slices, traceability, and state. Use when turning approved intent into its initial plan.
- ▌ Rite Doctor 4 · viktorsbaikersCheck DevRites install, installed pack, or host configuration. Not for application bugs.
- ▌ Rite Polish 5 · 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 Plan 6 · viktorsbaikers bundleRe-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.
- ▌ Rite Seal 5 · viktorsbaikers bundleDecide GO/NO-GO for an active feature; /rite-ship owns commit, push, tag, and close.
- ▌ Rite Ship 6 · 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 6 · 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 Fast 4 · viktorsbaikers bundleFast 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.
- ▌ Rite Seal 6 · viktorsbaikers bundleDecide GO/NO-GO for an active feature; /rite-ship owns commit, push, tag, and close.
- ▌ Rite Adopt 4 · viktorsbaikers bundleAdopt an existing codebase into DevRites by reverse-engineering current behavior and establishing a baseline workspace.
- ▌ Rite Build 5 · viktorsbaikers bundleBuild 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.
- ▌ Rite Frame 4 · 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 4 · viktorsbaikersReview recurring cross-feature evidence and propose durable project guidance.
- ▌ Rite Prove 4 · 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 Quick 5 · viktorsbaikersExpress 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.
- ▌ Overhaul 5 · viktorsbaikers bundleApproval-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.
- ▌ Overhaul 6 · viktorsbaikers bundleApproval-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.
- ▌ Rite Pov 4 · viktorsbaikersProject-grounded verdict for adopting, switching, rejecting, or revisiting a named external technology, library, platform, CVE, or pattern.
- ▌ Rite Vet 5 · viktorsbaikers bundleReview a defined engineering plan before code. Use for plan vetting or lock-in; not for implementation review or final readiness sealing.
- ▌ Overhaul 3 · viktorsbaikers bundleApproval-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.
- ▌ Rite Pov 5 · viktorsbaikersProject-grounded verdict for adopting, switching, rejecting, or revisiting a named external technology, library, platform, CVE, or pattern.
- ▌ Rite Vet 6 · viktorsbaikers bundleReview a defined engineering plan before code. Use for plan vetting or lock-in; not for implementation review or final readiness sealing.
- ▌ Overhaul 4 · viktorsbaikers bundleApproval-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.
- ▌ Rite Pov 6 · viktorsbaikersProject-grounded verdict for adopting, switching, rejecting, or revisiting a named external technology, library, platform, CVE, or pattern.
- ▌ Rite Fast 2 · viktorsbaikers bundleFast 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.
- ▌ Rite Plan 5 · viktorsbaikers bundleRe-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.
- ▌ Rite Seal 4 · viktorsbaikers bundleDecide GO/NO-GO for an active feature; /rite-ship owns commit, push, tag, and close.
- ▌ Rite Ship 5 · 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 5 · 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 Fast 3 · viktorsbaikers bundleFast 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.
- ▌ Overhaul · viktorsbaikers bundleApproval-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.
- ▌ Rite Fast · viktorsbaikers bundleFast 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.
- ▌ Rite 5 · viktorsbaikers bundleUser-invoked DevRites menu and router; no args renders the menu, a verb invokes the matching `rite-<verb>` skill.
- ▌ Rite 6 · viktorsbaikers bundleUser-invoked DevRites menu and router; no args renders the menu, a verb dispatches to the matching `rite-<verb>` skill.
- ▌ Rite Harness · viktorsbaikers bundleGenerate or maintain a project-local verify skill that launches, drives, and proves the real app with a user-POV feature map.
- ▌ Rite 7 · viktorsbaikers bundleUser-invoked DevRites menu and router; no args renders the menu, a verb invokes the matching `rite-<verb>` skill.
- ▌ Overhaul 2 · viktorsbaikers bundleApproval-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.
- ▌ Rite Upgrade 3 · 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 4 · 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 4 · 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 4 · viktorsbaikersAudit one feature read-only for security, performance, or simplification risks. Use for one bounded audit axis; not for code changes.
- ▌ Devrites Doubt 3 · viktorsbaikersStress-test one consequential decision independently. Use for uncertainty around boundaries, data, auth, APIs, or migrations; not trivial choices.
- ▌ Rite Customize 3 · viktorsbaikersCustomize a project instruction, skill, agent, plugin, or legacy import.
- ▌ Rite Prototype 4 · viktorsbaikersUser-invoked throwaway prototype for one logic or UI design question; delete or absorb after the answer.
- ▌
- ▌ Devrites UX Shape 3 · viktorsbaikers bundleShape UX/UI direction, states, and interactions before code. Use for screens, forms, dashboards, or settings; not for implementation or polish.
- ▌ Rite Autocomplete 4 · 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 2 · 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 3 · 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 3 · 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 3 · 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.
- ▌ Devrites Source Driven 2 · viktorsbaikersVerify uncertain framework or library behavior in installed source or official docs. Use for unfamiliar APIs; not internal code.
- ▌ Devrites Debug Recovery 3 · 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 3 · 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 4 · viktorsbaikers bundleUser-invoked DevRites menu and router; no args renders the menu, a verb dispatches to the matching `rite-<verb>` skill.
- ▌ Rite Pov 3 · viktorsbaikersProject-grounded verdict for adopting, switching, rejecting, or revisiting a named external technology, library, platform, CVE, or pattern.
- ▌ Rite Vet 4 · 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 3 · viktorsbaikers bundleDecide GO/NO-GO for an active feature; /rite-ship owns commit, push, tag, and close.
- ▌ Rite Ship 4 · viktorsbaikers bundleCommit, push, tag, archive, or close a sealed feature after /rite-seal GO. Use for repository mutation; not for GO/NO-GO readiness.