Claude Skills by Dadmin88

Build backend tests at the right layer to prove domain behavior, API contracts, persistence interactions, authorization, and important failure paths without brittle implementation coupling.

Design and implement reliable background work with explicit delivery semantics, idempotency, retry policy, concurrency control, observability, and recovery behavior.

Model backend business behavior with explicit terminology, invariants, state transitions, ownership boundaries, persistence mapping, and concurrency rules.

Diagnose backend failures systematically from reproducible symptom through evidence, hypothesis, root cause, minimal fix, regression proof, and production-relevant verification.

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

Author approved portable Hermes profile distributions.

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

Review real applications of a brand for correct identity use, hierarchy, tone, typography, color, imagery, layout, adaptability, and contextual consistency.

Build or extend a visual brand system with identity principles, typography, color, imagery, layout, logo behavior, and practical usage rules.

Define a brand color system with functional roles, accessible combinations, tonal scales, dark or light context, reproduction guidance, and consistent application across media.

Develop or evaluate logo direction through brand meaning, distinctiveness, form, scalability, typography, lockups, monochrome behavior, and practical application rather than decoration alone.

Define a brand typography system with role hierarchy, typeface rationale, scale, weights, spacing, fallback, language coverage, accessibility, and cross-medium behavior.

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

Build a decision-ready business case from problem, beneficiaries, options, costs, benefits, risks, assumptions, timing, and measurable outcomes without manufacturing financial precision.

Analyze the likely business and operational impact of a proposed change across users, processes, systems, data, roles, controls, costs, dependencies, and transition risk.

Analyze a business process to clarify goals, actors, rules, data, bottlenecks, exceptions, and opportunities for better system support.

Trace business needs through product requirements, design, implementation, validation, release evidence, and change history so important intent cannot disappear between teams.

Map stakeholders by decision rights, impact, influence, information needs, incentives, concerns, dependencies, and engagement strategy without reducing people to a power-interest grid.

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

Perform a business impact analysis that identifies critical services, dependencies, maximum tolerable disruption, recovery priorities, minimum operating levels, and downstream consequences without inventing executive risk tolerance.

Run tabletop or functional continuity exercises against realistic scenarios to test activation, decision rights, communications, manual workarounds, dependencies, and return-to-normal behavior.

Create a continuity plan for a critical business service covering activation criteria, roles, communications, alternate workflows, minimum resources, supplier dependencies, technology recovery interfaces, and return to normal.

Plan and validate transition from continuity mode back to normal operations, including backlog, data/state reconciliation, customer/vendor communication, access, financial records, and post-event learning.

Assess continuity risk in critical suppliers and external dependencies through outage scenarios, concentration, contractual support, data portability, alternatives, communication paths, and exit capability.

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

Align multiple functions around a shared outcome by making decision rights, dependencies, commitments, conflicts, evidence, and handoffs explicit without making every team interchangeable.

Maintain durable records of consequential decisions with context, owner, options, evidence, rationale, consequences, dependencies, and revisit conditions.

Turn complex cross-functional information into a concise decision brief with priorities, tradeoffs, risks, and recommended next actions.

Triage competing executive or cross-functional priorities by outcome, urgency, reversibility, dependency, consequence, capacity, and decision ownership instead of reacting to whoever is loudest.

Escalate material strategic or delivery risk with evidence, consequence, urgency, options, owner, and requested decision so leadership attention is used where it can change the outcome.

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

Review public or cross-component interface changes for consumer breakage across syntax, semantics, errors, defaults, ordering, timing, schemas, deprecation, and migration behavior.

Review a code change independently for correctness, regression risk, maintainability, compatibility, tests, and unsafe assumptions.

Use when reviewing bounded schema/value-object diffs.

Review implementation structure for clarity, cohesion, coupling, complexity, duplication, ownership, extension pressure, and operational readability without turning style preference into blockers.

Review a change for behavior it can accidentally break by tracing affected callers, data, state, interfaces, concurrency, configuration, migrations, and operational assumptions.

Review whether tests provide meaningful evidence for the changed contract, important failures, boundaries, concurrency, integration behavior, and regression risk without rewarding brittle or superficial coverage.

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

Evaluate community health through member value, participation quality, contributor concentration, responsiveness, retention, safety, sentiment, moderation burden, and operator sustainability rather than size alone.

Run a healthy community loop across engagement, moderation, recurring questions, feedback capture, escalation, and member value.

Design a community program around member value, audience, purpose, participation loops, roles, events or content, governance, moderation, measurement, and sustainable operator workload.

Plan community engagement around specific member behaviors, content and event formats, response rhythms, contributor activation, re-engagement, and measurable value rather than posting for activity's sake.

Synthesize community feedback into evidence-backed themes, frequency and severity context, affected segments, representative examples, product implications, and routing without turning loudness into priority.

Define community moderation procedures for rules, context, evidence, proportionate response, escalation, appeals, privacy, documentation, and moderator wellbeing without making every conflict a punishment workflow.

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

Compare competitors and alternatives using current evidence on positioning, capabilities, pricing, distribution, strengths, weaknesses, and strategic implications.

Maintain a current, decision-focused view of competitor and substitute changes across product, pricing, positioning, partnerships, distribution, organization, and market signals without reacting to every announcement.

Compare competing products or alternatives at the capability and workflow level using current evidence, comparable scope, user relevance, and explicit uncertainty rather than checklist theater.

Research what people actually say about any topic in the last 30 days. Pulls posts and engagement from Reddit, X, YouTube, TikTok, Hacker News, Polymarket, GitHub, and the web. Includes a doctor health check to diagnose broken or missing sources.

Map competitors and alternatives on customer-relevant positioning dimensions using evidence about target audience, category claim, value proposition, proof, pricing or business model, and perceived tradeoffs.