omk-project-rules

Discover repository conventions and derive lint, typecheck, test, and build commands.

130|14|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/dmae97/oh-my-kimi --skill omk-project-rules
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: omk-project-rules
Source: https://github.com/dmae97/oh-my-kimi/tree/main/templates/skills/agents/omk-project-rules
Command: npx skills add https://github.com/dmae97/oh-my-kimi --skill omk-project-rules

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents inconsistent or incorrect changes by helping you discover and follow a repository’s existing coding conventions and validation workflow before you implement anything.

Core Features & Use Cases

  • Rule discovery from project docs: Reads AGENTS.md and DESIGN.md (when relevant) to learn intended behaviors and UI/frontend conventions.
  • Config-driven workflow inference: Inspects common package and framework config files to infer the correct lint, typecheck, test, and build commands instead of guessing.
  • Style and safety alignment: Derives guidance from existing code style and repository patterns to avoid inventing conventions that conflict with the codebase.

Quick Start

Ask the AI to summarize the repository’s project rules for making a safe code change and include the derived commands, style expectations, testing approach, and any missing information.

Frequently Asked Questions about omk-project-rules

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

FAQPage Schema
How do I discover existing project conventions before making code changes?

You discover project conventions by inspecting repository files like AGENTS.md, DESIGN.md, and framework configuration to derive lint, typecheck, test, and build commands for safe code changes.

How do I infer lint, test, and build commands from a repository config?

Infer lint, test, and build commands by inspecting common package manager files and framework configuration files, which reveal the exact validation workflow rather than requiring you to guess.

How can I align my code style with existing repository patterns?

Align code style with existing repository patterns by deriving guidance from current linting configurations and code conventions, ensuring new changes avoid inventing rules that conflict with the codebase.

Does this project rules discovery work with both JavaScript and Python repositories?

Yes, project rules discovery works across JavaScript and TypeScript as well as Python repositories, reading standard package manager files and framework configs to infer correct validation workflows.

Why does my code change conflict with existing repository conventions?

Code changes conflict with existing repository conventions when new patterns are invented without inspecting AGENTS.md, DESIGN.md, and lint or test configurations to align with intended behaviors.