Claude Skills by Dadmin88

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

MUST load first for Academy learning or go-learn requests.

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.

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

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.

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.

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

MUST load first for Academy learning or go-learn requests.

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

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

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.

Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, passive voice, negative parallelisms, and filler phrases.

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.

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.

MUST load first for Academy learning or go-learn requests.

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.

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

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.

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

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

MUST load first for Academy learning or go-learn requests.

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

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

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

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

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

MUST load first for Academy learning or go-learn requests.

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.

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

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

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

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

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

MUST load first for Academy learning or go-learn requests.

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.

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.

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

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

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.

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

MUST load first for Academy learning or go-learn requests.

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.

Prepare a bounded full-stack feature for deployment by reconciling client/server artifacts, migrations, configuration, assets, compatibility, health, observability, rollback, and post-release validation.

Diagnose a full-stack defect by following one user operation across rendered UI, client state, network contract, backend logic, persistence, async work, and returned state until the first divergence is identified.

Test a bounded full-stack feature with complementary client, server, persistence, contract, and assembled-flow evidence while avoiding duplicate brittle tests at every layer.

Implement a bounded end-to-end feature slice across UI, API, domain logic, and persistence while preserving contracts and avoiding unnecessary cross-system redesign.

MUST load first for Academy learning or go-learn requests.

Balance game systems using explicit goals, comparable metrics, parameter sensitivity, simulation, controlled playtests, telemetry, and dominant-strategy analysis rather than tuning by feel alone.

Design a game economy around sources, sinks, currencies, resources, exchange, scarcity, pacing, player incentives, inflation, exploits, and recovery using explicit flow models.

Design a game mechanic or system around player goals, rules, feedback, progression, balance, failure, and interaction with the broader game loop.