arch:maintain-constraints-registry

Read, add, and update YAML project constraints with filtering by enforcement level.

2|Updated Jan 30, 2026

Search Tags:#architecture #aws #yaml #governance #registry #constraints

Ready to run

npx skills add https://github.com/amdmax/claude_marketplace --skill arch-maintain-constraints-registry

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: arch:maintain-constraints-registry
Source: https://github.com/amdmax/claude_marketplace/tree/main/.claude/skills/arch%3Amaintain-constraints-registry
Command: npx skills add https://github.com/amdmax/claude_marketplace --skill arch-maintain-constraints-registry

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a centralized and structured way to manage project-wide constraints, ensuring consistency and adherence to architectural guidelines throughout the development lifecycle.

Core Features & Use Cases

Read Constraints: Easily view all defined project constraints, filter by enforcement level (hard/soft), or by category.
Add Constraints: Define new hard or soft constraints with clear rules and rationales, ensuring new requirements are captured.
Update Constraints: Modify the enforcement level or rationale of existing constraints without deleting them, maintaining a historical record.
Use Case: Before proposing a new microservice design, an architect uses this Skill to review all 'hard' constraints related to cloud provider usage and licensing to ensure the proposal is compliant from the outset.

Quick Start

List all hard constraints from the project constraints registry.

Frequently Asked Questions about arch:maintain-constraints-registry

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

FAQPage Schema

What is a project constraints registry and why do I need one in YAML?▼

A project constraints registry is a centralized YAML structure for managing architectural guidelines. It ensures development consistency by capturing rules, rationales, and enforcement levels in a structured format.

How do I add a new hard constraint to a YAML governance registry?▼

You can add a new hard constraint to the YAML registry by defining an entry with a unique ID, category, rule, rationale, and setting the enforcement level to 'hard'. The schema guides defining new constraints.

How do I filter architectural constraints by enforcement level or category?▼

Filtering architectural constraints is done by querying the YAML registry based on enforcement types like hard or soft, or by specific categories. This allows quick retrieval of relevant project rules.

Can I update the rationale of an existing constraint without deleting it?▼

Yes, you can update the enforcement level or rationale of existing constraints without deleting them. This maintains a historical record while keeping the project governance registry current.

When do I need to manage project constraints as hard or soft rules?▼

You need to manage constraints as hard or soft rules when enforcing strict architectural guidelines versus flexible recommendations. Hard constraints block non-compliance, while soft constraints allow contextual deviations.