Przejdź do treści
Biblioteka skilli
Programowanie · Automatyzacja

strict-validation-setup

/strict-validation-setup

Jednorazowo konfiguruje rygorystyczne narzędzia typów i lintingu dla TypeScript, Pythona, Rusta, Go i OCaml oraz plik GOALS.md dla każdego zadania, by pętla agenta mogła sama weryfikować wyniki.

Licencja
Apache-2.0
Ostatnia zmiana repozytorium
08.07.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
7
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

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

Licencja

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

Co robi i kiedy

Jednorazowo konfiguruje rygorystyczne narzędzia typów i lintingu dla TypeScript, Pythona, Rusta, Go i OCaml oraz plik GOALS.md dla każdego zadania, by pętla agenta mogła sama weryfikować wyniki.

Oryginalny opis (EN)

One-shot bootstrap of strict-mode tooling per ecosystem plus per-task GOALS.md scaffolding so an agentic loop can self-verify. Writes typechecker/linter/schema-validator config for TS (strict + noUncheckedIndexedAccess + exactOptionalPropertyTypes), Python (Pyright strict, Ruff strict), Rust (Clippy deny-correctness), Go (golangci-lint with staticcheck), OCaml (dune --release); establishes `.agent-tasks/<id>/GOALS.md` per-task convention distinct from project-stable AGENTS.md. C++/Java/Kotlin and framework specifics (Spring Boot, Nest, React-strict) are out of scope. Trigger on new project boo

Jak działa

  1. Modality differentiation
  2. Three parts
  3. Cross-references
  4. Posture
Sekcje z nagłówków SKILL.md, w oryginale · 67 linii, 639 słów
Podgląd SKILL.md
---
name: strict-validation-setup
description: One-shot bootstrap of strict-mode tooling per ecosystem plus per-task GOALS.md scaffolding so an agentic loop can self-verify. Writes typechecker/linter/schema-validator config for TS (strict + noUncheckedIndexedAccess + exactOptionalPropertyTypes), Python (Pyright strict, Ruff strict), Rust (Clippy deny-correctness), Go (golangci-lint with staticcheck), OCaml (dune --release); establishes `.agent-tasks/<id>/GOALS.md` per-task convention distinct from project-stable AGENTS.md. C++/Java/Kotlin and framework specifics (Spring Boot, Nest, React-strict) are out of scope. Trigger on new project bootstrap, agentic-task setup, "make this self-verifying", "set the loop's goal", "scaffold goals for this issue". Pairs with `llm-self-loop` runtime.
disable-model-invocation: true
---

The skill ships two distinct concerns split by *temporal phase*:

- **Project-stable** — strict-mode tooling config + AGENTS.md authoring (defer the AGENTS.md content to `init`; this skill only ensures it exists and references the per-task pattern).
- **Task-ephemeral** — `.agent-tasks/<task-id>/GOALS.md` per task plus failing-test scaffolding co-located with it.

These never mix. Task goals never go into AGENTS.md (would leak as project policy). Project invariants never go into per-task GOALS.md (would duplicate per task and drift).

## Modality differentiation

| Skill                       | Owns                                                                             |
| --------------------------- | -------------------------------------------------------------------------------- |
| **`strict-validation-setup`** | Strict-mode tooling configs + per-task `GOALS.md` convention (this file)        |
| `init`                      | AGENTS.md authoring (project-stable) — defer to it for content                  |
| `test-driven`               | TDD discipline (RED → GREEN → REFACTOR) — defer for test-writing methodology   |
| `type-driven`               | Refined-type / typestate specs — defer for type-system invariants               |
| `design-by-contract`        | Pre/post conditions, runtime contracts — defer for assertion patterns           |
| `validation-first`          | State-machine specs (typestate / FSM / actor) — defer for FSM modeling         |
| `tests-adversarial`         | Assumption-violation tests — defer for the adversarial test pattern             |
| `setup-pre-commit`          | Commit-hook installation — defer for hook tooling                               |
| `setup-gitignore`           | Gitignore patterns — defer for ignore-file composition                          |

Duplication with the existing skills was audited and accepted; bodies cite each rather than re-doing the work. When the surface narrows to a single concern above, defer.

## Three parts

### 1. Strict-mode tooling bootstrap (project-stable)

Detect the ecosystem from manifests, then write strict-mode config per the relevant `references/<ecosystem>.md`. Idempotency: merge with existing config; raise if a destructive overwrite would be required and `--overwrite` is not explicit. Never silently replace.

Languages with bundled references (Q5-approved set; framework specifics deferred to a follow-up):

- `references/typescript.md`
- `references/python.md`
- `references/rust.md`
- `references/go.md`
- `references/ocaml.md`

Languages noted but not yet bundled — write deferred per Q8 rollback path: C++, Java, Kotlin, plus framework specifics (Spring Boot, Nest, React-strict). When the user invokes the skill on one of these, surface the gap explicitly and propose authoring the reference now or escalating to a follow-up commit.

### 2. AGENTS.md and per-task GOALS.md split (load-bearing)

- **AGENTS.md** — project-wide, stable across sessions and tasks. Contains: build/test commands, banned tooling, conventions, contract patterns, and the *location pattern* of per-task goal files (`.agent-tasks/<task-id>/GOALS.md` or whatever path the project chooses). **Defer authoring the AGENTS.md content to `init`** — this skill only ensures the file exists and contains the goal-location pointer.
- **`.agent-tasks/<task-id>/GOALS.md`** — task-ephemeral. Contains: the user's goal in prose, the success criteria the loop checks against, links to the failing tests in `.agent-tasks/<task-id>/tests/`. Cleaned up after the task merges.

The architectural rule: task A's goals never appear in AGENTS.md. AGENTS.md never contains task-specific success criteria. If the line blurs, surface and refuse.

### 3. Verifiable-goals scaffolding (task-ephemeral)

For the current task, translate the user's stated goal into failing tests / contract assertions. The tests live in `.agent-tasks/<task-id>/tests/` alongside the GOALS.md. The loop runs until the tests pass. Goals therefore exist both as prose (GOALS.md) and as code (tests).

Three sub-shapes, decide while drafting per task:

- **Interactive** — ask the user what success means, stub failing tests, hand back for review before agent loop begins.
- **Template-driven** — language-specific test stubs in `references/` (per-ecosystem). Pick the matching language template; let the user fill specifics.
- **Hybrid** — start template-driven; promote to interactive when the user's goal does not fit the template.

The term *verifiable goals* (Devin Agents101, Jun 2025) is preferred over *TDD-for-agents* (non-idiomatic in 2026 production stacks).

## Cross-references

Pairs with `llm-self-loop` runtime: this skill runs once at bootstrap, then `llm-self-loop` runs many times against the gates and goal files this skill installed. The pair is: *bootstrap → run-many*.

## Posture

Bootstrap is a one-shot mode. After running, do not stay resident. The loop that follows is `llm-self-loop`'s territory.
Pliki w paczce (7)
  • SKILL.md 6 KB
  • references/agent-goals.md 3 KB
  • references/go.md 3 KB
  • references/ocaml.md 2 KB
  • references/python.md 2 KB
  • references/rust.md 2 KB
  • references/typescript.md 2 KB

Wersje

RepozytoriumWynikLicencja
Ta strona · OutlineDriven/odin-codex-plugin90Apache-2.0
gosuda/dalcom-skills98Apache-2.0
OutlineDriven/outline-driven-development98Apache-2.0

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

  • 100typescript-strict
    Pisze i recenzuje TypeScript w trybie strict z flagami noUncheckedIndexedAccess i exactOptionalPropertyTypes oraz migruje luźne bazy kodu do pełnej ścisłości flaga po fladze.
  • 100python-tooling
    Konfiguruje narzędzia repozytorium Python: uv, Ruff, mypy strict, pytest, vulture, import-linter i bramkę CI.
  • 100typescript-strict
    Pomaga pisać i naprawiać TypeScript tam, gdzie liczy się bezpieczeństwo typów: zawężanie, rzutowania i tsc.
  • 100dune-migration
    Pomaga migrować projekty OCaml z ocamlbuild i topkg na dune: pliki _tags, .mllib, pkg/pkg.ml i zmiana systemu budowania.
  • 100typescript-strict
    Wprowadza konwencje ścisłego TypeScript: tryb strict, zakaz any, typy narzędziowe i obsługę błędów.
  • 100code-quality
    Pomaga konfigurować narzędzia jakości kodu Python: Ruff, mypy w trybie strict, pyright, nowoczesne typowanie (PEP 695, TYPE_CHECKING), znaczniki py.typed, hooki pre-commit i zestawy reguł lintera.

Uwagi i zgłoszenia

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