Dadmin88/hermes-agency - Page 4

experiment-design-science

Design controlled experiments with valid assignment, power, estimands, guardrails, analysis plans, and stopping rules.

forecasting-model

Build and evaluate a forecast with time-aware validation, baselines, uncertainty intervals, covariates, and scenario sensitivity.

predictive-modeling

Build an interpretable predictive model from a decision need through features, validation, calibration, error analysis, and deployment handoff.

statistical-analysis

Perform decision-oriented statistical analysis with explicit population, sampling, assumptions, uncertainty, effect size, and sensitivity.

backup-recovery

Design and prove database backup recovery around consistency, recovery point/time objectives, encryption, retention, corruption/deletion scenarios, point-in-time recovery, and tested restoration.

concurrency-consistency

Design and diagnose database concurrency using explicit invariants, transaction boundaries, isolation, locking or optimistic control, retries, deadlock handling, and consistency guarantees.

indexing

Design and validate database indexes from real query predicates, joins, ordering, selectivity, data distribution, write cost, storage, maintenance, and engine-specific planner behavior.

query-optimization

Optimize database queries by reproducing the workload, measuring latency and resource cost, reading the actual execution plan, fixing access strategy or data shape, and proving improvement without semantic regression.

schema-design

Design transactional database schemas around domain invariants, access patterns, keys, constraints, relationships, lifecycle, engine semantics, and safe evolution without cargo-cult rules.

schema-migration

Design and execute a database schema migration with compatibility, locking, data backfill, validation, rollback or forward recovery, and deployment sequencing.

accessibility-design-check

Check design artifacts for accessibility requirements and implementation-ready semantics across hierarchy, controls, focus, keyboard, errors, contrast, motion, responsive adaptation, and non-text content.

design-handoff-review

Review a design handoff for implementation readiness by checking source artifacts, flows, states, responsive behavior, components, tokens, content, accessibility, assets, interaction details, and unresolved decisions.

design-review

Review product or visual design work for coherence, usability, consistency, accessibility, completeness, and implementation readiness.

interaction-consistency

Review interaction patterns across a product for consistent control behavior, navigation, input, feedback, terminology, selection, destructive actions, loading, and recovery without forcing visual sameness where context differs.

state-completeness

Review a design for complete user-visible states, transitions, permissions, loading, empty data, validation, failure, interruption, concurrency, success, and recovery so implementation does not invent missing product behavior.

visual-verify

Prove a visual or interaction change on the rendered product by capturing the real surface, comparing it with the intended reference and neighboring system, checking relevant states, and recording visible discrepancies before sign-off.

accessibility-patterns

Codify reusable accessible interaction patterns with semantic intent, keyboard and focus behavior, state communication, content guidance, and implementation notes for recurring UI needs.

contribution-governance

Govern additions and changes to a design system through evidence of recurring need, ownership, review, compatibility, documentation, release, adoption, and deprecation.

design-system-component

Define or evolve a design-system component by reusing existing primitives and tokens first, then specifying semantics, variants, states, accessibility, responsive behavior, and implementation guidance only where a recurring gap truly exists.

design-tokens

Design and govern semantic design tokens for color, typography, spacing, size, motion, elevation, and other reusable decisions with clear naming, themes, aliases, and implementation contracts.

pattern-library

Define reusable interaction and composition patterns with anatomy, behavior, states, accessibility, variants, content guidance, and selection criteria beyond individual components.

desktop-app-architecture

Design desktop application boundaries across shell, renderer/UI, background services, local state, privileged capabilities, IPC, and crash/restart lifecycle.

desktop-ipc-security

Design and implement desktop IPC with narrow message schemas, capability boundaries, validation, authentication/context, error semantics, cancellation, and observability.

desktop-packaging-signing

Build reproducible desktop packages with correct assets, native dependencies, permissions, signing/notarization inputs, architecture targets, and install/uninstall behavior.

desktop-update-runtime-debugging

Design update/rollback behavior and diagnose failures that occur only in installed/packaged desktop builds.

native-os-integration

Implement native desktop integrations such as tray/menu, notifications, clipboard, file associations, deep links, startup behavior, file pickers, and platform permissions.

developer-adoption-program

Plan and measure a developer adoption initiative using target personas, activation behavior, enablement assets, channels, feedback, and downstream usage.

developer-feedback-loop

Turn developer conversations, support patterns, sample failures, and community questions into prioritized product and documentation feedback.

developer-quickstart-demo

Create an executable developer quickstart or demo that reaches first value quickly while remaining technically honest and reproducible.

sample-app-production

Build and maintain a small sample application that demonstrates recommended integration patterns without becoming an unofficial framework or stale toy.

technical-talk-workshop

Design a developer talk or workshop around one learnable technical outcome with executable exercises, timing, checkpoints, and recovery paths.

build-reproducibility

Make builds traceable and reproducible by controlling inputs, dependency resolution, toolchains, generated state, environment influence, artifact identity, and verification across clean builders.

ci-cd-pipeline

Design or improve CI/CD so changes are reproducibly built, tested, secured, promoted, deployed, observed, and recoverable.

deployment-automation

Automate deployment from an immutable release artifact through environment targeting, concurrency control, health validation, progressive rollout, failure handling, and auditable completion.

environment-management

Manage delivery environments through explicit configuration, controlled secrets, reproducible differences, drift detection, lifecycle policy, and parity focused on behavior rather than identical infrastructure.

release-observability

Observe software delivery from commit through build, artifact, promotion, deployment, health, rollback, and post-release behavior so release state and failures are traceable to exact revisions.

rollback-strategy

Design rollback and forward-recovery for releases by identifying reversible surfaces, data/schema constraints, compatibility windows, triggers, decision authority, and post-recovery validation.

branching-dialogue

Design branching dialogue around player intent, character goals, state conditions, choice meaning, convergence, consequences, memory, and implementation identifiers without creating combinatorial branches that add no meaningful agency.

character-voice

Define and preserve a character's dialogue voice through worldview, goals, status, vocabulary, rhythm, syntax, humor, avoidance patterns, relationships, and situational variation without reducing voice to catchphrases.

dialogue-edit

Edit dialogue for character voice, intention, subtext, rhythm, redundancy, exposition, continuity, speakability, pacing, and scene function while preserving the writer's dramatic intent.