rules

Enforce project constraints to prevent risky actions and unsafe tooling.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Rule set enforces essential project constraints to prevent risky actions and maintain safe, predictable workflows.

Core Features & Use Cases

  • Enforces directory and workflow constraints to prevent accidental structural changes
  • Prohibits dangerous actions and unsafe tooling to reduce human error
  • Provides guidance for compliant, auditable task execution across teams

Quick Start

Follow these rules before starting any task to ensure safe, compliant operation.

Frequently Asked Questions about rules

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

FAQPage Schema
How do I enforce project safety rules to prevent risky actions during development workflows?

Project safety rules prevent risky actions by enforcing directory constraints, disallowing unsafe tools, and forbidding background tasks to maintain predictable development workflows.

What are the best practices for development workflow compliance and risk avoidance?

Development workflow compliance best practices involve specifying operational guardrails and validation checks to ensure compliant, auditable task execution across teams and prevent human error.

How can I prevent accidental structural changes to project directories?

Preventing accidental structural changes requires enforcing directory and workflow constraints, establishing operational guardrails that block risky actions before task execution begins.

Does this governance ruleset prohibit dangerous tools and background tasks?

Yes, this governance ruleset prohibits dangerous actions, disallows unsafe tooling, and forbids background tasks to reduce human error and enforce essential project discipline.

When do I need to apply operational guardrails for compliant task execution?

Apply operational guardrails before starting any task to ensure safe, compliant operation and prevent risky actions across your development workflows.

Are there limitations to using basic project rules for governance and risk avoidance?

Basic project rules provide essential constraints for risk avoidance but are limited to enforcing directory changes, unsafe tools, and background tasks without advanced validation logic.