rules

Enforce project rules for directory, tool, and git command constraints.

Updated Jun 3, 2026
One-click install
npx skills add https://github.com/mgreenly/ikigai --skill rules-mgreenly
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rules
Source: https://github.com/mgreenly/ikigai/tree/main/.claude/library/rules
Command: npx skills add https://github.com/mgreenly/ikigai --skill rules-mgreenly

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Critical project operations frequently drift into unsafe or inconsistent workflows; this skill enforces a concise, hard-walled set of rules to prevent such issues.

Core Features & Use Cases

  • Never change directories - Always stay in root, use relative paths
  • Never use AskUserQuestion tool - Forbidden in this project
  • Never use git commands - This is a jj (Jujutsu) project; always use jj commands instead of git
  • Never use background tasks - Always run tasks in foreground unless explicitly asked
  • Centralized governance: rules define a predictable, auditable workflow.

Quick Start

Install and acknowledge the rules to automatically enforce directory, tool, and background task constraints in your project.

Frequently Asked Questions about rules

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

FAQPage Schema
How do I enforce strict project rules and safe workflows in software development?

You establish safe workflows by implementing a centralized governance skill that enforces critical project operations. This prevents unsafe actions and ensures predictable, auditable consistency across version control usage and software development workflows.

Can I enforce team policy to always run foreground tasks and never change directories?

Yes, you can enforce team policy rules to always run tasks in the foreground and stay in the root directory using relative paths. This prevents inconsistent workflows and maintains strict project governance across the development team.

What do I need to configure project rules using a SKILL.md file?

Configuring project rules requires a SKILL.md file with YAML frontmatter including name and description fields. You can also utilize optional scripts, references, and assets to support on-demand tasks and enforce safe workflows.

What is the best way to prevent unsafe actions and inconsistent workflows in version control?

The best way to prevent unsafe actions in version control is to apply centralized governance rules that explicitly forbid specific commands like git. This creates a hard-walled set of constraints ensuring safe, predictable, and auditable development workflows.

Can I block specific tools like AskUserQuestion from being used in my project workflows?

Yes, you can block specific tools like AskUserQuestion by defining them as forbidden in your project rules. This restricts unsafe actions and enforces strict, consistent workflows across your software development environment.