
Claude Skills by risadams
github.com/risadamsUse when you need to audit dependencies for vulnerabilities, resolve version conflicts, optimize bundle sizes, or implement automated dependency updates.
Use when designing, building, or optimizing CI/CD pipelines and deployment automation strategies.
Use when you need to translate a DESIGN.md into polished Claude Code instructions for building user interfaces that faithfully match the chosen brand. Invoke this skill whenever a developer or designer asks to replicate the look and feel of an existing product or website.
Use when building or optimizing infrastructure automation, CI/CD pipelines, containerization strategies, and deployment workflows to accelerate software delivery while maintaining reliability and security.
Use when actively responding to production incidents, diagnosing critical service failures, or conducting incident postmortems to implement permanent fixes and preventative measures.
Use when building Django 4+ web applications, REST APIs, or modernizing existing Django projects with async views and enterprise patterns.
Use when you need to build, optimize, or secure Docker container images and orchestration for production environments.
Use when you need to create, architect, or overhaul comprehensive documentation systems including API docs, tutorials, guides, and developer-friendly content that keeps pace with code changes.
Actively build and sharpen a project's domain model — challenge fuzzy terms, stress-test with scenarios, and write CONTEXT.md and ADRs inline as decisions crystallise. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.
Use when building .NET Core applications requiring cloud-native architecture, high-performance microservices, modern C# patterns, or cross-platform deployment with minimal APIs and advanced ASP.NET Core features.
Use when working on legacy .NET Framework 4.8 enterprise applications that require maintenance, modernization, or integration with Windows-based infrastructure.
Use when optimizing the complete developer workflow including build times, feedback loops, testing efficiency, and developer satisfaction metrics across the entire development environment.
Use when building Electron desktop applications that require native OS integration, cross-platform distribution, security hardening, and performance optimization. Use electron-pro for complete desktop app development from architecture to signed, distributable installers.
Use when you need to build fault-tolerant, concurrent systems leveraging OTP patterns, GenServer architectures, and Phoenix framework for real-time applications.
Use when developing firmware for resource-constrained microcontrollers, implementing RTOS-based applications, or optimizing real-time systems where hardware constraints, latency guarantees, and reliability are critical.
Score today's load (meetings, sensory demand, social events, deep work), flag burnout risk, and suggest what to drop or defer. Use when the user says "energy budget", "spoon check", "am I overcommitted", "what should I drop", or invokes /energy-budget.
Use when distributed system errors occur and need coordinated handling across multiple components, or when you need to implement comprehensive error recovery strategies with automated failure detection and cascade prevention.
Use when you need to diagnose why errors are occurring in your system, correlate errors across services, identify root causes, and prevent future failures.
Use when building mobile applications with Expo and React Native that require native module integration, navigation setup, performant animations, push notifications, OTA updates, or App Store/Play Store deployment.
Use when building modern async Python APIs with FastAPI, implementing Pydantic v2 validation, dependency injection patterns, or deploying high-performance ASGI applications.
Use when building payment systems, financial integrations, or compliance-heavy financial applications that require secure transaction processing, regulatory adherence, and high transaction accuracy.
Use when the user wants to challenge assumptions, break down a complex problem from scratch, or approach something with first principles reasoning. Triggers on: 'first principles', 'challenge assumptions', 'why do we do it this way', 'rethink', 'from scratch', 'fundamental truths'.
Use when building cross-platform mobile applications with Flutter 3+ that require custom UI implementation, complex state management, native platform integrations, or performance optimization across iOS/Android/Web.
Use when building complete frontend applications across React, Vue, and Angular frameworks requiring multi-framework expertise and full-stack integration.
Use when you need to build complete features spanning database, API, and frontend layers together as a cohesive unit.
Use when implementing game systems, optimizing graphics rendering, building multiplayer networking, or developing gameplay mechanics for games targeting specific platforms.
Use when the user needs to understand GDPR or CCPA compliance, review data practices, or assess privacy requirements. Triggers on: 'GDPR', 'CCPA', 'privacy compliance', 'data privacy', 'right to deletion', 'consent', 'data subject rights', 'California privacy'.
Use when you need to design, establish, or optimize Git workflows, branching strategies, and merge management for a project or team.
Use when building Go applications requiring concurrent programming, high-performance systems, microservices, or cloud-native architectures where idiomatic patterns, error handling excellence, and efficiency are critical.
Morning kickoff wrapper running sprint-snapshot, daily-standup-prep, and daily-briefing in order; idempotent on same-day re-runs. Use when the user says "good morning", "morning routine", "kick off my day", "start my day", or invokes /good-morning.
Use when building and configuring Gradle projects, optimizing build performance, managing dependencies, implementing multi-module architectures, or modernizing legacy build systems. Expert in Gradle 7+/8+ and build automation best practices.
Use when designing or evolving GraphQL schemas across microservices, implementing federation architectures, or optimizing query performance in distributed graphs.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
Use when the user wants to design a growth loop, understand PLG mechanics, or build sustainable acquisition. Triggers on: 'growth loop', 'flywheel', 'viral loop', 'PLG growth', 'product-led growth', 'growth mechanics', 'how do we grow', 'word of mouth'.
Compact the current conversation into a handoff document for another agent to pick up.
Use when working on healthcare administration tasks including revenue cycle management, HIPAA/compliance auditing, medical coding (ICD-10, CPT, DRGs), CMS cost reports, payer contract analysis, quality improvement, clinical operations, health IT/interoperability, population health, and pharmacy benefits.
Use when the user is building a healthcare product and needs to understand HIPAA compliance. Triggers on: 'HIPAA', 'protected health information', 'PHI', 'healthcare compliance', 'covered entity', 'business associate', 'BAA', 'HITECH', 'health data'.
Park a deep work session before an interruption — capture what is only in your head, write a park file, drop a breadcrumb at the cursor. Use when the user says "I have to stop", "meeting in 10", "park this", "save my place", or invokes /hyperfocus-exit.
Reconstruct context after a deep session or interruption from git diff, modified files, and recent commits, then propose the next concrete action. Use when the user says "what was I doing", "where did I leave off", "lost my place", or invokes /hyperfocus-recovery.
Shape every response for an autistic reader — direct statements, required/optional labels, literal language, quantified uncertainty, named social subtext. Use when the user says "I'm autistic", asks for literal or direct output, or invokes /i-am-autistic — then keep applying it all session.
Shape every response for a reader with ADHD — next action first, numbered steps, progress restated each turn, one thread, numeric time estimates. Use when the user says "I have ADHD", asks for ADHD-shaped output, or invokes /i-have-adhd — then keep applying it all session.
Weigh one or more ideas with a structured pros-and-cons analysis and a Go / Go with caveats / Don't recommendation. Use when the user wants to evaluate an idea before committing, compare options on the merits, score tradeoffs, or asks "should I do X" / "is X worth it".
Force a binary pick when the user is stuck between options — three clarifying questions, then a verdict with reasoning. The fast counterpart to idea-choice. Use when the user says "I can't decide", "help me pick", "decision paralysis", "break the tie", or invokes /idea- decision-maker.
Helps users generate, refine, and stress-test ideas from loose topics. Use when user asks to brainstorm, find new ideas, or needs creative inspiration for a topic.
Build a piece of work (ticket, spec, or free-form request) through a tunable pipeline — test-first, verify, review, and track — where every phase can be skipped or tuned. Use when the user wants to actually build something, from a throwaway prototype to a CCB-gated feature.
Use when an active security breach, service outage, or operational incident requires immediate response, evidence preservation, and coordinated recovery.
Capture the current hyperfixation into the Obsidian vault fast, so it isn't lost and doesn't derail today's work. Use when the user says "capture this idea", "hyperfixation dump", "interest capture", "stash this", "don't let me forget", or invokes /interest- capture.
Use when designing and deploying IoT solutions requiring expertise in device management, edge computing, cloud integration, and handling challenges like massive device scale, complex connectivity scenarios, or real-time data pipelines.
Draft a customer-facing release note for a Jira ticket from its context and linked merge requests. Read-only unless the user opts in to publish. Use when the user says "draft release notes", "write a release note", "release note for [TICKET-KEY]", or invokes /issue-draft-release-notes.