unikit-devcontext
SolidSenior {{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.
Install
Quality Score: 78/100
Skill Content
Details
- Author
- NintendaDev
- Repository
- NintendaDev/unikit-ai
- Created
- 3 months ago
- Last Updated
- 5 days ago
- Language
- Shell
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
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.
unikit-explore
Enter explore mode for technical work — a thinking partner for {{engine_name}} code, architecture, and implementation decisions before you write any code. Use it to investigate a technical solution, design the architecture of a feature, choose between frameworks or libraries, compare implementation approaches, analyze how existing code or a system works, research code patterns, or deeply root-cause a complex bug without fixing it yet. Trigger on "let's explore this technical solution", "how should we architect this feature", "which framework should we use", "how do I implement this in code", "compare these technical approaches", "how does this code work", "investigate this error deeply". Research and analysis only — it never writes code. This is the CODE / engineering explorer — for GAME-DESIGN, GDD, mechanics, or balance research (no code) use /unikit-gd-explore.
unikit-implement
Execute the tasks from an already-created feature plan in .unikit/code/plans/ — read the plan (TASKS.md + PLAN-BRIEF.md), work through the uncompleted tasks in order, write the code, mark progress, and resume across sessions. Supports selective runs by phase or by task numbers, and continuing from where the last session stopped. Use whenever a plan exists and the user wants to build it, e.g. "implement", "implement the plan", "start coding", "execute the plan", "run the plan", "do the next task", "implement phase 3", "implement tasks 2.1 and 2.3", "continue implementation", "continue where we left off", "keep going on the feature". To create the plan first, use the planning skill — this one carries an existing plan out.