Przejdź do treści
Biblioteka skilli
Programowanie · Nauka i wyjaśnianie

principles

/principles

Zbiera zasady inżynierskie dotyczące wielkości zmiany, typów, debugowania, weryfikacji, pomiarów i delegowania, gdy zadanie trafia w jeden z wyzwalaczy.

Repozytorium
skills ↗
Licencja
MIT
Ostatnia zmiana repozytorium
03.11.2026

Ocena i bezpieczeństwo

90/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść25 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
26
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 03.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Zbiera zasady inżynierskie dotyczące wielkości zmiany, typów, debugowania, weryfikacji, pomiarów i delegowania, gdy zadanie trafia w jeden z wyzwalaczy.

Oryginalny opis (EN)

Engineering principles for sizing a change, designing types and state, debugging, verifying work, measuring, and delegating. Use when a task hits one of the triggers in the index, or when another skill names a principle.

Jak działa

  1. Core
  2. Architecture
  3. Verification
  4. Delegation
  5. Meta
Sekcje z nagłówków SKILL.md, w oryginale · 44 linii, 778 słów
Podgląd SKILL.md
---
name: principles
description: "Engineering principles for sizing a change, designing types and state, debugging, verifying work, measuring, and delegating. Use when a task hits one of the triggers in the index, or when another skill names a principle."
---

# Principles

Each entry says when it applies. Read the full file for any principle you apply, and name it in your reply with the choice it changed.

## Core

- [laziness-protocol](laziness-protocol.md). Apply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading. Bias toward deletion and the smallest change that solves the problem.
- [foundational-thinking](foundational-thinking.md). Apply before writing logic: choosing core types and data structures, sequencing scaffold-vs-feature work, asking what concurrent actors share. Get the data structures right so downstream code becomes obvious.
- [redesign-from-first-principles](redesign-from-first-principles.md). Apply when integrating a new requirement into an existing design.
- [attack-the-premise](attack-the-premise.md). Apply when two or more fixes that share one premise have failed the same gate. Write the premise down and test it directly before you write another fix that assumes it.
- [subtract-before-you-add](subtract-before-you-add.md). Apply when sequencing an addition, refactor, or rewrite. Remove dead code, redundant validators, and stub references first, then build on the simpler base.
- [minimize-reader-load](minimize-reader-load.md). Apply when reviewing or shaping code that's hard to trace. Count layers between question and answer, and hidden state in the reader's head; collapse one-caller wrappers and shrink mutable scope.
- [outcome-oriented-execution](outcome-oriented-execution.md). Apply during planned rewrites and migrations with explicit phase boundaries. Converge on the target architecture; don't preserve smooth intermediate states with throwaway compatibility code.
- [experience-first](experience-first.md). Apply when product, UX, or feature-scope tradeoffs come up. Choose user delight over implementation convenience; ship fewer polished features over more rough ones.
- [exhaust-the-design-space](exhaust-the-design-space.md). Apply when facing a novel UI interaction or architectural decision with no precedent in the codebase. Build 2-3 competing prototypes and compare side by side before committing.
- [build-the-lever](build-the-lever.md). Apply to any non-trivial work, not just bulk work: edits, migrations, analyses, checks. Build the tool that does it or proves it (codemod, script, generator, or a skill any worker follows) instead of working by hand. The tool is the artifact a reviewer can rerun.

## Architecture

- [model-the-domain](model-the-domain.md). Apply when writing stateful logic, or when code branches a lot or repeats a shape assumption across files.
- [boundary-discipline](boundary-discipline.md). Apply when wiring validation, error handling, or framework adapters. Concentrate guards at system boundaries (CLI, config, network, external APIs); trust internal types and keep business logic in pure functions.
- [type-system-discipline](type-system-discipline.md). Apply when designing types, reviewing a function signature, or writing code in any statically-typed language. Make illegal states unrepresentable, brand semantic primitives, parse external data at boundaries, exhaust variants, derive from authoritative schemas.
- [make-operations-idempotent](make-operations-idempotent.md). Apply when designing commands, lifecycle steps, or processing loops that run amid crashes, restarts, and retries. Converge to the same end state regardless of partial prior runs.
- [migrate-callers-then-delete-legacy-apis](migrate-callers-then-delete-legacy-apis.md). Apply when introducing a new internal API while old callers still exist. Migrate callers and delete the old API in the same wave instead of preserving compatibility layers.
- [separate-before-serializing-shared-state](separate-before-serializing-shared-state.md). Apply when concurrent actors might write to the same file, branch, key, or state object. Eliminate the sharing first; serialize structurally only when one shared writer is a real invariant.

## Verification

- [prove-it-works](prove-it-works.md). Apply after completing a task, before declaring done. Verify against the real artifact (run the feature, read the actual value, inspect the diff), not a proxy, self-report, or 'it compiles.'
- [fix-root-causes](fix-root-causes.md). Apply when debugging. Trace each symptom back to the first place the system went wrong and fix it there. A guard is a fix only when the state it handles is legitimate.
- [sequence-verifiable-units](sequence-verifiable-units.md). Apply to multi-step work (sweeps, migrations, runs of similar edits) and to how you stack commits and PRs. Break work into small units that each end in a verifiable state, check each before the next, and order delivery so the sequence proves itself to a reviewer.
- [test-behavior-not-implementation](test-behavior-not-implementation.md). Apply when you write, change, or keep a test. Assert what the code's users can observe, so that the test fails when that behavior breaks and keeps passing when only the internals change.
- [explain-the-number](explain-the-number.md). Apply before you measure, and before you trust, report, or act on a number you measured: a speedup, a regression, a throughput, a latency, or an eval result. Find what limits it, and rule out that it measured something other than the work you think.

## Delegation

- [guard-the-context-window](guard-the-context-window.md). Apply when context is filling up: large outputs, long files, repeated reads, fan-out planning. Read excerpts, write bulk to files, and keep summaries in the conversation, not raw payloads.
- [never-block-on-the-human](never-block-on-the-human.md). Apply when tempted to ask 'should I do X?' on reversible work.

## Meta

- [encode-lessons-in-structure](encode-lessons-in-structure.md). Apply when you catch yourself writing the same instruction a second time, or notice a recurring correction. Encode the rule as a lint, metadata flag, runtime check, or script instead of more text.
Pliki w paczce (26)
  • SKILL.md 6 KB
  • attack-the-premise.md 2 KB
  • boundary-discipline.md 2 KB
  • build-the-lever.md 2 KB
  • encode-lessons-in-structure.md 1 KB
  • exhaust-the-design-space.md 1 KB
  • experience-first.md 1 KB
  • explain-the-number.md 2 KB
  • fix-root-causes.md 2 KB
  • foundational-thinking.md 1 KB
  • guard-the-context-window.md 1 KB
  • laziness-protocol.md 1 KB
  • make-operations-idempotent.md 1 KB
  • migrate-callers-then-delete-legacy-apis.md 1 KB
  • minimize-reader-load.md 2 KB
  • model-the-domain.md 2 KB
  • never-block-on-the-human.md 1 KB
  • outcome-oriented-execution.md 1 KB
  • prove-it-works.md 1 KB
  • redesign-from-first-principles.md 1 KB
  • separate-before-serializing-shared-state.md 1 KB
  • sequence-verifiable-units.md 1 KB
  • subtract-before-you-add.md 1 KB
  • test-behavior-not-implementation.md 2 KB
  • type-system-discipline.md 1 KB
  • agents/openai.yaml 1 KB

Wersje

RepozytoriumWynikLicencja
Ta strona · KyrosHendrix/skills90MIT
ongtungduong/legion100MIT
mimshins/ork100MIT
OutlineDriven/outline-driven-development95Apache-2.0
vahaah/astack90MIT
overextended/skills90GPL-3.0
autocss-com/ai90MIT
melodic-software/claude-code-plugins84MIT

Migawka bazy z 13.11.2026 · wersja paczki 497756a69151 (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

  • 90ds-principles
    Podaje zwięzłe zasady projektowania, debugowania, weryfikacji i delegowania, każda z wyzwalaczem, np. przy doborze struktury lub testach.
  • 90ds-principles
    Podaje zwięzłe zasady inżynierskie z wyzwalaczami, np. przy wymianie API, rozmiarze zmiany lub debugowaniu.
  • 85engineering-principles
    Stosuje 24 zasady inżynierskie do decyzji projektowych, implementacyjnych, testowych i pomiarowych, nazywając zasadę, która zmieniła daną decyzję.
  • 100frontend-engineering-principles
    Zbiera wspólne zasady inżynierskie dla skilli FEOS: sposób myślenia, proces decyzji technicznych i mapę, którego skilla użyć.
  • 85engineering-principles
    Stosuje podstawowe zasady inżynierii oprogramowania przy projektowaniu systemów, strukturze kodu, przeglądzie zmian i obsłudze stanu.
  • 100using-python-package-principles
    Wskazuje, którego z 12 skilli zasad pakietów Python użyć, i prowadzi przy tworzeniu, przeglądzie lub modernizacji projektu Python.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.