All authors
Claude Skills by Dadmin88
github.com/Dadmin88818 skills21 installs1,070 views
- Architecture DecisionMake and document a consequential software architecture decision using constraints, alternatives, tradeoffs, boundaries, failure modes, migration, and validation.Votes: 0GitHub stars: 16
- Architecture ReviewReview a proposed or implemented architecture against real product constraints, boundaries, dependency direction, data ownership, failure behavior, operability, security, migration, and unnecessary complexity.Votes: 0GitHub stars: 16
- Dependency BoundariesDesign and review dependency direction so components own clear responsibilities, depend on stable contracts, avoid cycles, and keep infrastructure or framework details from contaminating domain boundaries.Votes: 0GitHub stars: 16
- Failure Mode AnalysisAnalyze architectural failure modes by tracing what can fail at each boundary, how failures propagate, what remains available or consistent, and which controls detect, contain, recover, or deliberately accept the impact.Votes: 0GitHub stars: 16
- Interface DesignDesign durable software interfaces between components or services with explicit ownership, contracts, semantics, evolution, trust boundaries, and failure behavior.Votes: 0GitHub stars: 16
- Migration DesignDesign safe architectural migrations across data, interfaces, components, deployments, and consumers using compatibility stages, observability, rollback or forward recovery, and explicit completion criteria.Votes: 0GitHub stars: 16
- Technical ResearchResearch technical approaches from project documents of record through current primary sources and prior art, evaluate evidence and licenses, and convert findings into architecture or implementation implications without answering from memory.Votes: 0GitHub stars: 16
- Implementation HandoffHand a validated solution to implementation/customer-success owners with architecture, configuration, acceptance evidence, gaps, dependencies, and unresolved risks.Votes: 0GitHub stars: 16
- Proof Of ConceptDesign and execute a bounded proof of concept that validates the riskiest customer-specific technical assumptions with real evidence.Votes: 0GitHub stars: 16
- Solution Architecture BriefProduce a customer-facing solution architecture that maps supported product components and integration boundaries to the customer environment without redefining core product architecture.Votes: 0GitHub stars: 16
- Technical DemoDeliver a customer-specific technical demonstration that proves relevant workflows, handles likely questions, and distinguishes configured demo behavior from product guarantees.Votes: 0GitHub stars: 16
- Technical DiscoveryRun technical customer discovery that surfaces current architecture, workflows, constraints, success criteria, security/compliance needs, and decision risks without prematurely designing a solution.Votes: 0GitHub stars: 16
- Bug ReproductionReproduce a reported customer issue from exact environment, inputs, account state, sequence, and evidence so engineering receives a bounded defect instead of an anecdote.Votes: 0GitHub stars: 16
- EscalationEscalate a support case with severity, impact, evidence, attempted work, decision needed, owner, and customer context so the receiving specialist can act without restarting intake.Votes: 0GitHub stars: 16
- Response DraftingDraft support responses that acknowledge the actual problem, answer what is known, avoid invented certainty, give concrete next steps, and preserve ownership through resolution.Votes: 0GitHub stars: 16
- Support Trend AnalysisAnalyze support volume and case evidence to identify recurring product, documentation, reliability, onboarding, policy, or operational problems without mistaking ticket count for root cause.Votes: 0GitHub stars: 16
- Support TriageTriage a support request into a reproducible problem, user impact, severity, workaround, and correct escalation path.Votes: 0GitHub stars: 16
- Capacity ModelBuild a system-level capacity model that connects workload demand to bottlenecks across services, nodes, queues, storage, network, shared dependencies, redundancy, and placement constraints.Votes: 0GitHub stars: 16
- Deployment TopologyDesign how distributed components may be placed and rolled out across failure domains, networks, state, trust boundaries, heterogeneous nodes, and upgrade cohorts without confusing architecture with live scheduler state.Votes: 0GitHub stars: 16
- Distributed Systems DesignDesign distributed behavior explicitly around ownership, coordination, consistency, ordering, retries, duplicate delivery, partitions, discovery, membership, and evolution rather than assuming a reliable single machine.Votes: 0GitHub stars: 16
- Fault ToleranceDesign and test fault tolerance by defining expected faults, containment boundaries, detection, failover, retry/replay semantics, state reconciliation, and safe recovery after partial failure.Votes: 0GitHub stars: 16
- Reliability DesignDesign system reliability from user-critical outcomes through service objectives, dependency budgets, redundancy, graceful degradation, recovery, observability, and operational ownership.Votes: 0GitHub stars: 16
- Systems DesignDesign a multi-service or distributed system around responsibilities, protocols, topology, identity, consistency, failure, capacity, observability, and evolution.Votes: 0GitHub stars: 16
- Systems TopologyModel a system's logical and physical topology across services, nodes, networks, state, control planes, trust boundaries, failure domains, dependencies, and communication paths.Votes: 0GitHub stars: 16
- Art PipelineDesign or troubleshoot an art production pipeline across DCC tools, import/export, shaders, assets, validation, automation, and runtime constraints.Votes: 0GitHub stars: 16
- Asset PerformanceProfile and optimize art-asset runtime cost across geometry, materials, textures, animation, VFX, draw calls, overdraw, memory, streaming, and scene density without sacrificing visible intent blindly.Votes: 0GitHub stars: 16
- Engine HandoffDefine and validate the art-to-engine contract for formats, scale, naming, materials, rigs, animation, metadata, import settings, automation, and ownership across distributed production.Votes: 0GitHub stars: 16
- Procedural ToolsDesign procedural art tools that encode repeatable artistic constraints while exposing useful controls, deterministic generation, editable outputs, performance limits, and safe artist override.Votes: 0GitHub stars: 16
- Shader DebuggingDiagnose shader and material failures using reproduction, render-state inspection, inputs, spaces, precision, variants, platform differences, and frame or debugger evidence.Votes: 0GitHub stars: 16
- Codebase ScopingScope an engineering change in an unfamiliar or evolving codebase by tracing entry points, ownership, callers, data flow, tests, configuration, generated artifacts, and adjacent contracts before assigning implementation work.Votes: 0GitHub stars: 16
- Implementation CoordinationCoordinate parallel engineering implementation by keeping ownership, contracts, dependencies, integration state, blockers, and validation evidence aligned without taking over specialists' work.Votes: 0GitHub stars: 16
- Integration PlanPlan how independently owned engineering changes will combine into one working system, including interface readiness, merge order, data/schema compatibility, feature exposure, test environments, and rollback checkpoints.Votes: 0GitHub stars: 16
- Technical Execution PlanConvert approved product scope and architecture into a coordinated technical execution plan across engineering specialties.Votes: 0GitHub stars: 16
- Technical Risk AssessmentAssess implementation risk across uncertainty, blast radius, compatibility, data, concurrency, dependencies, performance, security, operations, and reversibility so engineering effort follows the risks that can actually derail delivery.Votes: 0GitHub stars: 16
- Configuration DiagnosisDiagnose configuration failures by comparing effective values, precedence, environment, defaults, validation, and version compatibility rather than assuming the visible file is authoritative.Votes: 0GitHub stars: 16
- Engineering Escalation PackagePrepare an engineering escalation with minimal reproduction, impact, evidence, suspected boundary, failed hypotheses, workaround status, and exact decision or fix needed.Votes: 0GitHub stars: 16
- Environment ReproductionRecreate a customer or operator environment closely enough to validate a technical failure without copying secrets or unnecessary private data.Votes: 0GitHub stars: 16
- Log Trace TriageTurn noisy logs and traces into a precise failure timeline by correlating identifiers, requests, retries, dependencies, resource state, and user-visible outcomes.Votes: 0GitHub stars: 16
- Technical Case DiagnosisDiagnose a complex support case by reconstructing environment, configuration, timeline, logs, network, dependencies, and reproduction evidence before assigning cause.Votes: 0GitHub stars: 16
- Api DocsWrite API documentation that lets a developer correctly authenticate, call, interpret, retry, paginate, version, and troubleshoot an interface using verified contracts and executable examples.Votes: 0GitHub stars: 16
- Code Example ValidationValidate documentation code examples by executing them against the documented version, checking dependencies, setup, security, output, cleanup, platform assumptions, and consistency with current APIs.Votes: 0GitHub stars: 16
- Migration GuideWrite a technical migration guide from a known old state to a supported new state with compatibility, prerequisites, staged changes, data or configuration transformation, verification, mixed-version behavior, and recovery.Votes: 0GitHub stars: 16
- Release DocsCoordinate the technical documentation required for a release by identifying changed behavior, affected pages, new reference, migration, configuration, examples, troubleshooting, and versioned notices tied to the released state.Votes: 0GitHub stars: 16
- RunbookWrite an operational runbook that turns a recurring or incident response task into safe prerequisites, diagnostics, actions, verification, rollback or recovery, escalation, and evidence capture.Votes: 0GitHub stars: 16
- Technical DocumentationProduce precise developer and operator documentation from verified implementation, interfaces, constraints, examples, and failure behavior.Votes: 0GitHub stars: 16
- Build ToolingDesign and improve build tooling around dependency graphs, incremental correctness, caching, generated inputs, hermeticity, diagnostics, parallelism, reproducibility, and developer/CI feedback time.Votes: 0GitHub stars: 16
- Cli DesignDesign command-line interfaces with task-oriented commands, predictable arguments, composable output, stable exit behavior, safe destructive operations, discoverable help, and script compatibility.Votes: 0GitHub stars: 16
- Code GenerationBuild maintainable code generators with explicit source schemas, deterministic output, minimal generated surface, safe overwrite rules, versioning, validation, and a migration path for generated consumers.Votes: 0GitHub stars: 16
- Developer ToolingBuild developer tooling that turns a repeated engineering workflow into a fast, safe, discoverable, scriptable, and diagnosable interface.Votes: 0GitHub stars: 16
- Editor IntegrationIntegrate engineering capabilities into editors/IDEs with explicit protocol boundaries, workspace awareness, incremental updates, cancellation, diagnostics, compatibility, and fallback behavior.Votes: 0GitHub stars: 16