unikit-skills-context

Solid

Customize how a built-in unikit skill behaves in this specific project by writing workflow overrides into its skill-context file. These are per-skill workflow rules (e.g. "/unikit-review should also flag TODO comments", "/unikit-implement should run tests after each task"), not coding conventions. Use when the user wants to change, customize, or override how a particular unikit skill works in this project — "customize the review skill", "make /unikit-fix always add logging here", "the implement skill should do X differently", "add a skill rule for /unikit-commit". Use "validate" to find stale overrides against updated base skills. For a general coding convention (not tied to one skill) use /unikit-rules; to derive rules from past mistakes use /unikit-evolve.

Code & Development 16 stars 1 forks Updated 4 days ago MIT

Install

View on GitHub

Quality Score: 84/100

Stars 20%
41
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# UniKit Skills — Skill Context Management Add workflow rules to `.unikit/skill-context/<skill>/SKILL.md`. These are project-level overrides that change how built-in unikit skills behave in this specific project. **When to use skill-context vs RULES.md:** - **RULES.md** (via `/unikit-rules`) — coding conventions: HOW to write code (naming, patterns, style) - **Skill-context** (this skill) — workflow overrides: HOW a skill should work (priorities, steps, guards) ## 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. ## Critical: Never Edit Built-in Skills Directly **NEVER modify files inside `{{skills_dir}}/unikit-*/`.** **ALWAYS write to:** `.unikit/skill-context/<skill-name>/SKILL.md` ## Workflow ### Step 0: Determine Mode ``` Check $ARGUMENTS: ├── starts with "validate" → Validate Mode ├── <skill-name> <rule-text> → Mode A: Direct Add └── No arguments → Mode B: Interactive ``` **Parsing arguments:** - **Mode detection:** If first word is `validate` → Validate Mode. Otherwise → Add Mode. - **Add Mode:** First token = skill name, rest = rule text. - **Validate Mode:** `validate` alone → all skills. `validate <skill>` → specific skill. **Skill name normalizati...

Details

Author
NintendaDev
Repository
NintendaDev/unikit-ai
Created
3 months ago
Last Updated
4 days ago
Language
Shell
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Data & Documents Solid

unikit-rules

Add a short, project-specific rule, convention, or override to .unikit/RULES.md — the quick-capture inbox for this project's rules; each invocation appends a rule, automatically loaded by /unikit-implement before execution (later promotable into the knowledge base via /unikit-memory migrate-rules). Works only with a rule typed as a prompt — it does NOT read files, folders, URLs, or PDFs. Cross-checks against the knowledge base (RULES_INDEX.md) to avoid duplicating core/stack entries. Use for fast, one-line conventions and corrections: "add a rule", "remember this", "convention", "always do X", "never use Y", "from now on do Z", or when the user corrects agent behavior and wants it remembered. If the user points to a source (file, folder, URL, PDF, article, book) or wants to research/document framework usage, use /unikit-memory; for architecture decisions use ARCHITECTURE.md.

16 Updated 4 days ago
NintendaDev
AI & Automation Solid

unikit-evolve

Learn project rules from accumulated fix patches in .unikit/code/patches/. Analyzes past mistakes, extracts prevention points, classifies each as a coding rule (→ RULES.md) or a per-skill workflow rule (→ skill-context), and proposes them for approval. Use when the user wants to turn past fixes into rules — "evolve", "evolve the rules", "learn from past mistakes", "learn from the fixes", "analyze the patches", "what rules should we add from recent fixes". Best run after several /unikit-fix sessions have left patches behind. This derives rules from accumulated patch history — to add a single rule by hand use /unikit-rules, and to promote mature RULES.md entries into the knowledge base use /unikit-memory migrate-rules.

16 Updated 4 days ago
NintendaDev
AI & Automation Solid

unikit-devcontext

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.

16 Updated 4 days ago
NintendaDev