skills.rest
Vel-Labs
Vel-LabsOFFICIAL
Explore all skills by this author →
GitHub

core-enforcement

Enforce core enforcement logic against canonical contracts before adapter or UI work.

Updated Apr 26, 2026
Search Tags:#validation#enforcement#contracts#core#authority#clearintent
One-click install
npx skills add https://github.com/Vel-Labs/ClearIntent --skill core-enforcement
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: core-enforcement
Source: https://github.com/Vel-Labs/ClearIntent/tree/main/skills/core-enforcement
Command: npx skills add https://github.com/Vel-Labs/ClearIntent --skill core-enforcement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforce core enforcement logic against canonical contracts before adapters, demos, providers, UI, or deployment work.

Core Features & Use Cases

  • Define and enforce core governance for authority semantics in ClearIntent.
  • Ensure modular, reusable enforcement logic under packages/core, with strict boundaries from adapters and UIs.
  • Provide deterministic, testable behavior with clear error reporting and upgrade guidance.

Quick Start

Create a small, deterministic core enforcement module under packages/core and run the contract validation tests.

Frequently Asked Questions about core-enforcement

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

FAQPage Schema
How do I enforce contract validation before building adapters or UI layers?▼

Contract validation is enforced by applying core enforcement logic against canonical contracts under packages/core before any adapter, UI, provider, or deployment work begins. This ensures strict boundaries and deterministic behavior.

What is the best way to structure modular enforcement logic for ClearIntent contracts?▼

Structure modular enforcement logic as small, deterministic components under packages/core with clear interfaces. This architecture isolates core behavior from adapters and UIs, providing testable governance for authority semantics.

How do I test core enforcement logic for contract regressions?▼

Test core enforcement logic by placing regression tests under tests/core. These tests validate deterministic behavior and clear error reporting, ensuring core governance rules hold during contract upgrades and modifications.

Why should I avoid putting adapter or UI scope logic in core contract enforcement?▼

Keeping adapter and UI scope out of core contract enforcement prevents scope creep and maintains strict architectural boundaries. Core enforcement must remain modular and isolated to ensure deterministic, reusable validation.

Can I use core enforcement modules without explicit architecture documentation?▼

No, core enforcement modules require explicit documentation of architecture decisions. This documentation guides test coverage for core behavior and ensures deterministic enforcement logic remains maintainable during future contract upgrades.

When do I need to apply core enforcement validation in my deployment workflow?▼

Apply core enforcement validation at the very beginning of your workflow, before any demos, providers, UI, or deployment work. Validating canonical contracts first ensures downstream components build against compliant authority semantics.

Related Skills

Explore More Software Engineering Skills→
memorysavermemorysaver

openspec-sync-specs

Merge delta specs under openspec/changes into main specs.

Community
Intermediate
NUbivekNUbivek

sb

Run argument-based commands to manage Searchbar3 reliability and development tasks.

Community
Advanced
mwathibenmwathiben

bats-testing-patterns

Automate shell-script testing with Bats for CLI tools.

Community
Advanced
beomeodevbeomeodev

api-testing-patterns

Test REST, GraphQL, and microservice APIs with contract and integration patterns.

Community
Advanced