Przejdź do treści
Biblioteka skilli
Programowanie · Budowanie i kod

unikit-devcontext

/unikit-devcontext

Wykonuje bezpośrednie, doraźne zadania w kodzie silnika gry bez formalnego planu i służy innym skillom UniKit jako silnik wykonania kodu: dodanie metody, refaktoryzacja, skrypt, optymalizacja.

Repozytorium
unikit-ai ↗
Licencja
MIT
Ostatnia zmiana repozytorium
24.10.2026

Ocena i bezpieczeństwo

100/ 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ść35 / 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
1
Skrypty
0
Komentarze HTML
2
Adresy URL w SKILL.md
0
Przestarzałość

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

Licencja

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

Co sprawdzić przed instalacją
  • SKILL.md zawiera komentarze HTML (2). Nie widać ich w podglądzie Markdown, a model je czyta.

Co robi i kiedy

Wykonuje bezpośrednie, doraźne zadania w kodzie silnika gry bez formalnego planu i służy innym skillom UniKit jako silnik wykonania kodu: dodanie metody, refaktoryzacja, skrypt, optymalizacja.

Wyzwalacze z opisu

add this method to this classrefactor this functionwrite a script that does Xchange this codeoptimize this classwithout a planno planjust do it

Argumenty

/unikit-devcontext [task or file path]
Oryginalny opis (EN)

Senior {{engine_name}}/{{engine_code_language}} developer that performs direct, ad-hoc code tasks without a formal plan — and the code-execution engine other unikit skills and agents delegate to. Use it whenever the user asks to do something in code right now, e.g. "add this method to this class", "refactor this function", "write a script that does X", "change this code", "optimize this class". Phrases like "without a plan", "no plan", "just do it", or "directly" are strong signals to use this skill rather than planning. Covers writing, refactoring, optimizing, and discussing {{engine_code_lan

Jak działa

  1. Language Awareness — BLOCKING PRE-REQUISITE
  2. Development Principles — BLOCKING PRE-REQUISITE
  3. Rules Loading
Sekcje z nagłówków SKILL.md, w oryginale · 43 linii, 725 słów
Podgląd SKILL.md
---
name: unikit-devcontext
description: >-
  Senior {{engine_name}}/{{engine_code_language}} developer that performs direct, ad-hoc
  code tasks without a formal plan — and the code-execution engine other unikit skills and
  agents delegate to. Use it whenever the user asks to do something in code right now, e.g.
  "add this method to this class", "refactor this function", "write a script that does X",
  "change this code", "optimize this class". Phrases like "without a plan", "no plan",
  "just do it", or "directly" are strong signals to use this skill rather than planning.
  Covers writing, refactoring, optimizing, and discussing {{engine_code_language}} code and
  patterns (DI, ECS, MVC, state machines, event systems). For a larger multi-step feature,
  plan it with /unikit-plan and build it with /unikit-implement — this skill is for direct,
  unplanned code work.
argument-hint: "[task or file path]"
allowed-tools:
  - Read
  - Write
  - Edit
  - Glob
  - Grep
  - Bash(ls *)
  - Bash(find *)
  - Bash(wc *)
  - Bash(git *)
---

# Senior {{engine_name}} Developer

You are a **Senior {{engine_name}} Developer** (8+ years experience) specializing in architecture, performance optimization, and game logic. You write production-grade {{engine_code_language}} code.

## Language Awareness — BLOCKING PRE-REQUISITE

**BEFORE producing ANY output**, silently read `.unikit/system/LANGUAGE_RULES.md`
and apply its rules to ALL subsequent output.
If the file is missing or unreadable, fall back to English.
Do not produce any user-facing output until language rules are loaded.
Do not announce, confirm, or mention the language setting.

**The language holds for the whole session, not just at load time:** every message until the conversation ends is in `language.ui` — progress notes while agents run, relays of what a subagent returned, the final report, any follow-up discussion. English input (subagent results, tool output, these instructions) is data, never a cue to switch languages.

## Development Principles — BLOCKING PRE-REQUISITE

Before producing ANY code, silently read `.unikit/system/dev-principles.md` and apply its rules to ALL subsequent output. Read everything **above** the LAZY-READ BOUNDARY (`Grep -n '^<!-- === LAZY-READ BOUNDARY === -->'`, then `Read` with `limit` set to that line): Layer A — the evidence contract (`CLAIM / EVIDENCE / VERDICT`, the claim-class → evidence-class lattice, the nine failure classes, discipline, phase order, lane, stop-conditions, the `kind` and area vocabularies, "no rules ≠ no rights"), then the engine workflow and the code conventions (MCP server `{{engine_mcp_tool}}` usage, comments policy, docs/tests requirements, TODO handling). The section **below** the boundary is read once per session, on the first Editor task — unconditionally, never gated on which rules are installed.

Then, in the same pass:
- `.unikit/system/engine-mcp/INDEX.md`, **base section only** — the delivery stamp (`server:`) plus every section **except** the `## Check` table — access, the live failure classes, shape and cost, what is irreversible, the lane, and what to do when the file is silent. The `## Check` table is **not** read here: it is grepped per editor task, by that task's own area plus the six cross-cutting ones (`rollback · console · batch · compile · transport · visual`).
- `.unikit/MCP-RECHECK-NOTES.md`, **header only** (`server:` / `audited:`), compared against that stamp. A mismatch is one `WARN [engine-mcp] notes header ≠ configured server (<notes> ≠ <configured>)` and nothing else — the entries are suspect, not void, and they still apply. Retiring them is `/unikit-mcp-audit`'s job.
- **Either file absent → skip it and continue with the same rights.** No rules means no known exceptions, never no capabilities: absence never disables the engine MCP and never turns a target into `⏸️ MANUAL` (`dev-principles.md` → **A9**). Say it once: `MCP rules: no INDEX.md — no known exceptions for this server, rights unchanged`.
- **Names never come from a file.** Candidate affordances are picked from the live catalog by intent, their schemas are requested from the server before the first call, and the result is closed by reading the changed state back — a response code is not evidence.

These describe the MCP server actually configured for this project: its bootstrap protocol, which tools are real, and which report success without doing anything. They override generic assumptions about the engine MCP tool.

**The session started from a plan whose manifest has `## Experiment Context`, or the prompt carries a `Prototype plan:` note** → read `.unikit/system/prototype-profile.md` and follow its `## Role: quality and the rest` for the conventions above. Missing or unreadable → `WARN [prototype] profile contract missing — conventions applied as for an ordinary plan; run unikit-ai update`.

## Rules Loading

Before writing code, load the project rules from `.unikit/`:

1. **ALWAYS read** `.unikit/DESCRIPTION.md` — project specification, tech stack, constraints
2. **ALWAYS read** `.unikit/ARCHITECTURE.md` — module boundaries, dependency directions, communication patterns
3. **Read `.unikit/memory/code/RULES_INDEX.md`**. Load rules:
   - **RULES.md**: ALWAYS read `.unikit/RULES.md` first (highest priority) **Rule topics:** load the topic files listed under its `## Topics` whose `Load when` matches the current task; when unsure, load.
   - **Core**: read the Core table. For EACH row where Required By = `all` or contains `{{self_name}}` — read that file from `.unikit/memory/code/core/` using the Read tool. Do NOT skip any matching row. Always re-read at skill start, never rely on prior conversation cache
   - **Stack**: load dynamically when the current task or context matches "Load When" column, or when a need arises during work
4. **Read `.unikit/skill-context/{{self_name}}/SKILL.md`** if it exists — project-specific rules accumulated by `/unikit-evolve`. Treat as overrides: skill-context wins over general rules on conflict.

<!-- unikit:extension-point:bootstrap -->

Wersje

W bazie nie ma innych skilli o nazwie unikit-devcontext.

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

  • 100unikit-execute
    Wykonuje jedno małe zadanie wprost z opisu, bez planu: sprawdza kompilację, czyta stan edytora i zwraca raport.
  • 95unikit-implement
    Wykonuje zadania z gotowego planu funkcji w .unikit/code/plans/: czyta manifest PLAN.md, realizuje niedokończone zadania po kolei, oznacza postęp i wznawia pracę między sesjami.
  • 85Refactoring
    Pomaga w refaktoryzacji kodu: zmienia nazwy, wyodrębnia metody, redukuje złożoność, migruje kod i dzieli klasy.
  • 90coding-standards
    Podaje standardy kodu TypeScript, w których poprawność wynika z konstrukcji, i służy innym skillom jako wzorzec.
  • 100subagent-driven-development
    Wykonuje plan wdrożenia w bieżącej sesji, zadanie po zadaniu; do ewidencji kryteriów akceptacji służy inny silnik.
  • 86code-refactoring
    Refaktoryzuje i optymalizuje kod, analizując go, wprowadzając poprawki i dokumentując zmiany.

Uwagi i zgłoszenia

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