design-identity

Design a user identity model with axes, personas, and privacy rules for the target OS.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/SujinHwang27/agent-os-lab --skill design-identity
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-identity
Source: https://github.com/SujinHwang27/agent-os-lab/tree/main/agent-os-factory-v2.0/.claude/skills/design-identity
Command: npx skills add https://github.com/SujinHwang27/agent-os-lab --skill design-identity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Defines a scalable, privacy-conscious user identity model to power a domain-specific OS, ensuring consistent context, personas, and data governance.

Core Features & Use Cases

  • Identity axes design: establish 4-7 axes (e.g., capability inventory, goals, preferences, target list, relationship map) to drive personalization and access controls.
  • Foundation and governance: designate a foundation file (e.g., experience-library.md) and implement privacy rules for private data.
  • Persona variants: outline user types with detection logic and workflow adjustments.

Quick Start

Draft the identity model by specifying identity axes, foundation file, persona variants, and privacy rules, then deliver domain-input/identity-model.md.

Frequently Asked Questions about design-identity

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

FAQPage Schema
How do I design a user identity model for a context-aware OS?

A user identity model for a context-aware OS requires defining 4-7 identity axes like capability inventory and goals to drive personalization, designating a foundation file, and establishing privacy rules for data governance.

What are identity axes and how do they power personalization in domain onboarding?

Identity axes are defined dimensions like goals, preferences, and relationship maps established during onboarding to drive personalization and access controls within a domain-specific OS.

How do I set up privacy rules and persona variants for domain-specific user models?

You set up privacy rules by designating a foundation file like experience-library.md and implementing data governance, while persona variants are outlined by defining user types with detection logic and workflow adjustments.

What is the best way to structure an identity model output file for context-aware systems?

The best way to structure identity model output is to deliver domain-input/identity-model.md containing the context file schema, empty-state behavior, and reading/writing rules per the designated template.

Do I need any dependencies to create a scalable user identity model?

No dependencies are required to create a scalable user identity model; you draft identity axes, foundation files, persona variants, and privacy rules directly into the output template.

When should I establish empty-state behavior in my user identity model?

Empty-state behavior should be established when defining the context file schema in the identity model to ensure the OS handles missing user data gracefully during initial onboarding.