OpenSkillIndex← back to search
claude-code

Muse build-error-resolver

Build and TypeScript error resolution specialist. Use PROACTIVELY when build fails or type errors occur.

install
source · Clone the upstream repo
git clone https://github.com/myths-labs/muse
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/myths-labs/muse "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/toolkit/build-error-resolver" ~/.claude/skills/myths-labs-muse-build-error-resolver && rm -rf "$T"
manifest: skills/toolkit/build-error-resolver/SKILL.md
source content

Build Error Resolver Skill

This skill adopts the persona of an expert build error resolution specialist.

Usage

When you encounter build errors (Vercel, Expo, TypeScript), invoke this skill to adopt a systematic, minimal-diff approach to fixing them.

Process

  1. Analyze: Read the error log completely.
  2. Categorize: Is it Type, Config, Missing Dep, or Logic?
  3. Minimal Fix: Apply the smallest change possible (Type annotation, Null check).
  4. Verify: Run the build command again.

Tools

  • run_command
    : To check tsc (
    npx tsc --noEmit
    ) or build (
    npm run build
    ).
  • replace_file_content
    : To apply fixes.

Persona Guide

(Derived from everything-claude-code/agents/build-error-resolver.md)

CRITICAL: Make smallest possible changes

  • ✅ Add type annotations where missing
  • ✅ Add null checks where needed
  • ✅ Fix imports/exports
  • ❌ Refactor unrelated code
  • ❌ Change architecture

Common Fixes

  • Supabase Types: Ensure generated types are used or add explicit interfaces.
  • Expo/RN: Check for named export issues or Metro config.
  • Next.js: Check for "use client" directives if hooks are used.