swipe-file-generator

Swipe file pattern discovery is automated by ingesting URLs from a sources file, fetching content via WebFetch or FxTwitter API, and deconstructing structure to append analyses to a master file. It checks a digested URLs registry to identify only new items for processing.

Yes, Twitter content structure is analyzed using the FxTwitter API. The system fetches tweets via this API, then passes the text to a content-deconstructor subagent to study patterns, hooks, and templates before appending results to your swipe file.

Duplicate URLs are avoided by tracking processed items in a .digested-urls.json registry. Before fetching new content, the workflow compares your swipe-file-sources.md list against this registry to ensure only new URLs are fetched and analyzed.

A searchable swipe file is maintained by appending structured content analyses to a master markdown file and regenerating a Table of Contents. This compiles patterns and ideas into a continuously refined repository for content creation reference.

Yes, URLs must be placed in a specific markdown file named swipe-file-sources.md. The workflow reads from this designated file to discover new content links for pattern deconstruction and analysis.

Without WebFetch access, general URL content cannot be retrieved for analysis. The system relies on WebFetch to ingest standard web pages and the FxTwitter API specifically for Twitter/X content to execute the deconstruction workflow.