Dadmin88/hermes-agency - Page 5

dialogue-writing

Write character dialogue that serves voice, relationship, subtext, pacing, and scene purpose without exposition-heavy speech.

localization-ready-dialogue

Prepare dialogue for localization by preserving meaning, context, speaker metadata, variables, gender or plurality constraints, line relationships, timing, and cultural clarity while avoiding source-language wordplay that cannot travel without annotation.

delivery-semantics

Design and implement message delivery semantics for retries, duplicates, reordering, acknowledgement, deadlines, and uncertain outcomes.

distributed-fault-testing

Prove distributed behavior with deterministic and stochastic tests for delay, loss, duplication, reorder, partition, crash, restart, and clock-sensitive edges.

distributed-state-machine

Implement a distributed state machine with explicit commands, invariants, authority, transitions, persistence, replay, and recovery semantics.

membership-coordination

Implement node membership, discovery, leases, leadership or coordination without allowing stale identity or split authority to silently corrupt state.

replication-consistency

Implement replicated state with an explicit consistency model, conflict policy, convergence mechanism, and durability/recovery behavior.

docs-information-architecture

Organize documentation by user audience, task, learning stage, concept, reference surface, and maintenance ownership so readers can find the right kind of answer without knowing repository structure.

docs-validation

Validate documentation against the current product by executing commands and flows, checking links, versions, screenshots, prerequisites, terminology, code examples, and claimed outcomes before publication.

how-to-guide

Write a task-oriented how-to guide for an already oriented user, focusing on prerequisites, direct steps, variants, verification, and recovery without turning the page into a tutorial or conceptual essay.

tutorial-writing

Write a tutorial that teaches a new user to accomplish one meaningful outcome through a verified sequence, explanatory context, checkpoints, troubleshooting, and final proof rather than documenting every option.

user-documentation

Create task-oriented user documentation that explains current product behavior with prerequisites, steps, examples, troubleshooting, and expected results.

content-brief

Create an editorial content brief that defines audience, purpose, angle, scope, evidence, format, tone, contributors, deliverables, review path, and publication outcome before drafting begins.

editorial-review

Perform an editorial review for factual integrity, structure, voice, clarity, audience fit, and publication readiness.

fact-check-review

Review the fact-checking quality of an editorial draft by auditing consequential claims, source fit, citation coverage, quote context, current-status evidence, uncertainty, and unresolved contradictions before publication.

publication-planning

Plan an editorial publication pipeline across audience needs, themes, formats, cadence, contributors, dependencies, review capacity, distribution, maintenance, and measurable value without filling a calendar for its own sake.

style-guide

Create and maintain an editorial style guide covering voice, tone, mechanics, terminology, numbers, capitalization, citations, inclusivity, product names, and exceptions so distributed writers can make consistent decisions.

deliverability-review

Review email deliverability using current sender authentication, list quality, consent and complaint signals, bounce behavior, reputation, content, sending patterns, and provider evidence without relying on folklore.

email-campaign

Design and write an email campaign around audience state, value, segmentation, sequence logic, deliverability, and measurable action.

email-experiment

Design and evaluate email experiments on message, timing, sequence, audience, or call to action using stable assignment, delivered-population awareness, downstream outcomes, and negative-signal guardrails.

lifecycle-email

Design lifecycle email journeys around user state, trigger, value, timing, frequency, suppression, personalization, action, and measurable downstream behavior.

segmentation

Build email audience segments from meaningful customer state, behavior, value, lifecycle, consent, and message relevance with stable definitions, exclusions, and measurable differences.

environment-production

Build an environment or scene from narrative/gameplay goals through composition, modular planning, assets, materials, lighting, optimization, and in-engine validation.

lighting-pass

Create and validate an environment lighting pass for readability, mood, focal hierarchy, gameplay or navigation, material response, state variation, performance, and exposure.

material-language

Define and apply a coherent environment material language through surface categories, roughness and value relationships, wear logic, scale, reuse, variation, and narrative consistency.

modular-kit

Design a reusable environment kit with coherent dimensions, pivots, snapping, variation, material strategy, seams, collision, LOD, and composition flexibility.

scene-optimization

Optimize environment scenes using measured visibility, geometry, materials, lighting, textures, VFX, culling, streaming, LOD, and instance behavior while preserving composition and gameplay.

budget-tracking

Track an operating budget from approved plan through commitments, actuals, forecast, variance, ownership, and evidence so teams can understand remaining capacity without confusing budget with cash.

cash-flow-forecast

Forecast organizational cash inflows, outflows, timing, committed obligations, scenarios, and liquidity headroom from current financial evidence without presenting uncertain future amounts as guaranteed.

expense-review

Review organizational expenses for policy fit, business purpose, evidence, coding, approval, duplication, anomaly, allocation, and recurring-cost opportunity without substituting for accounting judgment.

financial-controls

Design and review operational financial controls around authorization, segregation of duties, reconciliations, evidence, access, change management, exception handling, and periodic verification.

financial-operations-review

Review operational financial records, budgets, invoices, recurring costs, forecasts, and controls for accuracy and decision usefulness.

invoice-reconciliation

Reconcile invoices against purchase or contract terms, receipts or delivery evidence, approvals, accounting records, payments, credits, taxes, and duplicates before operational closeout.

accessibility-implementation

Implement accessible frontend behavior using semantic structure, native controls, keyboard and focus management, clear names and errors, adaptable visuals, and assistive-technology-aware state changes.

api-integration

Integrate a frontend with backend or third-party APIs using explicit contracts, resilient async state, safe credential handling, cancellation, retries, and user-visible failure behavior.

frontend-implementation

Implement a user-facing interface from product/design specs through state, accessibility, responsive behavior, API integration, tests, and runtime validation.

frontend-testing

Build frontend tests that prove user-observable behavior, interaction states, accessibility, and integration contracts at the smallest reliable layer.

performance-debugging

Diagnose and improve frontend performance by measuring user-visible symptoms, isolating the dominant bottleneck, changing one high-impact cause at a time, and proving the improvement without regressions.

state-management

Design and implement frontend state ownership, transitions, synchronization, persistence, and async behavior without duplicating sources of truth or creating race-prone UI logic.

api-ui-contract

Define and implement the contract between a user-facing interface and its backend API so user states, server semantics, validation, authorization, concurrency, and compatibility remain coherent across both sides.