Kinds / Canonical
blueprints/
How and why a system is designed: patterns and architecture an agent must respect.
71 files · 14 projects
astro-knots22
Maintain an Elegant Open Graph System
A scalable, consistent architecture for Open Graph metadata optimized for the messaging-first share economy.
Maintain Base Engagement Analytics
Page views say someone arrived. Time on page, scroll depth and downloads say whether they read it. One definition of each, for every site.
Maintain Privacy Gates in Three Modes
One gate, three doors: a shared passcode, a verified email on the firm's list, or a link minted for one person. Each opens only what it names.
Maintain Themes and Modes Across CSS and Tailwind
Implementation blueprint for dual-axis theme and mode control using Tailwind CSS v4 custom properties, with runtime utilities and Vitest verification.
Build an Upgrade Ladder Cart from Superset Tiers
Make every tier a strict superset of the one below and the cart can show you the delta instead of swapping in a whole new cart.
Continuous Integration for Astro Knots Sites
Every Astro Knots site has a deploy workflow and none has a test. That is defensible right up until a site imports package source, ships a broken link, or renders raw `[[wikilinks]]` to production — none of which a successful build notices.
Guarantee Text Wrapping and No Horizontal Bleed at Any Width
One Tailwind class caused it: `mx-auto` on a flex item disables stretch, so `<main>` sized to its content instead of its parent.
A Standard Table of Contents for Every Markdown Collection
One reading-position ToC everywhere, built on LFM's heading outline — the only source that tells a heading from a `#` inside a code fence.
Maintain Confidential Access with Persistent Sessions and Auth Telemetry
Signed pre-authed links for named stakeholders, passcodes for everyone else, and telemetry so every silent auth failure leaves a row.
Generate a Pseudomonorepo Rollup of Changelog and Context
Deliberate sync: a human runs `pnpm rollup:sync`, each child's changelog and context-v lands in `src/rollup/`, and the build stays file IO.
Build a Fundraise Deck Workspace
Step-by-step playbook for standing up a private, gated, two-surface fundraise deck workspace, as proven on `sites/calmstorm-decks`.
Build a Promotion Surface for Investment Opportunities
A hard-gated `/promote` hub per opportunity, surfacing deck and memo behind real auth, built for 3–5 minute variant iteration cycles.
Maintain an Interactive Polling System
Embeddable theme-aware polls on Astro SSG: data model, flat-file→database storage progression, vote integrity, Svelte + GSAP contracts.
Maintain an Interactive Polling System
Embeddable theme-aware polls on Astro SSG: the Session/Poll model, Astro DB on Turso, DB→markdown archive, Svelte + GSAP UI contracts.
Maintain Design System and Brand Kit Motions
Every Astro-Knots site ships `/brand-kit` for stakeholders and `/design-system` for developers — this is the scope split and the upkeep.
Citation System Architecture
A citation and reference management system for Astro sites using hex codes as stable identifiers that convert to sequential integers at render time.
Codeblock Syntax Highlighting with Shiki
Blueprint for implementing syntax-highlighted code blocks across astro-knots sites using Shiki with the tokyo-night theme and reusable wrapper components.
Styles Architecture Blueprint
Architecture blueprint for Dark Matter's CSS and Tailwind v4 theming system, defining named brand colors, derived scales, semantic tokens, and three display modes.
Confidential Content Access Control Blueprint
A tiered pattern for protecting privileged or confidential content across astro-knots sites, from simple passcodes to full OAuth integration.
GitHub Secure Content Pattern
A pattern enabling Astro sites to fetch confidential content from a private GitHub repository at runtime, keeping sensitive documents out of static assets.
Slides System for Astro and Markdown
A comprehensive specification for building presentation slide systems in Astro-Knots sites with RevealJS, Three.js, and full theme/mode integration.
astro-knots/blueprints
augment-itai-labs10
Augment-It as Working App and Architecture Demonstration
Augment-it is a working product and a live architecture showcase at once; every decision answers to both lenses so neither quietly wins.
Webhook as Wake-Up, Not as Truth — relaying platform events into CI without trusting them
Polling gets throttled and push payloads are unsigned. Forward the interrupt, not the claim, and both problems stop mattering at once.
Connecting To And Using SurrealDB
The one place that codifies how augment-it talks to SurrealDB Cloud — the five env vars, the connect → signin → use dance, the client-tagging write contract, and the dev-only-credentials posture that a proxy service eventually replaces.
Response–Row Identity Across Promote — Why Responses Outlive Their Rows, and the `record_uuid`-on-Response Fix
Promote deletes parent rows, leaving responses pointed at dead `row_id`s; carrying `record_uuid` on the response resolves them by identity.
Packs and Bundles — The Two-Tier Pattern for Entity-Profile Augmentation (and Beyond)
Two tiers: a pack is one source, one remote, one schema; a bundle is a named composition of packs fired by a single chat verb.
Original and Enhanced Record Instances — the Record-Instance Model
No mutation, no derived set per run: one immutable original plus one mutable enhanced instance per round, promoted to seed the next.
Module Federation + Rsbuild — Dev Loop Gotchas
Five Rsbuild + Module Federation gotchas, cross-origin HMR first: none block adoption, all cost time if you don't see them coming.
Spec-Kit and Context-V Coexistence — How They Work Together in Augment-It
context-v holds the project's living memory; spec-kit drives per-feature implementation flow. Complementary, not competing.
Why Response Reviewer and Highlight Collector Exist — The Verbose-Prose-to-Tabular Bridge
CRM cells are terse and LLM answers are prose; no structured-output regime removes the human integrity check that bridges them.
augment-it/blueprints
ai-labs6
Show the Filesystem of a Workspace
Every ai-labs app sits on a folder the user cannot see. The tree is the same five decisions each time; the backend is the only part that differs.
The Source Curation Gate — A Convergent Prune-and-Promote Surface for AI-Assisted Web Research
Three apps grew the same organ — a human prune-and-promote step between retrieval and generation that the writer cannot then escape.
Install Auth Across Applied AI Labs Apps
Don't re-derive the auth pattern — astro-knots already shipped it. This is the ai-labs handle: what to pull in, which DB, what to translate.
Chat-As-Verb-Surface Patterns — How the In-App Chat Calls Skills, MCP Tools, and Scripts; How it Reads State and Anticipates Lightly
Five conventions that let three apps share a chat surface without sharing a package, starting with capability adapters and one envelope.
Per-App Workspace Conventions — Discipline, Not a Shared Package
No universal `@lossless/workspace` package. What every app shares is the shape: singleton state, an activeView union, a capability registry.
ai-labs/blueprints
cite-widecontent-farm6
Lossless Citation Standards — Schema, Audiences, Portability Thesis
The schema layer: what fields exist, why each exists, and how they outlive any one rendering target. The WHAT and WHY, not the HOW.
Citation Acquisition Pipeline — Agent Architecture, Phases, Output Contract
The HOW for filling the Lossless Citation schema: decouples the cheap capture moment from the expensive canonicalization moment.
Citation Field Acquisition Guide — Per-Field Reference for Filling the Lossless Schema
Per-field reference for the acquisition agent: source of truth, cheap path, expensive fallback, validation rule, and failure behavior.
Maximize Data Collection on Cannonical Sources
Only 1–5 of the 40 sources in a memo earn the rich schema — and a field-by-field split of what is deterministic versus what needs AI.
Parse Common Citation Formats
Six citation patterns coexist in one file; the existing regex only matches [1], so Google's [1, 2, 3] and Perplexity's [1][2] slip through.
cite-wide/blueprints
lossless-monorepo5
Preferred Format for Changelog
Continuous Integration with GitHub Actions
Sixteen workflows across the tree and fourteen of them are deploys. We have automated shipping thoroughly and automated checking almost not at all — so every silent failure still gets caught by a person, in another repo, weeks later.
Understanding codebases with graphify — scope the corpus, take the free tier first
Point graphify at a repo and it will happily graph everything, which is how you get a 4.2M-word hairball that buries the architecture under client PDFs. Scope the corpus first, build code-only for zero tokens, and layer the docs in later.
Browser-drive verification — agents click the buttons before a human walks the surface
Agents prove the buttons work with Playwright MCP before a human judges whether the surface is usable.
lossless-monorepo/blueprints
Lost in Public4
Maintain an Elegant Open Graph System
A scalable, consistent architecture for Open Graph/Twitter share metadata across multi-site Astro projects.
Maintain a Map of Content Paradigm
Implement MOC directive-driven content capacity management for centralized, markdown-native content curation
Improvise a few Creative Component Variants
Generate a few variants of a web component with similar functionality and consistent with the overall design, style, theme, and mode using CSS variables.
Keep a Changelog
Standardized approach to maintaining comprehensive changelogs for code and content changes
lfm4
Maintain Table of Contents from the Heading Outline
`remarkHeadingIds` already attaches a ToC-ready outline. Nobody renders it: the outline is flat and can't flag headings buried in a callout.
Conditional Component Rendering in Layout Pipelines
Implement flexible layout component rendering with optional parameter controls for InfoSidebar and TableOfContents suppression
Maintain Embeddable Slides
lfm/blueprints
dark-matterastro-knots3
Jumbotron Popdown Patterns
Navigation dropdowns that are big enough to preview real content, and consistent enough that adding a new one is a props change rather than a new component.
Using Heartbeat Patterns to Save Session Data
`beforeunload` lies — especially on mobile — so you never really know when a reader stopped reading. Periodic still-here pings turn session duration into something you can actually measure, with no dependencies.
dark-matter/blueprints
context-v-corpus3
Sweep for Frontmatter Consistency & Improvements
The running order for a frontmatter sweep across 40+ repos — including the two steps that, taken out of order, published client material.
Browser-drive verification as a kit practice — operationalizing the Playwright-MCP rung across every Lossless repo
Not how an agent drives a browser — how the practice rolls out: a core-MCP registry, idempotent per-repo wiring, a CLAUDE.md block.
context-v-corpus/blueprints