lubochka
- 29 skills
- 0 followers
- 17 hours ago last updated
- ▌ No Secrets · lubochkaPrevent publishing sensitive material. Use before commits, reports, examples, adaptation outputs, and release.
- ▌ Debug Session · lubochkaPackage debugging work so another agent or human can resume it. Use for longer debugging tasks or handoffs.
- ▌ Code Execution · lubochkaRun commands safely and intentionally. Use before executing build, test, lint, generation, migration, deploy, or cleanup commands.
- ▌ Failure Triage · lubochkaClassify failures before changing implementation. Use after failed builds, tests, commands, or smoke checks.
- ▌ Test Integrity · lubochkaKeep tests meaningful and honest. Use when writing, changing, disabling, or interpreting tests.
- ▌ Authority Chain · lubochkaResolve which instructions win when rules conflict. Use at the start of every task and whenever instructions disagree.
- ▌ E2e Test Matrix · lubochkaDesign end-to-end coverage across critical paths. Use for release readiness, user workflows, UI/API flows, and adapter validation.
- ▌ Review Fix Loop · lubochkaClose actionable feedback through repeated review and repair. Use after plan review, code review, content review, or release-gate review.
- ▌ Code Examination · lubochkaUnderstand local code before changing it. Use before implementation, refactoring, test fixes, or architecture changes.
- ▌ Decision Capture · lubochkaRecord important decisions and rationale. Use when selecting architecture, stack guide, adapter output, or release policy.
- ▌ Claim Verification · lubochkaVerify claims before presenting them as facts. Use in final answers, reports, reviews, and architecture decisions.
- ▌ Document Hierarchy · lubochkaAvoid competing sources of truth. Use when adding, moving, or adapting docs.
- ▌ Documentation Sync · lubochkaKeep documentation aligned with behavior. Use when changing workflows, commands, APIs, examples, or user-facing behavior.
- ▌ Root Cause Tracing · lubochkaFind the cause behind a symptom. Use when a failure repeats, appears indirect, or has multiple possible causes.
- ▌ Scope And Blockers · lubochkaKeep scope and blockers explicit. Use when requirements are broad, ambiguous, or blocked by missing information.
- ▌ Assumption Registry · lubochkaMake assumptions visible and testable. Use during planning, architecture adaptation, and unclear requirements.
- ▌ Code Request Safety · lubochkaCheck risk before code actions. Use before running commands, editing files, deleting files, moving data, or changing configuration.
- ▌ Integration Testing · lubochkaVerify boundaries between components. Use when behavior crosses services, modules, tools, adapters, or data formats.
- ▌ Project Rules First · lubochkaEnsure project-specific rules are read before meaningful action. Use at task startup, before editing files, running commands, or adapting skills.
- ▌ Stale Baseline Guard · lubochkaAvoid acting on outdated context. Use after interruptions, long sessions, branch changes, or concurrent edits.
- ▌ Systematic Debugging · lubochkaMake debugging reproducible and disciplined. Use for unclear failures, regressions, or unstable behavior.
- ▌ User Journey Testing · lubochkaValidate work through a realistic user path. Use for UX, tool workflows, onboarding, and generated instructions.
- ▌ Evidence Before Final · lubochkaPrevent claiming completion without proof. Use before final responses, handoffs, releases, or review closure.
- ▌ Generated Code Review · lubochkaReview generated code before trusting it. Use after AI-generated code, scaffolding, migration output, or copied snippets.
- ▌ Plan Before Execution · lubochkaCreate a bounded plan before non-trivial work. Use for multi-file, high-risk, ambiguous, or delegated work.
- ▌ Output Readability Gate · lubochkaKeep outputs readable for humans. Use before delivering plans, reports, READMEs, reviews, and adaptation output.
- ▌ Session Output Contract · lubochkaMake session output useful, complete, and resumable. Use at handoff, final response, or long-running task summary.
- ▌ Goal Delivery Completeness · lubochkaCheck that delivered work matches the user's goal. Use before final response, release, or handoff.
- ▌ Executor Cannot Self Finish · lubochkaSeparate execution from completion approval. Use when an agent both implements and reviews its own work.