agents-united 0.5.0

package/registry/skills/database-design/SKILL.md

@@ -0,0 +1,135 @@
+---
+name: database-design
+description: Production-grade Database Design playbook for high-throughput
+  transactional schemas, indexing, and migrations.
+metadata:
+  author: agents-united
+  version: 2.0.0
+  icon: 🗄️
+disable-slash-command: true
+---
+
+# Relational & NoSQL Database Schema Design
+
+## Overview & Purpose
+The Relational & NoSQL Database Schema Design skill provides a deterministic, battle-tested framework for executing database-design processes across the Agents United multi-agent ecosystem.
+
+Following this skill ensures high quality, zero-regression execution, rigorous testing gates, and seamless cross-functional team alignment.
+
+## Execution Triggers & Prerequisites
+### Execution Triggers
+- Direct request or workflow step invoking database-design.
+- Auditing, implementing, or standardizing database-design procedures.
+- Addressing technical debt, architectural reviews, or production readiness gates.
+- Preparing pull requests or automated release validations.
+
+### Prerequisites
+- Active project repository workspace with version control configured.
+- Operational testing, typechecking, and build toolchains.
+- Domain requirements, architectural constraints, or user stories defined.
+- Clean git working tree before beginning execution.
+
+## Input & Output Requirements
+### Inputs
+| Parameter | Type | Required | Description |
+|---|---|---|---|
+| `target_scope` | String | Yes | Target module, service, component, or file path |
+| `config` | Object | Optional | Specific domain configurations, thresholds, and options |
+| `output_dir` | Directory Path | Optional | Destination directory for generated artifacts and reports |
+| `strict_mode` | Boolean | Optional | Enforce strict zero-warning validation and high test coverage |
+
+### Outputs
+| Artifact | Path / Format | Description |
+|---|---|---|
+| Specification Document | `docs/database-design/spec.md` | Full technical specification and architectural plan |
+| Implementation Files | `src/database-design/*` | Production-ready source code, tests, and configurations |
+| Execution Report | `reports/database-design/summary.json` | Verification metrics, test results, and audit summary |
+
+## Step-by-Step Execution Runbook
+
+### Phase 1: Entity-Relationship Modeling & Normalization
+1. Map business entities, cardinality (1:1, 1:N, N:M), and ownership relationships.
+2. Normalize relational schema to Third Normal Form (3NF) to eliminate data redundancy.
+3. Identify strategic denormalization opportunities for read-heavy query paths.
+4. Choose appropriate primary key strategy: UUIDv7 / ULID (distributed) vs BIGINT IDENTITY.
+5. Design foreign key constraints with explicit ON DELETE RESTRICT / CASCADE policies.
+
+### Phase 2: Index Strategy & Partitioning Architecture
+1. Analyze query access patterns (filter predicates, join columns, order-by clauses).
+2. Design composite B-tree indexes following Equality-Range-Sort (ESR) rule.
+3. Implement partial/filtered indexes for status flags (WHERE status = 'active').
+4. Configure range/hash partitioning on high-volume tables (>10M rows per month).
+5. Audit index overhead against write-amplification tradeoffs.
+
+### Phase 3: Migration Script Authoring & Versioning
+1. Write deterministic, bidirectional migration scripts (up.sql and down.sql).
+2. Wrap DDL operations in atomic transactions where supported by database engine.
+3. Use lock-free DDL patterns (e.g. CREATE INDEX CONCURRENTLY in PostgreSQL).
+4. Ensure zero-downtime expand-and-contract pattern for schema column renames/drops.
+5. Test migration rollback (down) in isolated staging environment.
+
+### Phase 4: Query Optimization & EXPLAIN ANALYZE Verification
+1. Execute EXPLAIN (ANALYZE, BUFFERS) on critical path database queries.
+2. Verify elimination of sequential table scans on multi-million row datasets.
+3. Verify connection pool sizing (HikariCP/pgpool) against database max connections.
+4. Set statement timeouts to prevent long-running runaway transactions.
+5. Audit query memory consumption during batch processing.
+
+### Phase 5: Data Integrity & Backup Validation
+1. Define database checkpointing and Point-In-Time-Recovery (PITR) policies.
+2. Implement automated data corruption and constraint integrity checks.
+3. Update ORM entity schema mappings (Prisma, TypeORM, Drizzle) and generate typings.
+4. Commit schema migrations to version control.
+5. Deploy migrations to production database cluster.
+
+## Code & Configuration Exemplars
+
+### Exemplar 1: Relational & NoSQL Database Schema Design Configuration & Specification
+```yaml
+CREATE TABLE orders (
+  id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
+  tenant_id UUID NOT NULL REFERENCES tenants(id) ON DELETE RESTRICT,
+  customer_id UUID NOT NULL REFERENCES customers(id),
+  total_cents BIGINT NOT NULL CHECK (total_cents >= 0),
+  status VARCHAR(32) NOT NULL DEFAULT 'pending',
+  created_at TIMESTAMPTZ NOT NULL DEFAULT NOW(),
+  updated_at TIMESTAMPTZ NOT NULL DEFAULT NOW()
+);
+CREATE INDEX idx_orders_tenant_status_created ON orders (tenant_id, status, created_at DESC);
+```
+
+### Exemplar 2: Relational & NoSQL Database Schema Design TypeScript Type Contract
+```typescript
+export interface MigrationStep {
+  version: number;
+  name: string;
+  up: string;
+  down: string;
+  transactional: boolean;
+  reversible: boolean;
+}
+```
+
+## Edge Cases & Error Recovery Procedures
+
+### Scenario A: Validation Failure in Relational & NoSQL Database Schema Design
+1. **Diagnosis**: Static analysis, typechecking, or unit tests fail validation rules during execution.
+2. **Recovery Protocol**:
+   - Step 1: Inspect detailed error log output in test/build terminal.
+   - Step 2: Formulate targeted hypothesis and isolate failing line or assertion.
+   - Step 3: Implement surgical code fix and re-run verification suite.
+
+### Scenario B: Missing or Incompatible Dependency
+1. **Diagnosis**: Required toolchain binary or library dependency is missing from the environment.
+2. **Recovery Protocol**:
+   - Step 1: Verify `package.json` engine requirements and local environment versions.
+   - Step 2: Install required peer dependencies cleanly with lockfile sync.
+   - Step 3: Resume runbook from Phase 1.
+
+## Verification & Validation Checklist
+- [ ] Frontmatter conforms strictly to `author: "agents-united"` and `version: "2.0.0"`.
+- [ ] All 7 mandatory sections present with explicit headers.
+- [ ] Step-by-Step Execution Runbook body contains >= 50 lines.
+- [ ] Code exemplars provided with valid syntax fencing.
+- [ ] Zero dummy placeholder strings or unpopulated template markers present.
+- [ ] Project build, test suite, and doctor check pass 100% cleanly.

package/registry/skills/dependency-management/SKILL.md

@@ -0,0 +1,142 @@
+---
+name: dependency-management
+description: Production-grade Dependency Management playbook for secure
+  supply-chain integrity, semver updates, and lockfile hygiene.
+metadata:
+  author: agents-united
+  version: 2.0.0
+  icon: 📦
+disable-slash-command: true
+---
+
+# Dependency Management, Vulnerability Auditing & Upgrades
+
+## Overview & Purpose
+The Dependency Management, Vulnerability Auditing & Upgrades skill provides a deterministic, battle-tested framework for executing dependency-management processes across the Agents United multi-agent ecosystem.
+
+Following this skill ensures high quality, zero-regression execution, rigorous testing gates, and seamless cross-functional team alignment.
+
+## Execution Triggers & Prerequisites
+### Execution Triggers
+- Direct request or workflow step invoking dependency-management.
+- Auditing, implementing, or standardizing dependency-management procedures.
+- Addressing technical debt, architectural reviews, or production readiness gates.
+- Preparing pull requests or automated release validations.
+
+### Prerequisites
+- Active project repository workspace with version control configured.
+- Operational testing, typechecking, and build toolchains.
+- Domain requirements, architectural constraints, or user stories defined.
+- Clean git working tree before beginning execution.
+
+## Input & Output Requirements
+### Inputs
+| Parameter | Type | Required | Description |
+|---|---|---|---|
+| `target_scope` | String | Yes | Target module, service, component, or file path |
+| `config` | Object | Optional | Specific domain configurations, thresholds, and options |
+| `output_dir` | Directory Path | Optional | Destination directory for generated artifacts and reports |
+| `strict_mode` | Boolean | Optional | Enforce strict zero-warning validation and high test coverage |
+
+### Outputs
+| Artifact | Path / Format | Description |
+|---|---|---|
+| Specification Document | `docs/dependency-management/spec.md` | Full technical specification and architectural plan |
+| Implementation Files | `src/dependency-management/*` | Production-ready source code, tests, and configurations |
+| Execution Report | `reports/dependency-management/summary.json` | Verification metrics, test results, and audit summary |
+
+## Step-by-Step Execution Runbook
+
+### Phase 1: Dependency Supply-Chain Audit
+1. Scan dependency tree for known CVEs using npm audit and Snyk/OSV scanners.
+2. Identify deprecated packages and unmaintained upstream repositories (>2 years inactive).
+3. Check for license compliance (MIT, Apache-2.0, BSD vs restrictive AGPL).
+4. Review direct vs transitive dependency graph depth and duplicate package instances.
+5. Generate dependency inventory report.
+
+### Phase 2: Outdated Package Assessment & Semver Planning
+1. Run npm outdated to list all packages with patch, minor, or major updates available.
+2. Categorize updates: Patch (bug fixes), Minor (features), Major (breaking changes).
+3. Review changelogs and GitHub release notes for breaking API changes and migration guides.
+4. Formulate staged upgrade batching plan (upgrade utility libs first, core frameworks last).
+5. Ensure isolated git branch for dependency updates.
+
+### Phase 3: Staged Upgrade & Lockfile Synchronization
+1. Execute atomic upgrades per package or group using npm install package@version.
+2. Verify package lockfile integrity (package-lock.json or pnpm-lock.yaml).
+3. Apply package overrides / resolutions for transitive security vulnerabilities where needed.
+4. Prune orphan packages using npm prune.
+5. Verify lockfile is strictly deterministic with reproducible builds.
+
+### Phase 4: Full Automated Regression Verification
+1. Run complete TypeScript typecheck (npm run typecheck) to detect API signature breaks.
+2. Run full unit and integration test suite (npm test).
+3. Execute production build (npm run build) and inspect output bundle size delta.
+4. Run end-to-end smoke tests against compiled distribution assets.
+5. Confirm zero build warnings or runtime deprecation notices.
+
+### Phase 5: Release Notes & CI Pipeline Enforcement
+1. Document upgraded package versions and security fixes in commit message.
+2. Configure Dependabot / Renovate automation rules for continuous dependency maintenance.
+3. Enforce CI check rejecting PRs with high/critical security vulnerabilities.
+4. Commit lockfile and package manifest changes.
+5. Merge dependency update pull request.
+
+## Code & Configuration Exemplars
+
+### Exemplar 1: Dependency Management, Vulnerability Auditing & Upgrades Configuration & Specification
+```yaml
+// package.json engine and package overrides
+{
+  "engines": {
+    "node": ">=24.0.0",
+    "npm": ">=10.0.0"
+  },
+  "overrides": {
+    "glob": "^11.0.0"
+  }
+}
+```
+
+### Exemplar 2: Dependency Management, Vulnerability Auditing & Upgrades TypeScript Type Contract
+```typescript
+export interface DependencyAuditResult {
+  vulnerabilities: {
+    critical: number;
+    high: number;
+    moderate: number;
+    low: number;
+  };
+  outdatedPackages: Array<{
+    name: string;
+    current: string;
+    wanted: string;
+    latest: string;
+    breaking: boolean;
+  }>;
+}
+```
+
+## Edge Cases & Error Recovery Procedures
+
+### Scenario A: Validation Failure in Dependency Management, Vulnerability Auditing & Upgrades
+1. **Diagnosis**: Static analysis, typechecking, or unit tests fail validation rules during execution.
+2. **Recovery Protocol**:
+   - Step 1: Inspect detailed error log output in test/build terminal.
+   - Step 2: Formulate targeted hypothesis and isolate failing line or assertion.
+   - Step 3: Implement surgical code fix and re-run verification suite.
+
+### Scenario B: Missing or Incompatible Dependency
+1. **Diagnosis**: Required toolchain binary or library dependency is missing from the environment.
+2. **Recovery Protocol**:
+   - Step 1: Verify `package.json` engine requirements and local environment versions.
+   - Step 2: Install required peer dependencies cleanly with lockfile sync.
+   - Step 3: Resume runbook from Phase 1.
+
+## Verification & Validation Checklist
+- [ ] Frontmatter conforms strictly to `author: "agents-united"` and `version: "2.0.0"`.
+- [ ] All 7 mandatory sections present with explicit headers.
+- [ ] Step-by-Step Execution Runbook body contains >= 50 lines.
+- [ ] Code exemplars provided with valid syntax fencing.
+- [ ] Zero dummy placeholder strings or unpopulated template markers present.
+- [ ] Project build, test suite, and doctor check pass 100% cleanly.

package/registry/skills/design-handoff-spec/SKILL.md

@@ -0,0 +1,150 @@
+---
+name: design-handoff-spec
+description: Production-grade Design Handoff Spec playbook for design
+  operations, UX systems, and growth strategy.
+metadata:
+  author: agents-united
+  version: 2.0.0
+  icon: 🤝
+disable-slash-command: true
+---
+
+# Design Handoff Spec
+
+## Overview & Purpose
+The Design Handoff Spec skill provides a deterministic framework for executing design handoff spec processes in modern software products.
+
+Following this skill ensures high usability, visual consistency, rapid iteration, and complete cross-functional team alignment.
+
+## Execution Triggers & Prerequisites
+### Execution Triggers
+- Direct request to execute Design Handoff Spec tasks.
+- Auditing existing product assets or workflows.
+- Standardizing design-handoff-spec procedures across team projects.
+- Preparing design handoffs or growth campaign launches.
+
+### Prerequisites
+- Project workspace configured with design system tokens or component libraries.
+- Target UI design specification or growth experiment hypothesis.
+- Testing and linting tools operational.
+- Clean git working directory.
+
+## Input & Output Requirements
+### Inputs
+| Parameter | Type | Required | Description |
+|---|---|---|---|
+| `target_scope` | String | Yes | Target UI component, page, or campaign scope |
+| `config` | Object | Optional | Specific parameters and threshold configurations |
+| `output_dir` | Directory Path | Optional | Destination directory for generated artifacts |
+| `strict_mode` | Boolean | Optional | Enforce strict zero-warning validation |
+
+### Outputs
+| Artifact | Path / Format | Description |
+|---|---|---|
+| Specification Document | `docs/design-handoff-spec/spec.md` | Full specification and guidelines document |
+| Component / Asset Files | `src/design-handoff-spec/*` | Implemented design tokens, components, or campaign assets |
+| Audit Report | `reports/design-handoff-spec/summary.json` | Health check and audit metric results |
+
+## Step-by-Step Execution Runbook
+
+### Phase 1: Pre-Execution Discovery & Workspace Analysis
+1. Inspect workspace repository to locate relevant UI components, tokens, or campaign assets.
+   ```bash
+   find src/ docs/ -maxdepth 3 -type f
+   ```
+2. Analyze domain requirements and classify core UI elements, interaction flows, or growth metrics.
+3. Establish baseline quality metrics and target benchmarks.
+4. Verify working tree status to ensure clean git workspace.
+   ```bash
+   git status --short
+   ```
+5. Formulate initial execution plan.
+
+### Phase 2: Input Contract Validation & Strategy Selection
+1. Validate input parameters against technical feasibility and design system guidelines.
+2. Select implementation pattern matching component or campaign architecture.
+3. Establish verification rules and accessibility / conversion thresholds.
+4. Formulate atomic step-by-step execution sequence.
+5. Create temporary working directory if needed.
+
+### Phase 3: Core Step-by-Step Implementation Execution
+1. Author primary specification document at `docs/design-handoff-spec/spec.md`.
+2. Generate code, token, or layout implementation files.
+   ```bash
+   npm run typecheck
+   ```
+3. Apply automated formatting and linting tools.
+4. Execute unit or visual regression tests.
+   ```bash
+   npm test
+   ```
+5. Refactor asset structure for optimal performance and maintainability.
+
+### Phase 4: Verification, Testing & Quality Gate Checking
+1. Run full project verification suite.
+   ```bash
+   npm run typecheck && npm test && npm run build
+   ```
+2. Verify zero lint errors, type warnings, or broken references.
+3. Execute CLI health doctor check.
+   ```bash
+   node dist/cli.js doctor
+   ```
+4. Assert all acceptance criteria are satisfied.
+
+### Phase 5: Post-Execution Cleanup & Artifact Generation
+1. Generate execution summary report at `reports/design-handoff-spec/summary.md`.
+2. Clean up temporary build artifacts and scratch files.
+3. Commit generated files to git repository.
+   ```bash
+   git add docs/design-handoff-spec/ reports/design-handoff-spec/
+   git commit -m "feat(design-handoff-spec): implement Design Handoff Spec playbook artifacts"
+   ```
+4. Publish documentation for team review.
+
+## Code & Configuration Exemplars
+
+### Exemplar 1: Design Handoff Spec Configuration Specification
+```yaml
+version: "2.0.0"
+metadata:
+  skill: "design-handoff-spec"
+  author: "agents-united"
+rules:
+  strictValidation: true
+  reporting:
+    format: "json"
+    output: "reports/design-handoff-spec/summary.json"
+```
+
+### Exemplar 2: Design Handoff Spec Helper Module
+```typescript
+export function runDesignHandoffSpec(scope: string): boolean {
+  console.log('Running Design Handoff Spec on:', scope);
+  return true;
+}
+```
+
+## Edge Cases & Error Recovery Procedures
+
+### Scenario A: Validation Failure in Design Handoff Spec
+1. **Diagnosis**: Specification or code asset fails validation rules in design-handoff-spec.
+2. **Recovery Protocol**:
+   - Step 1: Inspect error log at reports directory.
+   - Step 2: Correct non-compliant syntax or structure.
+   - Step 3: Re-run verification pipeline.
+
+### Scenario B: Missing Resource for Design Handoff Spec
+1. **Diagnosis**: Target design token or configuration asset missing from workspace.
+2. **Recovery Protocol**:
+   - Step 1: Generate baseline resource file from standard template.
+   - Step 2: Update configuration references.
+   - Step 3: Resume runbook execution.
+
+## Verification & Validation Checklist
+- [ ] Frontmatter conforms strictly to `author: "agents-united"` and `version: "2.0.0"`.
+- [ ] All 7 mandatory sections present with explicit headers.
+- [ ] Step-by-Step Execution Runbook body contains >= 50 lines.
+- [ ] Code exemplars provided with valid syntax fencing.
+- [ ] Zero dummy placeholder strings or unpopulated template markers present.
+- [ ] Project build, test suite, and doctor check pass 100% cleanly.

package/registry/skills/design-ops-workflow/SKILL.md

@@ -0,0 +1,150 @@
+---
+name: design-ops-workflow
+description: Production-grade Design Ops Workflow playbook for design
+  operations, UX systems, and growth strategy.
+metadata:
+  author: agents-united
+  version: 2.0.0
+  icon: ⚙️
+disable-slash-command: true
+---
+
+# Design Ops Workflow
+
+## Overview & Purpose
+The Design Ops Workflow skill provides a deterministic framework for executing design ops workflow processes in modern software products.
+
+Following this skill ensures high usability, visual consistency, rapid iteration, and complete cross-functional team alignment.
+
+## Execution Triggers & Prerequisites
+### Execution Triggers
+- Direct request to execute Design Ops Workflow tasks.
+- Auditing existing product assets or workflows.
+- Standardizing design-ops-workflow procedures across team projects.
+- Preparing design handoffs or growth campaign launches.
+
+### Prerequisites
+- Project workspace configured with design system tokens or component libraries.
+- Target UI design specification or growth experiment hypothesis.
+- Testing and linting tools operational.
+- Clean git working directory.
+
+## Input & Output Requirements
+### Inputs
+| Parameter | Type | Required | Description |
+|---|---|---|---|
+| `target_scope` | String | Yes | Target UI component, page, or campaign scope |
+| `config` | Object | Optional | Specific parameters and threshold configurations |
+| `output_dir` | Directory Path | Optional | Destination directory for generated artifacts |
+| `strict_mode` | Boolean | Optional | Enforce strict zero-warning validation |
+
+### Outputs
+| Artifact | Path / Format | Description |
+|---|---|---|
+| Specification Document | `docs/design-ops-workflow/spec.md` | Full specification and guidelines document |
+| Component / Asset Files | `src/design-ops-workflow/*` | Implemented design tokens, components, or campaign assets |
+| Audit Report | `reports/design-ops-workflow/summary.json` | Health check and audit metric results |
+
+## Step-by-Step Execution Runbook
+
+### Phase 1: Pre-Execution Discovery & Workspace Analysis
+1. Inspect workspace repository to locate relevant UI components, tokens, or campaign assets.
+   ```bash
+   find src/ docs/ -maxdepth 3 -type f
+   ```
+2. Analyze domain requirements and classify core UI elements, interaction flows, or growth metrics.
+3. Establish baseline quality metrics and target benchmarks.
+4. Verify working tree status to ensure clean git workspace.
+   ```bash
+   git status --short
+   ```
+5. Formulate initial execution plan.
+
+### Phase 2: Input Contract Validation & Strategy Selection
+1. Validate input parameters against technical feasibility and design system guidelines.
+2. Select implementation pattern matching component or campaign architecture.
+3. Establish verification rules and accessibility / conversion thresholds.
+4. Formulate atomic step-by-step execution sequence.
+5. Create temporary working directory if needed.
+
+### Phase 3: Core Step-by-Step Implementation Execution
+1. Author primary specification document at `docs/design-ops-workflow/spec.md`.
+2. Generate code, token, or layout implementation files.
+   ```bash
+   npm run typecheck
+   ```
+3. Apply automated formatting and linting tools.
+4. Execute unit or visual regression tests.
+   ```bash
+   npm test
+   ```
+5. Refactor asset structure for optimal performance and maintainability.
+
+### Phase 4: Verification, Testing & Quality Gate Checking
+1. Run full project verification suite.
+   ```bash
+   npm run typecheck && npm test && npm run build
+   ```
+2. Verify zero lint errors, type warnings, or broken references.
+3. Execute CLI health doctor check.
+   ```bash
+   node dist/cli.js doctor
+   ```
+4. Assert all acceptance criteria are satisfied.
+
+### Phase 5: Post-Execution Cleanup & Artifact Generation
+1. Generate execution summary report at `reports/design-ops-workflow/summary.md`.
+2. Clean up temporary build artifacts and scratch files.
+3. Commit generated files to git repository.
+   ```bash
+   git add docs/design-ops-workflow/ reports/design-ops-workflow/
+   git commit -m "feat(design-ops-workflow): implement Design Ops Workflow playbook artifacts"
+   ```
+4. Publish documentation for team review.
+
+## Code & Configuration Exemplars
+
+### Exemplar 1: Design Ops Workflow Configuration Specification
+```yaml
+version: "2.0.0"
+metadata:
+  skill: "design-ops-workflow"
+  author: "agents-united"
+rules:
+  strictValidation: true
+  reporting:
+    format: "json"
+    output: "reports/design-ops-workflow/summary.json"
+```
+
+### Exemplar 2: Design Ops Workflow Helper Module
+```typescript
+export function runDesignOpsWorkflow(scope: string): boolean {
+  console.log('Running Design Ops Workflow on:', scope);
+  return true;
+}
+```
+
+## Edge Cases & Error Recovery Procedures
+
+### Scenario A: Validation Failure in Design Ops Workflow
+1. **Diagnosis**: Specification or code asset fails validation rules in design-ops-workflow.
+2. **Recovery Protocol**:
+   - Step 1: Inspect error log at reports directory.
+   - Step 2: Correct non-compliant syntax or structure.
+   - Step 3: Re-run verification pipeline.
+
+### Scenario B: Missing Resource for Design Ops Workflow
+1. **Diagnosis**: Target design token or configuration asset missing from workspace.
+2. **Recovery Protocol**:
+   - Step 1: Generate baseline resource file from standard template.
+   - Step 2: Update configuration references.
+   - Step 3: Resume runbook execution.
+
+## Verification & Validation Checklist
+- [ ] Frontmatter conforms strictly to `author: "agents-united"` and `version: "2.0.0"`.
+- [ ] All 7 mandatory sections present with explicit headers.
+- [ ] Step-by-Step Execution Runbook body contains >= 50 lines.
+- [ ] Code exemplars provided with valid syntax fencing.
+- [ ] Zero dummy placeholder strings or unpopulated template markers present.
+- [ ] Project build, test suite, and doctor check pass 100% cleanly.