skills.rest
SujinHwang27
SujinHwang27COMMUNITY
Explore all skills by this author →
GitHub

design-data-contract

Inventory and classify agent OS files by ownership type into a data contract.

Updated Aug 23, 2026
Search Tags:#governance#access-control#file-ownership#data-ownership#domain-design#policy-design
One-click install
npx skills add https://github.com/SujinHwang27/agent-os-lab --skill design-data-contract
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-data-contract
Source: https://github.com/SujinHwang27/agent-os-lab/tree/main/agent-os-factory-v2.0/.claude/skills/design-data-contract
Command: npx skills add https://github.com/SujinHwang27/agent-os-lab --skill design-data-contract

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Defines who owns files in the OS design, clarifying ownership between user, system, and hybrids to prevent ambiguity and data loss.

Core Features & Use Cases

  • Inventory and classify persistent files by ownership type (user-owned, system-managed, hybrid).
  • Enforce a Golden Rule for user overrides to maintain integrity and safety.
  • Generate and maintain a domain-input/data-contract.md that codifies ownership decisions.

Quick Start

Define and apply data ownership rules for your OS by running the design-data-contract workflow to categorize files and write the resulting contract.

Frequently Asked Questions about design-data-contract

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

FAQPage Schema
What is a data contract for OS file ownership?▼

A data contract codifies data ownership boundaries for OS files by inventorying persistent files, classifying them by ownership type, and generating a machine-readable domain-input/data-contract.md artifact.

How do I define data ownership rules for agent OS files?▼

You define data ownership rules by executing a Step 1–5 design process that inventories persistent files, applies ownership rules, and produces a machine-readable domain-input/data-contract.md artifact.

When do I need to generate a data contract for domain inputs?▼

You need to generate a data contract when organizing domain inputs and outputs across OS designs to enforce clear file ownership boundaries and prevent ambiguity or data loss between user and system.

How does the Golden Rule for user overrides maintain file integrity?▼

The Golden Rule for user overrides enforces safety and integrity by ensuring user-managed changes do not corrupt system-managed files, maintaining clear ownership boundaries across hybrid data structures.

Does the data contract workflow require YAML frontmatter?▼

Yes, the data contract workflow requires YAML frontmatter with name and description fields to satisfy the structural requirements of the domain-input/data-contract.md artifact generation process.

What are the limitations of using a single data contract for hybrid file ownership?▼

Classifying hybrid file ownership requires careful application of the Golden Rule for user overrides, as ambiguous boundaries between user-owned and system-managed persistent files can still risk data loss if misapplied.

Related Skills

Explore More Legal & Compliance Skills→
understudylabsunderstudylabs
10

capture-evidence

Generate harness, metric, splits, and baseline artifacts from workloads.

Official
Advanced
EnigmaWUEnigmaWU
1

design-ddd-aggregates

Design DDD aggregates using Vaughn Vernon's 4 Rules of Aggregate Design.

Community
Advanced
Owl-ListenerOwl-Listener
157

consent-and-agency

Design consent and agency controls for AI features with governance artefacts.

Community
Intermediate
personamanagmentlayerpersonamanagmentlayer
41

data-mesh-expert

Design decentralized data systems using data mesh principles and governance frameworks.

Official
Advanced