Fabric is an open-source framework for augmenting humans using AI, centered on a large library of crowdsourced prompt templates called 'patterns'. The system provides a CLI tool, a REST API server, and a SvelteKit web UI, all sharing a common pattern engine that applies structured prompts to user input (text, URLs, YouTube videos, PDFs, images). The architecture is modular: a plugin registry manages AI vendor adapters (OpenAI, Anthropic, Gemini, Ollama, Azure, Bedrock, Vertex AI, and 25+ OpenAI-compatible providers), a template engine supports variable substitution and executable extensions, and a filesystem-backed storage layer handles patterns, sessions, and contexts with path-traversal protection. Key entry points include the Go CLI (`cmd/fabric`), the Gin-based REST API (`internal/server`), and the SvelteKit web app (`web/`). External dependencies span multiple AI SDKs, web scraping libraries (go-readability), YouTube transcription (yt-dlp), and SQLite for caching. The pattern library itself is a data asset with over 100 markdown files, each defining identity, steps, and output instructions for tasks like summarization, analysis, code review, and creative writing.
This repository is an 'awesome list' — a curated reference index, not a software application or data pipeline. The only source content is README.md and a cover image; there is no executable code, build system, CI configuration, dependency manifest, or test suite. The README renders on GitHub as a single structured markdown table cataloging roughly 130 design systems from organizations including Adobe, Google, IBM, Microsoft, Shopify, GOV.UK, Salesforce, and many others. Each entry records four attributes: coded Components, Voice & Tone guidance, Designers Kit availability, and public Source code links. Editorial scaffolding includes tag definitions, a note distinguishing design systems from UI/pattern libraries, and a licensing caveat that open-source status does not guarantee free reuse. The closest classification is 'application' as a static documentation/curation artifact, though it is genuinely neither an application nor a data-research repository — the README's table could be parsed as a small dataset, but no pipeline exists around it. Maintenance is demonstrably active: the last commit is recent, only 9 issues are open against 26k stars, and the table contains newly launched design systems (e.g., Cloudflare Kumo, HeroUI, shadcn/ui, Semrush Intergalactic, AWS Cloudscape) that could only have been added recently. The contribution model is pull-request based, and the table format has stayed consistent while the catalog grew. For its genre, editorial quality is good: a consistent column schema, clean symbols, stable anchor links to external documentation, and clearly separated source-code hosts. There are no highlighted components. A markdown table is the entire artifact, so nothing can be extracted as a reusable code module and there is no architecture to assess. The practical reuse value is as a discovery index: an AI agent or engineer could scrape the table to build a design-systems directory dataset, since the format is regular and machine-parseable. Technical drift is low by definition — plain markdown does not age — though a handful of external links point to discontinued projects (e.g., Pivotal, Materialize, Bolt), which is a content-level concern rather than a codebase one. This is a high-value reference resource for frontend engineers and designers, but it is not an engineering codebase.