ub-mode
/ub-mode
Stosuje zasady: najpierw działa, potem porządnie, a na końcu dobra praktyka, przy każdej zmianie kodu.
- Repozytorium
- ub-discipline ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 12.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 2
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 12.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Stosuje zasady: najpierw działa, potem porządnie, a na końcu dobra praktyka, przy każdej zmianie kodu.
Oryginalny opis (EN)
Follow the reduced principles when writing or changing code. Every change follows First Make it Work, then Then Make it Right, then Follow Practice. Use when the user runs /ub-mode or asks for the reduced principles.
Jak działa
- Laziness Protocol
- Foundational Thinking
- TDD
- Redesign From First Principles
- Attack the Premise
- Subtract Before You Add
- Outcome-Oriented Execution
- Build the Lever
- Architecture
- Fix Root Causes
Podgląd SKILL.md
--- name: ub-mode description: "Follow the reduced principles when writing or changing code. Every change follows First Make it Work, then Then Make it Right, then Follow Practice. Use when the user runs /ub-mode or asks for the reduced principles." disable-model-invocation: true license: MIT metadata: language: en translation_of: ub-mode-hans version: "1.0.0" --- # ub-mode Every time you are asked to make a change follow: * First Make it Work. * Then Make it Right. * Follow Practice # First Make it Work ## Laziness Protocol * One decision lives in one place. * Ship the smallest edit that solves the problem. ## Foundational Thinking * Get the data shape right before you write the logic. * Do first whatever helps every later phase. * If a concurrent writer would matter, do not share state. ## TDD * Write the failing test before you change the code. * See it fail for the reason you expect. * Make the smallest change that makes it pass. * If an honest test is impractical, do not write a bad one. ## Redesign From First Principles * Do not bolt a new requirement onto the old design. * Ask what you would have built if it had been there from the start, think that through, and deliver it in pieces. ## Attack the Premise * When two fixes that share one premise fail the same gate, write that premise in one sentence and count which actors hold the imbalance. * Remove the assignment. * Do not start another fix until you have done that. ## Subtract Before You Add * Take complexity out before you add anything. ## Outcome-Oriented Execution * Aim at the end state you can check. * A break in the middle is allowed when you planned it and can undo it. ## Build the Lever * If the work is not obvious at a glance, build the tool that does it. * Do one unit by hand, then make the tool match that unit. ## Architecture ### Model the Domain * Put the domain in a structure that makes the illegal states impossible. * Maintain a glossary of domain terms. * If the code is already clear and local, leave it. ### Boundary Discipline * Check the data where it enters. * Inside, trust it. * Keep the business logic in a pure function. ### Type System Discipline * Make the illegal value impossible to write. * Parse outside data once, where it comes in. * Do not silence the compiler. ### Make Operations Idempotent * Running it twice, or running it after a crash halfway through, ends in the same state. ### Separate Before Serializing Shared State * If they do not need the same mutable thing, give each its own. * If they do, allow one writer, and enforce that in the structure. # Then Make it Right ## Fix Root Causes * Reproduce it. * Fix the cause. * A guard that only hides the crash is not a fix. ## Sequence work into verifiable units * Finish one small unit and check it. * Then start the next. ## Test Behavior, Not Implementation * The test calls the code the way its user does and checks the result that user would see. * If the test would still pass when every function returned nothing, throw it out. ## Refactoring * Pin what the code does. * Change the structure. * Prove the behavior did not change. # Practice ## Keep a Log * Keep a log of every action you take and the reason you took it. * Report that log upon completion. ## Guard the Context Window * Keep the main thread small. * Send the bulk elsewhere, and keep the summary. ## Worktree Cleanup * Find what is safe to remove, confirm nothing still in use needs it, then reclaim the disk. * Uncommitted work waits for a decision. ## Commit and Push * Commit often, in small ordered commits. * Each commit says why, what changed, and how you proved it. * Push to the main line at the end.
Pliki w paczce (2)
- SKILL.md 4 KB
- agents/openai.yaml 1 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · ontology-of-everything/ub-discipline | 90 | MIT |
| unclebob/ub-mode | 90 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki f3d17e864be2 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 90make-it-work-right-fast
Ustala kolejność pracy nad zmianą: najpierw działanie, potem poprawność, na końcu szybkość, z jedną sprawą naraz. - 100code-quality-principles
Stosuje zasady KISS, YAGNI i SOLID, aby uprościć kod i uniknąć nadmiarowej inżynierii podczas refaktoryzacji lub przeglądu. - 100test-driven-development
Stosuje zasady TDD przy nowych funkcjach, poprawkach i refaktoryzacji: najpierw testy, które nie przechodzą, potem implementacja i porządkowanie kodu. - 92conventions-testing
Stosuje zasady pisania i przeglądania testów w projekcie przy każdej zmianie kodu testowego. - 86ub-mode-hans
Pisze i zmienia kod według zasady minimalizmu: najpierw działanie, potem poprawność, a na końcu dobre praktyki. - 85engineering-principles
Stosuje podstawowe zasady inżynierii oprogramowania przy projektowaniu systemów, strukturze kodu, przeglądzie zmian i obsłudze stanu.