Claude Skills by spideynolove

CodeGraphContext (CGC) parses source code with tree-sitter and builds a queryable graph of functions, classes, and their relationships. Use it to answer structural questions that text search can't: "who calls this?", "what would break?", "where is dead code?" Supports 14 languages: Python, JS/TS, Java, C/C++, C#, Go, Rust, Ruby, PHP, Swift, Kotlin, Dart, Perl.

Interactive lesson-level quiz for Claude Code tutorials. Tests understanding of a specific lesson (01-10) with 8-10 questions mixing conceptual and practical knowledge. Use before a lesson to pre-test, during to check progress, or after to verify mastery. Use when asked to "quiz me on hooks", "test my knowledge of lesson 3", "lesson quiz", "practice quiz for MCP", or "do I understand skills".

Comprehensive Claude Code self-assessment and learning path advisor. Runs a multi-category quiz covering 10 feature areas, produces a detailed skill profile with per-topic scores, identifies specific gaps, and generates a personalized learning path with prioritized next steps. Use when asked to "assess my level", "take the quiz", "find my level", "where should I start", "what should I learn next", "check my skills", "skill check", or "level up".

Fast headless browser for fetching real web pages and scraping content. 9x less memory than Chrome, instant startup. Use instead of Playwright when you only need HTML content — no MCP overhead, pure CLI. Binary at ~/.local/bin/lightpanda.

Browser automation via Playwright MCP through mcporter. Use when you need to navigate pages, extract data, take screenshots, interact with UI elements, or scrape web content. All tools called via mcporter to avoid context pollution.

Use this skill when: - Starting work on a codebase you want to remember across sessions - Extracting and persisting architectural facts (components, dependencies, decisions) - Building a project knowledge graph from a repomix-packed codebase - Querying previously stored architectural context instead of re-reading files

Invoke repomix **before** any task that requires whole-repository understanding: - Writing specs or architecture docs that reference multiple directories - 04-uiux planning stage (before IntentSpec, LayoutSpec, TokenSpec) - Reviewing consistency across many files - Answering "how does X work across the codebase" questions - Onboarding to an unfamiliar codebase

Structure cognitive analysis using sequential reasoning chains. Use for codebase analysis, pattern extraction, complex problem decomposition, and building mental models before implementation.

Sync Claude Code skills to Codex CLI and Qwen Code via filesystem symlinks. One source of truth at ~/.claude/skills/, symlinked into ~/.codex/skills/ and ~/.qwen/skills/. Respects targets: frontmatter field.

Autonomous Goal-directed Iteration. Apply Karpathy's autoresearch principles to ANY task. Loops autonomously — modify, verify, keep/discard, repeat. Supports bounded iteration via Iterations: N inline config.

Combine vector and keyword search for improved retrieval. Use when implementing RAG systems, building search engines, or when neither approach alone provides sufficient recall.