unikit-rules

Add and manage project-specific rules in .unikit/RULES.md.

16|1|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/NintendaDev/unikit-ai --skill unikit-rules
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unikit-rules
Source: https://github.com/NintendaDev/unikit-ai/tree/main/skills/unikit-rules
Command: npx skills add https://github.com/NintendaDev/unikit-ai --skill unikit-rules

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

UniKit AI relies on base knowledge rules and project-specific conventions to govern code and workflows. This skill provides a formal mechanism to add, validate, and centralize project rules into the .unikit/RULES.md file, ensuring overrides are intentional and discoverable.

Core Features & Use Cases

  • Cross-check new rules against RULES_INDEX.md to avoid duplication and conflicts with existing knowledge.
  • Add explicit overrides to .unikit/RULES.md with notes on what they override and why.
  • Respect skill-context overrides and language rules when applying changes, enabling project-specific governance.
  • Follow a repeatable workflow to load context, determine mode, and place rules in the correct section.

Quick Start

Provide the rule text to add, and the system will classify, validate, and insert it into .unikit/RULES.md under the correct section.

Frequently Asked Questions about unikit-rules

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I centralize project rules and conventions for my codebase?

To centralize project rules, you add project-specific conventions to a .unikit/RULES.md file, which overrides base knowledge and ensures all governance rules are intentional and discoverable across your workflow.

How does rule management prevent duplicate conventions in a knowledge base?

Rule management prevents duplicate conventions by cross-checking every new rule against a RULES_INDEX.md file before insertion, validating that no conflicts exist with the current knowledge base before applying the override.

What is the best way to override base knowledge rules for a specific project?

The best way to override base knowledge rules is adding explicit entries to .unikit/RULES.md with notes explaining what they override and why, honoring skill-context overrides to maintain project-specific governance.

Can I use optional directories like scripts and references to augment rule behavior?

Yes, you can use optional directories such as scripts, references, and assets to augment rule behavior and governance, extending how project rules are applied and managed across different projects.

How do I add a new project rule to the correct section automatically?

To add a new project rule, provide the rule text and the system will classify, validate, and insert it into .unikit/RULES.md under the correct section by following a repeatable workflow to load context and determine mode.

Why are my project-specific conventions not overriding base knowledge correctly?

Project-specific conventions fail to override base knowledge when rules are not formally centralized in .unikit/RULES.md, meaning the system lacks the explicit override entries needed to govern your workflow.