Skill UI

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 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.

A comprehensive technical guide covering the entire lifecycle of Python packaging. It teaches developers how to structure, build, test, and distribute robust Python libraries using modern standards like pyproject.toml, generating wheels, and publishing artifacts reliably to PyPI or private package indexes. Ideal for creating reusable, professional-grade Python code.

Automated quickstart guide generator that kicks in whenever you mention the trigger phrase, offering step-by-step technical documentation guidance, code samples, and validation to ensure API docs, user guides, and architecture notes stay production-ready.

This skill functions as an expert technical writer, generating comprehensive and structured README.md documentation for software projects. It meticulously analyzes the codebase, identifying project structure, tech stack, prerequisites, dependencies, and deployment pipelines, ensuring users receive a complete guide for local setup and production deployment.

Guidelines for responding to code review feedback with technical rigor: read every comment, restate requirements, verify against the codebase, ask clarifying questions, push back when technically needed, and implement fixes one at a time with testing.

This skill specializes in creating exhaustive, searchable, and highly structured technical references. It generates comprehensive API documentation, detailed parameter listings, configuration guides, and schema definitions, ensuring the output serves as the definitive source of truth for any technical system.

This comprehensive guide serves as a quick reference for diagnosing and fixing the most common technical errors encountered in the Replit development environment. It covers critical infrastructure issues such as container lifecycle failures, port binding conflicts, Nix build failures, database limitations, and deployment timeouts, ensuring users can effectively troubleshoot and maintain continuous development workflows.

This workflow guides developers through the systematic process of requesting and acting upon code reviews. It emphasizes the core principle of reviewing early and often, providing structured inputs (commits, requirements, implemented features) via a subagent to catch technical issues, ensure compliance with requirements, and maintain high code quality before merging.