Menu
SkillsMP has collected 13 skills from infinyte/custom_claude_skills. Open a skill to review its source and details.
Showing 13 of 13 collected skills.
Transform GitHub repositories into production-ready portfolio websites. Auto-detects project type, guides interactive customization, generates multi-page responsive sites with GitHub Actions deployment. Triggers on any GitHub URL + portfolio/website/showcase…
Performs a structured analysis of any GitHub repository with user-selectable report depth and output formats. Users choose between Full (comprehensive, all sections, editorial depth) or Short (essentials-focused, condensed) reports, then select output format:…
Transform technical projects into compelling portfolio pieces with executive summaries, technical deep-dives, architecture diagrams, impact metrics, and demo-ready GitHub Pages. Analyzes GitHub repos and project descriptions to generate audience-specific…
Transforms any combination of inputs — text descriptions, uploaded images, uploaded files (PDF, DOCX, code, etc.) — into a high-quality, reusable prompt optimized for a specified target (Claude system prompt, autonomous agent instruction, image generation…
Transform unstructured project plans, task lists, or feature descriptions into standardized, well-formatted todo issues in Markdown. Use this skill whenever the user provides raw project notes, feature lists, requirements docs, or any informal task…
A rigorous multi-lens review of any codebase, design doc, architecture, API, or artifact. Runs a Feynman clarity check (can it be explained simply?) plus three lenses: an Enterprise Architect (systems, boundaries, evolvability, reversibility), a Principal…
Manages session continuity for a long-running investigation, audit, or research project that spans multiple Claude sessions. Because Claude has no memory between sessions, this skill defines a structured session-package format carrying findings, open…
Applies Michael Feathers' Working Effectively with Legacy Code discipline when changing code that lacks trustworthy tests or has unclear, hard-to-observe behavior: characterize current behavior before redesigning it, find or create a seam, break the one…
Applies Andrew Hunt and David Thomas's Pragmatic Programmer discipline as a general engineering operating style: own the result beyond the local edit, keep one authoritative source for each piece of system knowledge (DRY), preserve orthogonality between…
Applies Michael Nygard's Release It! discipline when building or reviewing services, APIs, jobs, or queues that must survive production failure: put explicit timeouts on outbound calls, retry only when safe and bounded, isolate failures with circuit breakers…
Applies Martin Fowler's Refactoring discipline when changing existing code: preserve observable behavior, work in small reversible steps, establish a safety net before risky changes, and remove real structural friction without turning cleanup into a rewrite.…
Applies John Ousterhout's A Philosophy of Software Design discipline when designing or reshaping modules and interfaces: treat cognitive load as the primary metric, prefer deep modules with narrow interfaces that hide real complexity, and eliminate special…
Enforce disciplined vertical-slice, test-driven design and development for any requested code implementation. Use whenever the user asks Claude to implement, build, modify, refactor, fix, add behavior, create a feature, address a bug, or perform any…