digital-identity-design

Design digital identity systems and wallet architectures with W3C Verifiable Credentials and NIST 800-63 compliance.

8|Updated Nov 26, 2025
One-click install
npx skills add https://github.com/infiquetra/infiquetra-claude-plugins --skill digital-identity-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: digital-identity-design
Source: https://github.com/infiquetra/infiquetra-claude-plugins/tree/main/plugins/identity-toolkit/skills/digital-identity-design
Command: npx skills add https://github.com/infiquetra/infiquetra-claude-plugins --skill digital-identity-design

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you design robust digital identity systems and wallet architectures, ensuring compliance with modern standards and regulations.

Core Features & Use Cases

  • System Design: Architect identity solutions using W3C VC, DIDs, ISO 18013-5, and NIST 800-63.
  • Wallet Architectures: Choose between custodial, non-custodial, or hybrid models.
  • Compliance: Integrate KYC/AML flows and adhere to GDPR.
  • Use Case: You need to design a new digital wallet that supports verifiable credentials and adheres to NIST 800-63 identity assurance levels.

Quick Start

Use the digital-identity-design skill to explore custodial wallet architecture patterns.

Frequently Asked Questions about digital-identity-design

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

FAQPage Schema
How do I design a digital identity system that complies with W3C Verifiable Credentials and DIDs?

Digital identity systems compliant with W3C Verifiable Credentials and Decentralized Identifiers require structured credential schemas mapped to DID resolution flows. This Skill designs architectures integrating standards alongside ISO 18013-5 and NIST 800-63 assurance levels.

What is the difference between custodial and non-custodial wallet architectures for verifiable credentials?

Custodial wallets manage cryptographic keys server-side, while non-custodial wallets store keys locally on user devices. This Skill helps evaluate custodial, non-custodial, and hybrid wallet models to determine the right architecture for your identity verification needs.

How do I integrate KYC and AML processes while ensuring GDPR compliance in a digital identity wallet?

Integrating KYC/AML flows with GDPR compliance requires embedding data minimization and consent management into the identity verification process. This Skill designs wallet architectures aligning regulatory requirements with NIST 800-63 assurance levels.

When do I need NIST 800-63 identity assurance levels in a decentralized identity system?

NIST 800-63 assurance levels are needed when your digital identity system requires specific Identity Assurance Level thresholds for risk mitigation. This Skill designs identity verification processes mapped to appropriate NIST 800-63 compliance tiers.

Can I use a hybrid wallet model to support both W3C Verifiable Credentials and ISO 18013-5?

A hybrid wallet model can support both W3C Verifiable Credentials and ISO 18013-5 by combining local secure enclaves with cloud backup. This Skill designs hybrid architectures balancing decentralized identifiers with mDL compliance requirements.

What are the limitations of non-custodial wallets for GDPR compliance in digital identity systems?

Non-custodial wallets limit GDPR compliance capabilities because user-controlled keys prevent centralized data deletion or portability enforcement. This Skill helps navigate these constraints by designing hybrid architectures that balance regulatory compliance with user sovereignty.