Skill UI

This guide provides comprehensive principles for developing games specifically for mobile platforms. It covers essential technical constraints and best practices, including optimizing for touch input, managing battery life and thermal performance, adhering to platform-specific requirements (iOS/Android), and selecting appropriate monetization models. Use this when designing highly optimized, user-centric mobile gaming experiences.

This elite workflow simulates the comprehensive process of a Senior Software Engineer and Product Designer. It enforces a rigorous development pipeline: starting with planning, solid architecture, and TDD implementation, through clean code practices, and technical auditing. Crucially, it includes mandatory, pixel-perfect UX visual validation to ensure the output is flawless, consistent, and production-grade.

This advanced workflow emulates an elite Senior Software Engineer and Senior Product Designer, ensuring maximum quality output. It enforces a rigorous, multi-step process including ultra-fast planning, solid architecture design, TDD implementation, clean code refactoring, technical auditing, and crucially, mandatory pixel-perfect UI/UX validation. Use this for complex projects demanding both robust code and flawless visual presentation.

Converts product or technical specs into detailed Notion implementation plans, tasks, and progress logs so Claude code can execute requirements tracking from inception to completion.

A comprehensive guide for developers to diagnose and fix the six most common errors encountered when building Obsidian plugins. It covers critical technical issues such as null pointer exceptions, manifest loading failures, incorrect CSS paths, command registration timing, and state persistence bugs, ensuring reliable and stable plugin functionality.

This runbook provides systematic procedures for diagnosing and resolving critical failures within the Obsidian knowledge base. It guides users through recovering from plugin crashes, vault corruption, sync conflicts, and performance degradation using advanced command-line tools and developer console access. Essential for advanced users and technical support.

This comprehensive checklist guides developers through the pre-release verification process for Obsidian community plugins. It covers critical technical areas such as validating manifest structure, ensuring clean production builds (e.g., removing sourcemaps), identifying potential memory leaks, and verifying cross-platform readiness, ensuring a high-quality user experience upon submission.

This comprehensive guide defines the secure data lifecycle management for OpenEvidence, an AI-powered platform for clinical evidence synthesis. It outlines data classification (e.g., clinical queries, patient responses), strict adherence to global regulations (HIPAA, GDPR, FDA), and technical requirements for handling Protected Health Information (PHI). Key processes include PHI de-identification, data validation, secure API integration, and compliant data export, ensuring the system maintains the highest level of patient privacy and regulatory compliance.

This deep dive guide provides comprehensive strategies and detailed checklists for migrating to the OpenEvidence platform. It covers various migration methods, such as parallel run, Strangler fig, and Big bang approaches. The guide assists technical teams in planning the transition by addressing key areas including API mapping, data migration plans, rollback procedures, and performance baselines, ensuring a secure and smooth transition for healthcare IT systems.

A comprehensive technical audit checklist designed to validate the production readiness of OpenRouter API integrations. It covers critical areas including security practices (e.g., secret management, key rotation), system reliability (e.g., fallbacks, retries, timeouts), and observability requirements (e.g., structured logging, cost tracking). Use this guide before launching or during major operational reviews to ensure robust, scalable, and compliant deployments.

This tool is designed to collect comprehensive diagnostic evidence for troubleshooting Perplexity API issues. It automatically gathers critical environment details (OS, Node/Python versions), tests API connectivity, and captures redacted configuration settings. The resulting secure bundle is ideal for submitting detailed support tickets or sharing with technical teammates.

This comprehensive guide teaches the best practices for writing effective, blameless postmortem reports following technical incidents. It provides a structured approach to documenting timelines, conducting root cause analysis (RCA), identifying systemic failures, and creating actionable follow-up items. Mastering this skill is crucial for fostering organizational learning and preventing future service disruptions.