opencode-skills-collection 4.1.3 → 4.1.4

package/bundled-skills/soroban-storage-ttl-lifecycle/SKILL.md

@@ -0,0 +1,118 @@
+---
+name: soroban-storage-ttl-lifecycle
+description: 'Soroban ledger state rent and TTL extension register: live state tracking, bump thresholds, rent fee reserves, and archive boundaries.'
+category: engineering
+risk: safe
+source: self
+source_type: self
+date_added: "2026-10-01"
+author: Ranjeet2063
+tags: [soroban, storage, ttl, state-archival, stellar, gas, rust]
+tools: []
+source_repo: Ranjeet2063/agentic-awesome-skills
+---
+
+# Soroban Storage TTL & Rent Lifecycle
+
+**What it is:** Tracks storage TTL exhaustion boundaries, automated ledger rent extensions, and archival prevention policies for production Soroban contracts.
+
+## Overview
+
+Provides a standardized, auditable framework and data model for **Soroban Storage TTL & Rent Lifecycle** operations across distributed engineering and decentralized application systems.
+
+## When to Use This Skill
+
+- When formalizing architectural contracts, security invariants, or operational limits for Soroban Storage TTL & Rent Lifecycle.
+- When cross-functional review is required between protocol developers, smart contract auditors, and AI engineering agents.
+- When generating reproducible CSV, SQL DDL, JSON Schema, and Notion property registers for tracking compliance.
+
+## How It Works
+
+1. Define the parameters, thresholds, and identity bindings required for the target operational register.
+2. Select appropriate boundary enforcement values from validated enum select sets.
+3. Export standardized artifacts (CSV table, SQL DDL, JSON Schema) to integrate into validation CI pipelines.
+
+## Field Reference
+
+| # | Field Name | Type | SQL Type | JSON Schema Type | Notion Property Type | Example Value |
+|---|------------|------|----------|------------------|----------------------|---------------|
+| 1 | TTL Monitoring ID | `id` | `SERIAL PRIMARY KEY` | `integer` | Text | `TTL-001` |
+| 2 | Contract Address | `text` | `VARCHAR(56)` | `string` | Text | `CVLT...` |
+| 3 | Storage Tier Lifetime | `select` | `VARCHAR(32)` | `string` | Select | `Persistent` |
+| 4 | Key Identifier Name | `text` | `VARCHAR(64)` | `string` | Text | `UserShareBalance` |
+| 5 | Current TTL Remaining Ledgers | `number` | `INTEGER` | `number` | Number | `125000` |
+| 6 | Minimum Threshold Ledgers | `number` | `INTEGER` | `number` | Number | `50000` |
+| 7 | Auto-Bump Amount Ledgers | `number` | `INTEGER` | `number` | Number | `250000` |
+| 8 | Rent Fee Budget XLM | `currency` | `NUMERIC(14,7)` | `number` | Number | `10.0000000` |
+| 9 | Archival Risk Status | `select` | `VARCHAR(32)` | `string` | Select | `Safe Extended` |
+| 10 | Last Extended Ledger | `number` | `BIGINT` | `number` | Number | `54820100` |
+| 11 | Monitoring Audit Date | `date` | `DATE` | `string, format: date` | Date | `2026-10-01` |
+
+## Select Options
+
+**Storage Tier Lifetime**
+
+```
+Instance | Persistent | Temporary
+```
+
+**Archival Risk Status**
+
+```
+Safe Extended | Threshold Reached | Critical Expiring | Archived
+```
+
+## Relations
+
+- `Audit Reference` -> links to the formal review documentation or test repository.
+- `Target Architecture` -> links to the deployed contract or autonomous agent runtime component.
+
+## Examples
+
+**Prompt**
+
+```
+How do I configure and track Soroban Storage TTL & Rent Lifecycle for our production environment?
+```
+
+**Recommended Next Step**
+
+> Generate the unified field schema, SQL DDL migration, and JSON validation schema to register into your system catalog.
+>
+> Workflow: Define criteria -> Run automated verification -> Record baseline -> Monitor invariants.
+
+## Best Practices
+
+- Enforce strict typing on numerical bounds and currency amounts; avoid unstructured free-text fields for critical states.
+- Re-run validation test suites on every state-altering commit or parameter change.
+- Keep example data synthetic and isolated from production cryptographic keys or private endpoints.
+
+## Limitations
+
+- Provides architectural specifications, data models, and verification schemas; does not execute direct transaction signing without authorized external tooling.
+- Requires network connectivity and valid RPC credentials when querying on-chain states.
+
+## Security & Safety Notes
+
+- All parameters declare `risk: safe`. No unauthorized state modification or privileged credential access is performed.
+- Use synthetic dummy keys and mock addresses in test suites and local verification scripts.
+
+## Common Pitfalls
+
+- **Problem:** Mismatched decimal precision between contract runtime and database register.
+  **Solution:** Always verify decimals using the explicit field mapping in this reference.
+- **Problem:** Missing authorization checks prior to state update.
+  **Solution:** Cross-validate against the Security Audit register before deployment.
+
+## Related Skills
+
+- @soroban-contract-audit - provides the security checklist and vulnerability categorization.
+- @soroban-oracle-data-feed-audit - covers oracle heartbeat and stale-price handling.
+- @web3-rate-limiting-circuit-breaker - provides operational guardrails and threshold breakers.
+
+## Reusable Prompt
+
+```
+I want to establish a verified Soroban Storage TTL & Rent Lifecycle register for our production protocol.
+Guide me through the required field parameters and output the corresponding SQL DDL and JSON Schema.
+```

package/bundled-skills/soroban-token-minter/SKILL.md

@@ -0,0 +1,124 @@
+---
+name: soroban-token-minter
+description: 'Soroban SEP-41 token contract architecture register: admin control, supply caps, metadata standard, and transfer event emissions on Stellar.'
+category: engineering
+risk: safe
+source: self
+source_type: self
+date_added: "2026-10-01"
+author: Ranjeet2063
+tags: [stellar, soroban, token, sep-41, defi, web3, rust]
+tools: []
+source_repo: Ranjeet2063/agentic-awesome-skills
+---
+
+# Soroban Token Minting Architecture
+
+**What it is:** Maintains technical specifications, supply parameters, and administrative controls for SEP-41 compliant fungible token implementations on Soroban.
+
+## Overview
+
+Provides a standardized, auditable framework and data model for **Soroban Token Minting Architecture** operations across distributed engineering and decentralized application systems.
+
+## When to Use This Skill
+
+- When formalizing architectural contracts, security invariants, or operational limits for Soroban Token Minting Architecture.
+- When cross-functional review is required between protocol developers, smart contract auditors, and AI engineering agents.
+- When generating reproducible CSV, SQL DDL, JSON Schema, and Notion property registers for tracking compliance.
+
+## How It Works
+
+1. Define the parameters, thresholds, and identity bindings required for the target operational register.
+2. Select appropriate boundary enforcement values from validated enum select sets.
+3. Export standardized artifacts (CSV table, SQL DDL, JSON Schema) to integrate into validation CI pipelines.
+
+## Field Reference
+
+| # | Field Name | Type | SQL Type | JSON Schema Type | Notion Property Type | Example Value |
+|---|------------|------|----------|------------------|----------------------|---------------|
+| 1 | Token Registry ID | `id` | `SERIAL PRIMARY KEY` | `integer` | Text | `TOK-001` |
+| 2 | Token Symbol | `text` | `VARCHAR(12)` | `string` | Text | `FOX` |
+| 3 | Token Name | `text` | `VARCHAR(64)` | `string` | Text | `GrantFox Utility Token` |
+| 4 | Decimals | `number` | `INTEGER` | `number` | Number | `7` |
+| 5 | Total Supply Cap | `currency` | `NUMERIC(24,7)` | `number` | Number | `10000000.0000000` |
+| 6 | Admin Address | `text` | `VARCHAR(56)` | `string` | Text | `GA7QY...` |
+| 7 | SEP-41 Interface Compliant | `select` | `VARCHAR(16)` | `string` | Select | `Yes` |
+| 8 | Clawback Enabled | `select` | `VARCHAR(16)` | `string` | Select | `No` |
+| 9 | Mint Rate Limit Per Epoch | `number` | `INTEGER` | `number` | Number | `50000` |
+| 10 | Contract Lifecycle State | `select` | `VARCHAR(32)` | `string` | Select | `Active` |
+| 11 | Deployment Timestamp | `date` | `DATE` | `string, format: date` | Date | `2026-10-01` |
+
+## Select Options
+
+**SEP-41 Interface Compliant**
+
+```
+Yes | No
+```
+
+**Clawback Enabled**
+
+```
+Yes | No
+```
+
+**Contract Lifecycle State**
+
+```
+Draft | Testnet Deployed | Audited | Mainnet Live | Paused | Deprecated
+```
+
+## Relations
+
+- `Audit Reference` -> links to the formal review documentation or test repository.
+- `Target Architecture` -> links to the deployed contract or autonomous agent runtime component.
+
+## Examples
+
+**Prompt**
+
+```
+How do I configure and track Soroban Token Minting Architecture for our production environment?
+```
+
+**Recommended Next Step**
+
+> Generate the unified field schema, SQL DDL migration, and JSON validation schema to register into your system catalog.
+>
+> Workflow: Define criteria -> Run automated verification -> Record baseline -> Monitor invariants.
+
+## Best Practices
+
+- Enforce strict typing on numerical bounds and currency amounts; avoid unstructured free-text fields for critical states.
+- Re-run validation test suites on every state-altering commit or parameter change.
+- Keep example data synthetic and isolated from production cryptographic keys or private endpoints.
+
+## Limitations
+
+- Provides architectural specifications, data models, and verification schemas; does not execute direct transaction signing without authorized external tooling.
+- Requires network connectivity and valid RPC credentials when querying on-chain states.
+
+## Security & Safety Notes
+
+- All parameters declare `risk: safe`. No unauthorized state modification or privileged credential access is performed.
+- Use synthetic dummy keys and mock addresses in test suites and local verification scripts.
+
+## Common Pitfalls
+
+- **Problem:** Mismatched decimal precision between contract runtime and database register.
+  **Solution:** Always verify decimals using the explicit field mapping in this reference.
+- **Problem:** Missing authorization checks prior to state update.
+  **Solution:** Cross-validate against the Security Audit register before deployment.
+
+## Related Skills
+
+- @soroban-contract-audit - provides the security checklist and vulnerability categorization.
+- @soroban-liquidity-pool - covers AMM invariant and LP-share modelling.
+- @stellar-anchor-integration - covers SEP-10 and SEP-24 anchor compliance flows.
+
+## Reusable Prompt
+
+```
+I want to establish a verified Soroban Token Minting Architecture register for our production protocol.
+Guide me through the required field parameters and output the corresponding SQL DDL and JSON Schema.
+```

package/bundled-skills/stellar-anchor-integration/SKILL.md

@@ -0,0 +1,136 @@
+---
+name: stellar-anchor-integration
+description: 'Stellar anchor protocol compliance register: SEP-10 web authentication, SEP-24 interactive deposit and withdrawal, and KYC lifecycle.'
+category: engineering
+risk: safe
+source: self
+source_type: self
+date_added: "2026-10-01"
+author: Ranjeet2063
+tags: [stellar, sep-10, sep-24, anchor, on-ramp, off-ramp, fintech]
+tools: []
+source_repo: Ranjeet2063/agentic-awesome-skills
+---
+
+# Stellar Anchor Protocol Integration
+
+**What it is:** Manages regulatory and technical conformance for Stellar Anchor protocols including SEP-10 challenge signing and SEP-24 interactive fund flows.
+
+## Overview
+
+Provides a standardized, auditable framework and data model for **Stellar Anchor Protocol Integration** operations across distributed engineering and decentralized application systems.
+
+## When to Use This Skill
+
+- When formalizing architectural contracts, security invariants, or operational limits for Stellar Anchor Protocol Integration.
+- When cross-functional review is required between protocol developers, smart contract auditors, and AI engineering agents.
+- When generating reproducible CSV, SQL DDL, JSON Schema, and Notion property registers for tracking compliance.
+
+## How It Works
+
+1. Define the parameters, thresholds, and identity bindings required for the target operational register.
+2. Select appropriate boundary enforcement values from validated enum select sets.
+3. Export standardized artifacts (CSV table, SQL DDL, JSON Schema) to integrate into validation CI pipelines.
+
+## Field Reference
+
+| # | Field Name | Type | SQL Type | JSON Schema Type | Notion Property Type | Example Value |
+|---|------------|------|----------|------------------|----------------------|---------------|
+| 1 | Anchor Service ID | `id` | `SERIAL PRIMARY KEY` | `integer` | Text | `ANC-001` |
+| 2 | Anchor Domain | `text` | `VARCHAR(128)` | `string` | Text | `anchor.stellar-gateway.org` |
+| 3 | TOML Endpoint Status | `select` | `VARCHAR(32)` | `string` | Select | `Active 200 OK` |
+| 4 | SEP-10 JWT Issuer | `text` | `VARCHAR(56)` | `string` | Text | `GCAUTH...` |
+| 5 | SEP-24 Interactive Deposit Enabled | `select` | `VARCHAR(16)` | `string` | Select | `Yes` |
+| 6 | SEP-38 Quote Server Active | `select` | `VARCHAR(16)` | `string` | Select | `Yes` |
+| 7 | Supported Asset Codes | `text` | `VARCHAR(64)` | `string` | Text | `USDC, EURC, NPRC` |
+| 8 | KYC Compliance Level | `select` | `VARCHAR(32)` | `string` | Select | `Tier 2 Enhanced` |
+| 9 | Webhook Callback Latency Ms | `number` | `INTEGER` | `number` | Number | `120` |
+| 10 | Integration Health | `select` | `VARCHAR(32)` | `string` | Select | `Operational` |
+| 11 | Audit Review Date | `date` | `DATE` | `string, format: date` | Date | `2026-10-01` |
+
+## Select Options
+
+**TOML Endpoint Status**
+
+```
+Active 200 OK | Degraded | Unreachable
+```
+
+**SEP-24 Interactive Deposit Enabled**
+
+```
+Yes | No
+```
+
+**SEP-38 Quote Server Active**
+
+```
+Yes | No
+```
+
+**KYC Compliance Level**
+
+```
+Tier 0 None | Tier 1 Basic | Tier 2 Enhanced | Corporate Institutional
+```
+
+**Integration Health**
+
+```
+Operational | Maintenance | Deprecated
+```
+
+## Relations
+
+- `Audit Reference` -> links to the formal review documentation or test repository.
+- `Target Architecture` -> links to the deployed contract or autonomous agent runtime component.
+
+## Examples
+
+**Prompt**
+
+```
+How do I configure and track Stellar Anchor Protocol Integration for our production environment?
+```
+
+**Recommended Next Step**
+
+> Generate the unified field schema, SQL DDL migration, and JSON validation schema to register into your system catalog.
+>
+> Workflow: Define criteria -> Run automated verification -> Record baseline -> Monitor invariants.
+
+## Best Practices
+
+- Enforce strict typing on numerical bounds and currency amounts; avoid unstructured free-text fields for critical states.
+- Re-run validation test suites on every state-altering commit or parameter change.
+- Keep example data synthetic and isolated from production cryptographic keys or private endpoints.
+
+## Limitations
+
+- Provides architectural specifications, data models, and verification schemas; does not execute direct transaction signing without authorized external tooling.
+- Requires network connectivity and valid RPC credentials when querying on-chain states.
+
+## Security & Safety Notes
+
+- All parameters declare `risk: safe`. No unauthorized state modification or privileged credential access is performed.
+- Use synthetic dummy keys and mock addresses in test suites and local verification scripts.
+
+## Common Pitfalls
+
+- **Problem:** Mismatched decimal precision between contract runtime and database register.
+  **Solution:** Always verify decimals using the explicit field mapping in this reference.
+- **Problem:** Missing authorization checks prior to state update.
+  **Solution:** Cross-validate against the Security Audit register before deployment.
+
+## Related Skills
+
+- @stellar-escrow-timelock - covers conditional escrow and timelock settlement.
+- @soroban-token-minter - covers SEP-41 token supply, admin and event modelling.
+- @cross-chain-relayer-audit - covers message hashes, nonces and quorum proofs.
+
+## Reusable Prompt
+
+```
+I want to establish a verified Stellar Anchor Protocol Integration register for our production protocol.
+Guide me through the required field parameters and output the corresponding SQL DDL and JSON Schema.
+```

package/bundled-skills/stellar-asset-clawback-compliance/SKILL.md

@@ -0,0 +1,118 @@
+---
+name: stellar-asset-clawback-compliance
+description: 'Regulated Stellar asset clawback architecture register: issuer authorization flags, claimable balance revocations, and regulatory audit trail.'
+category: engineering
+risk: safe
+source: self
+source_type: self
+date_added: "2026-10-01"
+author: Ranjeet2063
+tags: [stellar, clawback, compliance, fintech, regtech, security]
+tools: []
+source_repo: Ranjeet2063/agentic-awesome-skills
+---
+
+# Stellar Asset Clawback Compliance
+
+**What it is:** Provides an immutable compliance record and operational audit register for executing regulatory clawbacks on CAP-35 compliant Stellar assets.
+
+## Overview
+
+Provides a standardized, auditable framework and data model for **Stellar Asset Clawback Compliance** operations across distributed engineering and decentralized application systems.
+
+## When to Use This Skill
+
+- When formalizing architectural contracts, security invariants, or operational limits for Stellar Asset Clawback Compliance.
+- When cross-functional review is required between protocol developers, smart contract auditors, and AI engineering agents.
+- When generating reproducible CSV, SQL DDL, JSON Schema, and Notion property registers for tracking compliance.
+
+## How It Works
+
+1. Define the parameters, thresholds, and identity bindings required for the target operational register.
+2. Select appropriate boundary enforcement values from validated enum select sets.
+3. Export standardized artifacts (CSV table, SQL DDL, JSON Schema) to integrate into validation CI pipelines.
+
+## Field Reference
+
+| # | Field Name | Type | SQL Type | JSON Schema Type | Notion Property Type | Example Value |
+|---|------------|------|----------|------------------|----------------------|---------------|
+| 1 | Clawback Case ID | `id` | `SERIAL PRIMARY KEY` | `integer` | Text | `CLAW-001` |
+| 2 | Asset Code | `text` | `VARCHAR(12)` | `string` | Text | `USDC` |
+| 3 | Issuer Account ID | `text` | `VARCHAR(56)` | `string` | Text | `GISS...` |
+| 4 | Target Account ID | `text` | `VARCHAR(56)` | `string` | Text | `GTGT...` |
+| 5 | Clawback Amount | `currency` | `NUMERIC(24,7)` | `number` | Number | `5000.0000000` |
+| 6 | Clawback Enabled Flag Verified | `select` | `VARCHAR(16)` | `string` | Select | `Yes` |
+| 7 | Legal Regulatory Reference | `text` | `VARCHAR(128)` | `string` | Text | `COURT-ORD-2026-0914` |
+| 8 | Clawback Claimable Balance ID | `text` | `VARCHAR(64)` | `string` | Text | `00000000...` |
+| 9 | Action Execution State | `select` | `VARCHAR(32)` | `string` | Select | `Executed Confirmed` |
+| 10 | Compliance Officer Signoff | `text` | `VARCHAR(64)` | `string` | Text | `Ranjeet Kumar Sah` |
+| 11 | Execution Timestamp | `date` | `DATE` | `string, format: date` | Date | `2026-10-01` |
+
+## Select Options
+
+**Clawback Enabled Flag Verified**
+
+```
+Yes | No
+```
+
+**Action Execution State**
+
+```
+Initiated Review | Executed Confirmed | Rejected Invalid | Reverted
+```
+
+## Relations
+
+- `Audit Reference` -> links to the formal review documentation or test repository.
+- `Target Architecture` -> links to the deployed contract or autonomous agent runtime component.
+
+## Examples
+
+**Prompt**
+
+```
+How do I configure and track Stellar Asset Clawback Compliance for our production environment?
+```
+
+**Recommended Next Step**
+
+> Generate the unified field schema, SQL DDL migration, and JSON validation schema to register into your system catalog.
+>
+> Workflow: Define criteria -> Run automated verification -> Record baseline -> Monitor invariants.
+
+## Best Practices
+
+- Enforce strict typing on numerical bounds and currency amounts; avoid unstructured free-text fields for critical states.
+- Re-run validation test suites on every state-altering commit or parameter change.
+- Keep example data synthetic and isolated from production cryptographic keys or private endpoints.
+
+## Limitations
+
+- Provides architectural specifications, data models, and verification schemas; does not execute direct transaction signing without authorized external tooling.
+- Requires network connectivity and valid RPC credentials when querying on-chain states.
+
+## Security & Safety Notes
+
+- All parameters declare `risk: safe`. No unauthorized state modification or privileged credential access is performed.
+- Use synthetic dummy keys and mock addresses in test suites and local verification scripts.
+
+## Common Pitfalls
+
+- **Problem:** Mismatched decimal precision between contract runtime and database register.
+  **Solution:** Always verify decimals using the explicit field mapping in this reference.
+- **Problem:** Missing authorization checks prior to state update.
+  **Solution:** Cross-validate against the Security Audit register before deployment.
+
+## Related Skills
+
+- @stellar-anchor-integration - covers SEP-10 and SEP-24 anchor compliance flows.
+- @stellar-multisig-threshold-coordinator - covers signer weights and threshold coordination.
+- @soroban-contract-audit - provides the security checklist and vulnerability categorization.
+
+## Reusable Prompt
+
+```
+I want to establish a verified Stellar Asset Clawback Compliance register for our production protocol.
+Guide me through the required field parameters and output the corresponding SQL DDL and JSON Schema.
+```

package/bundled-skills/stellar-escrow-timelock/SKILL.md

@@ -0,0 +1,118 @@
+---
+name: stellar-escrow-timelock
+description: 'Decentralized conditional escrow and timelock contract register: multi-signature release conditions, clawback expiry, and settlement triggers.'
+category: engineering
+risk: safe
+source: self
+source_type: self
+date_added: "2026-10-01"
+author: Ranjeet2063
+tags: [stellar, escrow, timelock, soroban, multisig, settlement]
+tools: []
+source_repo: Ranjeet2063/agentic-awesome-skills
+---
+
+# Stellar Escrow and Timelock Architecture
+
+**What it is:** Provides an auditable framework for conditional asset locking, timelock boundary verifications, and multi-signature release triggers on Stellar.
+
+## Overview
+
+Provides a standardized, auditable framework and data model for **Stellar Escrow and Timelock Architecture** operations across distributed engineering and decentralized application systems.
+
+## When to Use This Skill
+
+- When formalizing architectural contracts, security invariants, or operational limits for Stellar Escrow and Timelock Architecture.
+- When cross-functional review is required between protocol developers, smart contract auditors, and AI engineering agents.
+- When generating reproducible CSV, SQL DDL, JSON Schema, and Notion property registers for tracking compliance.
+
+## How It Works
+
+1. Define the parameters, thresholds, and identity bindings required for the target operational register.
+2. Select appropriate boundary enforcement values from validated enum select sets.
+3. Export standardized artifacts (CSV table, SQL DDL, JSON Schema) to integrate into validation CI pipelines.
+
+## Field Reference
+
+| # | Field Name | Type | SQL Type | JSON Schema Type | Notion Property Type | Example Value |
+|---|------------|------|----------|------------------|----------------------|---------------|
+| 1 | Escrow Agreement ID | `id` | `SERIAL PRIMARY KEY` | `integer` | Text | `ESC-001` |
+| 2 | Depositor Account | `text` | `VARCHAR(56)` | `string` | Text | `GDEP...` |
+| 3 | Beneficiary Account | `text` | `VARCHAR(56)` | `string` | Text | `GBEN...` |
+| 4 | Arbitrator Account | `text` | `VARCHAR(56)` | `string` | Text | `GARB...` |
+| 5 | Locked Asset Code | `text` | `VARCHAR(12)` | `string` | Text | `USDC` |
+| 6 | Locked Principal Amount | `currency` | `NUMERIC(24,7)` | `number` | Number | `15000.0000000` |
+| 7 | Unlock Timestamp Epoch | `number` | `BIGINT` | `number` | Number | `1790800000` |
+| 8 | Dispute Resolution Pathway | `select` | `VARCHAR(64)` | `string` | Select | `2-of-3 Multi-Sig` |
+| 9 | Clawback Grace Period Days | `number` | `INTEGER` | `number` | Number | `14` |
+| 10 | Settlement Status | `select` | `VARCHAR(32)` | `string` | Select | `Locked in Escrow` |
+| 11 | Creation Date | `date` | `DATE` | `string, format: date` | Date | `2026-10-01` |
+
+## Select Options
+
+**Dispute Resolution Pathway**
+
+```
+2-of-3 Multi-Sig | Automated Time Expiry | Arbitrator Sole Ruling
+```
+
+**Settlement Status**
+
+```
+Pending Deposit | Locked in Escrow | In Dispute | Released | Refunded
+```
+
+## Relations
+
+- `Audit Reference` -> links to the formal review documentation or test repository.
+- `Target Architecture` -> links to the deployed contract or autonomous agent runtime component.
+
+## Examples
+
+**Prompt**
+
+```
+How do I configure and track Stellar Escrow and Timelock Architecture for our production environment?
+```
+
+**Recommended Next Step**
+
+> Generate the unified field schema, SQL DDL migration, and JSON validation schema to register into your system catalog.
+>
+> Workflow: Define criteria -> Run automated verification -> Record baseline -> Monitor invariants.
+
+## Best Practices
+
+- Enforce strict typing on numerical bounds and currency amounts; avoid unstructured free-text fields for critical states.
+- Re-run validation test suites on every state-altering commit or parameter change.
+- Keep example data synthetic and isolated from production cryptographic keys or private endpoints.
+
+## Limitations
+
+- Provides architectural specifications, data models, and verification schemas; does not execute direct transaction signing without authorized external tooling.
+- Requires network connectivity and valid RPC credentials when querying on-chain states.
+
+## Security & Safety Notes
+
+- All parameters declare `risk: safe`. No unauthorized state modification or privileged credential access is performed.
+- Use synthetic dummy keys and mock addresses in test suites and local verification scripts.
+
+## Common Pitfalls
+
+- **Problem:** Mismatched decimal precision between contract runtime and database register.
+  **Solution:** Always verify decimals using the explicit field mapping in this reference.
+- **Problem:** Missing authorization checks prior to state update.
+  **Solution:** Cross-validate against the Security Audit register before deployment.
+
+## Related Skills
+
+- @stellar-anchor-integration - covers SEP-10 and SEP-24 anchor compliance flows.
+- @soroban-contract-audit - provides the security checklist and vulnerability categorization.
+- @cross-chain-relayer-audit - covers message hashes, nonces and quorum proofs.
+
+## Reusable Prompt
+
+```
+I want to establish a verified Stellar Escrow and Timelock Architecture register for our production protocol.
+Guide me through the required field parameters and output the corresponding SQL DDL and JSON Schema.
+```