agents__creating-folder-agents

Create or update folder-scoped AGENTS.md files with domain constraints and coding conventions.

1|1|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/erikhazzard/vasir --skill agents-creating-folder-agents
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agents__creating-folder-agents
Source: https://github.com/erikhazzard/vasir/tree/main/.agents/skills/agents__creating-folder-agents
Command: npx skills add https://github.com/erikhazzard/vasir --skill agents-creating-folder-agents

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill creates or rewrites AGENTS.md files for a specific folder or subsystem. It prevents documents that sound authoritative but fail to constrain coding agents where local architecture, performance budgets, generated-code boundaries, or legacy semantics make generic fixes unsafe.

Core Features & Use Cases

  • Create or update folder-scoped AGENTS.md to codify domain context, hard-no constraints, and local coding conventions.
  • Preserve and augment existing AGENTS.md content while ensuring consistency with repo standards.
  • Provide a structured template for future folder-specific rules and enable deterministic agent behavior in critical subsystems.

Quick Start

Create or update the AGENTS.md for a target folder by describing its domain, constraints, and local coding conventions.

Frequently Asked Questions about agents__creating-folder-agents

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

FAQPage Schema
How do I create AGENTS.md files to enforce folder-level AI governance?

You create AGENTS.md files to enforce folder-level AI governance by defining domain context, hard-no constraints, and local coding conventions. This ensures deterministic agent behavior and prevents unsafe generic fixes in critical subsystems.

What is the best way to constrain AI agent behavior in specific codebase folders?

Constraining AI agent behavior in specific folders is best handled by writing structured AGENTS.md files. These files codify local architecture rules and performance budgets to prevent authoritative but unsafe coding modifications.

How do I update existing AGENTS.md files without losing current documentation?

Updating existing AGENTS.md files without losing documentation requires augmenting the current content. The skill preserves existing rules while appending new folder constraints and ensuring consistency with repo standards.

When do I need folder-specific constraints for AI coding agents?

You need folder-specific constraints for AI coding agents when local architecture, performance budgets, generated-code boundaries, or legacy semantics make generic fixes unsafe. AGENTS.md files enforce these hard-no rules.

Can I use AGENTS.md to define hard-no rules for legacy code subsystems?

You can use AGENTS.md to define hard-no rules for legacy code subsystems. The files codify legacy semantics and domain context, preventing AI agents from applying generic fixes that violate local invariants.

What are the limitations of using AGENTS.md for AI workflow governance?

Limitations of using AGENTS.md for AI workflow governance include relying on the agent's ability to parse and respect structured constraints. It requires consistent updates to maintain alignment with evolving repo standards and local conventions.