Extract file analysis (functions, classes, imports) as structured output
From tldr-swintonnpx claudepluginhub mistakeknot/interagency-marketplace --plugin tldr-swintoncommands//extractExtracts UI design patterns like spacing scales, radii, buttons, cards, and depth from TSX/JSX/Vue/Svelte files; generates .interface-design/system.md.
/extractExtracts design tokens, components, architecture, and PRDs from codebases, live products, or PDFs. Prompts for page selection on large PDFs.
/extractExtracts functions, components, modules, hooks, or class methods from code into new units. Replaces originals with calls, updates imports/exports, and verifies behavior with tests.
/extractExtracts facts, examples, metaphors, quotes, and glossary terms from an EPUB book. Supports category filtering, handles parsing prerequisites, and outputs to a directory.
/extractExtract and consolidate reusable components, design tokens, and patterns into your design system. Identifies opportunities for systematic reuse and enriches your component library.
Extract structured metadata from a file — functions, classes, imports, and line ranges — without reading the full source.
tldrs extract "$ARGUMENTS.file"
When to use:
Tips:
tldrs cfg <file> <function> for control flow of a specific function