Agent skill
architectural-constraints
Critical requirement for [what the constraint enforces]. Reference when [situations where this applies].
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/architectural-constraints
SKILL.md
[Constraint Name] - CRITICAL REQUIREMENT
[One-line summary of the architectural principle.]
[Brief explanation of what this means and why it matters - 2-3 sentences max.]
What Violates This Constraint
1. [Violation Category 1]
// FORBIDDEN: [Description of what's wrong]
[code example]
Why it's wrong: [Explanation of consequences]
Correct approach:
// CORRECT: [Description of the fix]
[code example]
2. [Violation Category 2]
// FORBIDDEN: [Description]
[code example]
Why it's wrong: [Explanation]
Correct approach:
// CORRECT: [Description]
[code example]
Where [Constrained Code] IS Allowed
| Location | Allowed | Example |
|---|---|---|
[path/pattern] |
Yes | [Description of what's allowed] |
[path/pattern] |
Yes | [Description] |
[path/pattern] |
No | [Why not allowed] |
| Unit tests | No | Use [test helper] instead |
The Correct Pattern
All [type of code] MUST use [correct approach]:
// Import the helper
use [module]::[helper];
fn test_[feature]() {
// Create test context using the helper
let context = [helper]();
// Create entities/resources as needed for THIS test
let resource = [Resource]::new("[name]")
.with_property("[key]", [value]);
// Test the feature
assert!(context.[feature_works](resource));
}
Why This Matters
If [constrained code] assumes [specific things]:
- [Consequence 1]
- [Consequence 2]
- [Consequence 3]
- [Overall impact]
This requirement must survive context compaction. It is non-negotiable.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?