skills.rest
meaganewaller
meaganewallerCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

friction-deep-dive

Analyzes recurring friction domains from logs and generates a structured practice plan.

3|Updated Nov 19, 2025
Search Tags:#skill development#debugging#troubleshooting#learning#deliberate practice#friction analysis
One-click install
npx skills add https://github.com/meaganewaller/.dotfiles --skill friction-deep-dive
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: friction-deep-dive
Source: https://github.com/meaganewaller/.dotfiles/tree/main/home/.claude/skills/common/friction-deep-dive
Command: npx skills add https://github.com/meaganewaller/.dotfiles --skill friction-deep-dive

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you systematically understand and overcome recurring technical difficulties or areas of confusion that slow down your development process.

Core Features & Use Cases

  • Root Cause Analysis: Identifies why specific errors or challenges keep reappearing.
  • Concept Explanation: Breaks down complex underlying concepts in simple terms.
  • Deliberate Practice Plans: Creates structured, actionable plans to build mastery.
  • Use Case: If you consistently struggle with understanding Rust's ownership model, this skill will analyze your past errors, explain the core concepts, and provide a practice plan to improve your grasp of it.

Quick Start

Use the friction-deep-dive skill to analyze and create a practice plan for the 'dependency' friction domain.

Frequently Asked Questions about friction-deep-dive

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify the root cause of recurring debugging errors in my development workflow?▼

Root cause analysis for recurring debugging errors involves examining your past friction logs to identify whether issues stem from knowledge gaps, tool limitations, workflow mismatches, or environmental factors. This process categorizes recurring technical difficulties to pinpoint exactly why specific challenges keep reappearing.

What is a friction log and how does it help with troubleshooting?▼

A friction log is a record of recurring technical difficulties or areas of confusion encountered during development. It serves as the foundational data for troubleshooting, enabling systematic analysis of recurring friction domains to uncover underlying root causes rather than treating isolated symptoms.

How do I create a deliberate practice plan for skill development after identifying recurring errors?▼

Creating a deliberate practice plan for skill development requires analyzing your friction log to find root causes, then generating a structured, actionable plan to build mastery. This plan directly addresses specific technical domains and knowledge gaps to systematically overcome recurring development friction.

Can I use friction analysis to understand complex technical concepts like a specific programming language's ownership model?▼

Friction analysis can be used to understand complex technical concepts like a programming language's ownership model by analyzing your past errors, explaining the core concepts in simple terms, and providing a structured practice plan to improve your overall grasp of the domain.

What do I need to provide to start a friction analysis of my development environment?▼

To start a friction analysis of your development environment, you need to provide a friction log and a taxonomy of common friction types. These inputs allow the systematic examination of logs to identify root causes related to environmental factors, tool limitations, and workflow mismatches.

Related Skills

Explore More Software Engineering Skills→
parcadeiparcadei
3.9k

morph-apply

Apply targeted file edits using code markers via Morph Apply API.

Community
Advanced
GeargrindadminGeargrindadmin

retrospective-agent

Analyze completed agentic tracks to extract learnings and log errors.

Community
Advanced
allanninalallanninal
1

root-cause-tracing

Trace stack traces and logs to identify root causes of software failures.

Community
Intermediate
enchantednaturesenchantednatures

root-cause-tracing

Trace errors through call stacks to their original triggers.

Community
Advanced