---
schema: 1
type: term
title: '**friction to framework**'
description: >-
  **Friction to framework**: the practice of identifying a recurring point of
  friction in your writing work and converting it into a reusable framework —
  such as a style guide, a skill, or custom instructions — so the same problem
  does not need to be re-solved each time.
canonical: >-
  https://liquidgold.cc/channel/everyinc/explore/term/friction-to-framework-3ae583824843
markdown: >-
  https://liquidgold.cc/channel/everyinc/explore/term/friction-to-framework-3ae583824843.md
llms: null
parent: 'https://liquidgold.cc/channel/everyinc/llms.txt'
channel: everyinc
updated: '2026-10-23T22:12:35.346Z'
language: null
children: []
---


# \*\*friction to framework\*\*

Canonical: https://liquidgold.cc/channel/everyinc/explore/term/friction-to-framework-3ae583824843

Parent: [Channel index](https://liquidgold.cc/channel/everyinc/llms.txt)

## Definition

**Friction to framework**: the practice of identifying a recurring point of friction in your writing work and converting it into a reusable framework — such as a style guide, a skill, or custom instructions — so the same problem does not need to be re-solved each time.

**Friction to framework** describes the move Katie Parrott and Kate Lee discuss in the Q&A: taking a *recurring point of friction* — something that keeps going wrong or keeps needing explanation in your writing work — and turning it into a *reusable framework* your AI setup can apply automatically. In the material, that shows up as the difference between fixing the same problem over and over and encoding the fix once in a **style guide**, a **skill**, or **custom instructions** [^\@\].