aif-rules

Name: aif-rules
Availability: InStock
Author: Ichi

Append new entries to RULES.md and register area-specific rule files.

Updated Aug 23, 2026

Search Tags:#automation #rules #yaml-frontmatter #ai-workflow #config.yaml #project-governance #RULES.md

Ready to run

npx skills add https://github.com/ichinya/idshka --skill aif-rules-ichinya

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: aif-rules
Source: https://github.com/ichinya/idshka/tree/main/.codex/skills/aif-rules
Command: npx skills add https://github.com/ichinya/idshka --skill aif-rules-ichinya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Adds and enforces project-specific rules by extending the configured RULES.md artifact and ensuring they are loaded before execution.

Core Features & Use Cases

Appends new rules to RULES.md for ongoing governance
Supports area-specific rules with per-area files and config.yaml registrations
Facilitates project setup and ongoing conventions updates across modules

Quick Start

Provide the rule text to add and the skill will append it to RULES.md and update any necessary area registrations.

Frequently Asked Questions about aif-rules

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

FAQPage Schema

How do I enforce project-specific coding conventions and rules automatically?▼

You can enforce project conventions by appending new rule entries to a configured RULES.md artifact. This ensures the rules are loaded before execution to maintain governance across modules, naming, and compliance.

Can I define area-specific rules in separate files instead of one global configuration?▼

Yes, the skill supports area-specific rules by allowing per-area files and config.yaml registrations. This enables targeted governance across different modules while keeping a global changelog and preventing duplicates.

How do I add a new rule to RULES.md without creating duplicate entries?▼

Provide the rule text and the skill appends it to RULES.md while automatically preventing duplicates. It also updates any necessary area registrations in config.yaml and maintains a changelog of modifications.

When do I need to update RULES.md during the software development lifecycle?▼

Updating RULES.md is needed during project setup and ongoing governance. This captures evolving conventions for modules, naming, and compliance as the project develops and new architectural decisions are made.

Does config.yaml need manual updates when adding project governance rules?▼

Config.yaml does not require manual updates for governance rules. The skill automatically handles area registrations in config.yaml when appending entries to RULES.md, ensuring proper loading during implementation.