The Proof
The corpus.
1122 living docs from 40 projects. One small agency's actual work — specs, plans, prompts, blueprints, reminders, agent-skills, explorations, issues; the experimental tier of loops, handoffs, decisions, and contracts; and the long tail of habits, workflows, and journals we haven't yet fit into the canonical taxonomy. Browse, search, steal what's useful.
Sorted by repo, then by most recently modified. Use the search page to filter by kind, tag, or repo.
agent-harnesses 11 docs
-
Agent Harnesses — Answers to the Plan's Targeted Questions
Phase 2, not a survey: three questions — MCP tool scoping, trajectory logs, per-project config swaps — answered from the profiles.
inquiry/Targeted-Questions-for-Cross-Product-Shell.md -
aider
Aider has no tool-call loop and no MCP client — not a thin one, none at all. It reads diffs straight out of plain chat text.
profiles/Profile__Aider.md -
autogen
Every AutoGen team type overrides exactly one method — `select_speaker()` — and that single seam is the whole difference between them.
profiles/Profile__AutoGen.md -
cline
"Memory Bank", the cross-session memory pattern Cline is best known for, has zero lines of code behind it.
profiles/Profile__Cline.md -
codex
Codex compiles a real Apple Seatbelt profile and Landlock ruleset: a fully autonomous session that never prompts is still jailed by the OS.
profiles/Profile__Codex.md -
continue
Five differently-scoped assistants can ship side by side in one project and swap mid-session — hot-swapping a skillset per project.
profiles/Profile__Continue.md -
goose
In Goose, "extension" just means "a live MCP client" — and two variants skip the subprocess entirely to run in-process.
profiles/Profile__Goose.md -
mcp-python-sdk
The pinned checkout is the unstable half of a rework: v2 swaps `FastMCP`/`ClientSession` out for `MCPServer`/`Client`.
profiles/Profile__MCP-Python-SDK.md -
opencode
A terminal coding agent with 38 SQLite migrations and real OTLP tracing — built like a production SaaS backend, and no Go anywhere.
profiles/Profile__Opencode.md -
openhands
Pin `OpenHands/OpenHands` today and you do not get the agent — the CodeAct loop moved out to a versioned pip dependency.
profiles/Profile__OpenHands.md -
pi
Pi's docs refuse MCP, sub-agents, permission popups, and plan mode by name — then ship every one as a first-party example extension.
profiles/Profile__Pi.md
ai-labs 43 docs
-
corpora-builder on didi.sh Entities — signup, login, and who sees which corpus
The tenancy primitive is already built and it's flat. corpora-builder should inherit it, not invent a second one.
plans/Corpora-Builder-On-Didi-Entities.md -
didi.sh Login and Workspace-Delivered Config — the plan across three repos
corpora-builder should get its config — R2 credentials included — from the didi.sh workspace, not a local `.env`.
plans/Didi-Login-and-Workspace-Config-for-Corpora.md -
id.didi.sh — the Didi Identity Service
One owned identity service: headless-first API, a signed session cookie on `.didi.sh`, invite-only accounts — built on Elixir/Phoenix.
specs/Id-Didi-Sh-Identity-Service.md -
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.
blueprints/Show-The-Filesystem-Of-A-Workspace.md -
A Syncbox for Client Document Folders — Where Does History Actually Live?
The ask is one product. The prior art says it's three layers, and nothing on the shelf does all three on a bucket.
explorations/A-Syncbox-For-Client-Document-Folders.md -
Sync Corpora to R2, and Show Clients What Changed
The R2 prefix has held zero objects for fourteen days — and the corpus grew anyway, in git. Mirror first, version later.
plans/Sync-Corpora-to-R2-and-Show-Clients-What-Changed.md -
corpora-builder Is Not augment-it Tooling
It was born inside augment-it and split out. The relationship is inheritance, not overlap — and its purpose is bigger than either app.
reminders/Corpora-Builder-Is-Not-Augment-It-Tooling.md -
Load the theme system before touching tokens
Three layers, two axes, three modes. And the ai-labs palette is augment-it's — not the shared-styles package nothing renders.
reminders/Load-The-Theme-System-Before-Touching-Tokens.md -
Never Run jj in a Git LFS Repo
jj does not run smudge/clean filters. In an LFS repo it commits the real bytes over the pointers — 282 MB in one save.
reminders/Never-Run-JJ-In-A-Git-LFS-Repo.md -
didi.sh — One Login, One Agent, Three Services
memos, decks, and augment-it become one family coordinated by exactly two shared planes: a common identity service and one agent named didi. Consumer one is live; the local-auth question is now closed.
explorations/Didi-sh-One-Login-One-Agent-Three-Services.md -
Secrets for Collaborators Who Will Never Open a Terminal
Collaborators who will never open a terminal still carry API keys — so serve capabilities from a remote MCP plane, secrets held server-side.
explorations/Secrets-for-Collaborators-Who-Will-Never-Open-a-Terminal.md -
State-Inspector as a universal need — every ai-labs app hides its state from the people running it
No ai-labs app can answer "what does it currently believe?" — rune singletons, deck state, LangGraph FlowState, none inspectable.
issues/State-Inspector-As-A-Universal-Need-Across-Apps.md -
Cross-Product Native Agent Shell — Synthesis and Architecture Decision
Resolves the fork the in-app-agent docs left open — extend memopop-native or build standalone — against sixteen pinned repos' actual source.
explorations/Cross-Product-Native-Agent-Shell.md -
In-App Agent Chat — As-Built vs. As-Specced (Internal Audit)
`@lossless/in-app-agent` was never built — augment-it inlined the WorkspaceAdapter pattern into `@augment-it/workspace` instead.
explorations/In-App-Agent-Chat-As-Built-vs-As-Specced.md -
Study Agent Harnesses + Conversational UI, Then Decide the Cross-Product Native Shell
Pin two studies and audit in-house prior art before designing a Tauri shell that swaps context across three apps. No code lands here.
plans/Study-Agent-Harnesses-and-Conversational-UI-Before-Cross-Product-Shell.md -
SurrealDB MCP + a verification skill — querying augment-it's canonical layer directly, starting with FreedomFest 2026
plans/SurrealDB-MCP-Plus-Skill-for-Canonical-Layer-Verification.md -
Shared Auth for Applied AI Labs
Three sibling apps need login; none is at Auth0/Clerk scale. A small owned system: OAuth, invites, org-scoped roles, a roll-up seam.
explorations/Shared-Auth-for-Applied-AI-Labs.md -
Two Clients, One Flow — Corpora by Domain-Type, Auth, and Deployment Converge
reach-edu wants corpus→memos by strategy, humain-vc by thesis — and typed domains, shared auth, and deployment all came due at once.
explorations/Two-Clients-One-Flow-Corpora-Auth-and-Deployment-Converge.md -
Unlock: the humain-vc team (two people) logs into a deployed augment-it
One flow: a humain-vc member signs in with her work email, lands in her workspace, works the thesis corpus. Single-tenant deploy on purpose.
plans/Unlock-Humain-VC-Team-Access-To-Augment-It.md -
The Source Curation Surface — A Component Architecture for a Svelte Rebuild
Decomposes a proven single-file curation tool into Svelte components: a runes store, a tree of small components, one API contract.
specs/Source-Curation-Surface-Component-Spec.md -
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.
blueprints/Source-Curation-Gate.md -
The Drag in AI-Assisted Web Research — Diagnosis, Prior Art, and the Open Forks for a Source Curation Gate
AI research yields enough hallucinated sources that manual Google + Docs looks time-competitive. The drag is structural, not a prompt bug.
issues/Drag-in-AI-Assisted-Web-Research-and-the-Source-Curation-Gate.md -
Corpus-Grounded Generation — Memory & Graph Layers for Producing Decks and Memos Without Drift
A pipeline where every factual sentence in a deck or memo traces to a source span — and the model abstains when it can't.
explorations/Corpus-Grounded-Generation-of-Decks-and-Memos.md -
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.
blueprints/Install-Auth-Across-Applied-AI-Labs-Apps.md -
Cloud Variant of the Dididecks-AI Workspace — Recreating Local Privacy When the Filesystem Isn't Yours
Clients who won't install a desktop app still need the privacy local-fs gives for free. What a cloud runtime would have to do explicitly.
explorations/Cloud-Variant-of-Dididecks-AI-Workspace.md -
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.
blueprints/Chat-As-Verb-Surface-Patterns.md -
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.
blueprints/Per-App-Workspace-Conventions.md -
Memory Layers for the In-App Chat Package
Maps the eight pinned memory systems onto roles in the chat package, and picks the v1 stack given we already lean on Chroma.
explorations/Memory-Layers-for-the-In-App-Chat-Package.md -
Remote Mount Contract for @lossless/in-app-agent — How the Chat Surface Drives Federated Views Without Owning State
How the chat surface drives federated views without owning state: capability invocation goes through the per-app workspace, never the chat.
explorations/Remote-Mount-Contract-for-In-App-Agent.md -
In-App Agent Chat — Walking Skeleton Plan
One session's work: scaffold the package, do the Chroma tenant migration, and ship `slide.read` end-to-end as proof the abstractions hold.
plans/In-App-Agent-Chat-Walking-Skeleton.md -
Agent Capabilities — Hooking the Chat Surface into Memopop
How the In-App Agent Chat pattern maps onto memopop-ai: where each layer lands in the repo, and the smallest read-only proof-of-life.
plans/Slides_Agent-Capabilities_Hooking-the-Chat-Surface-into-Memopop.md -
The Anatomy of the In-App Agent Shell — Shell, Workspace, Window, Chat
"Shell" meant four things at once: layout frame, workspace package, Window, chat. The workspace is the source of truth — not the chat.
plans/Slides_Anatomy-of-the-In-App-Agent-Shell.md -
Per-App Workspaces and the Chat as Optional Surface — The Architecture We Walked To
State of truth lives per app in `@<app>/workspace`. The chat package is UI-only, reaching it through a typed WorkspaceAdapter.
plans/Slides_Per-App-Workspaces-and-the-Chat-as-Optional-Surface.md -
In-App Chat as the Agent Surface for Client Apps
Rather than design a button for every client request, wire one chat surface loaded with our patterns and context. The chat is the menu.
explorations/In-App-Chat-as-Agent-Surface-for-Client-Apps.md -
In-App Agent Chat — Core Package Spec
One package — capability registry, BYOK proxy contract, chat UI API, transcript schema — targeting web and Tauri, proven first on dididecks.
specs/In-App-Agent-Chat-Core-Package.md -
When Claud Code and When Pi
explorations/When-Claud-Code-and-When-Pi.md -
Add a Chroma Local UI Interface
Local Chroma in PersistentClient mode is an embedded SQLite library with no UI of its own. Three paths to a browseable surface — from a 30-line inspect script tonight to a /chroma route in the splash later — laid out in increasing commitment.
plans/Add-Chroma-Local-UI-Interface.md -
Context Vigilance Splash Page — Narrative Brief
Designer brief for the Context Vigilance splash. The functional plumbing exists; the structural skills are codified elsewhere. This doc is only about the *story* — the four-act narrative arc and the emotional move each act should produce.
plans/Context-Vigilance-Splash-Page-Narrative.md -
Track and Ingest Lossless Content into Chroma (with Change Detection)
A second ingestion pipeline parallel to the context-v corpus — for the ~5K Lossless content files scattered across the monorepo. Driven by its own sources map, with content-hash-based change detection so re-runs only re-embed what actually changed.
plans/Track-and-Ingest-Lossless-Content-into-Chroma.md -
Write Custom Chroma MCP Server (v0: a session-transcript ingester)
Defer djm81/chroma_mcp_server; write our own session-transcript ingester into the Chroma the corpus lives in, so the two cross-query.
plans/Write-Custom-Chroma-MCP-Server.md -
ChromaDB as Context Improvement Across Everything, Everyone
A founding-team demo reframed Chroma: not a place to put embeddings, but an ingestion layer for agent traces and session transcripts.
explorations/ChromaDB-as-Context-Improvement-Across-Everything-Everyone.md -
Collate Context Files into Context Vigilance as Repo & Project
A long-running, everywhere-distributed practice — context-v/ across a tree of pseudomonorepos — finally graduates into a project of its own, with a collator, a splash, and a vector index.
explorations/Collate-Context-Files-into-Context-Vigilance-as-Repo-&-Project.md -
Preferred Stack — uv over pip, and other defaults
reminders/Preferred-Stack.md
arthouse-site 2 docs
-
Services Section as a Tiered, Categorized Card Catalog
A Sveltia-driven Services surface shaped Category → Card → Tier, where optional tags tick the price up before the order goes to WhatsApp.
specs/Services-Section-as-Tiered-Card-Catalog.md -
Sveltia CMS — Constraints That Shape Architecture
Sveltia is not Decap: the extension points it dropped — above all the custom media library API — become silent no-ops, not errors.
issues/Sveltia-Constraints-for-CMS.md
astro-knots 83 docs
-
Dates are UTC at rest, viewer-local at render
reminders/Dates-Are-UTC-At-Rest-Viewer-Local-At-Render.md -
Nine hand-rolled frontmatter parsers, all functionally identical
One YAML bug had to be fixed nine times. The nine copies turn out to be byte-different and behaviourally identical — the drift is brace style, nothing more.
issues/Nine-Hand-Rolled-Frontmatter-Parsers-All-Functionally-Identical.md -
Versatile Component Library for Video Players
Videos links can come from various sources, and include metadata, playlists, and other information that handled to maximize the value of video content, all from simple markdown triggers.
specs/Versatile-Component-Library-for-Video-Players.md -
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.
blueprints/Continuous-Integration-for-Astro-Knots-Sites.md -
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.
blueprints/Guarantee-Text-Wrapping-and-No-Horizontal-Bleed-at-Any-Width.md -
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.
blueprints/Standard-Table-of-Contents-for-Every-Markdown-Collection.md -
Preference for Shortcuts in Config to Absolute Paths
`../../../components/basics/DeckHeader.astro` breaks the moment you move the importer; `@components/…` reads the same from anywhere.
reminders/Preference-for-Shortcuts-in-Config-to-Absolute-Paths.md -
Rule to Assure Collection Schema is Flexible
A lenient Zod schema doesn't remove the failure, it moves it — the build goes green and the date renders blank instead.
reminders/Rule-to-Assure-Collection-Schema-is-Flexible.md -
Include Full Search as a Default
Search ships from the first build via `astro-pagefind`, not at some size threshold. Seven surfaces have it; fifteen do not.
specs/Include-Full-Search-as-a-Default.md -
Images in LFM render without intrinsic dimensions
Both image paths in the LFM renderer emit an <img> with no width or height, so every image will shift the page as it loads. Latent today because no changelog has images — about to stop being latent.
issues/Images-in-LFM-Render-Without-Intrinsic-Dimensions.md -
Dependency Upgrade Loop
Fan out across all active Astro Knots sites, upgrade dependencies, fix breaking changes, verify builds, write changelogs, and push — looping until all sites are clean.
loops/Dependency-Upgrade-Loop.md -
AI Photo-to-Illustration Transform for Arthouse
Exploring how to take a real client photograph — sometimes NSFW-sensitive — and return an obviously AI-generated illustrative version (anime, painterly, or stylized) that is safe to publish on the public arthouse-site portfolio.
explorations/AI-Photo-to-Illustration-Transform-for-Arthouse.md -
Image Catalog and ImageKit Hosting for Arthouse
The repo stays public because it holds metadata only; ImageKit holds the bytes, and a privacy tier keeps NSFW originals out of the output.
specs/Image-Catalog-and-ImageKit-Hosting-for-Arthouse.md -
Polish Pass for Arthouse Site
Takes arthouse-site from scaffold-complete to client-presentable, with an AI photo-to-illustration pipeline for sensitive source material.
specs/Polish-Pass-for-Arthouse-Site.md -
Astro Frontmatter: Avoid Inline Block Comments and Risky Regex Literals
In `.astro` frontmatter, a `/* */` comment after a statement lexes as a regex literal — the error reports a column past EOF. Use `//`.
reminders/Astro-Frontmatter-Avoid-Inline-Block-Comments-and-Risky-Regex.md -
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.
blueprints/Maintain-Confidential-Access-with-Persistent-Sessions-and-Auth-Telemetry.md -
Rethinking Confidential Access with Persistent Sessions and Auth Telemetry
The calmstorm-decks lockout — busy client, no telemetry — exposed the passcode pattern's limit: you can't tell a failed cookie from a typo.
explorations/Rethinking-Confidential-Access-with-Persistent-Sessions-and-Auth-Telemetry.md -
Wikilink Resolution System for LFM
LFM parses `[[Obsidian-style]]` links; each site supplies the config resolving them to local or external URLs and styling the destination.
plans/Wikilink-Resolution-System.md -
Wrap Long String Values in Double Quotes
Long YAML string values — descriptions, titles with punctuation, URLs with query strings, ledes — should always be wrapped in double quotes. Cheap insurance against the entire class of YAML-syntax-collision bugs.
reminders/Wrap-Long-String-Values-in-Double-Quotes.md -
YAML Frontmatter Parsing Must Be Lenient
Across every Astro Knots site, content frontmatter parsing must tolerate messy YAML — log a warning and skip the file, never fail the whole build. No strict YAML parsers, ever.
reminders/YAML-Frontmatter-Parsing-Must-Be-Lenient.md -
Callout System (LFM)
Three-file split for rendering Lossless Flavored Markdown callouts — structure, type registry, and mode-aware styles. Every type obeys the light/dark/vibrant mode switcher.
sitemap/components/Component__Callout-System.md -
Dynamic Portfolio Page Specification and Implementation Plan
Three clickable levels — logo grid, expanding card, detail page — with a passcode gate that reveals placeholders, not real data.
specs/Dynamic-Portfolio-Page-Specification-and-Implementation-Plan.md -
Converge on an Animations Playbook
Lottie the format is open; every tool that produces one is proprietary SaaS. A tiered motion playbook for Astro Knots given that lock-in.
explorations/Converge-on-an-Animations-Playbook.md -
Implementing Full-Text Search by Default
Every Astro Knots site should ship with full-text search out of the box. This is a tour of what that costs, why Pagefind (a Rust-powered static indexer) is the strong default, and what the runner-up libraries are for the cases where it isn't.
explorations/Implementing-Full-Text-Search-by-Default.md -
Workspace vs JSR for LFM Consumers
Four sites got flipped to `workspace:*` during the LFM extraction. Only one should be — Vercel never checks out the parent workspace.
issues/Workspace-vs-JSR-for-LFM-Consumers.md -
Ideogram Style Prefix for Splash OG Images
Reusable Ideogram preamble that conditions generated OpenGraph and share images to match the astro-knots splash — knot-and-thread motif, the splash's three-mode palette, and an editorial typographic sensibility. Paste before your subject line.
prompts/Ideogram-Style-Prefix-for-Splash-OG-Images.md -
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.
blueprints/Generate-a-Pseudomonorepo-Rollup-of-Changelog-and-Context.md -
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`.
blueprints/Build-a-Fundraise-Deck-Workspace.md -
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.
blueprints/Build-a-Promotion-Surface-for-Investment-Opportunities.md -
Astro Check Type Errors on mpstaton-site
`pnpm build` passes while `astro check` reports 8 errors — five root causes, only one of which lossless-site shares.
issues/Astro-Check-Type-Errors-on-mpstaton-site.md -
Hot Reload for Raw-Filesystem Content (across astro-knots sites)
`readFileSync` content never hot-reloads — it sits outside Astro's content layer. Needs a Vite watcher AND a dev cache bypass, not either.
issues/Hot-Reload-for-Raw-Filesystem-Content.md -
Set up a Splash Page with Changelog and Context-V Rendering
Brief prompt for scaffolding a small standalone repo (its own GitHub project, deployed to GitHub Pages) that renders its own changelog and context-v markdown through @lossless-group/lfm.
prompts/Set-up-a-Splash-Page-with-Changelog-and-Context-V-Rendering.md -
Codifying a Comprehensive Extended Markdown Flavor and Shared Package
A named, versioned markdown flavor that codifies what we already render, backed by one shared remark/rehype package.
specs/Codifying-a-Comprehensive-Extended-Markdown-Flavor-and-Shared-Package.md -
Practices to Sense-Make Context Vigilance at Scale
An exploration of lightweight conventions, indices, templates, and tooling that keep a context-v library legible as it grows from dozens to hundreds of documents — without introducing a new system to maintain.
explorations/Practices-to-Sense-Make-Context-Vigilance-at-Scale.md -
Context-V — Context Vigilance for AI-Native Software Teams
A working library of the documents we feed to Claude Code so we can build sites, apps, and design systems at remarkable speed — and a directory schema that keeps that library legible as it grows.
README.md -
Web Research Agents for Content Augmentation
Point an agent at a URL and have it fill out a tool's YAML frontmatter — and why most agent-framework hype is the wrong tool for that job.
explorations/Web-Research-Agents-for-Content-Augmentation.md -
Write a Changelog Prior to Meaningful Commits
A quick reference for writing a changelog prior to meaningful commits.
reminders/Write-a-Changelog-Prior-to-Meaningful-Commits.md -
Maintain an Interactive Polling System
Embeddable theme-aware polls on Astro SSG: data model, flat-file→database storage progression, vote integrity, Svelte + GSAP contracts.
blueprints/Maintain-an-Interactive-Polling-System.md -
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.
blueprints/Maintain-an-Interactive-Polling-System--v2.md -
Choosing an Image Generator for Text-on-Background Banners
An April 2026 snapshot of image generators judged on one job: release-banner images with legible title text and a consistent brand feel.
explorations/Choosing-an-Image-Generator-for-Text-on-Background-Banners.md -
Discuss How to Publish Long Form Like eBook
Starlight, mdBook, and Quartz all lose to hand-rolling with LFM — because the 1,751-line handbook forces LFM's wishlist forward.
prompts/Discuss-how-to-Publish-Long-Form-like-eBook.md -
Quirks of Obsidian Flavored Markdown
A quick reference for the quirks of Obsidian Flavored Markdown.
reminders/Quirks-of-Obsidian-Flavored-Markdown.md -
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.
blueprints/Maintain-Design-System-and-Brandkit-Motions.md -
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.
blueprints/Maintain-Themes-Mode-Across-CSS-Tailwind.md -
Documentation Gaps Blocking New Site Onboarding
The canonical markdown package has no package.json, and the reference site uses the `workspace:*` pin CLAUDE.md forbids.
issues/Documentation-Gaps-Blocking-New-Site-Onboarding.md -
New Site Quickstart Guide
Step-by-step guide for scaffolding a new Astro site in the astro-knots monorepo, from empty directory to working markdown rendering.
prompts/New-Site-Quickstart-Guide.md -
Exploring GitHub Actions for Package Publishing
A practical walkthrough of what GitHub Actions are, how they work, and how to use them to publish packages to JSR and GitHub Packages with provenance — written for someone who has never set up CI/CD before.
explorations/Exploring-GitHub-Actions-for-Package-Publishing.md -
Remark-Citations: A Unified Plugin for Hex-Code Footnote Management
A standalone remark plugin that transforms footnote identifiers (hex codes, numeric, or mixed) into sequentially-numbered citations with structured metadata parsing, designed for the unified/remark ecosystem and bundled into @lossless-group/lfm.
specs/Remark-Citations-Plugin-for-Hex-Code-Footnote-Management.md -
Resolving Mode Switching Across Multiple Components
Astro scopes your `[data-mode]` selector to the component, but the attribute lives on `<html>` — it never matches. `:global()` is the fix.
issues/Resolving-Mode-Switching-Across-Multiple-Components.md -
Scripting Across Multiple Tables in NocoDB
Links emailAccess rows to Organizations by email domain, minting orgs as needed — via the `[linkField.id]: [{id}]` update syntax.
issues/Scripting-across-Multiple-Tables-in-NocoDB.md -
SSH Key Passphrase Prompts - macOS Keychain Integration
The passphrase prompt returned because `~/.ssh/config` had `UseKeychain` only under `Host gitlab.com` — a `Host *` block fixes the rest.
issues/SSH-Key-Passphrase-Prompts.md -
Create an Image-Heavy Portfolio Website for Boutique E-Commerce
A mobile-first, image-heavy portfolio site: carousel galleries, tiered pricing cards, WhatsApp CTA, all managed through markdown.
specs/Maintain-an-Image-Heavy-Portfolio-Site.md -
Flare: Concentric Wobble Rings
Creative brief and technical spec for an interactive concentric-rings animation — imperfect circles radiating from an off-center origin with mouse hover repulsion and click ripple effects. Inspired by greenoaks.com.
prompts/Flare__Concentric-Wobble-Rings.md -
Design System Pages Per Site
Every site should have a design-system route with browsable pages for components, flare, and layouts — built with zero-friction by Code Assistants, not a third-party documentation tool.
reminders/Design-System-Pages-Per-Site.md -
Flare Components — Creative Workflow
Flare is our naming convention for design-oriented components — images, illustrations, and animations as code. This reminder covers naming, preferred tech, and the creative brief workflow.
reminders/Flare-Components-Creative-Workflow.md -
Improvising within Design System Color Palettes
A reminder to AI code assistants and developers: use named colors and design tokens; when improvising raw hex or rgba values, reintegrate them into the system.
reminders/Improvising-within-Design-System-Color-Palettes.md -
Portfolio-Wide Job Aggregator
A specification for scraping, aggregating, and displaying job openings across a venture capital firm's portfolio companies — built as a reusable pattern for any VC client site.
specs/Portfolio-Wide-Job-Aggregator.md -
New Homebrew Formulae Worth Knowing About
A quick-hit survey of six new Homebrew formulae — dispenso, jsongrep, opentimestamps-client, proxelar, qtcanvaspainter, and qttasktree — with an honest assessment of what each does and whether our dev team should care.
explorations/New-Homebrew-Formulae-Worth-Knowing-About.md -
Understanding the JavaScript Runtime and Package Manager Landscape
A ground-up exploration of what Node, Deno, Bun, npm, pnpm, Yarn, Vite, tsup, and esbuild actually are, why they exist, how they relate to each other, and when to use which — because the JavaScript ecosystem never explains itself.
explorations/Understanding-the-JavaScript-Runtime-and-Package-Manager-Landscape.md -
Tags Must Use Train-Case
All tags in YAML frontmatter must use Train-Case — capitalize each word, hyphens between words, no spaces, no underscores, no all-lowercase.
reminders/Tags-Must-Use-Train-Case.md -
Implement Context-V Fetcher for mpstaton-site
Step-by-step implementation guide for adding a build-time GitHub content fetcher to mpstaton-site that pulls context-v documents from multiple repos.
prompts/Implement-Context-V-Fetcher-for-mpstaton-site.md -
Context-V GitHub Fetcher for Multi-Repo Content Aggregation
A build-time fetcher that pulls context-v documents from ~20 repos, so lossless.group can render them without copying or submodules.
specs/Context-V-GitHub-Fetcher-for-Multi-Repo-Content-Aggregation.md -
Develop a Slides-only Astro Site for a Fundraise Process
A slides-only Astro site that stays consistnent with relevant Context Vigilance files fed into AI Assistant context.
specs/Develop-a-Slides-only-Astro-Site-for-a-Fundraise-Process.md -
Maintain an Elegant Open Graph System
A scalable, consistent architecture for Open Graph metadata optimized for the messaging-first share economy.
blueprints/Maintain-an-Elegant-Open-Graph-System.md -
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.
blueprints/Citation-System-Architecture.md -
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.
blueprints/Codeblock-Syntax-Highlighting-with-Shiki.md -
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.
blueprints/Styles-Architecture-Blueprint.md -
Papermark Self-Hosted Dataroom Deployment
Complete deployment specification for self-hosting Papermark as an open-source virtual data room for sharing investment memos, pitch decks, and due diligence documents.
Papermark-Self-Hosted-Dataroom-Deployment.md -
Implement Portfolio with Confidential Access in New Site
Step-by-step implementation plan for adding portfolio features with confidential access control to the dark-matter site, based on proven patterns from hypernova-site.
prompts/Implement-Portfolio-with-Confidential-Access-in-new-Site.md -
Set Up Index and Basic Components Using Brand Theme
A prompt plan for evolving index pages and basic components to use the brand theme system instead of hard-coded colors, with step-by-step instructions for Cascade/Windsurf.
prompts/Set-Up-Index-and-Basic-Components-using-Brand-Theme.md -
Astro Knots is not a True Monorepo
A reminder that Astro-Knots is organized like a monorepo but functions as a collection of independent Astro projects for convenient pattern porting.
reminders/Astro-Knots-is-not-a-True-Monorepo.md -
Preferred Stack
A quick reference for the preferred technology stack: HTML/CSS first, Astro for SSG, Svelte for interactivity, Tailwind for styling, and no React.
reminders/Preferred-Stack.md -
Team Pages Specification
Agency-wide specification defining how astro-knots sites should implement data-driven team pages with role-based grouping, shared data models, and brand theming.
sitemap/pages/team/Team-Pages-Specification.md -
Team Spans Page Spec
Specification for a responsive grid layout displaying team members grouped by roles in contiguous spans with CSS Grid and consistent card styling.
sitemap/pages/team/Team-Spans-Page-Spec.md -
Introducing Features and UI Components
Prompt for introducing features and UI components to the Hypernova site, including team pages, responsive design patterns, and branded exports.
prompts/Introducing-Features-and-UI-Components.md -
Dynamic Webpage to Display Portfolio w Authentication
Dynamically display portfolio information on a branded webpage, with certain types of information only displayed for certain privileges connected to authentication.
specs/Dynamic-Webpage-to-Display-Portfolio-w-Authentication.md -
Jumbotron Popdown Patterns
Design and implementation patterns for consistent jumbotron popdown menus in the Lossless UI.
blueprints/Jumbotron-Popdown-Patterns.md -
Exploring Publishing Component Library for VC Firms
Strategic exploration of publishing @knots packages as a component library for venture capital firms, evaluating approaches from Web Components to shadcn-style CLI distribution.
strategy/Exploring-Publishing-Component-Library-for-VC-Firms.md -
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.
blueprints/Confidential-Content-Access-Control-Blueprint.md -
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.
blueprints/GitHub-Secure-Content-Pattern.md -
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.
blueprints/Slides-System-for-Astro-and-Markdown.md -
astro-knots/agent-skills/dependency-upgrade-loop/skill
Fan out across all active Astro Knots sites, upgrade dependencies in safe → risky order (patch/minor first, then major bumps like Astro and TypeScript), fix breaking changes, verify builds with `pnpm build` + `pnpm exec astro check`, write changelog entries, and push submodules. Loops until every site is current. Invoke via `/loop` to self-pace across all sites, or pass a specific site name to target one.
agent-skills/dependency-upgrade-loop/SKILL.md -
Fetch Brand and Tokens from Client Site
Extract colors, fonts, and design tokens from a client's existing website to bootstrap theme.css with brand-aligned values. Uses curl/fetch to grab CSS and design assets.
prompts/Fetch-Brand-and-Tokens-from-Site.md
augment-it 171 docs
-
Every remote hardcodes the workspace WebSocket to localhost — Org Workbench loads no data on augment.didi.sh
Sixteen remotes dial `ws://localhost:3001/ws` with no env read. On prod that points at the visitor's own laptop, so the socket shows `closed` and the roster never fills.
issues/Every-Remote-Hardcodes-The-Workspace-WS-To-Localhost-So-Prod-Loads-No-Data.md -
Tokens landed, components didn't — the UI needs an overhaul, and the drift linter can't see the problem
19 of 20 apps consume the theme package; shared-ui ships exactly two components. Every remote hand-rolls its own buttons, pills, and empty states against shared colours.
issues/Tokens-Landed-Components-Didnt-The-UI-Needs-An-Overhaul.md -
A failed deploy is silent, so nothing watches production after merge
Every frontend Docker build failed for twelve days unnoticed: the old container keeps serving and the health check keeps passing.
issues/A-Failed-Deploy-Is-Silent-Nothing-Watches-Production-After-Merge.md -
Domain type is ambient state, so a failed workspace load hides every corpus
humain-vc opened the Corpora Curator and saw 'strategy' and 'No corpora yet' — it has theses, and plenty of them. One guessed value at load time silently filtered the whole surface, and the same symptom was debugged out once already on 2026-07-07.
issues/Domain-Type-Is-Ambient-State-So-A-Failed-Workspace-Load-Hides-Every-Corpus.md -
One stuck message kills a NATS subject until restart — `domain.list: timeout` and the sequential handler loop
Every handler in `domains.ts` consumes its subject with a `for await` loop, so one unsettled request blocks the subject until a restart.
issues/One-Stuck-Message-Kills-A-NATS-Subject-Until-Restart.md -
Rename the corpora curator — finishing a rename that only ever reached the label
Four naming layers were tangled here and only three moved — the fourth is a data value living in two external client repos.
refactors/Rename-Strategy-Curator-To-Corpora-Curator.md -
Federated Component Libraries
One gallery runtime, seventeen sovereign catalogs — every member publishes what it is made of, at its own address.
specs/Federated-Component-Libraries.md -
Sharing code without breaking microfrontend autonomy: build-time import IS the copy
With no `shared` block, a workspace import is inlined into all seventeen bundles. The cost isn't runtime coupling, it's redeploy fan-out.
notes/Sharing-Code-Without-Breaking-Microfrontend-Autonomy.md -
Why this monorepo does not need Turbo: a task graph with no edges
Turbo's core directive is `dependsOn: ["^build"]` — build my dependencies first. No package in packages/ has a build step, so it resolves to nothing. We adopted a best practice for an architecture we then didn't build.
notes/Why-This-Monorepo-Does-Not-Need-Turbo.md -
Structural refactors surfaced by the codebase graph — the deadweight, the boilerplate, and the CSS convergence problem
A zero-token graph over 490 files found ~500 lines that delete cleanly, 11 near-identical `mount.ts` files, and no duplicate CSS after all.
refactors/Structural-Refactors-Surfaced-by-the-Codebase-Graph.md -
Move the rest of the app to remote hosting — prod still falls back to localhost for every undeployed remote
12 micro-frontends are hardcoded to `http://localhost:3XXX` in the prod shell, so augment.didi.sh fetches them from the visitor's machine.
issues/Move-Remaining-Remotes-To-Remote-Hosting-Prod-Falls-Back-To-Localhost.md -
Concurrent agent searches queue into a search-results column — fire many, deal with them as they come
Agent searches run 60–210s and each one hijacks a single column. Wanted: a rightmost queue where every fired search appends its own card.
issues/Concurrent-Agent-Searches-Queue-Into-A-Search-Results-Column.md -
Fetch full content clobbers the operator's metadata — resets the title to a URL approximation
`fetchSourceContent` never consulted the saved title, so Jina's guess — or the raw URL on failure — overwrote what the operator typed.
issues/Fetch-Full-Content-Clobbers-Operator-Metadata.md -
Jina metadata parser is blog-only — needs two profiles + fuzzy routing (academic sources lose their date/publisher)
The parser only reads OpenGraph keys, so scholarly sources lose date and publisher to `citation_*` / `dc.*` / `prism.*` it never looks at.
issues/Jina-Metadata-Parser-Is-Blog-Only-Needs-Two-Profiles-And-Routing.md -
No test coverage — TDD keeps getting deferred, despite being exactly the right fit for agentic development
Agents rewrite this codebase with zero automated tests — and the iterate-until-green loop is exactly what agents are best at. Pick a runner.
issues/No-Test-Coverage-TDD-Deferred-Despite-Agentic-Fit.md -
Parent-Child Nested Organizations Are Not Modeled — Initiatives, Funds, and Sub-Orgs Have Nowhere Canonical to Hang
`upmobility-foundation-urban-institute` welds a parent org to its initiative, so triaged content has no honest folder to land in.
issues/Parent-Child-Nested-Organizations-Not-Modeled.md -
Refactoring for API Speed — a single-user app should boot in milliseconds, not a minute
Measured: shell mount to workspaces ready is ~543ms. The perceived minute was a stale deploy plus remotes hanging on `localhost:3XXX`.
issues/Refactoring-for-API-Speed.md -
Search & Add's invokes never reach the workspace — the pane hangs at 'searching…' while every backend rung is green
SearXNG answers, `search.fire` answers, the org card loads — yet the 🔍 pane hangs forever. The frame dies inside the client transport.
issues/Search-And-Add-Invokes-Never-Reach-The-Workspace.md -
Session expiry turns the app into a zombie — the 12h JWT dies mid-use, the UI stays up, and every invoke times out
The `didi_session` cookie lives 30 days, the JWT inside ~12h, and nothing calls `/api/session/refresh` — the transport 4401-loops at 2/sec.
issues/Session-Expiry-Turns-The-App-Into-A-Zombie.md -
Tag input swallows commas into one mega-tag — commas should split into separate tags
`toDashed` splits on every non-alphanumeric, so commas behave like spaces and three intended tags fuse into one mega-tag.
issues/Tag-Input-Swallows-Commas-Into-One-Mega-Tag.md -
Troubleshooting workspace ↔ DB state alignment — humain-vc's corpora don't load, and the canonical layer holds fewer than the operator created
The humain-vc workspace renders empty-or-wrong corpora while the canonical layer itself holds fewer humain-vc domains than the operator remembers creating — four suspects, each with a discriminating signature.
issues/Troubleshooting-Workspace-DB-State-Alignment.md -
Workspace + corpora connection is slow-to-hanging, and the auth token won't persist
The Corpora Curator sits at 'connecting…' and the workspace switcher at 'loading…' — corpora never arrive — while the didi session drops within a minute of signing in, forcing a re-login. Two symptoms that most likely share one root cause.
issues/Workspace-And-Corpora-Connection-Slow-To-Hanging-And-Auth-Wont-Persist.md -
From a Raised Issue to Fixed-and-Shipped — the bug-to-ship loop
A raised issue becomes a context-v issue doc, a gh issue, then an attempt→verify cycle that safety-commits every failed try and milestone-commits the win — closing with a changelog beat and an offer to bump semver + tag.
loops/From-a-Raised-Issue-to-Fixed-and-Shipped.md -
Libraries We Do Not Use — Ever
A hard denylist of packages this codebase has removed on purpose. Do not import them, do not assume they are installed, do not re-add them.
reminders/Libraries-we-Do-Not-Use-Ever.md -
Source Content Storage — SurrealDB-Primary, Local as a Per-User Toggle
Flip the content store: the article body moves onto the canonical `sources` row and the local filesystem write demotes to a toggle.
specs/Source-Content-Storage-SurrealDB-Primary-Local-As-Toggle.md -
Design Language Audit — July 2026
The hand-counted baseline audit that measured the state of augment-it's CSS before the design system shipped. Superseded as the counting mechanism by design-drift.mjs.
explorations/Design-Language-Audit-2026-07.md -
Sweep — Local & Federated Design System for Fidelity
The repeatable procedure for checking a member's CSS against the federal contract. The one sanctioned exception to the two-file rule.
loops/Sweep-Local-Federated-Design-System-for-Fidelity.md -
Corpora Builder Harmony — the evolving test registry
Every proposed and implemented test guarding the corpora builder and the systems it must harmonize with — identity, workspace connector, transport, state, canonical layer, files — in human language, MECE, one ✓-phrase each.
specs/Corpora-Builder-Harmony-Test-Registry.md -
Design System Portal
Specification for the portal that renders the federated design system — the swatch page, the token catalogue, the member index.
specs/Design-System-Portal.md -
Federated Design System Architecture
The organising specification for augment-it's two-tier, seventeen-member design system.
specs/Federated-Design-System-Architecture.md -
The four layers: pnpm, Turbo, rsbuild Module Federation, and where Bun would fit
There isn't one 'monorepo' system — there are four independent ones, and the word 'federation' means two different things across them. Untangling which tool owns which job, and what Bun would actually replace.
notes/The-Four-Layers-pnpm-Turbo-rsbuild-Federation-Bun.md -
Two tiers: WebSocket to the gateway, NATS between services
The browser talks WebSocket to one gateway; the gateway talks NATS to every service. They aren't alternatives — they're two legs of one design, and the gateway between them is where tenancy lives.
notes/Two-Tiers-WebSocket-To-The-Gateway-NATS-Between-Services.md -
Test coverage — pick the harness, seed the suite from the prove-scripts, and loop the open bugs to green
Vitest + Playwright for this repo, ExUnit already standing in id-didi-sh — convert the six prove-scripts into a permanent suite, then write the humain-vc corpora bugs as failing tests and iterate until they pass.
plans/Test-Coverage-Harness-And-Regression-Floor.md -
Funder↔strategy is tags for now — whether it deserves a real edge is deferred
140 strategy tags landed on 69 funders, but a tag can't carry evidence counts, gift sizes, or recency. The edge question comes due later.
issues/Funder-Strategy-Connection-Tags-Now-Edges-Maybe.md -
Header polish — the FLOW label and shell suffix have outlived their jobs, and the chat toggle sits on the wrong side
Four findings from the first production walk-through — including a chat toggle on the right that opens a rail pinned to the left.
issues/Header-Polish-Flow-Label-Chat-Toggle-Placement-Shell-Suffix.md -
Relation kinds are inverse pairs — one stored string can't speak from both seats
NextLadder is funded_by Ballmer Group; Ballmer Group is funder_of NextLadder — the same edge needs a different kind string per perspective, and today only one pair is special-cased in a read-time map.
issues/Relation-Kinds-Are-Inverse-Pairs.md -
Open augment.didi.sh to reach-edu — a second tenant instance, and Stephenie Tesoro as the first client user
The data is already deployed; only the door is single-tenant. Open it with a per-client instance, not a relaxed org check.
plans/Open-Augment-Didi-Sh-To-Reach-Edu.md -
Implement-Feature Loop — plan → gh tickets → code/verify/changelog/commit per ticket → human browser test → ship
The generic feature-execution cadence: a signed-off plan becomes gh tickets, each ticket lands as verified code + a changelog beat + a conventions-clean commit, and the run closes with a human browser test and a ship() commit.
loops/Implement-Feature-Loop.md -
CRM Starter Export — the pipeline shape, enriched from the canonical layer: orgs first, then people attached
Two CSVs seed the empty CRM from the canonical layer: organizations first, people second, attached by a stable key. Corpora excluded.
plans/CRM-Starter-Export-Orgs-Then-People.md -
Org Relations (parent/child/peer) + Org Tags — model, capabilities, and the Org Workbench surface
Organizations finally get edges to each other — parent, child, or peer, with a typed flavor and free-text human context — plus their first tag mechanism (Initiative, Program, Funder), all workable from the Org Workbench card.
plans/Org-Relations-Parent-Child-Peer-Plus-Org-Tags.md -
Capability Gaps Surfaced by the First Triage Co-Pilot Run — One Collective Ledger, Not Five Tickets
Five gaps from the first triage run — including direct SurrealDB writes whose string-typed ids silently failed to join their org rows.
issues/Capability-Gaps-Surfaced-by-First-Triage-Run.md -
Tags Are Two Projections — Frontmatter `tags:` on Files, `has_tag` Observations in SurrealDB
Files say `tags:` because Obsidian reads files; the DB says `has_tag` because its predicates are verb-shaped. Same fact, two projections.
reminders/Tags-Are-Two-Projections-Frontmatter-and-Has-Tag-Observations.md -
Corpus adds don't fetch metadata — and the row gives no cue either way, and there's no inspector to see or fix it
`organization.corpus.add` writes url, kind, and domain then stops — the Jina metadata fetch never fires, and nothing on the row says so.
issues/Corpus-Adds-Dont-Fetch-Metadata-No-Cue-No-Inspector.md -
Corpus items aren't visible on person cards — and corpus coverage across entities is hard to assess anywhere
The person card says 'Corpus items 3' and shows nothing — the operator can add a fourth without ever seeing the three that exist.
issues/Corpus-Items-Not-Visible-On-Person-Cards-Coverage-Hard-To-Assess.md -
Crawl progress is a black box — 'crawling the web, this takes a minute…' needs traces the operator can watch
The model narrates as it crawls — `extractText` skips straight past it to the final answer, so the operator gets a minute of ellipsis.
issues/Crawl-Progress-Is-A-Black-Box-Needs-Traces-The-Operator-Can-Watch.md -
Crawl replies can be lost — the eternal 'crawling…' spinner (no client timeout, reconnect-dropped invokes, tight dispatch ceiling)
The Curry Foundation crawl finished in 87s and the tab spun forever: no client deadline, reconnect-dropped invokes, a 300s ceiling.
issues/Crawl-Replies-Can-Be-Lost-Eternal-Spinner-No-Client-Timeout.md -
The crawl's search substrate is fixed to Anthropic web search — the operator expected to choose
The manual 🔍 has a provider palette; `organization.crawl` is hardwired to Anthropic's server-side web_search with no dial and no label.
issues/Crawl-Substrate-Is-Fixed-To-Anthropic-Web-Search-Operator-Expected-A-Choice.md -
Switching flows from the Flows popdown doesn't surface the new flow's stage — a rotation-step click is required
Switching flows flips the pill but leaves the stage blank until a step-bubble click. Only tabs with persisted layout state reproduce it.
issues/Flow-Switch-Doesnt-Surface-The-New-Flows-Stage-Step-Bubble-Click-Required.md -
Invokes survive reconnects — the claim protocol closes the eternal-spinner root cause
Two crawls finished server-side while the tab spun forever. Pending invokes now survive a socket drop and re-attach by id via claim frames.
issues/Invokes-Survive-Reconnects-The-Claim-Protocol.md -
List rows show hostname only — the path is hidden, so same-domain entries are indistinguishable
`AdditiveList`'s `host()` drops the pathname, so two Gates Foundation links both render as `gatesfoundation.org` and can't be told apart.
issues/List-Rows-Show-Hostname-Only-Same-Domain-Entries-Indistinguishable.md -
Live/not-live indicator tooling — parts of the UI feel dead, and there's no single view that says whether everything is actually working
Five distinct failures — dead remote, dead socket, dead service, no refresh, unwired button — all present to the operator as one dead click.
issues/Live-Not-Live-Indicator-Tooling-And-Cross-Service-Error-Surfacing.md -
Merging organizations or people — when two objects turn out to be the same entity, dedupe non-destructively
Two rows are sometimes the same entity and nothing merges them — no edge re-pointing, no list union, no slug absorbed into `aliases[]`.
issues/Merge-Organizations-Or-People-Non-Destructive-Dedupe.md -
No component library — the UI is improvised per-remote instead of component-based, and it's starting to show
Fourteen remotes improvised their own UI, so status pills and candidate pickers now exist in parallel dialects. The bill is arriving.
issues/No-Component-Library-UI-Improvised-Not-Component-Based.md -
No user visibility into state — the app needs a State-Inspector surface
State lives in five places and none are inspectable from inside the app — nothing shows which remote currently believes what.
issues/No-User-Visibility-Into-State-Needs-A-State-Inspector.md -
Org Workbench in a narrow pane — the roster doesn't collapse, and the org card's contents spill out of their container
In a narrow pane the roster keeps its 300px and the card's link rows overflow — the flexbox `min-width: auto` trap, twice.
issues/Org-Workbench-Narrow-Layout-Roster-Doesnt-Collapse-Card-Contents-Spill.md -
The Org Workbench can't create an organization — and creation must sit behind a 'be sure there is no match' gate
The workbench can only find orgs that exist. Creation must sit behind the same show-every-match gate that already governs adding a person.
issues/Org-Workbench-Needs-Create-Organization-Behind-A-No-Match-Gate.md -
A person's bio page on another org's site is an affiliation signal, not just an identity link — the UI should offer the promotion
A bio on another org's domain is three facts — identity link, affiliation evidence, observation. The card captures one and drops two.
issues/Person-Bio-Pages-Are-Affiliation-Signals-Not-Just-Identity-Links.md -
Pulse streams need an editable kind and a user-facing name — 'Today's Credentials' is not an 'updates_index'
The operator can neither fix a stream's inferred kind nor record its name — `media_streams[]` has no title field for Today's Credentials.
issues/Pulse-Streams-Need-Editable-Kind-And-User-Facing-Names.md -
The search column holds stale results — a new agent search doesn't reload it
The team crawl bypasses the Search & Add envelope, so the column sits frozen on the last search's candidates, masquerading as current.
issues/Search-Column-Holds-Stale-Results-New-Agent-Searches-Dont-Reload-It.md -
Team-crawl accept drops the crawled links and leaves the staged row — double-save risk
`person.apply` writes `linkedin_profile_url` as a scalar only, so accept discards the crawl's links — and the staged row lingers.
issues/Team-Crawl-Accept-Drops-Crawled-Links-And-Leaves-The-Staged-Row.md -
Didi crawl — three targets (links, streams, team members), the relevance brief, and staged team ingest
One `organization.crawl` capability over Anthropic's server-side web_search, driven by a per-workspace, operator-editable relevance brief.
plans/Didi-Crawl-Three-Targets-Relevance-Brief-And-Staged-Team-Ingest.md -
Workbench usability sweep — corpus visibility, stream editing, and promote-to-affiliation (issues #20 · #26 · #25)
Today's scope from the first real workbench session: make the person card's three invisible corpus items visible, let the operator fix a stream's kind and give it its real name, and turn a bio-page link row into a three-click affiliation.
plans/Workbench-Usability-Sweep-Corpus-Visibility-Stream-Editing-Affiliation-Promotion.md -
Workspace-scope legibility — empty workspaces and stale org restores should explain themselves, not look broken
Switching to a workspace with 0 orgs made the workbench look dead — the visibility rules were right, only the messaging failed.
plans/Workspace-Scope-Legibility-Empty-Workspace-And-Stale-Restore-Handling.md -
Augment from DB — the Org Workbench + Search-and-Add flow: two new microfrontends over capabilities that mostly exist
Start from a canonical org, not a CSV row: an org workbench over links, streams, corpus and people, plus provider-pluggable search-and-add.
specs/Augment-From-DB-Flow.md -
Entity-Card Edit & Remove Affordances — every visible property gets a micro-button pair
The org card views and edits in place, but only additively — a misclicked ➕ today required a direct database write to undo. Every entry and identity property the card shows grows ✎ and × micro-buttons.
specs/Entity-Card-Edit-And-Remove-Affordances.md -
Search-Results Queue — a right-rail microfrontend where concurrent agent searches land, signal, and get triaged
Agent searches run minutes; the operator shouldn't. Every search becomes a card in a persistent right rail — fire many, triage on arrival.
specs/Search-Results-Queue-Remote.md -
Loop through a spec — write the plan, implement, test, changelog, commit, repeat until Shipped
The phase loop that took Augment-From-DB-Flow from Signed-Off to Shipped in one day: plan, implement, prove, changelog, commit — per phase.
loops/Loop-through-Spec-Write-Plans-Implement-Test-Changelog-Commit.md -
Augment from DB · Phase 1 — service capabilities + Exa, no UI
Four service-side deliverables that make the whole flow provable from a script before any remote exists: org detail + org affiliations reads, a registry-resolved search.fire, and Exa as a peer connector.
plans/Augment-From-DB-Phase-1-Service-Capabilities.md -
Augment from DB · Phase 2 — the org-workbench remote: flow registration, org search, org card
Autocomplete to a canonical org and work its card with a live ➕ on every list — plus the verb the spec missed, `organization.streams.add`.
plans/Augment-From-DB-Phase-2-Org-Workbench-Remote.md -
Augment from DB · Phase 3 — the search-and-add remote: editable term, provider palette, one-click add
Launched from any 🔍 on the org card: an always-editable term bar, a provider palette, one-click add back to the launching list.
plans/Augment-From-DB-Phase-3-Search-And-Add-Remote.md -
Augment from DB · Phase 4 — people reveal, person cards, add-person with automatic affiliation
The org card grows its people: every affiliated person revealed with role + relevance, nested identity links with their own ➕ and 🔍, and an inline add-person where the affiliation edge materializes without the operator ever managing it.
plans/Augment-From-DB-Phase-4-People-Reveal-And-Add-Person.md -
Augment from DB · Phase 5 — stream-scan mode: scan a pulse stream, badge the already-known, one-click the new into the corpus
Stream scan is a mode of search-and-add, not a third remote: the stream URL is the authoritative index, deduped against `content_items`.
plans/Augment-From-DB-Phase-5-Stream-Scan-Mode.md -
Augment from DB — the org-first workbench flow, and the two new microfrontends it needs
A flow that starts from SurrealDB, not a CSV: pick an org, reveal its people and pulse streams, augment through pluggable search packs.
explorations/Augment-From-DB-Flow-Two-New-Microfrontends.md -
augment-it has outgrown one flow — ROTATION is the CSV-augmentation pipeline's shape wearing a general-purpose name, and corpora-curator's promotion to its head is a splice, not a fit
ROTATION (`shell/src/remotes.ts`) is the CSV-augmentation flow hardcoded as THE nav — every other use case gets spliced onto it.
explorations/Augment-It-Has-Outgrown-One-Flow-The-Choose-A-Flow-Front-Door.md -
Search Providers as First-Class — Stand Up SearXNG as the New Default for Social Packs; Tavily Stays as a Peer; Per-Row Iteration as the Workflow We're Building Toward
Tavily is a content-RAG index — wrong substrate for social-profile pages. The fix isn't a swap — it's making provider plural per-fire.
issues/Search-Providers-as-First-Class-SearXNG-Default.md -
Connector Inventory & Per-Record Palette — Hot-Swap Providers, Re-Fire One Record at a Time
Per-record connector palette: click `f` to re-fire one row through the next Facebook provider, over a registry that resolves by capability.
specs/Connector-Inventory-and-Per-Record-Palette.md -
Strategy Curator — An Entry-Point App for augment-it
A canonical source registry in SurrealDB owns identity, the client's filesystem owns usage, and a shared UUID is the only bond.
specs/Corpora-Curator-Entry-Point-for-Augment-It.md -
Entity-Pulse Bundle — Press Releases, News Mentions, and the Social Voice of a Record
Official Updates fires first; its rollup becomes the relevance prior for Media and Socials Mentions — a foundation-first four-phase DAG.
specs/Entity-Pulse-Bundle.md -
Pulse pattern — one operator burst against one entity, expressed as N independent pulse-dimensions composed in a pulse-surface, each dimension potentially owning its own microservice
Operators enrich in bursts, not steps: one search fills name, socials, emails, and org, and a pulse-surface commits all of it in one save.
specs/Pulse-Pattern.md -
Record ↔ DB Resolver — operator-driven match/create bridge from row-store records to canonical organizations
Row-store records and canonical SurrealDB orgs were never bridged; the resolver closes the gap one record at a time, operator driving.
specs/Record-DB-Resolver.md -
Sparse-Person Enrichment Surface — per-email triage where the operator finds the human behind the address, picks or creates the org they belong to, and writes both back to the canonical layer
177 event attendees landed as 177 bare emails — the opposite shape from the URL-bearing records every other augment-it flow assumes.
specs/Sparse-Person-Enrichment-Surface.md -
Syncthing for Collaborator Access to the Corpus (R2 Backup Already Decided)
R2 already won the backup leg — rclone, not a live mount. This is the separate, still-open question: could Syncthing give other humans live access to the same corpus, without breaking the single-writer discipline that's kept things sane so far?
explorations/Syncthing-For-Collaborator-Access-To-The-Corpus.md -
Issue: How People, Organizations, and Their Relationships Actually Enter SurrealDB
Not a bug — a verified trace of the canonical write path, because the DB already does more than the UI or the operator's memory shows.
issues/How-People-Orgs-And-Relationships-Actually-Enter-SurrealDB.md -
Issue: Person · DB Resolver UI needs to accommodate multiple organizations per person
`person-db-resolver` resolves one org per row, but Lincoln Ellis's bio names four — no way to add an Nth without re-running the row.
issues/Person-DB-Resolver-Needs-Multiple-Organizations-Per-Person.md -
Plan stub: ingest the next reach-edu event CSV into the canonical layer
The mechanism already exists and is proven twice over (turning-jobs, FreedomFest) — this is the sequence to run the moment the next event CSV lands, so it's 'follow the stub' instead of 're-derive the pipeline.'
plans/Ingest-Next-Reach-Edu-Event-CSV-Into-Canonical-Layer.md -
Pickup notes — 2026-07-13: deploy hardening, doc audits, credential hygiene
Steps 1–10 are live at augment.didi.sh; this session cleared the production-only bugs that only using the deployed app surfaced.
plans/pickups/Pickup-2026-07-13.md -
Build order: the humain-vc unlock flow, step by step
The execution sequence for Flow 1 — each step names its repo, files, and verification, so a fresh session can pick up mid-sequence.
plans/Build-Order-Humain-VC-Unlock-Flow.md -
Augment from Affiliations — the first flow that starts from SurrealDB instead of a CSV, turning an event's speaker/org pairs into a rated, sourced prospect list
The first flow that starts in the canonical layer, not a CSV: export an event's affiliations, rate relevance offline, reimport.
specs/Augment-From-Affiliations.md -
Person-aware canonical resolver — closing the gap between the proven scripts and the shell-reachable capability
The resolver only knows organizations; every person and affiliation ever written came from CLI scripts no UI can reach.
plans/Person-Aware-Canonical-Resolver-Extension.md -
SurrealDB MCP + a verification skill — querying augment-it's canonical layer directly, starting with FreedomFest 2026
plans/SurrealDB-MCP-Plus-Skill-for-Canonical-Layer-Verification.md -
Migrate off the deprecated `nats` package to the `@nats-io/*` scoped v3 client — swap `nats@2` for `@nats-io/transport-node@3` across all 10 services, drop the removed `JSONCodec` in favor of `JSON.stringify` + `msg.json()`, and prove the inter-service bus still round-trips live before committing
`nats` → `@nats-io/transport-node` v3 across 27 files: mechanical, except the removed `JSONCodec` rewrites every encode and decode.
plans/Migrate-off-Deprecated-nats-Package-to-nats-io-Scoped-v3.md -
Grilling on the DB Resolver — questions to settle before v0.0.0.2 / v0.0.0.3
Three decisions before v0.0.0.2: where the join key lives, whether a slug can be renamed safely, and whether opportunities reopens Decile.
issues/Grilling-on-DB-Resolver--Future-Versions.md -
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.
blueprints/Connecting-To-And-Using-SurrealDB.md -
Workspaces as Tenant Primitive — toggling, tenant-aware microservices, per-tenant env-var pickup, and the seam that lets MCPs and connectors vary per client
`workspace` is the tenant boundary — humain-vc vs reach-edu. The vision is stated once, then step 1 is cut down to filesystem-only bones.
specs/Workspaces-as-Tenant-Primitive.md -
The Moat Is Grounded Deliverable Production, Not Chat
Chat-over-documents is commoditizing; the moat is the last mile — a shippable deck or memo with every claim traceable to source.
explorations/The-Moat-Is-Grounded-Deliverable-Production-Not-Chat.md -
First-Pass Corpus Quality Scan for reach-edu — a measured before/after baseline of the RAG corpus
A read-only baseline of 517 markdown files across 57 funder dirs, taken before RAG is wired, so 'after' has a 'before' to compare to.
plans/First-Pass-Corpus-Quality-Scan-for-reach-edu.md -
Funder-Fit Engine — Org-Anchored Corpora and the Bidirectional Story↔Funder Cycle
Fundraising matches both ways — funder→story and story→funder — on one org-anchored corpus. The differentiator is KAG, not plain RAG.
explorations/Funder-Fit-Engine-Org-Corpora-and-the-Story-Unlock-Cycle.md -
Forced One-By-One Tag Selector — a pulse-dimension pattern for deliberate triage instead of lazy bulk-tick
Bulk checkboxes produce uniform half-considered tags. Present one tag at a time — apply / skip / skip-rest — and each decision gets made.
explorations/Forced-One-By-One-Tag-Selector.md -
Joined People UI and the Network-First Pivot — augment-it's sibling-flow to org-first augmentation, and the canonical/proprietary layer split underneath it
Org-first and people-first are two pivots on one join — and the split that matters is canonical (shareable) vs proprietary (client-only).
explorations/Joined-People-UI-and-the-Network-First-Pivot.md -
Personal-link observations need named query lenses — without them, an accumulating fact log goes uninspected
`has_personal_link` observations carry rich qualifiers and no queries. One thought leader can contribute 50+ before anyone can look.
issues/Personal-Link-Observations-Need-Query-Lenses.md -
Canonical Entity Registry on SurrealDB Cloud — just write records
SurrealDB Cloud is up at main/main with three SCHEMALESS tables (persons, organizations, affiliations). Goal: write records from tonight's CSV+JSONL into those tables. SCHEMALESS stays. No field discipline up front.
plans/Canonical-Entity-Registry-on-SurrealDB-Cloud.md -
Client tagging on canonical writes — every observation carries the client that produced it, and every canonical entity carries the materialized set of clients that can see it
The canonical layer is cross-client by design — a materialized `client_access` array is how each workspace still sees only its own.
specs/Client-Tagging-on-Canonical-Writes.md -
Best Way to RAG Over the Corpus — design space for retrieval-augmented operations on augment-it's per-client corpus, given the structured frontmatter we just earned
245 corpus files carry `funder_slug` and `published_at`, so retrieval is facet-filter-first — embeddings handle the residual about-ness.
explorations/Best-Way-to-RAG-Over-the-Corpus.md -
Inbox Sort by Agent Tasks — moving the inbox from a flat 86-item pending queue into a task-typed work surface where the operator sees what's next and the agent does the safe parts automatically
86 pending inbox files render identically, so the operator context-switches between four task types on every scroll.
explorations/Inbox-Sort-by-Agent-Tasks.md -
Some records show empty corpus in the Sort & Filter Lens despite per-funder directories existing on disk — the lineage join is healthy but the workspace-service capability has no timeout override (defaults to 5000ms), the content-ingest handler processes requests serially, and each call walks every funder directory under clients/<id>/corpus/, so late requests in the 96-row fan-out time out and the lens swallows the error silently; the durable fix is to make corpus_funder_slug (a column the records sheet already populates) the primary join key, which limits each call to one small directory and dissolves the timeout race — this supersedes the originally-proposed corpus-overrides.yaml because the override surface is now the records-sheet cell
No `CAPABILITY_TIMEOUTS_MS` entry for `corpus.list_for_record` — 96 parallel calls hit the 5000ms default and the lens swallows the error.
issues/Some-Records-Show-Empty-Corpus-Despite-Directories-on-Disk.md -
Operator-built flows beyond the universal pipeline — the default augmentation path is a dud for most edge cases, and the cheaper-than-microfrontend escape is a view-spec the agent-chat composes from natural language and the UI renders generically
The default flow lands cleanly on 17 of 96 reach-edu records. The escape isn't a microfrontend per scenario — it's a generic spec-renderer.
explorations/Operator-Built-Flows-Beyond-The-Universal-Pipeline.md -
Augmentation-state preservation and snapshot promotion — the operator's CSV is the system of record, the filesystem is the truth, and `/promote-snapshot` is the verb that walks the corpus and emits the next CSV with system columns appended so flow-switches don't erase the prior cycle's work
One verb: `/promote-snapshot` joins the corpus filesystem into a fresh CSV version with system columns. No register, no write-hooks.
plans/Augmentation-State-Preservation-and-Snapshot-Promotion.md -
Records Surface sort step and UI — sort ships as part of the **Sort & Filter Lens**, the second lens in step 2's default set (alongside the existing **Pack Firing Lens**); `lens` is the architectural primitive this spec introduces and lenses are *swappable* (one active per step at a time), not stackable; each step ships with a small curated default lens set and the registry stays *open* so new lenses can join without architecture changes
Sort ships as the second swappable lens on step 2 — and the lens registry is open, so a new lens is a manifest drop, not an enum edit.
specs/Records-Surface-Sort-Step-and-UI.md -
In-App Browser vs Browser Plugin for Corpus Add — bridging the operator's own search into the per-record corpus without leaving the cockpit
Adding one operator-found URL to a funder's corpus is a ten-step round-trip out to Google and back. In-app browser, or browser plugin?
explorations/In-App-Browser-Or-Plugin-For-Corpus-Add.md -
Download PDFs into Corpus Inbox — preserve the original binary alongside Jina-extracted markdown; wire both inbox vectors (UI and agent-chat) so the operator's PDF discoveries land as commit-able evidence, not just summarized text
Jina gives the inbox text and throws the PDF away — nothing to cite by page or hand to a co-researcher. Save the binary alongside it.
plans/Download-PDFs-into-Corpus-Inbox.md -
Chat Context-Awareness Architecture — three layers (workspace as context broker, slab-assembly contract, verb registry) that grow the in-app chat from prompt-only to surface-aware verb router
Chat's verb roster is a hand-written prose block and its context slab carries only `record_set_id`; this closes both holes.
specs/Chat-Context-Awareness-Architecture.md -
Corpus Inbox — capture first, triage later; a zero-friction save destination for URLs without a home yet, with a future triage layer that sorts inbox content into the right places
A URL with no home yet shouldn't cost a filing decision: `corpus/inbox/` captures the page, its body, and a drive-by note, then waits.
specs/Corpus-Inbox-Capture-and-Triage.md -
Funder Content Corpus Workflow — what the system has to do, ranked by quality bar, with no implementation prescribed
Written so a future agent resists the pull to filter yesterday's bad data tighter instead of firing fresh for today's good data.
specs/Funder-Content-Corpus-Workflow.md -
Per-Client Privacy and the Path Off Local — when does single-operator-local-only stop scaling, what stack do we reach for, and how do we architect today so the move is cheap when it comes
Per-client corpus privacy and a client wanting login hit the same week. Not a stack decision — which choices keep the move off local cheap.
explorations/Per-Client-Privacy-and-the-Path-Off-Local.md -
Funder Corpus First Session Failed — 75 markdown files across 15 of 96 funders, 81 records unprocessable, hours spent layering filters on stale data instead of producing clean fresh data, rebuild against the goals spec exists in code but was never validated against a real pack fire because the session ended
Six hours produced 75 corpus files across 15 of 96 funders — 81 records still have nothing. This is the failure-mode list for morning-self.
issues/Funder-Corpus-First-Session-Failed-Most-Records-Unprocessable.md -
OfficialPulse URLs Appear as Junk in Promoted Versions — operator believes promote v6 → v7 → v8 wrote bad data into the array column; audit shows promote is clean and v6 itself already contained every URL
Promote added nothing — v5 through v8 carry identical 122-URL arrays. The new renderer just made them visible, and no UI can remove one.
issues/OfficialPulse-URLs-Appear-as-Junk-in-Promoted-Versions.md -
URL Auto-Detector and Clickable Rendering for List Fields — make socials, helpful_links, and official_updates_index_urls open-in-tab links instead of opaque JSON
`socials` and its list-shaped siblings render as 12px JSON; a shape-detecting extractor makes every URL clickable and drops the clutter.
plans/URL-Auto-Detector-and-Clickable-Rendering-for-List-Fields.md -
Record-Set Family Grouping — internal lineage vs. external-variant families in the Record Collector sidebar
The sidebar shows a tracker uploaded as v4–v8 as five unrelated CSVs. Two family kinds — promotion lineage and external variant — fix that.
specs/Record-Set-Family-Grouping.md -
Response Reviewer Shell and Content-Reader Mode — Response Reviewer becomes a wrapper whose inner review UI swaps based on what the bundle that fired actually produced
1,109 OfficialPulse responses, 3 accepts: 'is this URL right?' is the wrong question for content packs, so review mode becomes swappable.
specs/Response-Reviewer-Shell-and-Content-Reader-Mode.md -
In-App Chat v0.0.1 for Augment-It — The Prompt-Drafting Triad as the Demo Affordance
Gated enhancement made conversational: `prompts.draft` → `improve` → `apply`, with postconditions that check what the prompt promised.
plans/In-App-Chat-v0-0-1-for-Augment-It.md -
Augment Transformations Not Reliably Persisting — Hand-Curated Field Edits and Whole-Row Augmentations Are Disappearing Across Record-Set Versions
98 hand-curated URLs across 45 records with no save or promote affordance — only the row-store's auto-persisted JSON keeps them alive.
issues/Augment-Transformations-Not-Reliably-Persisting.md -
Troubleshooting UI for Official Blogs — The Bundle Fire Path Doesn't Fit the Flow That Was Built for Prompt Templates
Bundles fire end-to-end, but the Flow assumes every fire routes through a prompt template — so every step past 2 is wrong for a bundle.
issues/Troubleshooting-UI-for-Official-Blogs.md -
Record Count Stays Stable Across Versions — Augmenting Adds Columns, Never Rows
One dataset, one row count, forever — augmenting adds columns, not rows. 231 rows in the store for a 96-record dataset is a symptom.
reminders/Record-Count-Stays-Stable-Across-Versions.md -
Flow for Bundles & Packs — The Simplest Possible Thing
For 67 rows with a website URL, find each one's blog index. Two surfaces, no reviewers — this spec deliberately ignores the five before it.
specs/Flow-for-Bundles-Packs.md -
Per-Record Iteration as the Primary Surface for Pack and Bundle Fires — The Flow Rearranges Per Fire Type
A pack fired across 96 rows returned 0 found — so per-record iteration becomes primary and bulk fan-out waits until a chain is proven.
specs/Per-Record-Iteration-as-Primary-Surface-for-Pack-Fires.md -
Pulse Curation Layer & UI — Three Layers per Category, Triage Per Item, Finalize on Demand
Three layers per category: immutable `raw_output`, live `curated_output`, and a `finalized_output` snapshot locked when triage is done.
specs/Pulse-Curation-Layer-and-UI.md -
Shell & Micro-Frontend UX Coherence — Refactor Plan
Eight locked UX decisions sequenced into five phases — the Deck→Flow rename first, so every later phase speaks the right vocabulary.
plans/Shell-and-Micro-Frontend-UX-Coherence-Refactor.md -
Shell & Micro-Frontend UX Coherence — Affordances That Are Found, Consistent, and Talk Back
A demo-prep chain of 'I can't find / reach / trigger X' is a verdict: the shell's affordances hide, die, or mismatch. Fix the pattern.
specs/Shell-and-Micro-Frontend-UX-Coherence.md -
Tooltip System — A Versatile First-Class Family, Plus a Walkthrough for New and Returning Users
Apps fail at orientation, not functionality — so tooltips become a first-class family, not the browser's half-working `title=`.
specs/Tooltip-System.md -
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.
blueprints/Response-Row-Identity-Across-Promote.md -
Agent-Chat Skills and Commands — Candidates List
The chat's verb roster is four prompt-focused capabilities. A running list of shell scripts that should graduate into chat-callable verbs.
explorations/Agent-Chat-Skills-and-Commands-Candidates.md -
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.
blueprints/Packs-and-Bundles-Pattern.md -
Augment-It Prior Art Survey — What's Already Been Built, and What It Tells Us
Two prior attempts exist — Tanuj's three federated repos and Michael's bolt monolith. Both cover the core; neither is what we ship.
explorations/Augment-It-Prior-Art-Survey.md -
Bolt-Era API Provider Widget Analysis
The bolt widget picked Claude, GPT, or Perplexity per prompt section. The widget dies in the rewrite; the multi-provider shape stays.
explorations/Bolt-API-Provider-Widget-Analysis.md -
Bolt-Era Codebase Analysis
A faithful architectural map of the bolt monolith — React + TS + Vite + Supabase + zustand — lifted from its own `specs/` folder.
explorations/Bolt-Codebase-Analysis.md -
Bolt-Era Highlight Collector Analysis
The only existing description of the highlight-collector stage — one of two that never got split into Tanuj's microfrontend repos.
explorations/Bolt-Highlight-Collector-Analysis.md -
Bolt-Era Main Container UI Analysis
The bolt shell's five-column layout and auth gate — prior art for the rewrite's open question: one host shell, or a host per app?
explorations/Bolt-Main-Container-UI-Analysis.md -
Bolt Monolith As Built — The archive/bolt-code Branch
The earliest augment-it is a Vite + React monolith on `archive/bolt-code`: feature-richer than the federated repos, architecture we discard.
explorations/Bolt-Monolith-As-Built.md -
Bolt-Era Prompt Section Analysis
Prompt templates as MDX-rich, variable-aware, edit-toggle-preview blocks — the pattern prompt-template-manager should probably adopt.
explorations/Bolt-Prompt-Section-Analysis.md -
Bolt-Era Record Collector Analysis
Cross-reference against `Tanuj-Record-Collector-As-Built` — the diff between bolt-era and forked shows which patterns survived federation.
explorations/Bolt-Record-Collector-Analysis.md -
Entity-Profile Augmentation Workflow — Common Social + Vertical-Specific Sources, Per Entity Type
Two tiers replace prompt-by-prompt column filling: packs as atomic source-bound units, bundles as workflow-shaped compositions of packs.
explorations/Entity-Profile-Augmentation-Workflow.md -
Federation and Bundler Decision — Bun + Rsbuild + Module Federation, Workspace State, Optional Chat
We federate: Module Federation on rsbuild, bun over turbo, and state of truth in `@augment-it/workspace` — chat is just one consumer.
explorations/Federation-and-Bundler-Decision.md -
Tanuj's Prompt-Manager As Built
Full CRUD-shaped prompt UI over a hardcoded `samplePrompts` array — no store, no data flow. Keep the schema, throw away the implementation.
explorations/Tanuj-Prompt-Manager-As-Built.md -
Tanuj's Record-Collector As Built
The most-finished of Tanuj's three splits. One idea survives: the prompt template auto-generates from the imported CSV's columns.
explorations/Tanuj-Record-Collector-As-Built.md -
Tanuj's Request-Reviewer As Built — The Module Federation Proof
The only place Tanuj got federation working — a shared `RecordCard` — while the augmentation logic sits copy-pasted from record-collector.
explorations/Tanuj-Request-Reviewer-As-Built.md -
Augment-It Workspace — Walking Skeleton Plan
Browser ↔ Workspace Service over WebSocket, Workspace Service ↔ row-store over NATS, and two real spreadsheets as the proof-of-life payload.
plans/Augment-It-Workspace-Walking-Skeleton.md -
Impose the Three-Mode Theme System on augment-it
The two-tier tokens and light/dark/vibrant contract adapted to a federated, Tailwind-less app: one shared `packages/theme`, no raw hex.
plans/Impose-Theme-Modes-System.md -
Prompt-Template-Manager — Walking Skeleton Plan
Author `{{column}}` templates and run them per row — `prompt-runner` is the only container that calls the Anthropic API.
plans/Prompt-Template-Manager-Walking-Skeleton.md -
Run-as-First-Class-Operation — Pair Pack-Runner with Prompt-Template-Manager, Make Runs Legible Across the Pipeline
Lift `Run` from a string id buried on each response into a real entity, so any surface can see which batch produced what it's showing.
plans/Run-as-First-Class-Operation.md -
Common-Six Social Packs — First Real Packs on the Structured-Output Surface
Six pack identities — linkedin, x, bluesky, youtube, facebook, wikipedia — on one backend routing by `pack_id`, no microfrontend per pack.
prompts/Common-Six-Social-Packs.md -
Helpful Links on Records — Captured During Response-Reviewer Triage
The adjacent links a human finds while triaging die in the clipboard; `helpful_links` catches them in one click and survives derivations.
prompts/Helpful-Links-on-Records-Captured-During-Triage.md -
Response Reviewer — Structured-Output Extension (Packs-and-Bundles Foundation)
Build the surface every pack lands on — candidate cards, confidence pills, outcome enum — against mock fixtures. Zero packs ship here.
prompts/Response-Reviewer-Structured-Output-Extension.md -
Run /speckit-specify — Response Reviewer Structured-Output Extension (Packs-and-Bundles Feature 1)
Feature 1 of the packs-and-bundles series: the structured-output surface every pack will land on. Zero packs, zero bundles implemented.
prompts/Run-Speckit-Specify-Response-Reviewer-Structured-Output.md -
context-v for augment-it
Living documentation for augment-it — specs, habits, prompts, reminders, explorations, issues.
README.md -
Enhanced Records List — the Triage Checkpoint and the Promotion Loop
One record-grained view of a whole enrichment round: select the good rows, promote them to canonical, and the predecessors archive.
specs/Enhanced-Records-List-and-Promotion-Checkpoint.md -
Request Reviewer — the Pre-Flight Surface
See exactly what is about to leave the building — and guarantee the request you reviewed is byte-identical to the one that fires.
specs/Request-Reviewer-Pre-Flight-Surface.md -
Response Reviewer and Response Store — the Post-Flight Surface
No review surface until a fired response is a first-class stored object — so response-store and response-reviewer are specced as one.
specs/Response-Reviewer-and-Response-Store.md -
Walking-Skeleton Pre-Flight Decisions — Augment-It Rewrite
Five substrate decisions — state, transport, persistence, auth, agent scaffolding — settled before code so no session re-walks the tree.
specs/Walking-Skeleton-Pre-Flight-Decisions.md -
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.
blueprints/Original-and-Enhanced-Record-Instances.md -
Build the Shell Tiling & Peek-Deck — Window the Federated Frontends
The shell stops being a tab switcher: a peek-deck at 90% width with neighbours peeking, plus a two-remote split with a draggable seam.
prompts/Build-the-Shell-Tiling-and-Peek-Deck.md -
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.
blueprints/Module-Federation-Rsbuild-Dev-Loop-Gotchas.md -
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.
blueprints/Spec-Kit-and-Context-V-Coexistence.md -
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.
blueprints/Why-Response-Reviewer-and-Highlight-Collector-Exist.md -
Multi-Agent Research Fan-Out Per Row — The Real Shape of Augment-It's Capability Runtime
Capabilities aren't LLM calls — five research agents run per row in parallel, so the runtime needs (rows × agents) fan-out.
explorations/Multi-Agent-Research-Fan-Out-Per-Row.md -
Run /speckit-constitution — Seed Augment-It's Constitution from Context-V
The directive to paste with /speckit-constitution so the principles synthesize from our own context-v docs, not from training data.
prompts/Run-Speckit-Constitution.md -
Run /speckit-specify — Workspace + Sidecar Foundation (Feature 001)
The workspace package and bun sidecar, plus exactly one capability — `records.import` — end to end to prove the pipe. No federation yet.
prompts/Run-Speckit-Specify-Workspace-and-Sidecar-Foundation.md -
Augment-It as a CRM-Augmentation Pipeline (Microfrontends + Microservices)
memopop makes memos, dididecks makes slides, augment-it makes information that lands back in a CRM it doesn't own.
specs/Augment-It-as-CRM-Augmentation-Pipeline.md -
Changelog entries duplicated across augment-it/changelog/ and content/changelog--laerdal/
Eleven backfilled augment-it changelog entries currently live in two places. Either location can be the source of truth — but right now both are, and updates have to be made twice.
issues/Changelog-Duplicated-Across-Splash-And-Laerdal-Collection.md -
augment-it/agent-skills/decile-hub-interface/skill
The operator-facing workflow layer for getting real-world data INTO and OUT OF a client's Decile Hub CRM — sitting on top of the decile-hub-connector API contract. Use whenever importing a batch of real records into Decile (voice-note transcripts, CSV lead lists, LP rosters, event attendees), matching hand-collected records to existing Decile prospects by name, appending notes to people/prospects, or reasoning about the People-vs-Organizations-vs-Pipelines-vs-Prospects data model for a fundraising pipeline. Triggers when the user says "import these into Decile", "add these to the pipeline", "match these to Decile", "put these voice notes / this list into Decile", "attach a note to the prospect", "which pipeline do these belong to", or names the importer script decile-import-voicenotes.mjs. Encodes the read-only introspection recipe (whoami → pipelines?kind=investor → stages → prospect shape), the name-matching import pattern (Apple Voice Memos and most hand-collected records carry NO email, so the filename/typed-name is the identity key and Decile supplies the rest), where notes actually land (the Person/prospectable, NOT the pipeline row — so they surface across every pipeline that Person is in, tied to one pipeline only by the note's context label), the idempotent + additive + dry-run-first import discipline, the aliases.json spelling-bridge, and the .env gotchas that silently break the connector. The authoritative API contract is [[decile-hub-connector]] + the on-disk swagger; this skill is how a human operator drives it.
agent-skills/decile-hub-interface/SKILL.md -
augment-it/agent-skills/inbox-curation/skill
didi's triage discipline for filing captured links and sources into the right corpus (thesis/strategy/topic) inside augment-it. Use whenever the user gives didi a URL to save, asks to "file this under <corpus name>", names an existing thesis/strategy by name for a link to go under, or it's unclear which corpus a captured link belongs to. Encodes the decision tree (named + existing corpus → source.add directly; new corpus → propose domain.create first; unclear → propose or park in the inbox), the domain-resolution discipline (resolve names against the live "Existing corpora" list, never fabricate a domain_type/domain_slug), and the boundary with corpus.inbox.add (the untriaged capture-first fallback). The capability catalog and args shapes live in services/workspace/src/chat.ts's CURATOR_CHAT_VERBS slab — this skill is the reasoning on top of it.
agent-skills/inbox-curation/SKILL.md -
augment-it/agent-skills/triage-inbox-w-suggestions/skill
The operator+agent discipline for draining a client's corpus inbox (clients/<client>/corpus/inbox/) — agent scans each pending file, stamps a triage_suggestion, and proposes destinations in confidence-banded batches; the operator sweeps. Proven on the first co-pilot run (2026-07-25: reach-edu 141→4 in six batches); carries the run playbook, six-bucket org taxonomy, pointer/stream/gated routing, and reusable scripts/ helpers. Use whenever the user says "triage the inbox", "work through the inbox", "drain the inbox", "/triage-inbox", or asks to file/sort pending inbox captures. Encodes the destination model (funder org folder, person, or domain — with SurrealDB as the single canonical index and cheap reference .md copies fanned into any additionally-relevant folder), the six task lanes (TRIAGE/EXTRACT/ENRICH/DEDUPE/FLAG/DISCARD), the tagging convention (YAML array, Train-Case with lowercase connector words), and the batch/resume rhythm. Co-pilot phase: agent proposes, operator disposes; nothing files without an operator sweep.
agent-skills/triage-inbox-w-suggestions/SKILL.md
cite-wide 11 docs
-
Paste LLM Content drops prose structure and emits link-only citations
Paste rewrites citation tokens and nothing else — headings flatten, refs become self-referential links, and one URL gets two hex codes.
issues/Paste-LLM-Content-Drops-Structure-And-Emits-Link-Only-Citations.md -
Users need to define their own citation format — the Lossless house style is hardcoded
Cite Wide hardcodes one house style across four services. Templating is the feature; centralizing the format is the prerequisite.
issues/User-Definable-Citation-Format-Templates.md -
This Is an Obsidian Plugin — Read the Obsidian API Docs
The Obsidian API is the source of truth: `any`, innerHTML, and var are all outright bans, and Electron breaks browser muscle memory.
reminders/This-is-an-Obsidian-plugin-Read-Obsidian-API-Docs.md -
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.
blueprints/Maximize-Data-Collection-on-Cannonical-Sources.md -
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.
blueprints/Parse-Common-Citation-Formats.md -
Modal for Pasting LLM Native Content
Stop the parsing problem at the source: a paste-target textarea plus a Google/Perplexity selector, feeding the parser at the cursor.
specs/Modal-for-Pasting-LLM-Native-Content.md -
cite-wide/workflow/2026-05-01
A day's worklist: URL-validity checking with zero hallucinated replacements, dedupe-by-URL, and refdefs that stop repeating the publisher.
workflow/2026-05-01.md -
The Lossless Citation Open Specification
Hex codes instead of numerics so pasted sources never collide — plus exact spacing and the Claude cited_text blockquote the web strips.
reminders/Lossless-Citation-Spec.md -
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.
blueprints/Citation-Acquisition-Pipeline.md -
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.
blueprints/Citation-Field-Acquisition-Guide.md -
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.
blueprints/Lossless-Citation-Standards.md
content-farm 29 docs
-
Metafetch wraps tags array items in quotes
Metafetch re-serializes the whole frontmatter, so its quote-everything rule turns an inline `tags: [a, b]` into one quoted string.
issues/Metafetch-Wraps-Tags-Array-Items-In-Quotes.md -
Metafetch source notes — fetch from any journal URL, not just `url`
A note about a paper keys its link as `arxiv:`, not `url:` — and metafetch couldn't see it. A URL picker across every frontmatter property, a scholarly metadata tier, and vault-wide identity codes now make a source note worth having.
specs/Metafetch-Source-Notes-From-Any-Journal-URL.md -
Symlinked vault folders are invisible to the Obsidian index
Half our vault's top-level folders are symlinks into the monorepo. `vault.getAbstractFileByPath()` doesn't reliably see them, so every plugin that checks 'does this folder exist' before creating it is one symlink away from an EEXIST crash.
issues/Symlinked-Vault-Folders-Are-Invisible-To-The-Obsidian-Index.md -
Stenographer: an Obsidian Plugin that Transcribes Audio Content
Drop a YouTube, SoundCloud, or other listenable link into Obsidian and Stenographer turns it into a fully-frontmattered note with a streaming, AI-generated transcript — sources become searchable knowledge in one move.
specs/Stenographer-an-Obsidian-Plugin-that-transcribes-Audio-Content.md -
What to do with grab-reference — a citation-manager web stack living in the Obsidian plugin family
grab-reference turns out not to be an Obsidian plugin: it's a private 'citation-manager' pnpm workspace (web app + Prisma API + Docker) on a 2024-era toolchain. Decide its fate before spending any upgrade effort on it.
issues/What-To-Do-With-Grab-Reference.md -
Dependency-upgrade loop for the Obsidian plugin family — patch/minor sweep, then researched majors, every build proven
One loop that walks every Lossless-owned plugin in content-farm from stale to current: safe bumps first, majors only after reading the upstream release notes, and nothing lands without a green typecheck + esbuild bundle.
loops/Dependency-Upgrade-Loop-For-Obsidian-Plugin-Family.md -
Dependency upgrades across the Obsidian plugin family — full bump inventory, safe → major → forks
Every outdated dependency in the ten Lossless-original modules plus the umbrella, grouped patch → minor → major, with upstream release-notes research attached to every major before it moves.
plans/Dependency-Upgrades-Across-Plugin-Family.md -
Self-Hosting the Vault via Ignis — Team-Wide Browser Access to Content Farm
content-farm's whole plugin set assumes desktop Obsidian. Ignis runs Obsidian in a browser against a server-side vault — worth knowing about, not yet worth committing to.
explorations/Self-Hosting-the-Vault-via-Ignis.md -
Create a Study of the Best Obsidian Plugins
Pin the 10–15 most interesting Obsidian plugins as a real study, so we read their code instead of paraphrasing from training data.
plans/Create-a-Study-of-the-Best-Obsidian-Plugins.md -
Obsidian Review Bot Feedback on Perplexed Submission
165 bot findings, all in main.ts — plus the Appendix: the PR queue died mid-fix, and the plugin description lives in three places.
issues/Obsidian-Review-Bot-Feedback-on-Perplexed-Submission.md -
Obsidian Marketplace Compliance — Rules the Review Bot Enforces
The portal pins scans to a (tag, commit) pair, so a re-scan needs a new release tag — plus the description that lives in three places.
reminders/Obsidian-Marketplace-Compliance.md -
Moving Beyond Simple API Calls — LLM Orchestration Options for Our Plugins
Locks the `cf` codefence grammar and holds the line on direct vendor SDKs — Vercel AI SDK if we outgrow them, never LangChain.
explorations/Moving-Beyond-Simple-API-Calls.md -
Nudging AI search to return contextually appropriate images
The streaming pipeline silently drops Perplexity's images array — port the [IMAGE N] marker pattern the article generator already uses.
issues/Nudgeing-AI-Search-to-Return-Contextually-Appriate-Images.md -
Auto-Hyperlink Feature Names in Generated Tables
Crawls the entity's domain to turn feature-table cells into links to the real feature pages — deferred until the headless crawler exists.
plans/Auto-Hyperlink-Feature-Names-In-Tables.md -
Cite-Wide — dedupe inline repetition of identical hex citations
One backreferenced regex collapses runs like [^jtas3k] [^jtas3k] — a different problem from dedupe-by-URL, which must stay untouched.
plans/Cite-Wide-Dedupe-Inline-Repetition.md -
Image Drop Confirmation Gate
An Obsidian plugin that asks where a dropped image goes before anything hits disk or network — a private chart on imgur is a phone call.
plans/Image-Drop-Confirmation-Gate.md -
Per-Directory Profile Templates — v0.1 Spike
One Perplexity call per file, four template zones, and `***` as the scratch terminator — aborts rather than merge if the body has prose.
specs/Per-Directory-Profile-Templates.md -
Textgenerator Plugin — Analysis
Text Generator runs a local Koa proxy and a runtime package loader — borrow its async Handlebars helpers, not its remote-code surface.
studies/Textgenerator-Analysis.md -
Enabling Obsidian Plugins to Access Homegrown API Helpers
Architecture patterns for bridging Obsidian's JavaScript environment to powerful, non-JS backend logic (Python, Rust, CLI tools) via lightweight cloud proxies.
explorations/Enabling-Obsidian-Plugins-to-access-Homegrown-API-Helpers.md -
Citation Resolution and the Canonical Source
Link-rot recovery, lookup-before-create on save, and content preservation for RAG are three operations on one underlying entity.
explorations/Citation-Resolution-and-Canonical-Sources.md -
Using APIs to Ingest More Data
Beyond OpenGraph.io — what Jina.ai already gives us (we pay for it), what other fetching services do, and a rough sketch of how a portfolio-company site crawler would actually work.
explorations/Using-APIs-to-Ingest-More-Data.md -
Add a New API Provider to a Metadata-Fetching Plugin
Reusable prompt for wiring a new third-party metadata API (e.g. Microlink, Jina Reader, OpenGraph.io) into an Obsidian plugin like Metafetch as an additional fetcher, without breaking the existing flows.
prompts/Add-New-API-Provider-to-Plugin.md -
Renaming a Repo and managing Downstream Effects
It's not as simple as renaming the github path.
chores/Rename-Repo-Downstream-Renaming.md -
Tidy Naming — Repo Mentions of 'Obsidian' and 'Plugin'
Obsidian's community-plugin guidelines forbid using 'Obsidian' or 'Plugin' in the brand name (repo, manifest, README, description). Several of our repos still do. A punch list of what to rename, where, and why we held off until now.
chores/Tidy-Naming-Repo-Mentions-of-Obsidian-and-Plugin.md -
Migrating When an API Provider Rebrands
A vendor rebrands mid-integration — different name, different domain, sometimes different auth surface. What do you fix today, what do you leave alone, and what's the safe order? A short runbook from the day Freepik turned into Magnific.
Migrating-when-an-API-Provider-Rebrands.md -
A Component Inserter
An Obsidian command that scaffolds the right block — HTML, codefence, callout, embed — at the cursor, with frontmatter-driven defaults.
plans/A-Component-Inserter.md -
Github Splash Page for Content Farm
An in-repo Astro site that turns the content-farm pseudomonorepo into a public landing page — hero, plugin gallery, changelog and context-v rendering — deployed for free off GitHub Pages while we wait for a real marketing surface.
specs/Github-Splash-Page-for-Content-Farm.md -
Widening (and Re-Sizing) Obsidian Plugin Modals via CSS
Modal width lives on this.modalEl, not this.contentEl — the plugin-template convention that everyone copies is why modals stay narrow.
issues/Widen-Modals-in-Obsidian-using-CSS.md -
Obsidian Plugin Type Safety — Rules, Patterns, and Cite-Wide Conventions
Cite-wide was rejected for `any` with no appeal — even eslint-disable counts. Plus the coercion boundary treating frontmatter as untrusted.
reminders/Obsidian-Type-Safety.md
context-vigilance-kit 11 docs
-
Graphiti Over the Lossless Corpus
Chroma cannot answer "what changed, and when." Graphiti's bi-temporal graph can — pointed at the changelog rollup until the bet proves out.
explorations/Graphiti-Over-The-Lossless-Corpus.md -
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.
blueprints/Sweep-for-Frontmatter-Consistency-&-Improvements.md -
Frontmatter Normalization — Remaining Repos
Done. All 436 changelog entries in the tree carry the editorial date pair, the legacy `date:` key is gone, and every build-breaking trap is closed — including one nobody had a name for until a lenient schema let a live ordering bug through.
handoffs/Frontmatter-Normalization-Remaining-Repos.md -
Frontmatter Normalization — The Context-V Tier
821 living documents: the date must come from git, the lede must be written, and `publish: false` does not keep a doc out of the corpus.
handoffs/Frontmatter-Normalization-The-Context-V-Tier.md -
Chroma and Graphiti Gotchas
Neo4j has to be running. The model alias in graphiti-core's own default doesn't resolve. And `publish: false` means one thing to the changelog ingester and nothing at all to the context-v one. Short, sharp, learned the hard way.
reminders/Chroma-and-Graphiti-Gotchas.md -
MVP: context-v as a Claude Code Plugin
The kit's MVP is not the Chroma memory system the June specs planned — it's a plugin where `/plugin install` is the whole onboarding.
specs/MVP-to-Claude-Code-Plugin.md -
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.
blueprints/Browser-Drive-Verification-For-Agent-Sessions.md -
Commands and Agent Skills for context-v
Catalog of every command, slash command, and agent skill the kit ships — surfaced natively via `.claude/commands/` and `.claude/skills/`.
specs/Commands-and-Agent-Skills-for-Context-V.md -
Systematizing Chroma as the Loading Mechanism for context-v
Chroma holds 5,224 context-v chunks and we still load context by hand. Three loops turn the corpus into a session-start loading system.
specs/Systematizing-Chroma-as-Loading-Mechanism-for-Context-v.md -
Code-Comment Sections as Context-V Source
JSDoc made code comments the source of truth for API docs. Could section-level comment blocks be the source of truth for context-v entries?
explorations/Code-Comments-Sections-as-Context-V.md -
Tidy Context Vigilance Files Across All
A manifest-driven pass over 583 collated context-v files: worked-on (110) first, then idea-started (263), with concurrent duplicate hunting.
plans/Tidy-Context-Vigilance-Files-Across-All.md
conversational-ui-and-native-shells 8 docs
-
5ire
5ire's MCP layer has no apply button — editing a server row in PGlite makes the client reconnect via the live-query changefeed.
profiles/Profile__5ire.md -
anything-llm
A "workspace" is a config row over one always-shared backend: the chat provider varies per workspace, the vector DB never can.
profiles/Profile__Anything-LLM.md -
Conversational UI / Native Shells — Answers to the Plan's Targeted Questions
Phase 2, not a survey: two questions — Dive's Electron/Tauri migration and anything-llm's workspace switch — answered from the profiles.
inquiry/Targeted-Questions-for-Cross-Product-Shell.md -
dive
Two native shells, neither containing a line of agent logic — both are thin supervisors spawning the same Python subprocess.
profiles/Profile__Dive.md -
kaas
Every credential, provider quirk, and even context assembly lives in Rust; React gets typed `invoke()` calls and nothing else.
profiles/Profile__Kaas.md -
open-vibe
One real OS child process per workspace — but only ever one binary. What varies per workspace is the invocation, not the backend.
profiles/Profile__Open-Vibe.md -
openagent
Delegation recursion is prevented not by a depth counter but by never registering `spawn_agent` on the child's tool server.
profiles/Profile__Openagent.md -
routa
The swappable unit turns out to be the session, not the workspace: two sessions in one workspace can run two different agent CLIs.
profiles/Profile__Routa.md
corpora-builder 23 docs
-
Need an Elegant Resolution to Source Pointers vs. Master
One source, many folders, is the design. But for 75 sources the body sits in an untriaged inbox file the scoped read never reaches.
issues/Need-Elegant-Resolution-to-Source-Pointers-vs-Master.md -
didi.sh Auth and Multi-Org Corpora
Log in once, hold several organizations at once, and read one federated corpus across them. Three catches, and two specs that disagree.
plans/Didi-Auth-and-Multi-Org-Corpora.md -
Search Index, Then Pagefind
Search reads 845 files. Phase 1 writes a manifest so it reads one. Phase 2 puts Pagefind on top of that manifest, not in place of it.
plans/Search-Index-Then-Pagefind.md -
The Sidecar Port Is Adopted, Not Owned
Tauri probes 8787 and uses whatever answers. A stray dev sidecar becomes the app's backend, silently, and the app looks fine.
reminders/The-Sidecar-Port-Is-Adopted-Not-Owned.md -
Header Chrome
The workspace becomes a switcher, not a label. The mode toggle shows one icon and says what the next click gets you.
specs/Header-Chrome.md -
Ranked Search — Pagefind over the manifest
Substring matching cannot rank, stem, or take two words in any order. Pagefind can. It indexes the manifest, and never replaces it.
specs/Ranked-Search.md -
Search Index — the manifest that stops search reading the corpus
A search opens every file: 845 reads, up to 5.8 seconds. A manifest in the corpus makes it one, and closes the gap FOCUS-07 named.
specs/Search-Index.md -
Strategy Focus
A strategy chip narrows the list and compounds with search. The corpus count rides alongside, so a subset always says what it is a subset of.
specs/Strategy-Focus.md -
24 Orphaned bin/ Objects From a Half-Migration
A test that checked the object existed but never the pointer. Ghostscript's nondeterminism turned a sequencing mistake into 24 untraceable objects.
issues/Orphaned-Bin-Objects-From-A-Half-Migration.md -
Binary Ingest and the bin/ Store — one copy, optimized, fetched on demand
78 files are 90.5% of the corpus bytes. Compress once, store once by hash, fetch when asked, delete locally without fear.
specs/Binary-Ingest-And-Bin-Store.md -
Corpus Change Feed — what changed in a client's corpus, and why
A change record any history engine can emit, and a feed that renders it for someone who will never read a diff.
specs/Corpus-Change-Feed.md -
Corpus Tree
A corpus is a folder the client can't see. The tree is built from keys alone, so showing 944 files costs zero reads.
specs/Corpus-Tree.md -
Domain Navigation
112 folders in a dropdown is a list you scroll, not a list you use. Type any near-match; backspace walks back a segment at a time.
specs/Domain-Navigation.md -
Autonomy Gates — what an agent may do here unattended, and where it must stop
A written answer to "may I proceed?" — a green list that needs no permission, a red list that always does, and the four gates in between.
contracts/Autonomy-Gates.md -
Spec to Shipped with TDD — the two-role loop that runs unattended
A two-role loop — PM enumerates the tests, engineer implements to green — with status derived by running the suite, never asserted in prose.
loops/Spec-to-Shipped-With-TDD.md -
Browse Corpus — a screen for the work that already exists
The first surface: read-only over reach-edu's 892 existing files. Pulled out of Phase 7 because Tauri was never the cheapest first screen.
specs/Browse-Corpus.md -
Capture From The Screen — the surface stops being a viewer
Paste a URL and watch it get filed. Writing is opt-in at the server (`--writable`) because the first corpus this screen saw was a client's.
specs/Capture-From-The-Screen.md -
Capture, Link-First — the first command that pays for itself
`corpora add <url>` fetches, names, dedupes, and files a link as a source — metadata-only by default, because bulk enrichment goes haywire.
specs/Capture-Link-First.md -
Loop Harness — the ledger that lets an agent run unattended
Spec IDs bind to test functions, status is derived by running the suite, and a promise with no test is a build failure.
specs/Loop-Harness.md -
Source-File Model — the schema becomes code, and two silent failures become loud
The schema as a round-tripping dataclass — the stray `---` that hid 13 of ImmuneCo's 93 sources is now a hard error, not a silent one.
specs/Source-File-Model.md -
Storage Seam — one interface, three implementations, and the workspace that names the bucket
A CorpusStore over local, R2, and cache, proven by one conformance suite that runs against every backend with no test-side branching.
specs/Storage-Seam.md -
Corpora-Builder System Design
Corpus building has been rebuilt as a sub-feature three times across ai-labs. This exploration surveys what those iterations actually taught us, and sketches the system that deserves its own repo.
explorations/Corpora-Builder-System-Design.md -
Design Front-Loading and the Fable Build Loop
If frontier models can now carry complex builds end-to-end, the leverage moves to the documents. Can we front-load design so hard that the whole system gets built in a TDD loop — and impose design-system discipline from commit one?
explorations/Design-Front-Loading-and-the-Fable-Build-Loop.md
dark-matter 3 docs
-
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.
blueprints/Jumbotron-Popdown-Patterns.md -
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.
blueprints/Using-Heartbeat-Patterns-to-Save-Session-Data.md -
Master Dark Matter Site Specification
The whole front end in one document — theming, mode switching, layout hierarchy, and a porting checklist specific enough that another Astro Knots site can adopt the same system by working down the list.
specs/Master__Dark-Matter-Site-Specification.md
dididecks-ai 128 docs
-
/data-assets/slides — reviewer audit of the slide tier, one row per slot, adapted-vs-stub per variant
The third data-assets audit and the only one never promoted to the shell — adapted-vs-stub per variant, living only in calmstorm-decks.
sitemap/routes/data-assets-slides.md -
Never Use JSX Syntax
reminders/Never-Use-JSX-Syntax.md -
Shared Content Modules Across Deck Surfaces
One typed content module per deck variant drives Scroll-UI, Play-UI, and the PPTX exporter — so copy cannot drift between surfaces.
blueprints/Shared-Content-Modules-Across-Deck-Surfaces.md -
DeckFrame--Play-UI — Play-UI chrome wrapper around SlideCanvas, plus the keyboard contract
Play-UI's outer frame at `/play/[deck]/[variant]/[slot]/` — `<SlideCanvas>` plus the floating DeckChrome and document keyboard listener.
sitemap/components/DeckFrame--Play-UI.md -
DeckMatrix — the rich audit-rated dual-surface matrix; the deck-level review surface, embeddable on any landing
The embeddable variants × slots matrix: each cell pairs a Scroll-UI and Play-UI rating, with `≠` flagging where the two surfaces disagree.
sitemap/components/DeckMatrix.md -
DeckStatsPanel — the 4-tile quick-stats row above the matrix on landing pages (Variants · Slide Files · People · Companies)
Four-tile stats row above `DeckMatrix` — Variants, Slide Files, People, Companies — counted from the same globs `/data-assets/*` uses.
sitemap/components/DeckStatsPanel.md -
ModeToggle — three-mode color-toggle (light → dark → vibrant) with per-client localStorage namespace
Fixed top-right button cycling light → dark → vibrant, persisted under a per-client `{client}:mode` key so co-hosted decks don't collide.
sitemap/components/ModeToggle.md -
PageAsDeckWrapper — Scroll-UI navigation primitive: scroll-snap + keyboard + section counter + reveal-on-intersect
Wraps `<section data-slot data-variant>` children in a scroll-snap deck: keyboard contract, section counter, and `#s-N` hash nav.
sitemap/components/PageAsDeckWrapper.md -
PlayChrome — DEPRECATED thin shim around DeckChrome
Deprecated as of v0.2 — a thin shim around `<DeckChrome>` kept so external imports keep working. Removed in v0.3.
sitemap/components/PlayChrome.md -
ScrollDeckPage — THE single shell overlay for a scroll-deck variant page; one-import wiring
Collapses the three shell imports a variant page used to need — pagination, rating pill, mode toggle — into one component and mount site.
sitemap/components/ScrollDeckPage.md -
SlideShell — shared per-slide chrome (padding, min-height, snap-align, optional consumer-provided mark)
Outer `<section>` with shared per-slide layout plus a `<slot name="mark">` — consumers plug their own mark, the shell stays brand-agnostic.
sitemap/components/SlideShell.md -
lib/deck-overview — registry + filesystem walker; loadDeckOverview(deckSlug) returns DeckOverview with variants/slots/per-slide-file flags
`loadDeckOverview(deckSlug)` reads registry paths off `globalThis.__dididecksShellOptions`, so the shell never needs the consumer's imports.
sitemap/lib/deck-overview.md -
Sitemap — Living Map of the DidiDecks Universal-Frontend-over-Client-Decks Architecture
One mini-spec per `@dididecks/shell` artifact — the universal layer; per-client overrides live in each client-site's own `context-v/`.
sitemap/README.md -
/data-assets/companies — reviewer audit of portfolio-company metadata + brand assets across every engagement layout
Reviewer audit over `data/**/portfolio/*.md` — companies are told from people by the *absence* of `role_class`. SSR'd behind auth.
sitemap/routes/data-assets-companies.md -
/data-assets/people — reviewer audit of team / advisor / portco-ceo metadata + headshots across every engagement layout
Reviewer audit over `data/**/{team,portfolio}/*.md` — people are told from companies by the *presence* of `role_class`. SSR'd behind auth.
sitemap/routes/data-assets-people.md -
/play/[deckSlug]/[variantSlug]/print/ — one-shot PDF export surface; renders the whole variant stacked for the browser print dialog
Stacks every slot as SlideCanvas instances with `page-break-after: always`; no `@page` override, so the browser picks paper size.
sitemap/routes/play-print.md -
/toc/[deckSlug]/ — deck-level dual-surface review matrix (one row per slot × one column per variant)
The deck-level review matrix: variants × slots with dual-surface ratings per cell, distinct from the per-variant `/toc/[deck]/[variant]/`.
sitemap/routes/toc-deck.md -
runtime/mode-switcher — TS factory createModeSwitcher({client, defaultMode, respectSystemPreference}); per-client localStorage namespace
Three-mode state machine factory, namespaced to `{client}:mode` in localStorage and installed as a `window.modeSwitcher` singleton.
sitemap/runtime/mode-switcher.md -
/dev/icons — recurring design-review workbench
A kept design-review workbench — one `/dev/*` page rendering every candidate for a visual-primitive decision side by side, in real context.
sitemap/routes/dev-icons.md -
Init DidiDecks as Core Submodule of AI-Labs
Carve dididecks-ai out into its own repo and re-attach it to ai-labs as a git submodule, with branch-aligned tiers.
plans/Init-DidiDecks-as-core-Submodule-of-AI-Labs.md -
Refactor scroll-ported slides into true static play-format slides (per-client, repeat for every deck)
A reusable procedure for stripping scroll idioms — vw/vh units, reveals, marquees — from copied slides so `/play` and `/print` render them.
plans/Refactor-Scroll-Ported-Slides-to-Static-Play-Format.md -
DeckChrome — themable floating navigation capsule for Play-UI (and eventually Scroll-UI variant cycling)
Floating bottom-right nav capsule replacing v0.1's dark PlayChrome bar; styling comes only from `--ddd-chrome-*` custom properties.
sitemap/components/DeckChrome.md -
DeckOverlay--Play-UI — the floating overlay layer for Play-mode decks
Single mount point on the play-slot route composing DeckChrome and SlideRankPill; its `<section data-slot>` wrap is the play-mode adapter.
sitemap/components/DeckOverlay--Play-UI.md -
DeckOverlay--Scroll-UI — the floating overlay layer for Scroll-mode decks
Layout-neutral (`display: contents`) mount for the affordances riding over a scroll deck — each a named slot consumers can rearrange.
sitemap/components/DeckOverlay--Scroll-UI.md -
DecomposeFirstPlaceholder — empty-slot fallback rendered when a per-slide file doesn't exist yet
Empty-slot fallback on the play route — an invitation to begin the rank → decompose → recreate loop, deliberately not an error state.
sitemap/components/DecomposeFirstPlaceholder.md -
DididecksNav — shell-injected global header linking Scroll · TOC · Play · Changelog
Shell-injected global header auto-mounted on `/toc/*` and `/play/*`, with links derived from the consumer's own deck registry.
sitemap/components/DididecksNav.md -
SlideCanvas — pure-CSS 16:9 wrapper that scales a 1920×1080 stage to fit any canvas
Pure-CSS 16:9 stage — container queries scale a 1920×1080 design size to any canvas, so the Play-UI scaling pipeline needs no JS.
sitemap/components/SlideCanvas.md -
SlideRankPill — floating five-button classifier for the active slot (rename pending → SlideClassifierPill)
Bottom-right floating pill exposing the five-state classifier for the active slot, found via IntersectionObserver over `section[data-slot]`.
sitemap/components/SlideRankPill.md -
/api/slide-decompose — non-destructive stub generator for the Phase 1 → Phase 2 transition
Dev-only route that writes an empty per-slide stub and refuses to overwrite — 409 if the file exists. Static Vercel builds never carry it.
sitemap/routes/api-slide-decompose.md -
/api/slide-rank — read + write per-slide classifier state into the consumer's audits file
Dev-only GET/POST over `data/audits/slides.json` — `'pending'` is never persisted; posting it deletes the entry. 404s in production builds.
sitemap/routes/api-slide-rank.md -
/play/[deckSlug]/[variantSlug]/ — variant-index redirect to slot 01
Enumerates every (deck, variant) and 302s to slot 01 — unconditionally today, so slot-less variants like chroma's proto land on a 404.
sitemap/routes/play-index.md -
/play/[deckSlug]/[variantSlug]/[slot]/ — single-slot Play-UI renderer with keyboard nav
Static per-slot route: dynamic-imports `slides/{variant}/{slot}-{slug}.astro` into SlideCanvas, falling back to DecomposeFirstPlaceholder.
sitemap/routes/play-slot.md -
/toc/[deckSlug]/[variantSlug]/ — bird's-eye-view audit dashboard with rank pills + scaffold buttons
Per-variant TOC — one row per slot with five rank pills and a scaffold button POSTing to `/api/slide-decompose`. Read-write in dev only.
sitemap/routes/toc.md -
Implementation Notes for Deck Iteration Workflow
agent-skills/deck-iteration-workflow/references/implementation-notes.md -
Phase Implementation Template
agent-skills/deck-iteration-workflow/templates/phase-implementation.md -
Slide Variant Template
agent-skills/deck-iteration-workflow/templates/slide-variant.md -
dididecks-ai/agent-skills/astro-knots/references/ecosystem
agent-skills/astro-knots/references/ecosystem.md -
dididecks-ai/agent-skills/astro-knots/references/philosophy
agent-skills/astro-knots/references/philosophy.md -
dididecks-ai/agent-skills/astro-knots/references/playbooks/github-pages-deploy
agent-skills/astro-knots/references/playbooks/github-pages-deploy.md -
dididecks-ai/agent-skills/astro-knots/references/playbooks/llms-txt-and-md-sidecars
agent-skills/astro-knots/references/playbooks/llms-txt-and-md-sidecars.md -
dididecks-ai/agent-skills/astro-knots/references/playbooks/new-site-setup
agent-skills/astro-knots/references/playbooks/new-site-setup.md -
dididecks-ai/agent-skills/astro-knots/references/playbooks/opengraph-system
agent-skills/astro-knots/references/playbooks/opengraph-system.md -
dididecks-ai/agent-skills/astro-knots/references/tech-stack
agent-skills/astro-knots/references/tech-stack.md -
dididecks-ai/agent-skills/astro-knots/skill
The Lossless Group's Astro Knots conventions — vision, tech hierarchy, approved frameworks, and hard prohibitions for the family of ~10+ Astro sites and the Lossless Flavored Markdown ecosystem. Use whenever working on an Astro project in the lossless-monorepo (or any sibling repo), scaffolding new sites, choosing dependencies, building components, integrating LFM, or when the user mentions "Astro Knots", "LFM", "Lossless Flavored Markdown", or "pseudomonorepo". Hard prohibitions on React, JSX, Angular, and unnecessary dependencies.
agent-skills/astro-knots/SKILL.md -
dididecks-ai/agent-skills/changelog-conventions/references/changelog-first-development
agent-skills/changelog-conventions/references/changelog-first-development.md -
dididecks-ai/agent-skills/changelog-conventions/references/filename-conventions
agent-skills/changelog-conventions/references/filename-conventions.md -
dididecks-ai/agent-skills/changelog-conventions/references/frontmatter-spec
agent-skills/changelog-conventions/references/frontmatter-spec.md -
dididecks-ai/agent-skills/changelog-conventions/references/voice-and-shape
agent-skills/changelog-conventions/references/voice-and-shape.md -
dididecks-ai/agent-skills/changelog-conventions/references/what-counts
agent-skills/changelog-conventions/references/what-counts.md -
dididecks-ai/agent-skills/changelog-conventions/skill
How The Lossless Group writes and structures changelog/ entries across all repos (projects, true monorepos, pseudomonorepos). Use whenever shipping or pushing a coherent chunk of work, when scaffolding a new repo's changelog/ directory, when authoring a product release message, when the user says "log this", "write a changelog", or "ship note", or when reviewing a changelog/ file. Encodes the strict frontmatter (publish, lede, ISO dates), filename pattern, "it exists" priority, and the show-don't-enforce ethos.
agent-skills/changelog-conventions/SKILL.md -
Title in title case
One-sentence hook that makes the reader want to keep reading. Specific, not generic.
agent-skills/changelog-conventions/templates/entry.md -
PRODUCT vX.Y.Z — Release Title
What this release does in one attention-grabbing sentence
agent-skills/changelog-conventions/templates/release.md -
dididecks-ai/agent-skills/context-vigilance/references/developing-a-spec
agent-skills/context-vigilance/references/developing-a-spec.md -
dididecks-ai/agent-skills/context-vigilance/references/doc-type-guide
agent-skills/context-vigilance/references/doc-type-guide.md -
dididecks-ai/agent-skills/context-vigilance/references/frontmatter-spec
agent-skills/context-vigilance/references/frontmatter-spec.md -
dididecks-ai/agent-skills/context-vigilance/references/philosophy
agent-skills/context-vigilance/references/philosophy.md -
dididecks-ai/agent-skills/context-vigilance/references/status-discipline
agent-skills/context-vigilance/references/status-discipline.md -
dididecks-ai/agent-skills/context-vigilance/references/versioning
agent-skills/context-vigilance/references/versioning.md -
dididecks-ai/agent-skills/context-vigilance/skill
Lossless Group's framework for managing context-v/ directories in any project. Use whenever creating, updating, or organizing files in any context-v/ folder (specs, prompts, blueprints, reminders, explorations, issues), or when the user asks about context engineering, AI co-development workflow, or the "context-v" convention. Enforces directory roles, the four-part epoch.major.minor.patch versioning, YAML frontmatter standard, wikilink cross-references, and the prep/reflective/journey cognitive modes.
agent-skills/context-vigilance/SKILL.md -
Blueprint: TITLE HERE
agent-skills/context-vigilance/templates/blueprint.md -
TITLE HERE
agent-skills/context-vigilance/templates/exploration.md -
Issue: TITLE HERE
agent-skills/context-vigilance/templates/issue.md -
Prompt: TITLE HERE
agent-skills/context-vigilance/templates/prompt.md -
Reminder: TITLE HERE
agent-skills/context-vigilance/templates/reminder.md -
TITLE HERE
One sentence that makes a reader want to keep reading. Newsroom-style hook — not a description.
agent-skills/context-vigilance/templates/spec.md -
dididecks-ai/agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/15f60674bf070c2f
agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/15f60674bf070c2f.md -
dididecks-ai/agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/25f0de5c86750b7e
agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/25f0de5c86750b7e.md -
dididecks-ai/agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/38b666f4189ea895
agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/38b666f4189ea895.md -
dididecks-ai/agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/40f956e078923920
agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/40f956e078923920.md -
dididecks-ai/agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/6c019018c31645a0
agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/6c019018c31645a0.md -
dididecks-ai/agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/76082587295e27c1
agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/76082587295e27c1.md -
dididecks-ai/agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/795e94c1c0c2cc5a
agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/795e94c1c0c2cc5a.md -
dididecks-ai/agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/88d0ded5729b5482
agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/88d0ded5729b5482.md -
dididecks-ai/agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/a2c70d73d66ca2cc
agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/a2c70d73d66ca2cc.md -
dididecks-ai/agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/b1a9507c907e5868
agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/b1a9507c907e5868.md -
dididecks-ai/agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/ba5de0bff3839e6d
agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/ba5de0bff3839e6d.md -
dididecks-ai/agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/c4c0fa68d0682b61
agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/c4c0fa68d0682b61.md -
dididecks-ai/agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/e552f2b87caf8f63
agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/e552f2b87caf8f63.md -
dididecks-ai/agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/f57055e06641af3c
agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/f57055e06641af3c.md -
dididecks-ai/agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/fa616c0558874713
agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/fa616c0558874713.md -
dididecks-ai/agent-skills/crawl-fetch-ingest/future-work
Known v1 limitations and planned extensions for the crawl-fetch-ingest skill
agent-skills/crawl-fetch-ingest/future-work.md -
dididecks-ai/agent-skills/crawl-fetch-ingest/routines/investor-credibility-ingest
Sub-workflow of crawl-fetch-ingest. Company-anchored expansion through a list of backer firms — for each firm, ingest its team + its portfolio companies (with brand assets), so the operating company's deck/site can render credibility cards for readers starting from near-zero context. Stops at the firms' portfolio companies; does NOT descend to portco CEOs.
agent-skills/crawl-fetch-ingest/routines/investor-credibility-ingest.md -
dididecks-ai/agent-skills/crawl-fetch-ingest/routines/triage-brand-assets
Sub-workflow of crawl-fetch-ingest. Walks every brand asset that was fetched for a firm through a quality review, classifying each into good-to-go / not-urgent-passable / urgent-rework / deferred-for-now so the user can prioritize manual cleanup.
agent-skills/crawl-fetch-ingest/routines/triage-brand-assets.md -
dididecks-ai/agent-skills/crawl-fetch-ingest/schema/company
Canonical frontmatter shape for portfolio/{slug}.md (CP3 output — portfolio companies)
agent-skills/crawl-fetch-ingest/schema/company.md -
dididecks-ai/agent-skills/crawl-fetch-ingest/schema/firm
Canonical frontmatter shape for firm.md (the firm-level metadata file)
agent-skills/crawl-fetch-ingest/schema/firm.md -
dididecks-ai/agent-skills/crawl-fetch-ingest/schema/person
Canonical frontmatter shape for team/{slug}.md and portfolio/{slug}-ceo.md (CP1, CP2, CP4 outputs)
agent-skills/crawl-fetch-ingest/schema/person.md -
dididecks-ai/agent-skills/crawl-fetch-ingest/setup
One-time setup for the crawl-fetch-ingest skill — secrets file, MCP servers, helper scripts
agent-skills/crawl-fetch-ingest/setup.md -
dididecks-ai/agent-skills/crawl-fetch-ingest/skill
The Lossless Group's workflow for filling in team and portfolio metadata for VC firms and the operating companies they back — crawl a firm's site, fetch structured data + brand assets for people and companies referenced in a deck/PDF, ingest as canonical .md files with YAML frontmatter. Supports two starting anchors — firm-anchored (one VC → its team → its portfolio → portco CEOs) and company-anchored (one operating company → its backer firms → each backer's team + portfolio, stopping there) — for credibility-card use. Use whenever you need to recreate VC team pages, advisor sections, or portfolio company sections in HTML/Tailwind/Reveal slideshows; whenever the input is "here's a PDF and/or a firm URL, fill in the people and companies"; whenever you need headshots, LinkedIn URLs, company logos (SVG preferred), CEO metadata; whenever you need to "ingest our backers" or "make these investors legible to readers"; whenever the user mentions "fill out the team", "find the headshots", "credibility ingest", "we need their portfolio companies", or names this skill directly. Encodes the four-checkpoint cascade (VC team → advisors → portfolio companies → portco CEOs), the cross-tool fallback pattern (Firecrawl → Tavily → OpenGraph.io), the global-cache-per-firm convention so the same firm's data is reused across multiple decks/memos, and the loose canonical schema that sites converge toward on refactor (not enforced on ingest).
agent-skills/crawl-fetch-ingest/SKILL.md -
dididecks-ai/agent-skills/deck-iteration-workflow/skill
The Lossless Group's workflow for developing slides-only Astro sites for fundraise processes, aligned with the calmstorm-decks project patterns and the iterative approach from the "Develop a Slides-only Astro Site for a Fundraise Process" specification. Use when creating or modifying slide decks, managing slide variants, or implementing the structured iteration workflow for fundraise material development.
agent-skills/deck-iteration-workflow/SKILL.md -
dididecks-ai/agent-skills/generate-consistent-og-images/skill
agent-skills/generate-consistent-og-images/SKILL.md -
dididecks-ai/agent-skills/loops/git-conventions/references/body-structure
agent-skills/loops/git-conventions/references/body-structure.md -
dididecks-ai/agent-skills/loops/git-conventions/references/examples
agent-skills/loops/git-conventions/references/examples.md -
dididecks-ai/agent-skills/loops/git-conventions/references/header-patterns
agent-skills/loops/git-conventions/references/header-patterns.md -
dididecks-ai/agent-skills/loops/git-conventions/skill
The Lossless Group's git commit message conventions — structured headers with action verbs and effort groupings, paragraph-spaced bodies that explain impact before implementation, and "Also included" riders for minor changes. Use when writing commit messages, reviewing commits, or when the user mentions "commit message format", "git conventions", or asks how to structure a commit.
agent-skills/loops/git-conventions/SKILL.md -
dididecks-ai/agent-skills/loops/maintain-design-md/skill
How to author and maintain a `DESIGN.md` file at the root of any Lossless project (site, splash page, plugin landing, fundraise deck) following Google Stitch's open spec. Use whenever a project is missing a `DESIGN.md` and an agent needs the project's visual identity in machine-readable form; whenever the user mentions "design tokens", "design system", "DESIGN.md", or "Stitch spec"; whenever theme/CSS-token work changes the runtime values (new CSS custom property in `:root`, renamed token, new mode, new component pattern, refreshed palette, refreshed typography scale) and the documented contract has drifted; whenever a sibling skill (`generate-consistent-og-images`, `theme-system`, `astro-knots`) needs to read locked design values; whenever the user says "the agent doesn't know what color we use" or "let's write down the design system." Encodes (1) the Stitch spec's frontmatter token groups (colors, typography, rounded, spacing, components) and the eight prose sections in canonical order, (2) the maintenance triggers — what kinds of code changes should bounce back into the document, (3) the "runtime CSS is source of truth, DESIGN.md is the contract" discipline, (4) the precedent for off-spec extensions like an `imagery:` block, (5) anti-patterns. The skill never sees an API key or makes network calls — it's a pure-document discipline.
agent-skills/loops/maintain-design-md/SKILL.md -
dididecks-ai/agent-skills/loops/maintain-design-md/templates/design-md-scaffold
★ One paragraph describing the visual identity. Mention the runtime source-of-truth path so future agents know where to read the actual values.
agent-skills/loops/maintain-design-md/templates/design-md-scaffold.md -
dididecks-ai/agent-skills/loops/maintain-filemap/skill
Use whenever the directory shape of a Lossless pseudomonorepo (or any child repo) changes — a new top-level directory is added, a submodule is mounted or unmounted, a major subsystem is renamed — or on a weekly cadence, or before any release that would land on GitHub, to regenerate the `FILEMAP.md` at each affected repo's root so collaborators see the current shape without cloning. Triggers when the user mentions "filemap", "tree", "directory layout", "repo overview", "what does this repo even contain", "new collaborator joining"; also when the agent itself proposes adding/removing a top-level dir or a submodule, because that's exactly the moment the discipline matters.
agent-skills/loops/maintain-filemap/SKILL.md -
Loops — recurring maintenance disciplines that keep the repo legible over time
A new context-v category for skills that aren't one-shot specs or plans but **recurring rhythms** — the small, regular maintenance moves that keep a fast-moving repo readable to humans + agents who weren't there when the work happened. Each loop lives as its own subdirectory with a SKILL.md, optional scripts/, and templates/. Companion concept (TBD): `context-v/pairing/` for human-agent collaboration disciplines.
agent-skills/loops/README.md -
dididecks-ai/agent-skills/lossless-flavored-markdown/references/extensibility
agent-skills/lossless-flavored-markdown/references/extensibility.md -
dididecks-ai/agent-skills/lossless-flavored-markdown/references/frontmatter-schema
agent-skills/lossless-flavored-markdown/references/frontmatter-schema.md -
dididecks-ai/agent-skills/lossless-flavored-markdown/references/package-and-setup
agent-skills/lossless-flavored-markdown/references/package-and-setup.md -
dididecks-ai/agent-skills/lossless-flavored-markdown/references/syntax-and-directives
agent-skills/lossless-flavored-markdown/references/syntax-and-directives.md -
dididecks-ai/agent-skills/lossless-flavored-markdown/references/triggers-to-component-pipeline
agent-skills/lossless-flavored-markdown/references/triggers-to-component-pipeline.md -
dididecks-ai/agent-skills/lossless-flavored-markdown/skill
The Lossless Group's extended-markdown flavor — what LFM is, when to use it, how its directives normalize across syntaxes (CommonMark, GFM, Obsidian callouts, remark-directive, Markdoc), how citations and link previews work, and how sites extend it via trigger maps and theme tokens. Use whenever authoring or rendering content in any Astro Knots site, integrating the @lossless-group/lfm package, building or registering custom components for markdown, debugging callouts/embeds/citations, or when the user mentions "LFM", "Lossless Flavored Markdown", "extended markdown", "directive syntax", "wikilink", "trigger map", "callout", or "hex-code citation".
agent-skills/lossless-flavored-markdown/SKILL.md -
dididecks-ai/agent-skills/maintain-splash-pages/skill
The Lossless Group's pattern for repo-level splash pages — small Astro sites at <repo>/splash/ that ship to GitHub Pages on push to main, render the repo's changelog/ + context-v/ alongside curated marketing copy, and stay isolated from any package the repo also publishes. Use proactively whenever scaffolding a noteworthy new repo (every "important" repo wants one), when shipping a coherent chunk of work that an external reader would land on, when adding a feature (search, sort, tags row, theme mode) to an existing splash, when converting a legacy apps/<name>/ site to splash/, when troubleshooting a Pages deploy, or when the user mentions "splash", "GitHub Pages", "lossless-group.github.io", "Pagefind on our site", or working under a splash/ directory. Codifies the proven shape across three reference implementations (memopop-site, content-farm/splash, lfm/splash) and the package-isolation discipline that keeps splashes safe to add to repos that also publish to JSR/npm.
agent-skills/maintain-splash-pages/SKILL.md -
dididecks-ai/agent-skills/open-graph-share-seo-geo/references/llms-txt-implementation
agent-skills/open-graph-share-seo-geo/references/llms-txt-implementation.md -
dididecks-ai/agent-skills/open-graph-share-seo-geo/references/seo-best-practices
agent-skills/open-graph-share-seo-geo/references/seo-best-practices.md -
dididecks-ai/agent-skills/open-graph-share-seo-geo/references/sitemap-implementation
agent-skills/open-graph-share-seo-geo/references/sitemap-implementation.md -
dididecks-ai/agent-skills/open-graph-share-seo-geo/references/unfurler-matrix
agent-skills/open-graph-share-seo-geo/references/unfurler-matrix.md -
dididecks-ai/agent-skills/open-graph-share-seo-geo/references/user-tools-for-image-generation
agent-skills/open-graph-share-seo-geo/references/user-tools-for-image-generation.md -
dididecks-ai/agent-skills/open-graph-share-seo-geo/skill
How to make a page unfurl reliably in iMessage, WhatsApp, Slack, Discord, LinkedIn, and X; surface to search engines via sitemap.xml + robots.txt; and stay legible to generative engines (GEO), including the llms.txt standard for LLM corpus ingest. Use when adding or debugging OpenGraph / Twitter Card metadata, picking an OG image format, choosing where to host the image, fixing pages that "won't unfurl", auditing share previews, scaffolding /llms.txt and /llms-full.txt, or adding @astrojs/sitemap + robots.txt to a splash or marketing site. Encodes the JPEG-over-WebP rule, the ImageKit content-negotiation gotcha, the absolute-URL requirement, the og:image:type-must-match-bytes invariant, the cache-busting recipe for forcing a re-unfurl, the prose-in-markdown source-of-truth pattern for llms.txt, and the sitemap filter that keeps non-HTML routes (llms.txt, 404) out of the search-engine index.
agent-skills/open-graph-share-seo-geo/SKILL.md -
dididecks-ai/agent-skills/overlay-svg-text/skill
How to overlay on-brand SVG text on Lossless OG / share imagery — Hack Bold gradient-filled h1, thin sans eyebrow, Poor Story handwritten note. Use whenever a generated OG image needs title/eyebrow/sub text composited on top before it ships (the empty-region zone from `generate-consistent-og-images` is the canvas this skill paints into), whenever an unfurl preview looks too anonymous without a wordmark or subtitle, whenever a fundraise-deck slide needs a brand-flavored title overlay on a hero image, whenever the user says "overlay text on the OG image", "add a title to the banner", "make the unfurl say something", "drop a wordmark on this", or names this skill directly. Encodes the brand-wide type system (Hack Bold for gradient h1, thin sans for eyebrow, Poor Story for handwritten notes), the per-site gradient-from-DESIGN.md discipline (the brand SVGs are raster-baked references, not editable gradient sources — the editable gradient lives in each project's DESIGN.md), the canonical SVG fill-with-gradient pattern (simpler and more portable than mask/union for this use case), and the sharp-based compositing pipeline that writes JPEG-out for delivery per the open-graph-share-seo-geo skill.
agent-skills/overlay-svg-text/SKILL.md -
dididecks-ai/agent-skills/pseudomonorepos/references/anatomy
agent-skills/pseudomonorepos/references/anatomy.md -
dididecks-ai/agent-skills/pseudomonorepos/references/branch-alignment
agent-skills/pseudomonorepos/references/branch-alignment.md -
dididecks-ai/agent-skills/pseudomonorepos/references/content-rollup
agent-skills/pseudomonorepos/references/content-rollup.md -
dididecks-ai/agent-skills/pseudomonorepos/references/lifecycle-workflow
agent-skills/pseudomonorepos/references/lifecycle-workflow.md -
dididecks-ai/agent-skills/pseudomonorepos/references/search-first
agent-skills/pseudomonorepos/references/search-first.md -
dididecks-ai/agent-skills/pseudomonorepos/references/the-tree
agent-skills/pseudomonorepos/references/the-tree.md -
dididecks-ai/agent-skills/pseudomonorepos/skill
The Lossless Group's coined term and pattern — parent repos that aggregate child repos (often as git submodules) primarily to host a parent-level context-v/. Use whenever working anywhere in lossless-monorepo or its descendants, when starting any new task that might overlap with prior work, when scaffolding a new project, when the user mentions "pseudomonorepo", "submodule", "context-v", or names of the children (ai-labs, astro-knots, content-farm, tidyverse), AND ALWAYS when the user proposes to move/relocate/re-clone/re-nest a repo within the tree (which triggers the HARD STOP three-precondition checklist — local branches synced, remote branches catalogued, gitignored secrets backed up). Encodes the search-first-before-creating behavior, the tree-walking discipline, and the relocation-safety protocol.
agent-skills/pseudomonorepos/SKILL.md -
dididecks-ai/agent-skills/readme
agent-skills/README.md -
dididecks-ai/agent-skills/search-lossless-corpus/skill
Use whenever the user asks a question that prior work might already have answered — "what did we decide about X", "when did we ship X", "why did we choose X over Y", "has this failed before", "where did we put X" — and generally to ground answers in The Lossless Group's own corpus instead of training-data folklore. Encodes the four local Chroma collections (`context-vigilance-corpus`, `lossless-changelog`, `claude-code-sessions`, `claude-code-tool-traces`) reachable via the `chroma` MCP server, the four-step agentic-search loop (decompose → execute → evaluate → synthesize), the citation discipline (source path + timestamp + repo slug for every claim), and the metadata-filter patterns that make queries precise. Triggers on questions about prior decisions, shipped work, past Claude Code sessions, recurring tool failures, or any "did we already…" framing. Does not cover Chroma setup, ingestion pipelines, or maintenance — those are handled by [[chroma-local]] and the [[context-vigilance-kit]] scripts.
agent-skills/search-lossless-corpus/SKILL.md -
dididecks-ai/agent-skills/setup-new-dddecks-workspace/skill
Scaffold a new dididecks-ai client workspace end-to-end — submodule scaffold under `client-sites/<slug>/`, DESIGN.md from the client's brand identity, theme tokens, auth-surface wiring, initial substantiation-corpus connection, and a Scroll-UI starter deck the deck-iteration-workflow can pick up from. Two source-of-branding modes — **website-parse** (crawl the client's public site for tokens, fonts, logos via `crawl-fetch-ingest`) and **source-code-copy** (lift `theme.css` / `DESIGN.md` / brand assets directly from an existing repo when the client is us, an adjacent Lossless property, or otherwise hands over their source). Use whenever a new engagement starts and a `client-sites/<slug>/` submodule does not yet exist; whenever the user says "set up a workspace for <client>", "scaffold a new client", "we have a new client", "spin up a deck site for <firm>"; whenever The Lossless Group itself or any other internal Lossless property needs a deck-site of its own (source-code-copy mode triggers automatically when the brand source is a sibling Lossless repo); and as the cloud-workspace evolves, whenever the equivalent flow needs to fire from a chat surface rather than a CLI. Composes the existing skills — does not re-implement them — for crawl-fetch-ingest, maintain-design-md, theme-system, generate-consistent-og-images, deck-iteration-workflow, and pseudomonorepos (the submodule and branch-tier discipline).
agent-skills/setup-new-dddecks-workspace/SKILL.md -
dididecks-ai/agent-skills/slide-target/skill
Load the full working context for ONE DidiDecks slide (deck/variant/slot) so an agent can iterate on it slide-by-slide without re-explaining where things live. The first of the `slide-*` skill family (target → improve → rank → decompose). Use whenever the user wants to work on a specific slide of a DidiDecks/Astro deck — "let's work on slide 2", "fix this card", "/slide-target rural-income v1 02", "go slide by slide", "target the funder-pipeline slide" — or when iterating on a client-site deck under dididecks-ai (reach-edu-hub, chroma-decks, etc.). Assembles the section file, the slides.ts slot, the narrative slot, the rank/audit status, the live URLs, and the design-system tokens for exactly that slide, then scopes all work to it. Composes with deck-iteration-workflow and theme-system.
agent-skills/slide-target/SKILL.md -
dididecks-ai/agent-skills/study-repos-first/skill
The Lossless Group's discipline of pinning a curated collection of upstream repos (a "study") around a domain question *before* designing or coding in that domain. Use when starting work that touches conventions, file formats, schemas, protocols, or any decision where prior art exists; when the user mentions "study", "studies/", "reference collection", "prior art", "pin a submodule", or names of existing studies (open-specs-and-standards, memory-layers-for-agents, data-analytics-specifications-and-standards); when scaffolding a new study, extending one, or deciding whether something belongs in a study vs. a project. Encodes the "read upstream code, don't paraphrase from training data" behavior.
agent-skills/study-repos-first/SKILL.md -
dididecks-ai/agent-skills/theme-system/references/file-organization
agent-skills/theme-system/references/file-organization.md -
dididecks-ai/agent-skills/theme-system/references/two-tier-tokens
agent-skills/theme-system/references/two-tier-tokens.md -
dididecks-ai/agent-skills/theme-system/references/vibrant-mode-implementation
agent-skills/theme-system/references/vibrant-mode-implementation.md -
dididecks-ai/agent-skills/theme-system/skill
The Lossless Group's theme and mode architecture — two-tier token system, three-mode contract (light/dark/vibrant), theme.css organization, and design system conventions. Use when setting up themes/modes for any Astro Knots site, debugging mode toggles, working with CSS tokens, or when the user mentions "vibrant mode", "two-tier tokens", "theme.css", or design system patterns.
agent-skills/theme-system/SKILL.md
file-transporter 1 doc
filestarter 1 doc
flave-ai 6 docs
-
Ideas — the editor surface and the format
Fifteen ideas captured from a working session, sorted by what they would actually cost. Four are nearly free because the groundwork already shipped; two need work upstream in lfm before flave can touch them; one is already an open decision in the spec under a different name.
ideas/Editor-And-Format-Ideas.md -
The lfm barrel imports node builtins, so it cannot be bundled for a browser
A consumer that only wants `parseMarkdown` still drags `node:crypto`, `node:fs` and `node:path` into the bundle, because the main entry re-exports OGCache. Same class of defect lfm already documented for plantuml — but in the front door.
issues/LFM-Barrel-Imports-Node-Builtins.md -
Phase 0 — The Live Render Loop
Type Lossless Flavored Markdown, watch it become a styled document as you type, and invent new syntax without touching the renderer. The smallest thing that is already the product.
plans/Phase-0-The-Live-Render-Loop.md -
Phase 1 — One Operation Set, Four Callers
A menu, a palette, a rendered page you can type into, and an agent — all writing through the same named operations, so a human and an agent can never reach a state the other cannot describe.
plans/Phase-1-One-Operation-Set-Four-Callers.md -
Phase 2 — The Workspace and the Files Surface
Flave opens a folder, shows you what is in it, and lets you edit the theme that styles what you are reading — so design work is brought in once and reused, never recreated.
plans/Phase-2-The-Workspace-And-The-Files-Surface.md -
Flave — An Agent-Native Document Format and Desktop Publisher
The master spec. A package format (.flave) and an editor built on Lossless Flavored Markdown — a document that keeps its workings, publishes only what you choose, and is written in the languages agents already speak fluently.
specs/Master-Flave-An-Agent-Native-Document-Format-and-Publisher.md
fullstack-vc 23 docs
-
A Two-Perspective How-To Engine — Use-Cases ✕ Tool-Uses, Built on LFM (Not Starlight)
VCs arrive two ways: 'I need to automate dealflow' (a use-case) and 'I've heard I need Hermes Agent' (a tool). The same how-to should be reachable from both doors. This spec defines a docs engine on top of @lossless-group/lfm that renders one body of how-to content through two parallel navigation perspectives — with left-nav, right-hand TOC, prev/next pagination, wikilinks, callouts, citations, and video/GIF embeds — and deliberately does NOT adopt Astro Starlight.
specs/Two-Perspective-How-To-Docs-Engine-on-LFM.md -
What the room has told us
narratives/2026-05-27_monthly-all-hands/02a_data-from-previous-surveys.md -
Cover
narratives/2026-05-27_monthly-all-hands/01-cover.md -
What this is
narratives/2026-05-27_monthly-all-hands/02-what-this-is.md -
Format
narratives/2026-05-27_monthly-all-hands/04-format.md -
Create your account
narratives/2026-05-27_monthly-all-hands/05a_create-your-account.md -
The LPs as Co-Investors Conundrum
narratives/2026-05-27_monthly-all-hands/05b_lp-conundrum.md -
From Yes to Win
narratives/2026-05-27_monthly-all-hands/05c_from-yes-to-win.md -
Cortado Demo — Claude Teams for Firm Impact
narratives/2026-05-27_monthly-all-hands/06a_cortado-claude-teams.md -
Toby Demo — OpenClaw + Obsidian for Pipeline
narratives/2026-05-27_monthly-all-hands/06b_toby-openclaw-obsidian.md -
Track 1 · Internal Conviction → IC
narratives/2026-05-27_monthly-all-hands/07-track-internal-to-ic.md -
Track 2 · Syndicate to VCs
narratives/2026-05-27_monthly-all-hands/08-track-syndicate-to-vcs.md -
Track 3 · Offer to LPs
narratives/2026-05-27_monthly-all-hands/09-track-offer-to-lps.md -
How the breakouts run
narratives/2026-05-27_monthly-all-hands/10-breakout-mechanics.md -
Are you willing AND able?
narratives/2026-05-27_monthly-all-hands/11-willing-and-able.md -
Close
narratives/2026-05-27_monthly-all-hands/12-close.md -
Narratives — 2026-05-27 Monthly All-Hands deck
narratives/2026-05-27_monthly-all-hands/README.md -
Migrate Participant Stacks from Markdown to Turso with DB→Markdown Materialization
Stacks (current / aspirational / abandoned) live today in src/content/participants/<handle>.md and persist via GitHub App commits on every save — the same pattern the polling blueprint v2 §8.1 explicitly retired for time-sensitive data because of commit-history pollution, PEM brittleness, and concurrent-edit fragility. This task moves stacks to Astro DB on Turso as the authoritative store, with a periodic snapshot back to markdown so the build-in-public visibility stays intact. Generalizes the same materialization motion polling already uses (v2 §9), bringing two surfaces under one principled pattern.
tasks/Migrate-Participant-Stacks-from-Markdown-to-Turso-with-Materialization.md -
Redesign Stack Builder with Toggleable Multi-Column Layout and Cross-Column Drag-Drop
Today's StackBuilder is a single-column 'Current stack' editor — aspirational and abandoned entries are only reachable by scrolling far below and editing the markdown frontmatter by hand. Redesign as a wider three-bucket canvas with pill toggles for which buckets are visible, two-up side-by-side view when two are active, and drag-and-drop to move tools across buckets. Cross-column moves reshape data (notes ↔ intent ↔ reason) with inline prompts so nothing is silently lost. Mobile gracefully degrades to a tap-to-move modal.
tasks/Redesign-Stack-Builder-with-Multi-Column-Drag-Drop.md -
Wire Google Workspace OAuth as a Third Identity Provider
Env scaffolding for Google OAuth was added (uncommitted .env.example diff + real credentials in .env), but the code wiring was never written. This task implements the routes, session-payload union widening, header tooltip row, login button, and roster matching to bring Google to parity with the GitHub + LinkedIn providers — highest-leverage move before the May 27 All-Hands since most VC attendees convert better on Workspace than on either existing provider.
tasks/Wire-Google-Workspace-OAuth-Provider.md -
Troubleshooting SSG Authentication and the Port to SSR with a Database
issues/Troubleshooting-SSG-Authentication-and-Port-to-SSR-w-Database.md -
Optimize for Localized OpenGraph Metadata and Banner Image with Overlay
We want WhatsApp / iMessage / Twitter shares of any project page to surface a banner image that's visibly *about that project* — title baked in, not just a generic site-wide image. Today we have project-specific title and description in the OG meta tags but a shared placeholder image. Documents the four paths to a fix and the trigger that should reopen this work.
issues/Optimize-for-Local-OpenGraph-Metadata-and-Image-w-Overlay.md -
Page Spec — projects/index.astro & projects/[slug].astro
A specification for the FullStack VC Projects page (gallery + detail), the supporting content collection, the Hero and Project Gallery section components, and the Jumbo Popdown that surfaces projects from the site header.
sitemap/pages/Page__projects-index.astro.md
grab-reference 1 doc
id-didi-sh 4 docs
-
Dates are UTC at rest, viewer-local at render
reminders/Dates-Are-UTC-At-Rest-Viewer-Local-At-Render.md -
What Corpora-Builder Needs From didi.sh — the primitives list, handed over early
corpora-builder wants workspace identity from didi.sh. Two gaps: workspaces aren't a thing here yet, and a CLI has nowhere to put a cookie.
explorations/What-Corpora-Builder-Needs-From-didi-sh.md -
Serving Secrets Server-Side as an MCP Capability Plane
Implementation-local notes on a remote MCP endpoint that holds credentials server-side and hands collaborators capabilities, not secrets.
explorations/Serving-Secrets-Server-Side-as-an-MCP-Capability-Plane.md -
The canonical spec lives in the ai-labs parent, not here
This repo's context-v/ holds implementation-local docs only. The spec of record — contract, session model, schema, increments — is ai-labs/context-v/specs/Id-Didi-Sh-Identity-Service.md. Read it before changing anything load-bearing.
reminders/Canonical-Spec-Lives-in-Ai-Labs.md
image-gin 6 docs
-
Plan — Final ObsidianReviewBot cleanup round for image-gin v0.2.x
Local lint is clean but the bot flags 49 sentence-case hits — its default brand list has no Magnific or Ideogram, so they get a /skip reply.
plans/2026-05-10_Final-ObsidianReviewBot-Cleanup-Round.md -
Prompt — Add a New Model Provider to Image Gin
Agent-facing instruction for adding an image provider to Image Gin: the blueprint, the Recraft/Ideogram/Magnific prior art, the exact files.
prompts/Add-New-Model-Provider.md -
This Is an Obsidian Plugin — Read the Obsidian API Docs
The Obsidian API is the source of truth: `any`, innerHTML, and var are all outright bans, and Electron breaks browser muscle memory.
reminders/This-is-an-Obsidian-plugin-Read-Obsidian-API-Docs.md -
Blueprint — Add a New Image-Generation Provider (case study: Ideogram)
Recraft keeps brand style server-side as a style_id; Ideogram has none, so brand voice becomes a prefix/suffix prompt template in settings.
blueprints/Add-New-Image-API-to-Providers.md -
Plan — Bring Image Gin up to Obsidian Community-Plugin Publishing Standards
17 explicit-any sites, 2 innerHTML calls, and a hand-rolled YAML parser — tighten ESLint to error first so pnpm build surfaces the rest.
plans/2026-05-03_Assuring-Obsidian-Community-Plugin-Requirements.md -
Chore to Update All Dependencies
TS 6 forced moduleResolution bundler and a node types entry — and revealed esbuild had been silently dropping the Freepik stylesheet.
Chore-to-Update-All-Dependencies.md
lfm 8 docs
-
Heading Outline Cannot Distinguish Container Headings from Document Headings
`tree.data.headings` collects a `###` inside a `> [!info]` callout as a document section — right for anchors, wrong for a table of contents.
issues/Heading-Outline-Cannot-Distinguish-Container-Headings.md -
JSR Export Map Omits the Formats Subpaths
`deno.json` declares two exports; `package.json` declares six. The four it omits are the entire code-fence format registry — so the feature 0.4.1 was built around is unreachable for every consumer that installs from JSR, which is all nine of them.
issues/JSR-Export-Map-Omits-the-Formats-Subpaths.md -
Naming Plugins Against the Remark Ecosystem
Three questions pick the prefix — `remark-`, `remark-lfm-`, or `lfm-` — and the prefix tells a stranger on JSR how much of remark they know.
blueprints/Naming-Plugins-Against-the-Remark-Ecosystem.md -
Maintain Eyebrow, Heading and Subheading Blocks
Cards have had a three-part heading for years — eyebrow, heading, subheading — and long articles need it more than cards do. Three adjacent lines, one semantic unit, one `<hgroup>`, and only the middle one ever reaches the table of contents.
Maintain-Eyebrow-Heading-Subheading-Blocks.md -
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.
Maintain-Table-of-Contents-from-the-Heading-Outline.md -
Maintain Heading Anchors And Share Links
A fragment URL is a public contract, and we currently ship two incompatible definitions of it. This moves anchor identity into LFM as data, leaves the share affordance in the render layer, and fixes collisions nobody is handling.
Maintain-Heading-Anchors-and-Share-Links.md -
Workspace vs JSR for LFM Consumers
Why most consumer sites should pin @lossless-group/lfm to JSR while exactly one acts as the local workspace sandbox — and the boring deploy-host failure mode that forces the discipline.
Workspace-vs-JSR-for-LFM-Consumers.md -
Render AST in Debug
Exploration of AST structure at each stage of markdown processing to understand how to handle callouts
Render-AST-in-Debug.md
lmstud-yo 1 doc
lossless-changelog 2 docs
-
Aggregate Changelog Streams Across the Lossless Tree via the GitHub API
One hand-maintained collection becomes a live aggregation over 38 changelog streams, each pulled from its own repo at its own branch.
specs/Aggregate-Changelog-Streams-Across-the-Lossless-Tree-via-the-GitHub-API.md -
Extract the Lossless Brand Layer from lossless-site
The brand is worth keeping; its token system isn't — 14 Google fonts loaded to use none. Extract it into two-tier tokens, dark by decision.
specs/Extract-the-Lossless-Brand-Layer-from-lossless-site.md
lossless-decks 4 docs
-
Born from lived experience — Michael Staton, Convener
slides-content/lossless-group--born-from-lived-experience.md -
Firm-Wide Emergent Practices — Discovery, not prescription
slides-content/lossless-group--firm-wide-emergent-practices.md -
Ideal Engagement — One week on-site, then drag down, then white whales
slides-content/lossless-group--ideal-engagement.md -
Credibility — Two years of applied AI for clients
slides-content/lossless-group--credibility.md
lossless-monorepo 196 docs
-
Syncing Directories Across a Pseudomonorepo
Three annoyances that look like one problem. Symlinks break git, submodules cost too much, and rclone has no watcher.
explorations/Sync-Dirs-in-Pseudomonorepo-Architecture.md -
Check the Substrate Before Reasoning On Top Of It
A decision recorded in a plan is not a fact about the system. List the store before designing anything that writes to it.
reminders/Check-The-Substrate-Before-Reasoning-On-Top-Of-It.md -
Dates are UTC at rest, viewer-local at render
reminders/Dates-Are-UTC-At-Rest-Viewer-Local-At-Render.md -
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.
blueprints/Continuous-Integration-with-GitHub-Actions.md -
Maintain a current README and other root docs
84 repos in this tree have a README. Nineteen have a CLAUDE.md, sixteen a DESIGN.md, and exactly two have an AGENTS.md.
habits/Maintain-a-Current-README-and-other-Docs.md -
Public skills, private config — and the first skill to prove it
Some skills only work if they know who they're working for, which is exactly what a public repo can't hold. The answer is a gitignored config/private.json read at runtime by instruction rather than by templating, an example file that serves as the contract, and an audit grep that has to come back empty before you push. The CRM interface guidelines are the first skill built to that shape.
agent-skills/changelog/2026-08-14_01.md -
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.
blueprints/Understanding-Codebases-with-Graphify.md -
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.
blueprints/Browser-Drive-Verification-For-Agent-Sessions.md -
context-vigilance grows from six folders to eight — plus a universal tier and an experimental tier
plans/ and agent-skills/ earned canon the honest way: fourteen and five repos adopted them without anyone declaring them official. The skill now names them, blesses extra/ and sitemap/ as universal utilities (extra/ gitignored by default), and stakes out loops/, handoffs/, decisions/, and contracts/ as the experimental tier still finding its shape.
agent-skills/changelog/2026-07-21_01.md -
A new SurrealDB verification skill, a lede-length discipline propagated across two skills, and sync-skills-symlinks preps for an agent-skills migration
A skill for querying a SurrealDB canonical layer directly instead of writing a throwaway Node script per check. Plus: the lede field was drifting toward mini-essays, so changelog-conventions and context-vigilance both got a 'subtitle-length, not a paragraph' rule with the same wording. Plus: sync-skills-symlinks.sh now recognizes a context-v/agent-skills/ layout alongside the legacy context-v/skills/ one, ready for a migration that hasn't moved any actual skill directories yet.
agent-skills/changelog/2026-07-07_01.md -
New skill (gh-cli-projects-tasks-conventions), new credibility-ingest routine, and three skill updates from real-world incidents
A premature-on-purpose new skill for gh project task creation — codifying just two conventions (compose with pseudomonorepos to find the right repo, link to context-v files via clickable GitHub URLs) so they don't drift while the rest emerge. Plus a company-anchored credibility-ingest routine that inverts the crawl-fetch-ingest cascade so a fundraising deck can render its backers legibly. Plus three updates born from real incidents: an Astro Knots prerender-vs-auth rule (calmstorm-decks shipped a silent production bypass before we caught it), an audience-cascade cross-reference in git-conventions, and a full rewrite of the content-rollup reference now that two production splashes have implemented it.
agent-skills/changelog/2026-06-05_01.md -
Reframe the audience-cascade section in changelog-conventions — marketing up top, engineering as the narrative unfolds
The earlier framing read as 'marketing all the way down,' which fought the four-audience cascade the same section then described. Reframed to say what the cascade actually does: the lede / Why Care? / What's New? are marketing-shaped, the How it Works / Under the Hood / Files Touched are engineering-shaped, and both belong — what differs is sequence.
agent-skills/changelog/2026-05-22_01.md -
VC Self-Host Stack as a Pseudomonorepo (and a Paired Study)
Two orphan dirs, `twenty-crm/` and `twenty-deployment/`, hint at a deployable stack a VC firm could self-host instead of renting SaaS.
explorations/VC-Self-Host-Stack-as-Pseudomonorepo.md -
Dependabot Alerts — Triage Playbook for Lossless Repos
The bulk-dismiss script with categorized rationales cleared 86 Dependabot alerts across three Obsidian plugins in about five minutes.
issues/Dependabot-Alerts-Triage-Playbook-For-Lossless-Repos.md -
Maintain status discipline across context-v files
A periodic sweep promoting `status` to match reality, so an agent landing cold can read `status: Draft` and trust that nothing has happened.
habits/Maintain-Status-Discipline-Across-Context-V-Files.md -
Changelog entries duplicated across augment-it/changelog/ and content/changelog--laerdal/
Eleven backfilled augment-it changelog entries currently live in two places. Either location can be the source of truth — but right now both are, and updates have to be made twice.
issues/Changelog-Duplicated-Across-Splash-And-Laerdal-Collection.md -
Deduplicate the augment-it changelog between the splash and the Laerdal collection
plans/Deduplicate-Augment-It-Changelog-Across-Splash-And-Laerdal.md -
Three New Skills — Crawl-Fetch-Ingest, Maintain DESIGN.md, Generate Consistent OG Images
Codified three workflows the team had been doing freehand: VC firm metadata crawls (crawl-fetch-ingest), agent-readable project visual-identity contracts following Google Stitch's open spec (maintain-design-md), and consistent share-imagery generation via the Ideogram v3 API with WhatsApp/iMessage as the primary target (generate-consistent-og-images). The OG-images skill picked up an empirical refinement this session — empty space has to be declared as a first-class rendered subject, not left as residue — that pushed the BannerTall composition from a chronic 85% subject-fill to a clean 40-65%.
agent-skills/changelog/2026-05-11_01.md -
Scaffold the lossless-agent-skills splash page
Repo gets its own GitHub Pages splash — operator/CLI posture, skills catalog as the primary content surface, Pagefind search, llms.txt for LLM ingest, sitemap + robots for search engines.
agent-skills/changelog/2026-05-11_02.md -
Port Astro Deck Sections to Slides
Porting a scroll-deck section to a 16:9 slide is a copy/paste adaptation into an independent file, never a wrapper around the original.
prompts/Port-Astro-Deck-Sections-to-Slides.md -
Maintain the llms.txt standard across significant sites & splash pages
Every substantive site serves `/llms.txt` and `/llms-full.txt`, regenerated on deploy, so crawlers ingest the corpus in one fetch.
habits/Maintain-LLM-Txt-Standard-across-Significant-Sites-&-Splash-Pages.md -
Maintain sitemap.xml and robots.txt across significant sites & splash pages
Every site that wants to be found ships an `@astrojs/sitemap` build and a `robots.txt` with an absolute `Sitemap:` pointer.
habits/Maintain-Sitemap-and-Robots-across-Significant-Sites-&-Splash-Pages.md -
Implement Deeper Analytics Tracking
prompts/Implement-Deeper-Analytics-Tracking.md -
Setup Analytics across Sites
prompts/Setup-Analytics-Across-Sites.md -
Pseudomonorepo Settings — Fence Each Project from Parent pnpm Workspaces
reminders/Pseudomonorepo-Settings.md -
Two New Skills — Maintain Splash Pages, Chroma Agent Skills (Submodule)
Added the Maintain Splash Pages skill — codifying the <repo>/splash/ GitHub Pages pattern proven across three reference implementations — and pinned chroma-core/agent-skills as a submodule so agents loading the Lossless skills tree get upstream-authoritative Chroma guidance instead of paraphrased-from-training-data vector-store advice.
agent-skills/changelog/2026-05-07_01.md -
Explore: GitHub API for Live KPIs — Credibility Without Stars
60+ commits/day per person, 4,400+ content files, no 50K stars. What GitHub can give us for a credibility-by-shipping story.
explorations/Explore-GitHub-API-for-Live-KPIs.md -
Explore: Using PRs More — Why a Solo Dev Should Bother
PRs aren't a review ritual — they're an integration ritual: squash a granular trail into one shipped unit with a stable URL and a CI gate.
explorations/Using-PRs-More.md -
Maintain a Github Splash Page for each Repo
Every Lossless Group repo ships a small Astro site under splash/ that turns the repo into a free GitHub Pages landing page — hero, curated gallery, changelog and context-v rendering — without committing to a real marketing surface too early.
habits/Maintain-a-Github-Splash-Page-for-each-Repo.md -
Lossless Skills v0.0.0.1: From a Question to a Repo
We sat down to ask 'how is Pi different from Claude Code?' and ended the session with a public Lossless org repo of four interlocking Agent Skills, a global agent config, and the first principles of Changelog First Development.
agent-skills/changelog/2026-05-04_01.md -
First Aggregator Feedstock — 23 Changelogs, 222 Entries, One Data File
Walked the lossless-monorepo tree, found 23 changelog directories holding 222 entries across 18 upstream repos, and wrote the first machine-readable feedstock for the future Lossless Changelog umbrella aggregator — without waking the lossless-site beast that hosts it.
agent-skills/changelog/2026-05-04_02.md -
Implementation Notes for Deck Iteration Workflow
agent-skills/deck-iteration-workflow/references/implementation-notes.md -
Phase Implementation Template
agent-skills/deck-iteration-workflow/templates/phase-implementation.md -
Slide Variant Template
agent-skills/deck-iteration-workflow/templates/slide-variant.md -
example-vc
agent-skills/crawl-fetch-ingest/examples/example-firm.md -
lossless-monorepo/agent-skills/astro-knots/references/ecosystem
agent-skills/astro-knots/references/ecosystem.md -
lossless-monorepo/agent-skills/astro-knots/references/philosophy
agent-skills/astro-knots/references/philosophy.md -
lossless-monorepo/agent-skills/astro-knots/references/playbooks/github-pages-deploy
agent-skills/astro-knots/references/playbooks/github-pages-deploy.md -
lossless-monorepo/agent-skills/astro-knots/references/playbooks/llms-txt-and-md-sidecars
agent-skills/astro-knots/references/playbooks/llms-txt-and-md-sidecars.md -
lossless-monorepo/agent-skills/astro-knots/references/playbooks/new-site-setup
agent-skills/astro-knots/references/playbooks/new-site-setup.md -
lossless-monorepo/agent-skills/astro-knots/references/playbooks/opengraph-system
agent-skills/astro-knots/references/playbooks/opengraph-system.md -
lossless-monorepo/agent-skills/astro-knots/references/tech-stack
agent-skills/astro-knots/references/tech-stack.md -
lossless-monorepo/agent-skills/astro-knots/skill
The Lossless Group's Astro Knots conventions — vision, tech hierarchy, approved frameworks, and hard prohibitions for the family of ~10+ Astro sites and the Lossless Flavored Markdown ecosystem. Use whenever working on an Astro project in the lossless-monorepo (or any sibling repo), scaffolding new sites, choosing dependencies, building components, integrating LFM, or when the user mentions "Astro Knots", "LFM", "Lossless Flavored Markdown", or "pseudomonorepo". Hard prohibitions on React, JSX, Angular, and unnecessary dependencies.
agent-skills/astro-knots/SKILL.md -
lossless-monorepo/agent-skills/authoring
agent-skills/AUTHORING.md -
lossless-monorepo/agent-skills/candidates
Running backlog of potential future skills for the Lossless Group. Reference only - not a loadable skill.
agent-skills/CANDIDATES.md -
lossless-monorepo/agent-skills/changelog-conventions/references/changelog-first-development
agent-skills/changelog-conventions/references/changelog-first-development.md -
lossless-monorepo/agent-skills/changelog-conventions/references/filename-conventions
agent-skills/changelog-conventions/references/filename-conventions.md -
lossless-monorepo/agent-skills/changelog-conventions/references/frontmatter-spec
agent-skills/changelog-conventions/references/frontmatter-spec.md -
lossless-monorepo/agent-skills/changelog-conventions/references/voice-and-shape
agent-skills/changelog-conventions/references/voice-and-shape.md -
lossless-monorepo/agent-skills/changelog-conventions/references/what-counts
agent-skills/changelog-conventions/references/what-counts.md -
lossless-monorepo/agent-skills/changelog-conventions/skill
How The Lossless Group writes and structures changelog/ entries across all repos (projects, true monorepos, pseudomonorepos). Use whenever shipping or pushing a coherent chunk of work, when scaffolding a new repo's changelog/ directory, when authoring a product release message, when the user says "log this", "write a changelog", or "ship note", or when reviewing a changelog/ file. Also fires when the user drops screenshots for an entry or the work being logged is visual — composes with prep-images-for-embed so images get CDN-hosted with real alt text without the user naming both skills. Encodes the strict frontmatter (publish, lede, ISO dates), filename pattern, "it exists" priority, the never-use-relative-image-paths rule (entries get rolled up into parent sites, so relative paths break), and the show-don't-enforce ethos.
agent-skills/changelog-conventions/SKILL.md -
Title in title case
One-sentence hook that makes the reader want to keep reading. Specific, not generic.
agent-skills/changelog-conventions/templates/entry.md -
PRODUCT vX.Y.Z — Release Title
What this release does in one attention-grabbing sentence
agent-skills/changelog-conventions/templates/release.md -
Three Skills Shipped, Two Date Families Untangled, and a Repo That Can Keep a Secret
A skill library that publishes everything needs somewhere to put the things it can't. This session built that boundary — gitignored config read by instruction, an audit grep that has to come back empty, and a rule against injecting our conventions into repos we only have READ on — then shipped three skills through it and finally wrote down the frontmatter standard the tree had been running on tacitly for months.
agent-skills/changelog/2026-08-15_01.md -
lossless-monorepo/agent-skills/chroma-agent-skills/claude
agent-skills/chroma-agent-skills/CLAUDE.md -
lossless-monorepo/agent-skills/chroma-agent-skills/readme
agent-skills/chroma-agent-skills/README.md -
lossless-monorepo/agent-skills/chroma-agent-skills/skills/chroma-cloud/caching-collections
Reduce repeated collection lookup requests in high-traffic Chroma Cloud applications
agent-skills/chroma-agent-skills/skills/chroma-cloud/caching-collections.md -
lossless-monorepo/agent-skills/chroma-agent-skills/skills/chroma-cloud/chroma-cloud-qwen/python
Chroma's hosted Qwen embedding service
agent-skills/chroma-agent-skills/skills/chroma-cloud/chroma-cloud-qwen/python.md -
lossless-monorepo/agent-skills/chroma-agent-skills/skills/chroma-cloud/chroma-cloud-qwen/typescript
Chroma's hosted Qwen embedding service
agent-skills/chroma-agent-skills/skills/chroma-cloud/chroma-cloud-qwen/typescript.md -
lossless-monorepo/agent-skills/chroma-agent-skills/skills/chroma-cloud/cli
Getting started with the Chroma CLI for Chroma Cloud authentication and database management
agent-skills/chroma-agent-skills/skills/chroma-cloud/cli.md -
lossless-monorepo/agent-skills/chroma-agent-skills/skills/chroma-cloud/data-model
An overview of how Chroma stores data
agent-skills/chroma-agent-skills/skills/chroma-cloud/data-model.md -
lossless-monorepo/agent-skills/chroma-agent-skills/skills/chroma-cloud/error-handling/python
Handling errors and failures when working with Chroma
agent-skills/chroma-agent-skills/skills/chroma-cloud/error-handling/python.md -
lossless-monorepo/agent-skills/chroma-agent-skills/skills/chroma-cloud/error-handling/typescript
Handling errors and failures when working with Chroma
agent-skills/chroma-agent-skills/skills/chroma-cloud/error-handling/typescript.md -
lossless-monorepo/agent-skills/chroma-agent-skills/skills/chroma-cloud/forking/python
Instantly duplicate collections using copy-on-write forking in Chroma Cloud
agent-skills/chroma-agent-skills/skills/chroma-cloud/forking/python.md -
lossless-monorepo/agent-skills/chroma-agent-skills/skills/chroma-cloud/forking/typescript
Instantly duplicate collections using copy-on-write forking in Chroma Cloud
agent-skills/chroma-agent-skills/skills/chroma-cloud/forking/typescript.md -
lossless-monorepo/agent-skills/chroma-agent-skills/skills/chroma-cloud/metadata/python
Store and query metadata, including filters and array values
agent-skills/chroma-agent-skills/skills/chroma-cloud/metadata/python.md -
lossless-monorepo/agent-skills/chroma-agent-skills/skills/chroma-cloud/metadata/typescript
Store and query metadata, including filters and array values
agent-skills/chroma-agent-skills/skills/chroma-cloud/metadata/typescript.md -
lossless-monorepo/agent-skills/chroma-agent-skills/skills/chroma-cloud/querying/python
Query and Get Data from Chroma Collections
agent-skills/chroma-agent-skills/skills/chroma-cloud/querying/python.md -
lossless-monorepo/agent-skills/chroma-agent-skills/skills/chroma-cloud/querying/typescript
Query and Get Data from Chroma Collections
agent-skills/chroma-agent-skills/skills/chroma-cloud/querying/typescript.md -
lossless-monorepo/agent-skills/chroma-agent-skills/skills/chroma-cloud/quotas
Chroma Cloud quotas and request limits
agent-skills/chroma-agent-skills/skills/chroma-cloud/quotas.md -
lossless-monorepo/agent-skills/chroma-agent-skills/skills/chroma-cloud/regex/python
Learn how to use regex filters in Chroma queries
agent-skills/chroma-agent-skills/skills/chroma-cloud/regex/python.md -
lossless-monorepo/agent-skills/chroma-agent-skills/skills/chroma-cloud/regex/typescript
Learn how to use regex filters in Chroma queries
agent-skills/chroma-agent-skills/skills/chroma-cloud/regex/typescript.md -
lossless-monorepo/agent-skills/chroma-agent-skills/skills/chroma-cloud/schema/python
Schema() configures collections with multiple indexes
agent-skills/chroma-agent-skills/skills/chroma-cloud/schema/python.md -
lossless-monorepo/agent-skills/chroma-agent-skills/skills/chroma-cloud/schema/typescript
Schema() configures collections with multiple indexes
agent-skills/chroma-agent-skills/skills/chroma-cloud/schema/typescript.md -
lossless-monorepo/agent-skills/chroma-agent-skills/skills/chroma-cloud/search-api/python
An expressive and flexible API for doing dense and sparse vector search on collections, as well as hybrid search
agent-skills/chroma-agent-skills/skills/chroma-cloud/search-api/python.md -
lossless-monorepo/agent-skills/chroma-agent-skills/skills/chroma-cloud/search-api/typescript
An expressive and flexible API for doing dense and sparse vector search on collections, as well as hybrid search
agent-skills/chroma-agent-skills/skills/chroma-cloud/search-api/typescript.md -
lossless-monorepo/agent-skills/chroma-agent-skills/skills/chroma-cloud/skill
Provides expertise on Chroma Cloud integration for semantic search and hybrid search applications. Use when the user is working with Chroma Cloud, CloudClient, managed collections, Schema(), Search(), hybrid search, or Chroma Cloud CLI workflows.
agent-skills/chroma-agent-skills/skills/chroma-cloud/SKILL.md -
lossless-monorepo/agent-skills/chroma-agent-skills/skills/chroma-cloud/understanding-a-codebase
Guidance for adding Chroma search to an existing application
agent-skills/chroma-agent-skills/skills/chroma-cloud/understanding-a-codebase.md -
lossless-monorepo/agent-skills/chroma-agent-skills/skills/chroma-cloud/updating-deleting/python
Update existing documents and delete data from collections
agent-skills/chroma-agent-skills/skills/chroma-cloud/updating-deleting/python.md -
lossless-monorepo/agent-skills/chroma-agent-skills/skills/chroma-cloud/updating-deleting/typescript
Update existing documents and delete data from collections
agent-skills/chroma-agent-skills/skills/chroma-cloud/updating-deleting/typescript.md -
lossless-monorepo/agent-skills/chroma-agent-skills/skills/chroma-local/cli
Starting and managing a local open source Chroma server from the CLI
agent-skills/chroma-agent-skills/skills/chroma-local/cli.md -
lossless-monorepo/agent-skills/chroma-agent-skills/skills/chroma-local/data-model
An overview of how Chroma stores data
agent-skills/chroma-agent-skills/skills/chroma-local/data-model.md -
lossless-monorepo/agent-skills/chroma-agent-skills/skills/chroma-local/error-handling/python
Handling errors and failures when working with Chroma
agent-skills/chroma-agent-skills/skills/chroma-local/error-handling/python.md -
lossless-monorepo/agent-skills/chroma-agent-skills/skills/chroma-local/error-handling/typescript
Handling errors and failures when working with Chroma
agent-skills/chroma-agent-skills/skills/chroma-local/error-handling/typescript.md -
lossless-monorepo/agent-skills/chroma-agent-skills/skills/chroma-local/local-chroma/python
How to run and use local chroma
agent-skills/chroma-agent-skills/skills/chroma-local/local-chroma/python.md -
lossless-monorepo/agent-skills/chroma-agent-skills/skills/chroma-local/local-chroma/typescript
How to run and use local chroma
agent-skills/chroma-agent-skills/skills/chroma-local/local-chroma/typescript.md -
lossless-monorepo/agent-skills/chroma-agent-skills/skills/chroma-local/metadata/python
Store and query metadata, including filters and array values
agent-skills/chroma-agent-skills/skills/chroma-local/metadata/python.md -
lossless-monorepo/agent-skills/chroma-agent-skills/skills/chroma-local/metadata/typescript
Store and query metadata, including filters and array values
agent-skills/chroma-agent-skills/skills/chroma-local/metadata/typescript.md -
lossless-monorepo/agent-skills/chroma-agent-skills/skills/chroma-local/querying/python
Query and Get Data from Chroma Collections
agent-skills/chroma-agent-skills/skills/chroma-local/querying/python.md -
lossless-monorepo/agent-skills/chroma-agent-skills/skills/chroma-local/querying/typescript
Query and Get Data from Chroma Collections
agent-skills/chroma-agent-skills/skills/chroma-local/querying/typescript.md -
lossless-monorepo/agent-skills/chroma-agent-skills/skills/chroma-local/regex/python
Learn how to use regex filters in Chroma queries
agent-skills/chroma-agent-skills/skills/chroma-local/regex/python.md -
lossless-monorepo/agent-skills/chroma-agent-skills/skills/chroma-local/regex/typescript
Learn how to use regex filters in Chroma queries
agent-skills/chroma-agent-skills/skills/chroma-local/regex/typescript.md -
lossless-monorepo/agent-skills/chroma-agent-skills/skills/chroma-local/skill
Use when the user needs self-hosted or local Chroma for semantic search, including `ChromaClient`, `HttpClient`, or Python `EphemeralClient`, local persistence, Docker or `chroma run`, or OSS Chroma without Chroma Cloud features.
agent-skills/chroma-agent-skills/skills/chroma-local/SKILL.md -
lossless-monorepo/agent-skills/chroma-agent-skills/skills/chroma-local/understanding-a-codebase
Guidance for adding Chroma search to an existing application
agent-skills/chroma-agent-skills/skills/chroma-local/understanding-a-codebase.md -
lossless-monorepo/agent-skills/chroma-agent-skills/skills/chroma-local/updating-deleting/python
Update existing documents and delete data from collections
agent-skills/chroma-agent-skills/skills/chroma-local/updating-deleting/python.md -
lossless-monorepo/agent-skills/chroma-agent-skills/skills/chroma-local/updating-deleting/typescript
Update existing documents and delete data from collections
agent-skills/chroma-agent-skills/skills/chroma-local/updating-deleting/typescript.md -
lossless-monorepo/agent-skills/chroma-agent-skills/src/chroma-cloud/general/caching-collections
Reduce repeated collection lookup requests in high-traffic Chroma Cloud applications
agent-skills/chroma-agent-skills/src/chroma-cloud/general/caching-collections.md -
lossless-monorepo/agent-skills/chroma-agent-skills/src/chroma-cloud/general/cli
Getting started with the Chroma CLI for Chroma Cloud authentication and database management
agent-skills/chroma-agent-skills/src/chroma-cloud/general/cli.md -
lossless-monorepo/agent-skills/chroma-agent-skills/src/chroma-cloud/general/quotas
Chroma Cloud quotas and request limits
agent-skills/chroma-agent-skills/src/chroma-cloud/general/quotas.md -
lossless-monorepo/agent-skills/chroma-agent-skills/src/chroma-cloud/skill
Provides expertise on Chroma Cloud integration for semantic search and hybrid search applications. Use when the user is working with Chroma Cloud, CloudClient, managed collections, Schema(), Search(), hybrid search, or Chroma Cloud CLI workflows.
agent-skills/chroma-agent-skills/src/chroma-cloud/SKILL.md -
lossless-monorepo/agent-skills/chroma-agent-skills/src/chroma-cloud/templates/chroma-cloud-qwen
Chroma's hosted Qwen embedding service
agent-skills/chroma-agent-skills/src/chroma-cloud/templates/chroma-cloud-qwen.md -
lossless-monorepo/agent-skills/chroma-agent-skills/src/chroma-cloud/templates/error-handling
Handling errors and failures when working with Chroma
agent-skills/chroma-agent-skills/src/chroma-cloud/templates/error-handling.md -
lossless-monorepo/agent-skills/chroma-agent-skills/src/chroma-cloud/templates/forking
Instantly duplicate collections using copy-on-write forking in Chroma Cloud
agent-skills/chroma-agent-skills/src/chroma-cloud/templates/forking.md -
lossless-monorepo/agent-skills/chroma-agent-skills/src/chroma-cloud/templates/schema
Schema() configures collections with multiple indexes
agent-skills/chroma-agent-skills/src/chroma-cloud/templates/schema.md -
lossless-monorepo/agent-skills/chroma-agent-skills/src/chroma-cloud/templates/search-api
An expressive and flexible API for doing dense and sparse vector search on collections, as well as hybrid search
agent-skills/chroma-agent-skills/src/chroma-cloud/templates/search-api.md -
lossless-monorepo/agent-skills/chroma-agent-skills/src/chroma-local/general/cli
Starting and managing a local open source Chroma server from the CLI
agent-skills/chroma-agent-skills/src/chroma-local/general/cli.md -
lossless-monorepo/agent-skills/chroma-agent-skills/src/chroma-local/skill
Use when the user needs self-hosted or local Chroma for semantic search, including `ChromaClient`, `HttpClient`, or Python `EphemeralClient`, local persistence, Docker or `chroma run`, or OSS Chroma without Chroma Cloud features.
agent-skills/chroma-agent-skills/src/chroma-local/SKILL.md -
lossless-monorepo/agent-skills/chroma-agent-skills/src/chroma-local/templates/error-handling
Handling errors and failures when working with Chroma
agent-skills/chroma-agent-skills/src/chroma-local/templates/error-handling.md -
lossless-monorepo/agent-skills/chroma-agent-skills/src/chroma-local/templates/local-chroma
How to run and use local chroma
agent-skills/chroma-agent-skills/src/chroma-local/templates/local-chroma.md -
lossless-monorepo/agent-skills/chroma-agent-skills/src/chroma-shared/general/data-model
An overview of how Chroma stores data
agent-skills/chroma-agent-skills/src/chroma-shared/general/data-model.md -
lossless-monorepo/agent-skills/chroma-agent-skills/src/chroma-shared/general/understanding-a-codebase
Guidance for adding Chroma search to an existing application
agent-skills/chroma-agent-skills/src/chroma-shared/general/understanding-a-codebase.md -
lossless-monorepo/agent-skills/chroma-agent-skills/src/chroma-shared/templates/metadata
Store and query metadata, including filters and array values
agent-skills/chroma-agent-skills/src/chroma-shared/templates/metadata.md -
lossless-monorepo/agent-skills/chroma-agent-skills/src/chroma-shared/templates/querying
Query and Get Data from Chroma Collections
agent-skills/chroma-agent-skills/src/chroma-shared/templates/querying.md -
lossless-monorepo/agent-skills/chroma-agent-skills/src/chroma-shared/templates/regex
Learn how to use regex filters in Chroma queries
agent-skills/chroma-agent-skills/src/chroma-shared/templates/regex.md -
lossless-monorepo/agent-skills/chroma-agent-skills/src/chroma-shared/templates/updating-deleting
Update existing documents and delete data from collections
agent-skills/chroma-agent-skills/src/chroma-shared/templates/updating-deleting.md -
lossless-monorepo/agent-skills/claude
agent-skills/CLAUDE.md -
lossless-monorepo/agent-skills/context-vigilance/references/developing-a-spec
agent-skills/context-vigilance/references/developing-a-spec.md -
lossless-monorepo/agent-skills/context-vigilance/references/doc-type-guide
agent-skills/context-vigilance/references/doc-type-guide.md -
lossless-monorepo/agent-skills/context-vigilance/references/frontmatter-spec
agent-skills/context-vigilance/references/frontmatter-spec.md -
lossless-monorepo/agent-skills/context-vigilance/references/philosophy
agent-skills/context-vigilance/references/philosophy.md -
lossless-monorepo/agent-skills/context-vigilance/references/status-discipline
agent-skills/context-vigilance/references/status-discipline.md -
lossless-monorepo/agent-skills/context-vigilance/references/versioning
agent-skills/context-vigilance/references/versioning.md -
lossless-monorepo/agent-skills/context-vigilance/skill
Lossless Group's framework for managing context-v/ directories in any project. Use whenever creating, updating, or organizing files in any context-v/ folder (specs, plans, prompts, blueprints, reminders, agent-skills, explorations, issues — plus the universal extra/ and sitemap/, and the experimental loops/, handoffs/, decisions/, habits/, and contracts/), or when the user asks about context engineering, AI co-development workflow, or the "context-v" convention. Enforces directory roles, the four-part epoch.major.minor.patch versioning, YAML frontmatter standard, wikilink cross-references, and the prep/reflective/journey cognitive modes.
agent-skills/context-vigilance/SKILL.md -
lossless-monorepo/agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/15f60674bf070c2f
agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/15f60674bf070c2f.md -
lossless-monorepo/agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/25f0de5c86750b7e
agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/25f0de5c86750b7e.md -
lossless-monorepo/agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/38b666f4189ea895
agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/38b666f4189ea895.md -
lossless-monorepo/agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/40f956e078923920
agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/40f956e078923920.md -
lossless-monorepo/agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/6c019018c31645a0
agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/6c019018c31645a0.md -
lossless-monorepo/agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/76082587295e27c1
agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/76082587295e27c1.md -
lossless-monorepo/agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/795e94c1c0c2cc5a
agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/795e94c1c0c2cc5a.md -
lossless-monorepo/agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/88d0ded5729b5482
agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/88d0ded5729b5482.md -
lossless-monorepo/agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/a2c70d73d66ca2cc
agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/a2c70d73d66ca2cc.md -
lossless-monorepo/agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/b1a9507c907e5868
agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/b1a9507c907e5868.md -
lossless-monorepo/agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/ba5de0bff3839e6d
agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/ba5de0bff3839e6d.md -
lossless-monorepo/agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/c4c0fa68d0682b61
agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/c4c0fa68d0682b61.md -
lossless-monorepo/agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/e552f2b87caf8f63
agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/e552f2b87caf8f63.md -
lossless-monorepo/agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/f57055e06641af3c
agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/f57055e06641af3c.md -
lossless-monorepo/agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/fa616c0558874713
agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/fa616c0558874713.md -
lossless-monorepo/agent-skills/crawl-fetch-ingest/future-work
Known v1 limitations and planned extensions for the crawl-fetch-ingest skill
agent-skills/crawl-fetch-ingest/future-work.md -
lossless-monorepo/agent-skills/crawl-fetch-ingest/routines/investor-credibility-ingest
Sub-workflow of crawl-fetch-ingest. Company-anchored expansion through a list of backer firms — for each firm, ingest its team + its portfolio companies (with brand assets), so the operating company's deck/site can render credibility cards for readers starting from near-zero context. Stops at the firms' portfolio companies; does NOT descend to portco CEOs.
agent-skills/crawl-fetch-ingest/routines/investor-credibility-ingest.md -
lossless-monorepo/agent-skills/crawl-fetch-ingest/routines/triage-brand-assets
Sub-workflow of crawl-fetch-ingest. Walks every brand asset that was fetched for a firm through a quality review, classifying each into good-to-go / not-urgent-passable / urgent-rework / deferred-for-now so the user can prioritize manual cleanup.
agent-skills/crawl-fetch-ingest/routines/triage-brand-assets.md -
lossless-monorepo/agent-skills/crawl-fetch-ingest/schema/company
Canonical frontmatter shape for portfolio/{slug}.md (CP3 output — portfolio companies)
agent-skills/crawl-fetch-ingest/schema/company.md -
lossless-monorepo/agent-skills/crawl-fetch-ingest/schema/firm
Canonical frontmatter shape for firm.md (the firm-level metadata file)
agent-skills/crawl-fetch-ingest/schema/firm.md -
lossless-monorepo/agent-skills/crawl-fetch-ingest/schema/person
Canonical frontmatter shape for team/{slug}.md and portfolio/{slug}-ceo.md (CP1, CP2, CP4 outputs)
agent-skills/crawl-fetch-ingest/schema/person.md -
lossless-monorepo/agent-skills/crawl-fetch-ingest/setup
One-time setup for the crawl-fetch-ingest skill — secrets file, MCP servers, helper scripts
agent-skills/crawl-fetch-ingest/setup.md -
lossless-monorepo/agent-skills/crawl-fetch-ingest/skill
The Lossless Group's workflow for filling in team and portfolio metadata for VC firms and the operating companies they back — crawl a firm's site, fetch structured data + brand assets for people and companies referenced in a deck/PDF, ingest as canonical .md files with YAML frontmatter. Supports two starting anchors — firm-anchored (one VC → its team → its portfolio → portco CEOs) and company-anchored (one operating company → its backer firms → each backer's team + portfolio, stopping there) — for credibility-card use. Use whenever you need to recreate VC team pages, advisor sections, or portfolio company sections in HTML/Tailwind/Reveal slideshows; whenever the input is "here's a PDF and/or a firm URL, fill in the people and companies"; whenever you need headshots, LinkedIn URLs, company logos (SVG preferred), CEO metadata; whenever you need to "ingest our backers" or "make these investors legible to readers"; whenever the user mentions "fill out the team", "find the headshots", "credibility ingest", "we need their portfolio companies", or names this skill directly. Encodes the four-checkpoint cascade (VC team → advisors → portfolio companies → portco CEOs), the cross-tool fallback pattern (Firecrawl → Tavily → OpenGraph.io), the global-cache-per-firm convention so the same firm's data is reused across multiple decks/memos, and the loose canonical schema that sites converge toward on refactor (not enforced on ingest).
agent-skills/crawl-fetch-ingest/SKILL.md -
lossless-monorepo/agent-skills/decile-hub-connector/references/endpoint-inventory
agent-skills/decile-hub-connector/references/endpoint-inventory.md -
lossless-monorepo/agent-skills/decile-hub-connector/skill
How augment-it (and any Lossless VC-client workspace) talks to the Decile Hub API — the first per-client custom connector. Use whenever pulling from or pushing to Decile Hub (people, organizations, pipeline prospects, deal shares, deal memos, funds/entities, portfolio companies, capital accounts, notes, tasks, files, events), wiring the Decile connector for a new client, building or maintaining the decile-mcp server, mapping Decile records into the SurrealDB canonical layer, or when the user mentions "Decile", "DecileHub", "DECILE_API_URL", "DECILE_HUB_API_KEY", or a per-client CRM connector. Encodes the auth (raw API token in the Authorization header — no Bearer), the per-tenant subdomain base URL, the THREE distinct pagination patterns, the upsert-by-natural-key write semantics, the custom_data_points / variables (merge-tag) system, and the mapping of Decile people/organizations onto the SurrealDB canonical persons/organizations tables. The authoritative contract is the on-disk OpenAPI spec; this skill is the operating guide on top of it.
agent-skills/decile-hub-connector/SKILL.md -
lossless-monorepo/agent-skills/deck-iteration-workflow/skill
The Lossless Group's workflow for developing slides-only Astro sites for fundraise processes, aligned with the calmstorm-decks project patterns and the iterative approach from the "Develop a Slides-only Astro Site for a Fundraise Process" specification. Use when creating or modifying slide decks, managing slide variants, or implementing the structured iteration workflow for fundraise material development.
agent-skills/deck-iteration-workflow/SKILL.md -
lossless-monorepo/agent-skills/expense-report-generation/skill
How to turn raw card and bank statement downloads into a defensible, client-ready expense report. Use whenever the user asks to build an expense report, reconcile AmEx or bank statements, work out "what is this charge for", aggregate reimbursables for a client or trip, split a claim by month, or render an expense PDF; whenever a folder of statement CSVs/PDFs needs to become a submittable document; or whenever the user says "expense report", "reimbursement", "what am I paying for", "which card was that on", "make this a PDF". Encodes the parent-company descriptor trap (Loom bills as ATLASSIAN, Trae as BYTEDANCE), the never-invent-a-product-name rule, the statement-close gap that silently truncates trips, cheap PDF text extraction, and the two-section BASE/EXTENDED structure.
agent-skills/expense-report-generation/SKILL.md -
lossless-monorepo/agent-skills/generate-consistent-og-images/skill
How to generate share-imagery (OpenGraph banners, portraits, squares, tall WhatsApp/iMessage cards) for any Lossless site or splash page so the resulting images form a coherent visual family — via two coexisting techniques: Ideogram illustration, or rasterizing the project's own hero/specimen component with macOS's `qlmanage`+`sips` (or a Playwright screenshot for higher fidelity). Use whenever a site, splash, plugin page, or fundraise deck needs an OG image generated or refreshed; whenever the user says "make an og image", "generate a banner", "we need a share image", "regenerate banners across formats", "the unfurl looks stale", "screenshot the hero for the share image", "turn this component into an OG image"; whenever scaffolding a new Astro Knots site that doesn't yet have an `og:image` or a `DESIGN.md`; whenever per-page or per-component custom illustrative imagery is needed even if it deliberately departs from the OG-image canon; whenever an existing OG image (of either technique) might already be live and a decision is needed about replacing vs. keeping it. Encodes the pattern of (1) choose Ideogram illustration vs. hero rasterization per the Strategy Choice section, (2) check / create a DESIGN.md following the Google Stitch open spec, (3) check / add an `imagery:` recipe block to that DESIGN.md, (4) call Ideogram v3 generate with every field locked except `prompt` and `aspect_ratio` (or rasterize the hero via `qlmanage`+`sips`), (5) save with the canonical naming convention, (6) treat WhatsApp + iMessage chat-preview as the primary share surface and other socials as secondary, (7) run the Case Protocol before wiring anything into a live `og:image` tag. The skill never sees an API key in source — `IDEOGRAM_API_KEY` lives in `~/.secrets` and is inherited from the shell, same pattern as the `crawl-fetch-ingest` skill.
agent-skills/generate-consistent-og-images/SKILL.md -
lossless-monorepo/agent-skills/gh-cli-projects-tasks-conventions/skill
How The Lossless Group uses the `gh` CLI for GitHub issues and Projects v2 tasks across the pseudomonorepo tree. Use whenever creating, editing, or listing GitHub Project tasks via `gh project item-create`, `gh project item-add`, or `gh project item-edit`; whenever creating repo issues via `gh issue create`; whenever the user mentions "gh project", "create a task", "create an issue", "add to the project", "draft a project item", "ProjectV2", labels, milestones, issue types, or asks to script task/issue creation; whenever an agent is about to author a task body that references one or more `context-v/` files. Encodes the **task-body-is-a-github-link** convention — every task whose work-context lives in a `context-v/` file gets a body whose primary content is a clickable GitHub URL to that file in its own repo (NOT a deep path inside the parent monorepo, because each pseudomonorepo level is its own git repo and the URL must respect that) — and the **prefill-the-sidebar** convention: query the repo/org's actual labels, milestones, assignees, and issue types, infer the best fit, ask the user only when nothing fits logically. Composes with the `pseudomonorepos` skill to identify which repo a local context-v path belongs to and which branch tier (`development` / `main` / `master`) the link should target.
agent-skills/gh-cli-projects-tasks-conventions/SKILL.md -
lossless-monorepo/agent-skills/git-conventions/references/body-structure
agent-skills/git-conventions/references/body-structure.md -
lossless-monorepo/agent-skills/git-conventions/references/examples
agent-skills/git-conventions/references/examples.md -
lossless-monorepo/agent-skills/git-conventions/references/header-patterns
agent-skills/git-conventions/references/header-patterns.md -
lossless-monorepo/agent-skills/git-conventions/skill
The Lossless Group's git commit message conventions — structured headers with action verbs and effort groupings, paragraph-spaced bodies that explain impact before implementation, and "Also included" riders for minor changes. Use when writing commit messages, reviewing commits, or when the user mentions "commit message format", "git conventions", or asks how to structure a commit.
agent-skills/git-conventions/SKILL.md -
lossless-monorepo/agent-skills/lossless-crm-interface-guidelines/skill
Conventions for reading and writing the operator's Twenty CRM instances (Lossless, Palmer AI, The Water Foundation) via MCP. Use whenever adding or enriching a company, person, deal, thesis, event, or portfolio relationship; when triaging a list or export into the CRM; or when extending the CRM schema. Encodes instance routing, the custom object model (Investment, Deal Source, Deal Prospect, Thesis, Thesis Fit, Events, Interaction), the forced-choice scoring standard, provenance rules, the companion-timeline-row rule that makes custom objects visible on a Person or Company timeline, and known MCP pitfalls.
agent-skills/lossless-crm-interface-guidelines/SKILL.md -
lossless-monorepo/agent-skills/lossless-flavored-markdown/references/extensibility
agent-skills/lossless-flavored-markdown/references/extensibility.md -
lossless-monorepo/agent-skills/lossless-flavored-markdown/references/frontmatter-schema
agent-skills/lossless-flavored-markdown/references/frontmatter-schema.md -
lossless-monorepo/agent-skills/lossless-flavored-markdown/references/package-and-setup
agent-skills/lossless-flavored-markdown/references/package-and-setup.md -
lossless-monorepo/agent-skills/lossless-flavored-markdown/references/syntax-and-directives
agent-skills/lossless-flavored-markdown/references/syntax-and-directives.md -
lossless-monorepo/agent-skills/lossless-flavored-markdown/references/triggers-to-component-pipeline
agent-skills/lossless-flavored-markdown/references/triggers-to-component-pipeline.md -
lossless-monorepo/agent-skills/lossless-flavored-markdown/skill
The Lossless Group's extended-markdown flavor — what LFM is, when to use it, how its directives normalize across syntaxes (CommonMark, GFM, Obsidian callouts, remark-directive, Markdoc), how citations and link previews work, and how sites extend it via trigger maps and theme tokens. Use whenever authoring or rendering content in any Astro Knots site, integrating the @lossless-group/lfm package, building or registering custom components for markdown, debugging callouts/embeds/citations, or when the user mentions "LFM", "Lossless Flavored Markdown", "extended markdown", "directive syntax", "wikilink", "trigger map", "callout", or "hex-code citation".
agent-skills/lossless-flavored-markdown/SKILL.md -
lossless-monorepo/agent-skills/maintain-design-md/skill
How to author and maintain a `DESIGN.md` file at the root of any Lossless project (site, splash page, plugin landing, fundraise deck) following Google Stitch's open spec. Use whenever a project is missing a `DESIGN.md` and an agent needs the project's visual identity in machine-readable form; whenever the user mentions "design tokens", "design system", "DESIGN.md", or "Stitch spec"; whenever theme/CSS-token work changes the runtime values (new CSS custom property in `:root`, renamed token, new mode, new component pattern, refreshed palette, refreshed typography scale) and the documented contract has drifted; whenever a sibling skill (`generate-consistent-og-images`, `theme-system`, `astro-knots`) needs to read locked design values; whenever the user says "the agent doesn't know what color we use" or "let's write down the design system." Encodes (1) the Stitch spec's frontmatter token groups (colors, typography, rounded, spacing, components) and the eight prose sections in canonical order, (2) the maintenance triggers — what kinds of code changes should bounce back into the document, (3) the "runtime CSS is source of truth, DESIGN.md is the contract" discipline, (4) the precedent for off-spec extensions like an `imagery:` block, (5) anti-patterns. The skill never sees an API key or makes network calls — it's a pure-document discipline.
agent-skills/maintain-design-md/SKILL.md -
lossless-monorepo/agent-skills/maintain-design-md/templates/design-md-scaffold
★ One paragraph describing the visual identity. Mention the runtime source-of-truth path so future agents know where to read the actual values.
agent-skills/maintain-design-md/templates/design-md-scaffold.md -
lossless-monorepo/agent-skills/maintain-filemap/skill
Use whenever the directory shape of a Lossless pseudomonorepo (or any child repo) changes — a new top-level directory is added, a submodule is mounted or unmounted, a major subsystem is renamed — or on a weekly cadence, or before any release that would land on GitHub, to regenerate the `FILEMAP.md` at each affected repo's root so collaborators see the current shape without cloning. Triggers when the user mentions "filemap", "tree", "directory layout", "repo overview", "what does this repo even contain", "new collaborator joining"; also when the agent itself proposes adding/removing a top-level dir or a submodule, because that's exactly the moment the discipline matters.
agent-skills/maintain-filemap/SKILL.md -
lossless-monorepo/agent-skills/maintain-splash-pages/skill
The Lossless Group's pattern for repo-level splash pages — small Astro sites at <repo>/splash/ that ship to GitHub Pages on push to main, render the repo's changelog/ + context-v/ alongside curated marketing copy, and stay isolated from any package the repo also publishes. Use proactively whenever scaffolding a noteworthy new repo (every "important" repo wants one), when shipping a coherent chunk of work that an external reader would land on, when adding a feature (search, sort, tags row, theme mode) to an existing splash, when converting a legacy apps/<name>/ site to splash/, when troubleshooting a Pages deploy, or when the user mentions "splash", "GitHub Pages", "lossless-group.github.io", "Pagefind on our site", or working under a splash/ directory. Codifies the proven shape across three reference implementations (memopop-site, content-farm/splash, lfm/splash) and the package-isolation discipline that keeps splashes safe to add to repos that also publish to JSR/npm.
agent-skills/maintain-splash-pages/SKILL.md -
lossless-monorepo/agent-skills/open-graph-share-seo-geo/references/llms-txt-implementation
agent-skills/open-graph-share-seo-geo/references/llms-txt-implementation.md -
lossless-monorepo/agent-skills/open-graph-share-seo-geo/references/seo-best-practices
agent-skills/open-graph-share-seo-geo/references/seo-best-practices.md -
lossless-monorepo/agent-skills/open-graph-share-seo-geo/references/sitemap-implementation
agent-skills/open-graph-share-seo-geo/references/sitemap-implementation.md -
lossless-monorepo/agent-skills/open-graph-share-seo-geo/references/unfurler-matrix
agent-skills/open-graph-share-seo-geo/references/unfurler-matrix.md -
lossless-monorepo/agent-skills/open-graph-share-seo-geo/references/user-tools-for-image-generation
agent-skills/open-graph-share-seo-geo/references/user-tools-for-image-generation.md -
lossless-monorepo/agent-skills/open-graph-share-seo-geo/skill
How to make a page unfurl reliably in iMessage, WhatsApp, Slack, Discord, LinkedIn, and X; surface to search engines via sitemap.xml + robots.txt; and stay legible to generative engines (GEO), including the llms.txt standard for LLM corpus ingest. Use when adding or debugging OpenGraph / Twitter Card metadata, picking an OG image format, choosing where to host the image, fixing pages that "won't unfurl", auditing share previews, scaffolding /llms.txt and /llms-full.txt, or adding @astrojs/sitemap + robots.txt to a splash or marketing site. Encodes the JPEG-over-WebP rule, the ImageKit content-negotiation gotcha, the absolute-URL requirement, the og:image:type-must-match-bytes invariant, the cache-busting recipe for forcing a re-unfurl, the prose-in-markdown source-of-truth pattern for llms.txt, and the sitemap filter that keeps non-HTML routes (llms.txt, 404) out of the search-engine index.
agent-skills/open-graph-share-seo-geo/SKILL.md -
lossless-monorepo/agent-skills/overlay-svg-text/skill
How to overlay on-brand SVG text on Lossless OG / share imagery — Hack Bold gradient-filled h1, thin sans eyebrow, Poor Story handwritten note. Use whenever a generated OG image needs title/eyebrow/sub text composited on top before it ships (the empty-region zone from `generate-consistent-og-images` is the canvas this skill paints into), whenever an unfurl preview looks too anonymous without a wordmark or subtitle, whenever a fundraise-deck slide needs a brand-flavored title overlay on a hero image, whenever the user says "overlay text on the OG image", "add a title to the banner", "make the unfurl say something", "drop a wordmark on this", or names this skill directly. Encodes the brand-wide type system (Hack Bold for gradient h1, thin sans for eyebrow, Poor Story for handwritten notes), the per-site gradient-from-DESIGN.md discipline (the brand SVGs are raster-baked references, not editable gradient sources — the editable gradient lives in each project's DESIGN.md), the canonical SVG fill-with-gradient pattern (simpler and more portable than mask/union for this use case), and the sharp-based compositing pipeline that writes JPEG-out for delivery per the open-graph-share-seo-geo skill.
agent-skills/overlay-svg-text/SKILL.md -
lossless-monorepo/agent-skills/prep-images-for-embed/skill
Turn raw screenshots into embeddable, CDN-hosted images with real alt text — rename, resize, strip metadata, stage in a gitignored folder, upload to ImageKit, and emit SEO-correct markdown or HTML. Use whenever the user drops screenshots and wants them in a changelog entry, splash page, spec, or any markdown surface; whenever they say "add these screenshots", "put these images in the changelog", "upload these to the CDN", "make this post image-heavy"; whenever local image references need converting to CDN URLs; or whenever an image is destined for an og:image. Encodes the measured content-negotiation result (upload JPEG, never WebP — the WebP fallback is a PNG up to 3x larger), the alt-text-is-not-optional rule, the per-repo gitignored staging convention, and the naming scheme that makes filenames themselves carry SEO weight.
agent-skills/prep-images-for-embed/SKILL.md -
lossless-monorepo/agent-skills/pseudomonorepos/references/anatomy
agent-skills/pseudomonorepos/references/anatomy.md -
lossless-monorepo/agent-skills/pseudomonorepos/references/branch-alignment
agent-skills/pseudomonorepos/references/branch-alignment.md -
lossless-monorepo/agent-skills/pseudomonorepos/references/content-rollup
agent-skills/pseudomonorepos/references/content-rollup.md -
lossless-monorepo/agent-skills/pseudomonorepos/references/lifecycle-workflow
agent-skills/pseudomonorepos/references/lifecycle-workflow.md -
lossless-monorepo/agent-skills/pseudomonorepos/references/search-first
agent-skills/pseudomonorepos/references/search-first.md -
lossless-monorepo/agent-skills/pseudomonorepos/references/the-tree
agent-skills/pseudomonorepos/references/the-tree.md -
lossless-monorepo/agent-skills/pseudomonorepos/skill
The Lossless Group's coined term and pattern — parent repos that aggregate child repos (often as git submodules) primarily to host a parent-level context-v/. Use whenever working anywhere in lossless-monorepo or its descendants, when starting any new task that might overlap with prior work, when scaffolding a new project, when the user mentions "pseudomonorepo", "submodule", "context-v", or names of the children (ai-labs, astro-knots, content-farm, tidyverse), AND ALWAYS when the user proposes to move/relocate/re-clone/re-nest a repo within the tree (which triggers the HARD STOP three-precondition checklist — local branches synced, remote branches catalogued, gitignored secrets backed up). Encodes the search-first-before-creating behavior, the tree-walking discipline, and the relocation-safety protocol.
agent-skills/pseudomonorepos/SKILL.md -
lossless-monorepo/agent-skills/readme
Overview of the Lossless Skills collection - installation instructions, skill status, and contributing guidelines. Reference only.
agent-skills/README.md -
lossless-monorepo/agent-skills/search-lossless-corpus/skill
Use whenever the user asks a question that prior work might already have answered — "what did we decide about X", "when did we ship X", "why did we choose X over Y", "has this failed before", "where did we put X" — and generally to ground answers in The Lossless Group's own corpus instead of training-data folklore. Encodes the four local Chroma collections (`context-vigilance-corpus`, `lossless-changelog`, `claude-code-sessions`, `claude-code-tool-traces`) reachable via the `chroma` MCP server, the four-step agentic-search loop (decompose → execute → evaluate → synthesize), the citation discipline (source path + timestamp + repo slug for every claim), and the metadata-filter patterns that make queries precise. Triggers on questions about prior decisions, shipped work, past Claude Code sessions, recurring tool failures, or any "did we already…" framing. Does not cover Chroma setup, ingestion pipelines, or maintenance — those are handled by [[chroma-local]] and the [[context-vigilance-kit]] scripts.
agent-skills/search-lossless-corpus/SKILL.md -
lossless-monorepo/agent-skills/slide-target/skill
Load the full working context for ONE DidiDecks slide (deck/variant/slot) so an agent can iterate on it slide-by-slide without re-explaining where things live. The first of the `slide-*` skill family (target → improve → rank → decompose). Use whenever the user wants to work on a specific slide of a DidiDecks/Astro deck — "let's work on slide 2", "fix this card", "/slide-target rural-income v1 02", "go slide by slide", "target the funder-pipeline slide" — or when iterating on a client-site deck under dididecks-ai (reach-edu-hub, chroma-decks, etc.). Assembles the section file, the slides.ts slot, the narrative slot, the rank/audit status, the live URLs, and the design-system tokens for exactly that slide, then scopes all work to it. Composes with deck-iteration-workflow and theme-system.
agent-skills/slide-target/SKILL.md -
lossless-monorepo/agent-skills/splash/design
Design system for the lossless-agent-skills splash. Operator/CLI posture — the splash reads like a `man` page rendered on a high-end terminal. Mono- forward (JetBrains Mono is the headline AND the meta), brutalist hairline cards (no glow, sharp 2-3px radii), blueprint-grid backdrop. Dark ("operator") is the default mode; light ("daylight inspection") and vibrant ("demo") are first-class. Brand spine is terminal-teal + amber + magenta — deliberately diverged from sibling Lossless splashes (memopop's cyan-led, lfm's ink-violet, ai-labs's sodium-led). Tokens mirror the CSS custom properties in `src/styles/theme.css`; that file is the runtime source of truth, this DESIGN.md is the human- and agent-readable contract.
agent-skills/splash/DESIGN.md -
lossless-monorepo/agent-skills/splash/readme
agent-skills/splash/README.md -
lossless-monorepo/agent-skills/splash/src/llms/llms
agent-skills/splash/src/llms/llms.md -
lossless-monorepo/agent-skills/splash/src/llms/llms-full
agent-skills/splash/src/llms/llms-full.md -
lossless-monorepo/agent-skills/splash/src/llms/readme
How the /llms.txt and /llms-full.txt endpoints assemble their output — token vocabulary and edit conventions.
agent-skills/splash/src/llms/README.md -
lossless-monorepo/agent-skills/study-repos-first/skill
The Lossless Group's discipline of pinning a curated collection of upstream repos (a "study") around a domain question *before* designing or coding in that domain. Use when starting work that touches conventions, file formats, schemas, protocols, or any decision where prior art exists; when the user mentions "study", "studies/", "reference collection", "prior art", "pin a submodule", or names of existing studies (open-specs-and-standards, memory-layers-for-agents, data-analytics-specifications-and-standards); when scaffolding a new study, extending one, or deciding whether something belongs in a study vs. a project. Encodes the "read upstream code, don't paraphrase from training data" behavior.
agent-skills/study-repos-first/SKILL.md -
lossless-monorepo/agent-skills/surrealdb-canonical-layer/skill
Verify a SurrealDB-backed canonical layer directly, over the `surrealdb` MCP server, instead of writing a disposable Node script per check. Use whenever the user asks to confirm a batch of writes landed correctly ("did the FreedomFest speakers get tagged right", "do these people have an org relationship", "check that event's rows aren't duplicated"), whenever a new client/event/import needs its data audited for coherence, whenever setting up SurrealMCP for a new project, or when the user mentions "SurrealDB", "canonical layer", "client_access tagging", "affiliation edge", or names this skill directly. Encodes augment-it's live schema (persons/organizations/affiliations/observations/events) as the worked example, the per-table client_access shape (string[] on most tables, singular string on observations — a real inconsistency, not a typo), the flag-don't-fix verification discipline, and the read-only-vs-full-CRUD tradeoff of the official surrealmcp server. Generalizes past augment-it to any project (dididecks-ai, memopop-ai) that adopts the same schemaless-canonical-layer + observations-as-log pattern.
agent-skills/surrealdb-canonical-layer/SKILL.md -
lossless-monorepo/agent-skills/theme-system/references/file-organization
agent-skills/theme-system/references/file-organization.md -
lossless-monorepo/agent-skills/theme-system/references/two-tier-tokens
agent-skills/theme-system/references/two-tier-tokens.md -
lossless-monorepo/agent-skills/theme-system/references/vibrant-mode-implementation
agent-skills/theme-system/references/vibrant-mode-implementation.md -
lossless-monorepo/agent-skills/theme-system/skill
The Lossless Group's theme and mode architecture — two-tier token system, three-mode contract (light/dark/vibrant), theme.css organization, and design system conventions. Use when setting up themes/modes for any Astro Knots site, debugging mode toggles, working with CSS tokens, or when the user mentions "vibrant mode", "two-tier tokens", "theme.css", or design system patterns.
agent-skills/theme-system/SKILL.md
lost-in-public 189 docs
-
Running the Latest and Greatest LLM Locally
Step-by-step guide for installing and configuring local LLMs—including Ollama, LiteLLM, Fabric, and Perplexica—for modern AI workflows and toolchains.
issue-resolution/Running the latest and greatest LLM locally.md -
Enhance Visualizations with Use of Formats
explorations/Enhance-Visualizations-with-Use-of-Formats.md -
lost-in-public/explorations/self-hosting-multi-site-analytics-platforms
explorations/Self-Hosting Multi-Site Analytics Platforms.md -
Update an Older Codebase one Dependency at a time.
refactors/Upgrade-an-Older-Codebase-Dependencies.md -
Aggregating GitHub Statistics
Creating aggregate stats on GitHub commits using the gh CLI and GitHub APIs.
issue-resolution/Aggregating-GitHub-Stats.md -
Refactor Changelog Content By Project
refactors/Refactor-Changelog-Content-By-Project.md -
Maintain an Elegant Markdown and Extended Markdown Render Pipeline
blueprints/Maintain-Lossless-Markdown-and-Extended-Markdown-Render-Pipeline.md -
Integrate a Sources content collection.
Enhance our content through a new collection of sources, including books, people, events, lectures, media, meetings, reports, source extracts, ugc communities, and more.
prompts/render-logic/Introduce-Sources-as-Accessible-Content.md -
Be Creative with this Marketing Copy
Here's some messaging we want some creative thinking around. Expand on the messages and create a UI with good information design.
prompts/workflow/Be-Creative-with-this-Marketing-Copy.md -
Render AST in Debug
Exploration of AST structure at each stage of markdown processing to understand how to handle callouts
explorations/Render-AST-in-Debug.md -
Generate Investment Memo for Portfolio Company
Create investment opportunity briefs that match Hypernova's analytical voice, format, and depth using AI-assisted generation with structured inputs and validation.
prompts/workflow/Generate-Investment-Memo-for-Portfolio-Company.md -
Multi-Agent Orchestration for Investment Memo Generation
An exploration into using AI supervisors and specialized agents to generate high-quality content and documents.
explorations/Multi-Agent-Orchestration-for-Investment-Memo-Generation.md -
Broken YAML Key Replacement Workflow
Documenting a critical workflow bug and its resolution for YAML key replacement in Markdown frontmatter.
issue-resolution/Broken-YAML-Key-Replacement-Workflow.md -
Computing Entry Object Values in Astro
A practical guide to ensuring content collections in Astro have complete and valid entry objects for reliable builds.
issue-resolution/Computing entry object values in Astro.md -
Conditional Console Logging as a Standard Practice
Establishing a DRY, configurable approach to console logging for transparent debugging and maintainability.
issue-resolution/Conditional Console Logging.md -
Rendering AST Through a Thoughtful Transformation Pipeline
Achieving robust component-based markdown rendering by optimizing the AST transformation pipeline, fixing blockquote/callout handling, and leveraging the unified ecosystem for efficiency.
issue-resolution/Rendering-AST.md -
Rolling back in time with BTRFS
issue-resolution/Rolling-back-in-time-with-BTRFS.md -
Fixing Markdown Frontmatter Default Values
Resolving issues with missing frontmatter fields not being populated with template defaults
issue-resolution/Fixing-Markdown-Frontmatter-Default-Values.md -
Fixing MOC Content Filtering Across Multiple Collections
Resolving client reader sidebar issues when Map of Content files reference articles from different content collections with mismatched paths and titles
issue-resolution/MOC-Multi-Collection-Filtering-Fix.md -
Maintain Figma Object Embeds Using Embed Kit
blueprints/Maintain-Figma-Object-Embeds-using-Embed-Kit.md -
Multi-Site Astro Starter Kit Architecture
Exploration of building a comprehensive Astro starter kit optimized for rapid deployment of multiple marketing sites with environment-driven customization
explorations/Multi-Site-Astro-Starter-Kit-Architecture.md -
Maintain an Elegant Open Graph System
A scalable, consistent architecture for Open Graph/Twitter share metadata across multi-site Astro projects.
blueprints/Maintain-an-Elegant-Open-Graph-System.md -
Optimizing Share Functionality Across Content
Search and share are the only scalable organic growth engines. Optimizing some aspects are easy.
issue-resolution/Optimizing-Share-Functionality-Across-Content.md -
Repurpose Functionality from React to Astro
When you've built functionality several times it can feel like a slog to rewrite. Let AI Code Generators do it Step by Step.
prompts/workflow/Repurpose-Functionality-from-React-to-Astro.md -
Conditional Component Rendering in Layout Pipelines
Implement flexible layout component rendering with optional parameter controls for InfoSidebar and TableOfContents suppression
blueprints/Maintain-Conditional-Components-on-Render.md.md -
Maintain a Map of Content Paradigm
Implement MOC directive-driven content capacity management for centralized, markdown-native content curation
blueprints/Maintain-a-Map-of-Content-Paradigm.md -
YAML Frontmatter Corruption Correction
Automated tool for identifying and repairing corrupted YAML frontmatter across the content library
prompts/data-integrity/Isolate-Content-Wide-YAML-Corruptions.md -
Jumbotron Popdown Patterns
Design and implementation patterns for consistent jumbotron popdown menus in the Lossless UI.
blueprints/Jumbotron-Popdown-Patterns.md -
Foundational Workflow In The Terminal And Command Line
explorations/Foundational Workflow in the Terminal and Command Line.md -
Accessing Figma through a Windsurf MCP Server
Interact with Figma Designs while building an application, straight from the IDE
explorations/Accessing Figma through a Windsurf MCP Server.md -
Automating Content Generation With Local LLMs
explorations/Automating Content Generation with Local LLMs.md -
Creating a Custom GPT with OpenAI
explorations/Creating a Custom GPT with OpenAI.md -
Exploring Model Context Protocol SDK
Tinker with the Model Context Protocol SDK created by Anthropic
explorations/Exploring Model Context Protocol SDK.md -
Finding an Email Newsletter API that Supports Multiple Domains
Most email newsletter services boast the deliverability and the large number of emails. But what if you just need to send a limited number of emails but support multiple domains?
explorations/Finding an Email Newsletter API that supports Multiple Domains.md -
Using MCP Servers to Speed-up Astro Development
What kind of MCP Servers actually speed up Astro Development?
explorations/Using-MCP-Servers-to-Speed-up-Astro-Development.md -
Creating A Flavored Syntax Parsed To UI
explorations/Creating a flavored syntax parsed to UI.md -
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.
blueprints/Improvise-a-few-Creative-Component-Variants.md -
Maintain Directives In Extended Markdown Render Pipeline
Directives bring MDX like component rendering using special extended markdown syntax.
blueprints/Maintain-Directives-in-Extended-Markdown-Render-Pipeline.md -
Maintain Embeddable Slides
blueprints/Maintain-Embeddable-Slides.md -
Using Obsidian To Manage Markdown Based Content Collections For Static Site Generation Frameworks
explorations/Using Obsidian to manage Markdown-based Content Collections for Static-Site Generation Frameworks.md -
Using Test Coverage to Constrain AI Code Assistants
explorations/Using-Test-Coverage-to-Constrain-AI.md -
Create Storytelling Patterns through sequences of Markdown Files
Using an ordered list of markdown files, create a UI that tells a story of moving from one file to the next through the series.
prompts/user-interface/Create-Storytelling-Patterns-through-sequences-of-Markdown-Files.md -
Reminder of Specification Template and Guidelines for AI Code Assistants
Guidlines and templates only work if you use them.
reminders/Remind-a-Model-of-Specification-Guidelines.md -
Refactor Reference Lists into Reference Grid
Refactor reference lists into a grid-based component
refactors/Refactor-Reference-Lists-into-Reference-Grid.md -
Nested Scroll and Keyboard Behavior Conflicts in Interactive UI Components
Resolving conflicts between parent and child component event handling when nested interactive elements compete for mouse and keyboard control
issue-resolution/Nested-Scroll-and-Keyboard-Behavior-Conflicts.md -
Creating an Astro Collection from Multiple Directory Paths
Solving the challenge of combining multiple portfolio directories into a single unified collection
issue-resolution/Multi-Path-Portfolio-Collection-Setup.md -
Remark Plugin Implementation Plan for Astro Content
Create a custom remark plugin to enhance markdown processing in Astro with extended syntax features
prompts/render-logic/Remark-Plugin-Implementation.md -
Getting Through CORS
A practical guide to improving cross-origin data rendering and troubleshooting CORS issues in modern web development.
issue-resolution/Getting through CORS.md -
Handling Unexpected API Responses
Robust strategies for normalizing and integrating unpredictable API data into observer pipelines and frontmatter logic.
issue-resolution/Handling Unexpected API Responses.md -
Move functionality and style of Concepts and Vocabulary into specific components
We should use astro components as best we can, and try to keep styles managably within their own components
prompts/code-style/Move-Functionality-and-Style-to-Specific-Components.md -
Fetch Open Graph Data from API
Create a Node.js script to process Markdown files and fetch OpenGraph metadata and screenshots from external APIs
prompts/data-integrity/Fetch-Open-Graph-Data-from-API.md -
Fetch Open Graph Data from API
Create a Node.js script to process Markdown files and fetch OpenGraph metadata and screenshots from external APIs
prompts/data-integrity/Implement-Open-Graph-Data-from-API-Obsidian-Plugin.md -
Add a Site Preview to ToolKit Tool Card
Make your site more useful by adding a site preview using HTML iFrames and OpenGraph.io
prompts/user-interface/Add-a-Site-Preview-to-ToolKit-Tool-Card.md -
Ask a Model API to Perform a Task via API
Guidelines for making API calls to LLM services like Claude, GPT-4, and Groq
prompts/workflow/Ask-a-Model-API-to-perform-a-task-via-API.md -
Ask Generative AI Model to Generate a Style
Generate a custom style object for image requests using a Generative AI model. This prompt is for scripting and API integration workflows.
prompts/workflow/Ask-Generative-AI-model-to-generate-a-Style.md -
Introduce a New Feature to the Observer System
Enhance the observer system by introducing new functionality.
prompts/workflow/Introduce-a-New-Feature-to-Observer-System.md -
Ask a Model API to Perform a Task via API
Guidelines for making API calls to LLM services like Claude, GPT-4, and Groq
prompts/workflow/Write-an-AI-Model-request-Script.md -
Refactor a really long Obsidian Modal file.
Creating modular maintainable code for Obsidian Plugin Modals
refactors/Refactor-Obsidian-Modals.md -
Frontmatter consistency through filesystem observer
Leverage the file system libraries to observe directories for new files, insert frontmatter templates.
prompts/data-integrity/Use-Filesystem-Observer-to-Assert-Frontmatter.md -
Create a Basic Changelog
Guidelines for creating and maintaining a structured changelog
prompts/workflow/Create-a-Basic-Changelog.md -
How to manage gnarly routing with Static Site Generators
Guidlines for how to manage dynamic and static routing with Static Site Generators
reminders/Gnarly-Routing-with-Static-Site-Generators.md -
Maintain an Environment-based Build System
Build across environments, including different deployments, using environment variables and configuration files.
reminders/Maintain-an-Environment-based-Build-System.md -
Repurpose Functionality Found Elsewhere into an Obsidian Plugin
When you've built functionality several times it can feel like a slog to rewrite. Let AI Code Generators do it Step by Step.
prompts/workflow/Repurpose-Functionality-Found-Elsewhere-into-Obsidian-Plugin.md -
Technical Specification - Custom Code Block Rendering in Astro
Enhance markdown rendering with specialized components for custom code languages, ensuring graceful fallbacks and maintainable styling
prompts/render-logic/Handle-Custom-Codeblocks-in-Astro.md -
Implement a Comprehensive Code Block Rendering System in Astro
Brief description of the prompt functionality and purpose
prompts/render-logic/Handle-Custom-Codeblocks-in-Astro-Comprehensive.md -
Create a Canvas UI of our Content and Data Models
Visualize content and data models using JSON Canvas
prompts/user-interface/Create-a-Canvas-UI-of-our-Content-and-Data-Models.md -
Create a Changelog UI
Design and implement a modern, user-friendly changelog interface that handles both code and content changes
prompts/user-interface/Create-a-Changelog-UI.md -
Reintroduce something that worked.
Speed up time to solution by asking an AI Code Assistant to draw from old code.
prompts/workflow/Reintroduce-something-that-Worked.md -
Fire up the Observer
Ready to automate? Learn how to launch the Observer system for seamless citation and frontmatter processing across your content library.
reminders/Fire-up-the-Observer.md -
Integrate citations format and unique Hex into filesystem observer
Leverage Node.js filesystem APIs to monitor content directories, automatically transform citations into unique Hex values and create or update Footnotes section.
prompts/data-integrity/Integrate-Citations-Format-Hex-into-Observer.md -
Fix: Author Metadata Not Rendering on Custom Collection Pages
Resolve incomplete data propagation in a dynamic routing component.
issue-resolution/Fetch-Metadata-while-Rendering.md -
Refactor Plan: Consolidate Callout Processing to Pipeline Architecture
refactors/Extended-Markdown-Rendering-Consolidation.md -
Implement Client-Specific Content Routing in Astro
Create dynamic routes for client-specific content while maintaining existing general content structure
reminders/Maintain-Conditional-Client-Specific-Content-Paths.md -
Implement a specific task described in this Prompt as part of larger specification
Specifications are too large to use as prompts. Prompts are missing the larger context. Resolve the two by using both a Prompt and a Specification.
prompts/workflow/Implement-a-Specific-Task-as-Part-of-Larger-Specification.md -
Maintain Consistent Debugging Conventions
Debugging is a critical part of our development process. We should maintain consistent debugging conventions across all our code.
reminders/Maintain-Consistent-Debugging-Conventions.md -
Create a New Layout for an Existing Content Collection
Use existing logic and content, already working, to create and implement a new layout design.
prompts/user-interface/Create-a-New-Layout-for-Existing-Content-Collection.md -
Integrate a new content collection to our content rendering system.
Enhance our content base with a new collection of content.
prompts/render-logic/Integrate-Collection-into-Site.md -
Ways We Avoid Hard Validation
Prevent build failures and gracefully handle frontmatter inconsistencies.
reminders/Ways-We-Avoid-Hard-Validation.md -
Cursor and Claude 3.7 go Overkill with Regex & Validation
Diagnosing the pitfalls of excessive regex and validation logic in collaborative AI-powered workflows.
issue-resolution/Cursor and Claude 3.7 went overboard on Regex & Validation.md -
Fire up the Observer
Ready to automate? Learn how to launch the Observer system for seamless citation and frontmatter processing across your content library.
prompts/render-logic/Integrate-Collection-into-Observer-System.md -
Grid Layout Centering with Responsive Breakpoints
Solving complex CSS grid layout issues with simplified media queries
issue-resolution/Grid-Layout-Centering-with-Responsive-Breakpoints.md -
Ask Local LLM to be a Copywriter and generate content and metadata.
Use a local LLM to generate content and metadata for Markdown files in a content directory. This prompt is for scripting and content automation workflows.
prompts/workflow/Ask-Local-LLM-to-Be-a-Copywriter.md -
Persistent File Processing State in Observer
Assure the FileSystemObserver has a persistent file processing state, and also resets the state upon initialization and shutdown.
issue-resolution/Persistent-File-Processing-State-in-Observer.md -
Enhanced Filesystem Observer with Prompts and Specifications Support
Extend the filesystem observer to monitor prompts and specifications directories, validating frontmatter against templates and preparing for publication
prompts/data-integrity/Enhanced-Filesystem-Observer-with-Prompts-Support.md -
Comprehensive AST Transformation Pipeline
A robust approach to AST transformations inspired by astro-big-doc and content-structure patterns
prompts/render-logic/Render-Markdown-Deliberately-from-Inspiration.md -
Rendering Extended Markdown through AST
An alternative approach to rendering callouts and citations by working directly with the AST nodes
prompts/render-logic/Rendering-Extended-Markdown-through-AST.md -
Consolidate Multiple Documentation Sources into One Source
Consolidate multiple documentation sources into a single, cohesive source.
prompts/workflow/Consolidate-Multiple-Documentation-Sources-into-One-Source.md -
The Simplified Observer Logic
Clarify and streamline the Observer’s orchestration logic—ensuring every subsystem, expectation, and write operation is perfectly sequenced.
reminders/The-Simplified-Observer-Logic.md -
Use Safe Syntax in Mermaid Charts
Assure your Mermaid Charts render by avoiding unsafe characters and syntax while writing technical documentation
reminders/Use-Safe-Syntax-in-Mermaid-Charts.md -
An Exhaustive list of content YAML patterns.
Never repeat yourself—reference this comprehensive guide to all frontmatter YAML patterns for bulletproof data integrity and automation.
reminders/YAML-Patterns--Exhaustive-Cases.md -
Dynamic Image Masking Control in FeatureSideImage Component
Implementing flexible image masking with configurable dimensions via JSON data
issue-resolution/Dynamic-Image-Masking-Control.md -
Implement a Comprehensive Mermaid Chart Rendering System in Astro
Brief description of the prompt functionality and purpose
prompts/render-logic/Handle-Mermaid-Codeblocks-in-Astro.md -
Extending Astro Markdown with Remark and Rehype Plugins
How to enhance Astro's Markdown pipeline by integrating custom Remark and Rehype plugins for advanced content processing.
issue-resolution/Extend-with-Remark-and-Rehype-Plugins.md -
Getting Astro Collections to Work on Messy Frontmatter
How to configure Astro content collections to handle Markdown files with inconsistent or incomplete frontmatter, using .passthrough and transform for robust schema handling.
issue-resolution/Getting Astro Collections to work on Messy Frontmatter.md -
How Micromark Handles Markdown and the AST
A deep dive into how Micromark tokenizes Markdown and how the AST is built by higher-level utilities in the remark/unified ecosystem.
issue-resolution/How-Micromark-Handles-Markdown-AST.md -
How remark-gfm Renders Tables
A technical deep dive into how the remark-gfm plugin parses, transforms, and renders Markdown tables in the unified ecosystem.
issue-resolution/How-Remark-GFM-renders-Tables.md -
Managing Complex Integrations Through Git
Solutions and essential commands for managing complex Git integrations, especially in monorepos with submodules and loosely-coupled architectures.
issue-resolution/Managing complex integrations through Git.md -
Obsidian Stuck in Regex Memory Hang
Diagnosing and resolving a persistent regex-induced freeze in Obsidian, including hidden file investigation and advanced directory tree commands.
issue-resolution/Obsidian stuck in Regex memory hang.md -
Preventing Infinite Loops in Observers
Strategies and atomic patterns for preventing infinite loops and redundant writes in observers, with robust frontmatter repair and idempotency.
issue-resolution/Preventing Infinite Loops in Observers.md -
Preventing Infinite Loops in RemindersWatcher
Comprehensive breadcrumb and technical guide for debugging and resolving infinite loop issues in the RemindersWatcher observer system, with inspector-only enforcement and atomic property aggregation.
issue-resolution/Preventing-Infinite-Loops-in-RemindersWatcher.md -
ReferenceGrid Layout Issue Resolution (CSS vs Tailwind)
Troubleshooting and resolving the ReferenceGrid component's layout issue—switching from custom CSS/media queries to Tailwind utilities for robust responsive grids.
issue-resolution/ReferenceGrid-Layout-Issue.md -
Setting up Rehype to Better Parse Markdown
Implementing a custom unified pipeline with remark and rehype for Astro Flavored Markdown, solving file reference and plugin integration issues.
issue-resolution/Setting-up-Rehype-to-Better-Parse-Markdown.md -
Showing Hidden Directories in Tree Output
How to configure the `tree` command to display hidden directories and files when visualizing project folder structures.
issue-resolution/Showing Hidden Directories in Tree Output.md -
Tame Generative AI with Rule Sets
Canonical rules and technical conventions for controlling, documenting, and collaborating with code-generating LLMs in complex TypeScript/Astro projects.
issue-resolution/Tame Generative AI with rule sets.md -
Troubleshooting Rendering Citations
Resolving issues with citation rendering in Markdown pipelines—strategies for AST transformation, plugin fallback, and robust user experience in Astro/Remark environments.
issue-resolution/Troubleshooting-Rendering-Citations.md -
Write Git Commit Messages with Your Favorite Editor
How to configure Git to use your preferred editor (like Neovim) for writing multi-line commit messages, plus tips for advanced commit workflows.
issue-resolution/Write git commit messages with your favorite editor..md -
YAML Consistency for Content Collections & Script Actions
Ensuring reliable YAML frontmatter for Astro content collections and script automation—approaches, pitfalls, and tooling support.
issue-resolution/YAML Consistency for Content Collections & Script Actions.md -
Suggest a Non-Destructive Refactor
Provide recommendations for improving code organization and structure while preserving functionality and maintaining existing patterns
prompts/code-style/Merge-Functionality-into-One-File.md -
Suggest a Non-Destructive Refactor
Provide recommendations for improving code organization and structure while preserving functionality and maintaining existing patterns
prompts/code-style/Suggest-a-Non-Destructive-Refactor.md -
Integrate new content thread by creating a template
Use Astro Collections, audit frontmatter, and create template that can be used in Scripts, Observers, and Watchers
prompts/data-integrity/Integrate-New-Content-Thread-by-Creating-Template.md -
Fixing 404 Errors in Dynamic Routes with Proper Slug Generation
Resolving path mismatches between URL construction and getStaticPaths in Astro dynamic routes
issue-resolution/Dynamic-Route-Slug-Generation-404-Fix.md -
Write a Comprehensive Git Squash-Merge
A step-by-step, human-readable workflow for safely squash-merging development into master in a multi-contributor project.
prompts/workflow/Write-a-Comprehensive-Squash-Merge.md -
Change Role and Implement Prompt
Seamlessly switch roles from product manager to developer and implement prompts with context awareness and precision.
reminders/Change-Role-to-Developer-and-Implement-Prompt.md -
Comprehensive Rules to tame Code Generator LLMs
Unlock the secrets to taming LLM code generators with a masterclass in rules, conventions, and practical strategies for bulletproof automation.
reminders/Comprehensive-Rules-for-Code-Generation.md -
Create a permanent memory for project YAML conventions
Eliminate frustration by observing guidelines, working within hard rules and constraints, and learning to detect YAML irregularties that could cause bugs and failures.
reminders/Create-Permanent-Project-Memory-for-YAML-Handling.md -
Extending Markdown with Obsidian FlavoredSyntax
Discover how to supercharge your Markdown with Obsidian's advanced syntax, templates, and automation tricks for next-level note-taking and productivity.
reminders/Extended-Obsidian-Extended-Markdown.md -
Maintain a word-for-word dialog of our session
Capture every word of your human-AI dialog for perfect transparency, reproducibility, and context-aware automation.
reminders/Maintain-a-Session-Log.md -
Maintain Consistent Reporting
Master the art of consistent, auditable reporting for every automation, script, and observer in your content pipeline.
reminders/Maintain-Consistent-Reporting.md -
Maintain Consistent Reporting Templates
Build trust and clarity with consistent, reusable reporting templates that make every audit, fix, and automation step transparent and repeatable.
reminders/Maintain-Consistent-Reporting-Templates.md -
Maintain Robust Commenting in our Flavor
Unlock the power of readable, maintainable code with our signature commenting style—section openers, function docs, and clarity-first annotation for every project.
reminders/Maintain-Robust-Commenting-in-our-Flavor.md -
Maintain a Scripting Pipeline
Design modular pipelines to detect, clean, and report on markdown files—ensuring every content workflow is robust, maintainable, and auditable.
reminders/Maintain-Scripting-Pipeline.md -
Map of Dependencies
Eliminate frustration by observing guidelines, working within hard rules and constraints, and learning to detect YAML irregularities that could cause bugs and failures.
reminders/Map-of-Dependencies.md -
Map of Relevant Paths
Review this file to ensure code generation is using the correct paths and directory structure in this complex monorepo.
reminders/Map-of-Relevant-Paths.md -
Meticulous Constraints for Every Prompt
Master prompt engineering with essential, actionable constraints—ensuring every code generation task is robust, DRY, and error-resilient.
reminders/Meticulous-Constraints-for-Every-Prompt.md -
Read the relevant documentation before guessing.
Illuminate your coding journey by diving into relevant documentation, and transform assumptions into accurate, well-informed decisions.
reminders/Read-Relevant-Documentation-before-major-edits.md -
Remind a model to read documentation sources of included libraries
Give your AI Code Assistant the Aha! moment it needs to get through your blockers by learning directly from documentation sources.
reminders/Remind-a-Model-to-Read-Documentation-Sources.md -
Respect the framework nuances, read the docs
Brief description of the reminder functionality and purpose
reminders/Astro-Specifc-Nuances.md -
Discuss Spec init starter before Developing Spec
Brief description of the reminder functionality and purpose
reminders/Discuss-Spec-Init-before-Developing-Spec.md -
Create a permanent memory for project YAML conventions
Eliminate frustration by observing guidelines, working within hard rules and constraints, and learning to detect YAML irregularties that could cause bugs and failures
prompts/workflow/Help-Write-a-YAML-property-for-a-Directory-of-Files.md -
Manageable User Options
Configure and manage user options for build scripts and content processing
prompts/code-style/Maintain-Manageable-User-Options.md -
Move styles from Tailwind to CSS using our styles
We use Tailwind for speed and compact readability, but as we move to Astro, we should use CSS and try to maintain our CSS architecture
prompts/code-style/Move-Styles-from-Tailwind-to-CSS-using-our-Styles.md -
Streamline Interaction Design in CSS States
Create consistent, maintainable, and extensible patterns for CSS animations and transitions across components
prompts/code-style/Streamline-Interaction-Design-in-CSS-states.md -
Citation Processing for FileSystem Observer
In the tangled web of academic references, a robust citation processing system transforms chaotic footnotes into a harmonized knowledge registry, ensuring every intellectual debt is properly acknowledged and seamlessly tracked.
prompts/data-integrity/Another-attempt-at-Citation-Processing.md -
Known YAML Errors and Fixes Registry
Automated detection and correction system for common YAML frontmatter errors in Markdown content
prompts/data-integrity/Get-Known-Errors-and-Fixes.md -
Pull YAML properties from a diverged content collection, and merge them.
When content libraries diverge, and both libraries have important data and content, write a script that merges the matching files based on most recent or robust frontmatter and content.
prompts/data-integrity/Merge-Matching-Files-to-Add-YAML.md -
Frontmatter consistency through filesystem observer
Leverage Node.js filesystem APIs to monitor content directories, automatically validate and update frontmatter based on templates
prompts/data-integrity/Use-Filesystem-Observer-to-Assert-Frontmatter-Updated.md -
Writing Correction Functions
Create functions to fix known YAML errors in content files
prompts/data-integrity/Writing-Correction-Functions.md -
Our Extended Markdown Requirements as a Micromark Extension
Implement our proprietary extended markdown flavor as a micromark extension—bypassing remark, rehype, and all unified abstractions.
prompts/render-logic/Our-Extended-Markdown-Requirements-as-a-Micromark-Extension.md -
Dynamic Information Page Rendering in Astro
Empower developers to focus on layout and let MDX do the content and interaction
prompts/render-logic/Support-Dynamic-Information-Pages.md -
Create a Dynamic Footer
Design and implement a modern, user-friendly dynamic footer interface that handles both code and content changes
prompts/user-interface/Create-a-Dynamic-Footer.md -
Use Magazine Style Layout for new Specs Collection
Use a magazine-style layout for the new Specs Collection, reusing as many components and render pipeline as possible.
prompts/user-interface/Use-Magazine-Style-Layout-for-new-Specs-Collection.md -
Create a Simple Message Grid
Build a maintainable component pipeline for rendering simple messages dynamically generated from JSON data.
prompts/user-interface/Create-a-Simple-Message-Grid.md -
Create a Simple Question Answers Section
Build a maintainable component pipeline for rendering simple questions and answers dynamically generated from JSON data.
prompts/user-interface/Create-a-Simple-Question-Answers-Section.md -
Report on YAML Idiosyncracies
Write or run a script that iterates through content libraries and reports on YAML idiosyncracies.
prompts/workflow/Report-on-YAML-Idiosyncracies.md -
Frontmatter Date Formatting Fix
Resolving timestamp and quoted date issues in frontmatter
issue-resolution/Frontmatter--Date-formatting-fix.md -
Comprehensive Rules to tame Code Generator LLMs
A comprehensive, click-worthy guide to every YAML property and value syntax nuance you need to master for robust automation and content integrity.
reminders/Exhuastive-List-of-YAML-Properties-and-Value-Syntax.md -
Full-Width Separator Issue Resolution
Solving the challenge of creating truly full-viewport-width separators in a constrained layout
issue-resolution/Full-Width-Separator-Issue-Resolution.md -
Configure Yamllint based on our patterns.
Use a smart library, Yamllint, to audit and fix our YAML frontmatter based on our specified patterns.
prompts/data-integrity/Configure-Yamllint-based-on-our-patterns.md -
Create a Content Registry Script
Build a registry system for tracking and managing Markdown files
prompts/data-integrity/Create-a-Content-Registry-Script.md -
Create or Update Open Graph Data
Build a script to fetch and update Open Graph metadata for content files using a simple build orchestrator
prompts/data-integrity/Create-or-Update-Open-Graph-Data.md -
Fix one YAML Issue at a Time
Create a focused script to identify and fix individual YAML issues in frontmatter without causing cascading problems
prompts/data-integrity/Fix-one-YAML-Issue-at-a-Time.md -
Fix one YAML Issue at a Time
Systematic approach to cleaning URL properties in YAML frontmatter
prompts/data-integrity/Fix-one-YAML-Issue-at-a-Time--alt.md -
Integrate OpenGraph fetch into filesystem observer
Leverage Node.js filesystem APIs to monitor content directories, automatically fetch OpenGraph metadata and update frontmatter
prompts/data-integrity/Integrate-OpenGraph-Fetch-into-Observer.md -
Return only files with valid Frontmatter
Filter and validate markdown files based on frontmatter content
prompts/data-integrity/Return-only-files-with-valid-Frontmatter..md -
Conditional Logic for Content
Implement conditional rendering based on content status and user roles
prompts/render-logic/Conditional-Logic-for-Content.md -
Integrate the Concepts series into the "more-about" routing
Enhance the "more-about" path with Concepts as well as Vocabulary
prompts/render-logic/Convert-Static-Routing-to-Dynamic-Routing-in-Tags.md -
Create a Variant of an Existing Component
The component we have is great, but we need a variant of it.
prompts/render-logic/Create-a-Variant-of-an-Existing-Component.md -
Create Fallbacks, Error, and Waiting Components
Ideal, immediate renders are not always possible. We need to create components that handle these situations gracefully. They should be clever and on-brand.
prompts/render-logic/Create-Fallbacks-Error-Waiting-Components.md -
Handle Citations in Markdown Content
Handle citations in markdown content by extracting them and rendering them in a structured format
prompts/render-logic/Handle-Citations-Logic-and-Render-Citations-Component.md -
Handle iFrames in Markdown Content
Handle iFrames in markdown content by pulling them out before other content processing, then adding them back to the AST before rendering.
prompts/render-logic/Handle-iFrames-with-our-AST-Rendering-Pipeline.md -
Integrate the Concepts series into the "more-about" routing
Enhance the "more-about" path with Concepts as well as Vocabulary
prompts/render-logic/Integrate-Concepts-into-More-About.md -
Rendering Callout Blocks with Classes
Several forms of extended markdown make heavy use of callout blocks, which can be rendered with combinations of Astro Components, Semantic HTML, and CSS classes
prompts/render-logic/Rendering-Callout-Blocks-with-Classes.md -
Rendering Extended Markdown like Astro-Big-Doc
A simplified approach to rendering callout blocks by following astro-big-doc pattern of component-based AST handling
prompts/render-logic/Rendering-Extended-Markdown-like-Astro-Big-Doc.md -
Add Sort by Functionality to Tag Column
Make the tag column more powerful by allowing different kinds of sort patterns
prompts/user-interface/Add-Sort-by-Functionality-to-Tag-Column.md -
Create a Hero Component
Design and implement a modern, user-friendly hero component with gradient effects, responsive design, customizable content, and smooth scroll-based animations.
prompts/user-interface/Create-a-Hero-Component.md -
Create a Price Card
Design and implement a responsive pricing card component with modern styling
prompts/user-interface/Create-a-Price-Card.md -
Create a Reusable Content Collections UI Structure
Build a maintainable component pipeline for rendering content collections with separated structure and presentation
prompts/user-interface/Create-a-Reusable-Content-Collections-UI-Structure.md -
Create a Vocabulary Collection render pipeline
Build a render pipeline for vocabulary using the component pipeline for rendering content collections with separated structure and presentation
prompts/user-interface/Create-a-Vocabulary-Collection-UI-using-Prior-Components.md -
Get UI Inspiration From URL
Analyze and extract design patterns and UI components from external websites for inspiration
prompts/user-interface/Get-UI-Inspiration-From-URL.md -
Render Site Flavored Markdown
Render site flavored Markdown in layers with Marked Extensions
prompts/user-interface/Render-Site-Flavoured-Markdown-in-Layers.md -
Repurpose a UI Template in our Codebase
Adapt and reuse existing UI components and templates for new features
prompts/user-interface/Repurpose-a-UI-Template-in-our-Codebase.md -
Cleaning Build Scripts
Improve build scripts by following strict naming conventions and error handling patterns
prompts/workflow/Build-Scripts-that-Clean-Data.md -
Create a Content Generation Engine
Build a RAG-based content generation system with multi-model API integration
prompts/workflow/Create-a-Content-Generation-Engine.md -
Ask the AI Code Assistant to Improve your Prompts
Takes one to know one. Ask the AI Code Assistant to improve your prompt before you ask it to execute it.
prompts/workflow/Improve-on-a-User-Prompt-through-Iteration.md -
Resolving Local SVG Image Rendering Issues in Astro
Troubleshooting and fixing SVG images not rendering from the public directory
prompts/workflow/SVG-Image-Rendering-Issue-Resolution.md -
Use an LLM Gateway to Augment Content
Create the content of a thousand content marketers with an LLM Gateway -- LiteLLM, Fabric, Ollama, MSTY
prompts/workflow/Use-LLM-Gateway-to-Augment-Content.md -
Write a Code Changelog Entry
Create structured and informative changelog entries for code changes
prompts/workflow/Write-a-Code-Changelog-Entry.md -
Write a Changelog Entry
Create structured and informative changelog entries for code changes
prompts/workflow/Write-a-Content-Changelog-Entry.md -
Write a Git Commit for one Directory
Create structured and informative git commit messages for code changes
prompts/workflow/Write-a-Git-Commit-for-one-Dir.md -
Write a meaningful but concise git commit.
Make Git and GitHub work better for your team by leveraging LLM Code Assistants.
prompts/workflow/Write-a-Raw-Text-Git-Commit.md -
Write a Technical Specification with a Standard but Evolving Style
Create comprehensive technical specifications for completed tasks and features
prompts/workflow/Write-a-Technical-Specification.md -
Write an note that leaves a breadcrumb for future Issue Resolution
Create comprehensive technical specifications for completed tasks and features
prompts/workflow/Write-an-Issue-Resolution-Breadcrumb.md -
Prompt Rendering Pipeline Issue Resolution
Fixing content rendering issues in the dynamic prompt pages
issue-resolution/Prompt-Rendering-Pipeline-Issue.md -
Create A Magazine Style Layout
Design a flexible, reusable magazine-style layout for displaying content threads (e.g., blog posts, articles) in Astro using modular components and a clear render pipeline.
prompts/user-interface/Create-a-Magazine-Style-Layout.md -
Citation Processing for FileSystem Observer
Enhance the filesystem observer to automatically format citations, convert to hex IDs, and maintain a citation registry
prompts/data-integrity/Refactored-Citations-Observer.md -
Keep a Changelog
Standardized approach to maintaining comprehensive changelogs for code and content changes
blueprints/Keep-a-Changelog.md -
AstroMarkdown Mermaid Rendering Issue Resolution
Breadcrumb documenting the resolution of Markdown/AST rendering issues for Mermaid diagrams and code blocks in AstroMarkdown.astro.
issue-resolution/Mermaid-Rendering-tangles-Rehype-Remark.md -
lost-in-public/refactors/ongoing-log-of-opportunities-to-refactor
refactors/Ongoing-Log-of-Opportunities-to-Refactor.md -
lost-in-public/reminders/specification-guidelines-template
reminders/Specification-Guidelines-Template.md
memopop-ai 8 docs
-
Curating Only Valid Sources Across Runs
Downstream curation cannot fix what `citation_enrichment.py` invents upstream — 65 fabricated `example.com` URLs in a single run.
explorations/Curating-only-valid-Sources-across-Runs.md -
Human-Curated Source Sets and Per-Firm RAG for Memo Narrative
Keep Perplexity's take as quarantined commentary and route real research through validated harvesters plus a per-firm standing RAG store.
explorations/Human-Curated-Source-Sets-and-Per-Firm-RAG-for-Memo-Narrative.md -
Separating Retrieval from Generation in Agent Pipelines
An agent that both searches the web and writes the prose fabricates URLs — 65 `example.com` links in a single memo run.
explorations/Separating-Retrieval-from-Generation-in-Agent-Pipelines.md -
Crawl for Better Team Structured Output
The orchestrator writes prose about teams but never returns the structured roster the app needs to render cards: names, titles, photo URLs.
explorations/Crawl-for-Better-Team-Structured-Output.md -
MemoPop AI — Ideogram OG Image Brief
A house-style Ideogram prefix and suffix any scene description plugs into, so splash, changelog, and context-v imagery stay one family.
MemoPop-Creative-Brief.md -
Moving an Agent Orchestrator to an API
The orchestrator is a Python CLI today. To plug it into memopop-native, we need an HTTP-shaped surface. Three options, ranked by effort and time-to-value.
explorations/Moving-an-Agent-Orchestrator-to-an-API.md -
Preferred Format for Changelog
Preferred-Format-for-Changelog.md -
Grill Me: A Per-Section User-Input Moment in MemoPop Runs
A pause-point where MemoPop grills the user — the competitive section's synthesis frame is a judgment the model shouldn't make alone.
explorations/Grill-Me-Per-Section-User-Input-Moment.md
memopop-orchestrator 12 docs
-
Normalize Labels Gradually
One company says Total Revenue, another says Gross Revenue, a third says Top Line. One reports monthly, another quarterly, another H1/H2, another only annually. Collection never touches any of it. Normalization is a later, corpus-level act — a cluster of labels that mean the same thing, one chosen default, and an alias map — built by a person from real analysis across real portfolios, never by an agent guessing from what the words sound like.
reminders/Normalize-Labels-Gradually.md -
Round-Closing Timeline Nuances
Wires arrive before and after the close they belong to, rounds close later than anyone planned, and a fund and its SPV subscribe months apart on identical terms. None of that is an anomaly. Record every date as the document states it, never revise one to make a sequence tidy, and confine anomaly-noticing to the handful of series that are actually real at this stage — money spent, web traffic, signed contracts, billed subscription revenue. Everything else is a claim or a projection, and instinctive concerns about it belong in anomalies.json rather than in the memo or the conversation.
reminders/Round-Closing-Timeline-Nuances.md -
Long-Running Is Not a Reason to Fan Out
Duration is not the variable that decides whether work should be split across agents. Continuity is. Ask before parallelizing anything whose quality depends on what came before it.
reminders/Long-Running-Is-Not-A-Reason-To-Fan-Out.md -
Reconciling Perplexity Citations Against Retrieved Sources
Sonar hands us the sources it actually retrieved on every call, and we throw them away — so every URL in every memo is a guess.
plans/Reconciling-Perplexity-Citations-Against-Retrieved-Sources.md -
Research Agent Concatenates Multiple Sources Under One Citation ID — And No Validator Catches It
`research_enhanced.py` writes several sources onto one `[^N]:` line, so downstream parsers keep the first and silently drop the rest.
issue-resolution/Research-Agent-Concatenates-Multiple-Sources-Under-One-Citation-ID.md -
Section Citations Orphaned When Definitions Live in 1-research/
`consolidate_citations.py` reads `### Citations` only inside section files, so defs living in `1-research/` become orphans.
issue-resolution/Section-Citations-Orphaned-When-Defs-Live-In-1-Research.md -
Migrate `studies/open-specs-and-standards/` into its own pseudo-monorepo
plans/Migrating-Study-to-its-own-Pseudomonrepo.md -
Introducing a Content Density Mode System
A system-level content mode toggle (redundant vs concise) that alters the behavior of the writer, table generator, and quality agents to match different firm preferences for information density and repetition.
Introducing-a-Content-Density-Mode-System.md -
Introducing a Diagram Generator Agent
Add a diagram_generator.py agent that identifies opportunities to create visual diagrams explaining complex business concepts, starting with TAM/SAM/SOM market sizing and expanding to common finance and consulting visuals.
specs/Introducing-a-Diagram-Generator-Agent.md -
PDF Parser Agent Specification
A small specification for an agent and script to parse PDFs and convert them to markdown with properly formatted citations.
specs/Introducing-a-PDF-Parser-Agent.md -
Portfolio Listing Agent and Current Portfolio Section
Design notes for the portfolio_listing_agent that builds a Current Portfolio subsection and structured JSON for LP-commit emerging manager fund memos.
Portfolio-Listing-Agent-and-Current-Portfolio-Section.md -
memopop-orchestrator/agent-skills/setup-new-firm/skill
End-to-end procedure for onboarding a new VC firm into the memopop investment-memo orchestrator. Five phases — (1) brand acquisition via Firecrawl with analyst-override on the primary-color heuristic, (2) firm-directory scaffolding under io/<firm>/ with the canonical configs/templates/assets/deals layout and the strict brand-config YAML schema, (3) investment-framework outline selection (typically forking an existing outline like alpha-partners-7-Cs and customizing — section reordering, preambles, preferred-source swaps, stage-aware fallbacks), (4) first deal setup with deck-input handling (DocSend capture via cli/capture_docsend.py, ImageMagick screenshot stitching for NDA-gated decks, deal-config JSON, codified Sources.md), and (5) optional private-repo split via gh CLI with submodule re-add for confidential firm data. Use whenever the user says "I have a new client/firm/VC," "set up <firm name>," "add <firm> to memopop," "we need brand configs for <firm>," or pastes a VC firm's URL with implicit intent to generate memos for them. Encodes lessons from the alpha-jwc onboarding on 2026-06-07 — don't trust Firecrawl's primary-color field blindly, verify against the logo palette; the deck analyst will extract DocSend watermarks as the company name if you feed it watermarked screenshots; agents leak firm-geography context into company-analysis prose (Alpha JWC = Indonesia VC → Portland-OR company memo gained Indonesia/rupiah risks); citation-enrichment fabricates example.com URLs even in codified-source mode — codified Sources.md only constrains the upstream researcher, not the downstream enricher. Cross-references [[crawl-fetch-ingest]] for portfolio/team data, [[sources-md-curation]] for the Sources.md file mechanics, and the open issues in context-v/issue-resolution/ ([[Limiting-or-Omitting-Investor-Judgement]], [[Competitive-Research-Generated-But-Not-In-Prose]], [[Including-Comparable-Exits-Valuations-IPOs]]) for known failure modes the new firm's first run will hit.
agent-skills/setup-new-firm/SKILL.md
memory-layers-for-agents 18 docs
-
paxm
Paxm is not a memory store — it is routing and durability in front of seven-plus pluggable backends, and it does zero semantic dedup.
profiles/Profile__Paxm.md -
understand-anything
When an LLM authors your graph, the schema layer stops being a validator and becomes a repair shop — alias maps fold synonyms back.
profiles/Profile__Understand-Anything.md -
beads
Not one embedding anywhere in the recall path — retrieval is a SQL view and a graph walk over the agent's own work graph.
profiles/Profile__Beads.md -
byterover
The memory store is a directory of Markdown you can cat, grep, and diff, with its own git history. Recall is BM25, not embeddings.
profiles/Profile__ByteRover.md -
hindsight
`fact_type` is a database CHECK constraint: world facts and first-person experiences travel through different extraction prompts.
profiles/Profile__Hindsight.md -
honcho
Collections are unique on (observer, observed, workspace) — Honcho indexes memory by relationship rather than by user.
profiles/Profile__Honcho.md -
openviking
Memories, resources, and skills collapse into one `viking://` tree, and retrieval is a recursive directory walk, not a vector query.
profiles/Profile__OpenViking.md -
retaindb
Supersession as an actual indexed column — `validUntil`, `supersededBy` — rather than something the ranker is hoped to handle.
profiles/Profile__RetainDB.md -
supermemory
The most polished client surface in the study, wrapped around an engine that is not in the repo — every SDK points at a hosted API.
profiles/Profile__Supermemory.md -
graphify
The whole memory layer is one in-process NetworkX graph and a `graph.json` you can copy around — no database anywhere.
profiles/Profile__Graphify.md -
delta-mem
Memory as a dense rank-8 state matrix inside each attention head, updated token by token — the model never looks anything up.
profiles/Profile__Delta-Mem.md -
graphiti
`expired_at` is when the engine retired a fact; `invalid_at` is when it stopped being true in the world. Routinely different dates.
profiles/Profile__Graphiti.md -
letta
The one entry where the agent itself — not an extraction pipeline, not a background summarizer — is the memory manager.
profiles/Profile__Letta.md -
mem0
Despite the graph-memory marketing, the graph is an array of linked memory IDs hanging off spaCy-extracted entities.
profiles/Profile__Mem0.md -
mempalace
The counter-bet: extract nothing. Raw 800-character chunks score 96.6% R@5 on LongMemEval at zero LLM calls.
profiles/Profile__MemPalace.md -
neo
Familiar high-confidence queries get dialled down to low reasoning effort — memory shows up as a smaller bill, not better accuracy.
profiles/Profile__Neo.md -
statebench
The trade nobody advertises: more context raises decision accuracy and superseded-fact resurrection together.
profiles/Profile__StateBench.md -
volt
Numeric thresholds decide when to compact, and the model is only ever asked to write summaries. Long-horizon coding as a DB problem.
profiles/Profile__Volt.md
mpstaton-site 1 doc
open-specs-and-standards 13 docs
-
superpowers
A SessionStart hook injects the bootstrap skill as `<EXTREMELY_IMPORTANT>` before the agent has written its first word.
profiles/Profile__Superpowers.md -
openui
JSON spends ~30% of its bytes on punctuation an LLM has no reason to emit; the same seven UIs cost 47–67% fewer tokens in OpenUI Lang.
profiles/Profile__OpenUI.md -
12-factor-agents
Nothing to install — thirteen essays whose answer to "who owns the prompts, the context, the state, the control flow?" is always *you*.
profiles/Profile__12-Factor-Agents.md -
agent-2-agent
The load-bearing commitment isn't the JSON-RPC — it's *opacity*. An A2A agent publishes skills, never its prompts, memory, or tools.
profiles/Profile__Agent-2-Agent.md -
agents-md
The entire specification is one precedence rule: the closest `AGENTS.md` to the edited file wins. No schema, no validator.
profiles/Profile__AGENTS-md.md -
get-shit-done
GSD's wager is that the limiting factor is context rot, not spec rigor — so it ships no spec grammar and resets the window per task.
profiles/Profile__GSD.md -
llms-txt
The only behavioral semantic in the whole format is an H2 named `## Optional` — links there may be dropped when context is tight.
profiles/Profile__llms-txt.md -
mcp-api
However many APIs a user registers, the model only ever sees two tools: `ListAvailableApis` and `CallApi`.
profiles/Profile__MCP-API.md -
modelcontextprotocol
The three *client* primitives — Sampling, Roots, Elicitation — let a server use the host's model without ever getting the user's key.
profiles/Profile__Model-Context-Protocol.md -
symphony
OpenAI shipped the spec, not the product: 2169 lines of RFC 2119 with sections *deliberately made redundant* for coding agents.
profiles/Profile__Symphony.md -
frictionless-specs
This one specs *datasets*: every RFC 2119 "MUST" in the prose maps onto a constraint in a published JSON-Schema profile.
profiles/Profile__Frictionless-Specs.md -
open-spec
An LLM should never re-emit a whole spec to change one line, so changes ship as `ADDED` / `MODIFIED` / `REMOVED` deltas.
profiles/Profile__OpenSpec.md -
spec-kit
No plan gets past the Simplicity, Anti-Abstraction, and Integration-First gates without a written, paper-trailed exception.
profiles/Profile__Spec-Kit.md
perplexed 8 docs
-
Multi-Stage Cooperative Claude + Perplexity with RAG
What if a market-map draft were the output of three agents — a RAG pre-flight that names what to include, a Perplexity research run that finds the rest, and a Claude editorial pass that never steps on either — instead of one single-shot prompt?
explorations/Multi-Stage-Cooperative-Claude-and-Perplexity-with-RAG.md -
Wall-clock timeout cuts off long deep-research streams
The directory-template runtime caps every stream by wall clock, so a 7,500-word deep-research draft terminated mid-sentence.
issues/Wall-Clock-Timeout-Cuts-Off-Long-Deep-Research-Streams.md -
Partials and preambles for perplexed templates
Mermaid rules sit in all four templates and three directives are hardcoded in TS — pull both into vault-visible partials and preambles.
issues/Partials-And-Preambles-For-Perplexed-Templates.md -
This Is an Obsidian Plugin — Read the Obsidian API Docs
The Obsidian API is the source of truth: `any`, innerHTML, and var are all outright bans, and Electron breaks browser muscle memory.
reminders/This-is-an-Obsidian-plugin-Read-Obsidian-API-Docs.md -
Getting Claude to Respond with Research
Claude returns 60 URLs but zero per-claim citations — web_search_20260209's dynamic filter loses the attachment, so no inline markers.
issues/Getting-Claude-to-Respond-With-Research.md -
Plan — Bring Perplexed up to Obsidian Community-Plugin Publishing Standards
25 explicit-any sites plus the four-part 0.0.0.1 version the bot rejects as non-semver, a missing LICENSE, and three unused runtime deps.
plans/20206-05-02_Assuring-Obsidian-Community-Plugin-Requirements.md -
Plan — Submission Blockers Punch List (from docs.obsidian.md re-read)
Six docs-derived blockers — doubled command IDs, a description starting with A plugin for Obsidian, and no network-use disclosure.
plans/2026-05-02_Submission-Blockers-Punch-List.md -
Using Files as Prompt Outlines
Prompt outlines become ordinary vault markdown, so adding one is dropping a file — and ArticleGeneratorModal stops being special-cased.
specs/Using-Files-as-Prompt-Outlines.md
plunk-it 1 doc
reach-edu-hub 31 docs
-
Citation Registry for reach-edu-hub Narratives
One hex code per unique article, held once per client. Narratives cite [^abc123] inline; definitions resolve from here. Codes are minted once and never renumbered — reorder, split, or scramble content freely without breaking claim–source pairing.
narratives/citations/README.md -
Pitch Narrative — Agent Workflow Maxxing: Operate Like a Team Five Times Your Size
The internal pitch arc for the agent-workflow-maxxing strategy: the same catchy-line-plus-cited-numbers pattern as the funder decks, aimed at Reach/Lossless leadership. The case: a $25M campaign with an August 2026 anchor deadline and a funding landscape full of dated windows is exactly the workload a small team cannot cover manually — and agents are how it gets covered without abdicating judgment.
narratives/strategies/agent-workflow-maxxing/pitch.md -
Agent Workflow Maxxing
A small team has the surface area of a big one — sales conversations, travel, conferences, grant pipelines, stakeholder relationships — and historically had to triage most of it away. Dedicated agents and agent workflows change the math twice over: they reduce overwhelm on the work you already do, and they make possible work that simply wasn't (outreach nine months ahead, ten sales conversations at once, a grant corpus that drafts itself). This is the operating strategy — where to point agents first across travel, events, grants, ABM, and social — with examples, tools (paid + open source), and the human-in-the-loop guardrails that keep it from backfiring.
narratives/strategies/agent-workflow-maxxing/README.md -
Pitch Narrative — NCAD Forge: Charter the Lab
The pitch arc for the agentic product lab (corpus slug ncad-forge): the Apprenticeship Degree runs on a technology stack nobody built, the people who understand it can now prototype it themselves, and the AI-in-education funding wave of 2025–26 is looking for exactly this kind of shared infrastructure. What's next, with your gift: a chartered, shared lab at NCAD — domain experts prototyping, engineers hardening, the whole member network compounding.
narratives/strategies/agentic-product-lab/pitch.md -
NCAD Agentic Product Development Lab
Apprenticeship Degrees need a different technology stack than traditional or even online universities — one that integrates work and learning, gives employers visibility, and delivers chunked, assessable learning to busy working adults while still meeting credit-bearing accreditation. Historically that stack could only be built by expensive software-engineering teams. As of 2026, agentic 'vibe coding' tools let designers and domain experts prototype working software themselves. So the people closest to the problem — apprenticeship, industry-skills, and adult-education experts across NCAD's member network — can now prototype and build momentum on new pieces of that stack. This is the proposal to stand up that capability as a shared lab.
narratives/strategies/agentic-product-lab/README.md -
Pitch Narrative — Frontier Job Demand: The Job Is the Curriculum
The funder/employer-facing pitch arc for the frontier-job-demand strategy: course catalogs are lagging indicators, and the fields with the most unmet demand — advanced manufacturing, drones, applied AI — move faster than any curriculum committee. What's next, with your gift: the first apprenticeship degrees designed backward from frontier jobs, launched with the employers who are desperate for the talent.
narratives/strategies/frontier-job-demand/pitch.md -
Opinionated Program Design: Frontier Job Demand
Don't build apprenticeship-degree programs from a generic course catalog — design them opinionatedly toward where job demand is actually going. Three frontier fields have the rare combination of huge unmet demand, strong employer pull, and work that's perfect for a work-embedded degree: Advanced Manufacturing Operations, Drone Sciences, and AI Technology in Business Operations. The Apprenticeship Degree is uniquely suited to fast-moving fields where the job itself is the curriculum — and the outcomes (employment, wages) are already proven.
narratives/strategies/frontier-job-demand/README.md -
Pitch Narrative — Foundational Capabilities, Measured Improvements
The funder-facing pitch arc for the literacy-numeracy strategy: the labor market pays for the skill, not the diploma — and most working adults are below the line on exactly the skills that pay. K-12 already proved what works and how to measure it; postsecondary never tried, because the degree assumes. What's next, with your gift: foundational-skills instruction woven into work and sized for the moments working adults actually have, measured continuously by audio-based AI — the first university delivering measured improvements in foundational capabilities, shared onward through NCAD, and compounding into the next generation.
narratives/strategies/literacy-numeracy/pitch.md -
Improving Literacy & Numeracy in Working Adults
Literacy and numeracy independently predict wages and promotions — even controlling for degrees, experience, and demographics. Yet most working adults sit below proficiency, and a credential can be earned without the underlying basics improving. This strategy folds validated foundational-skills pedagogy (the science of reading, now reaching adult education, plus contextualized/embedded numeracy) into the Apprenticeship Degree, and *measures* the gain — so the degree doesn't just certify, it durably lifts the capability that the labor market actually pays for.
narratives/strategies/literacy-numeracy/README.md -
Pitch Narrative — Reverse Engineer Available Funding: Fish Where the Whales Are
The internal pitch arc for the reverse-engineer-funding strategy: funding is a power law, the campaign's own anchors prove the method, and the mega-gifts research just handed the team a reverse-engineered map of every whale in Reach's waters. What's next: point the team's scarce hours at capacity × alignment, and size every ask to the largest amount that fits the funder's pattern.
narratives/strategies/reverse-engineer-funding/pitch.md -
Reverse Engineer Available Funding
Grant funding follows a power law: a small number of mega-foundations move most of the dollars, and a fast-growing population of ultra-wealthy individuals — especially 'new money' — hold enormous discretionary giving capacity. So don't spray small applications across a long tail. Concentrate where the money is: study the biggest, most-aligned funders' public footprint, get an intro call to learn their actual strategy, pattern-match across their giving, and design the ask to hit the sweet spot for the largest plausible amount.
narratives/strategies/reverse-engineer-funding/README.md -
Pitch Narrative — Rural Income Boosts: The Raise That Stays
The funder-facing pitch arc for the rural-income strategy: rural America's bind is a loop — shortages, low incomes, brain drain — and the Apprenticeship Degree breaks it at the hinge point of income, in place. Arkansas already proved it with a ~2.4 effect size. What's next, with your gift: the Delta expansion at the exact moment Walton re-aimed its home-region strategy at the same map.
narratives/strategies/rural-income/pitch.md -
Rural Income Boosts through Apprenticeship Degrees
A strategic narrative: the Apprenticeship Degree is not only a teacher-pipeline fix — it is a rural economic-development engine. Because it starts with a paid job and ends with a better one, debt-free and work-embedded, it raises individual incomes in place, keeps talent (and its wages) local instead of exporting it, and compounds into a local-economy multiplier — exactly what rural communities facing workforce shortages and out-migration need.
narratives/strategies/rural-income/README.md -
Pitch Narrative — Upward Mobility: The Mobility Engine
The funder-facing pitch arc for the upward-mobility strategy: what's next, what could be — with your philanthropic gift. Builds on the CEO's June 2026 campaign deck ('what is') and extends it with the mobility evidence base and the funding-flows landscape. Catchy line per beat, KPIs underneath, every number cited by hex code.
narratives/strategies/upward-mobility/pitch.md -
Upward Mobility: The Apprenticeship Degree as a Mobility Engine
A strategic narrative: follow one person's trajectory, not a system or a region. For a first-generation working adult, the traditional mobility engine — go away to college — now carries debt risk, income disruption, and dropout risk that fall hardest on exactly the people who need the climb most. The Apprenticeship Degree re-engineers the engine: climb while working, without borrowing, without leaving. The evidence says the postsecondary degree is the single strongest predictor of lasting job quality, and philanthropy's biggest new pools — NextLadder, Blue Meridian, MacKenzie Scott's giving — are all organized around exactly this outcome: economic mobility.
narratives/strategies/upward-mobility/README.md -
Pitch Narrative — Workforce Development: Stop Training and Praying
The funder-facing pitch arc for the workforce-development strategy: the system trains and prays; the evidence says exactly what works; the Apprenticeship Degree is the only model that stacks every proven design feature — and the corporate-philanthropy wave of 2026 is funding everything around it except the degree itself. What's next, with your gift: the degree-bearing backbone of American workforce development.
narratives/strategies/workforce-development/pitch.md -
Workforce Development: The System Is Broken. The Model Is Here.
The U.S. workforce development system was built around employer demand, not worker mobility — producing credentials without career ladders, training without guaranteed outcomes, and a 'train and pray' model that leaves millions sidelined. The evidence is now clear on what actually works: work-based learning with adult relationships produces job quality gains that persist a decade. The Apprenticeship Degree is the only model that stacks all the evidence-based design features at once — earn-while-learn, employer co-design, post-secondary credential, and measured outcomes — at the exact moment federal policy aligned behind scaling it.
narratives/strategies/workforce-development/README.md -
Fundraising Story 01 — The Apprenticeship Degree Is a New Category
Reach didn't build a better program; it built a new category of higher education — the work-embedded, debt-free, employer-paid degree — and the field's biggest funders are converging on the idea right as Reach has the only proven national instance of it. Fund the category-definer.
narratives/pre-rag-synthesis/01-the-apprenticeship-degree-is-a-new-category.md -
Fundraising Story 02 — Teaching Already Proved It
Reach's apprenticeship degree isn't a pilot hoping to work; it already solved the teacher-shortage problem at scale — 420+ K-12 systems across 8+ states, debt-free, paid-while-you-learn. For education funders this is the rare 'fund the proven thing's next chapter' story.
narratives/pre-rag-synthesis/02-teaching-already-proved-it.md -
Fundraising Story 03 — The Care-Economy Workforce Emergency
Behavioral health and healthcare have an acute, quantified workforce shortage and a talent pool 'hidden in plain sight' — incumbent care workers who can't reach licensure. Reach's Apprenticeship College of Health turns those jobs into degrees. This is the corpus's hottest, best-funded, most urgent story.
narratives/pre-rag-synthesis/03-the-care-economy-workforce-emergency.md -
Fundraising Story 04 — Economic Mobility Without the Debt
Nearly every funder in the corpus shares one north star: economic mobility. Reach's distinct claim is that it delivers measurable earnings gains in the learner's own community with zero debt — arguably the highest-ROI mobility intervention a funder can buy. This is the macro story that unifies the portfolio.
narratives/pre-rag-synthesis/04-economic-mobility-without-the-debt.md -
Fundraising Story 05 — Workers, Not Employers: Fixing the Broken Talent Marketplace
The talent marketplace is broken — millions of open jobs, millions of underemployed degree-holders, and employers who can't retain. Reach flips the model: it credentials the workers an employer already has, so talent development becomes retention. This story speaks to the workforce-development and skills-based-hiring funders.
narratives/pre-rag-synthesis/05-workers-not-employers.md -
Fundraising Story 06 — Talent Hidden in Plain Sight: Place-Based & Rural Pipelines
Reach's degrees don't require leaving town — learners earn them in their home communities, in the jobs they already hold. That makes Reach the natural vehicle for place-based and rural funders who want talent to stay and strengthen the local economy. This is the geographic cut across the portfolio.
narratives/pre-rag-synthesis/06-place-based-and-rural-pipelines.md -
Fundraising Story 07 — The AI-Era Learning Institution
AI is reshaping the job pyramid into a diamond — hollowing out entry rungs and raising the bar for the rest. The durable answer isn't more front-loaded college; it's continuous, work-embedded learning. Reach is structurally the institution built for that world. This is the leading-edge, forward-looking story — and the one that ties Reach to Lossless's own AI work.
narratives/pre-rag-synthesis/07-the-ai-era-learning-institution.md -
Pre-RAG Fundraising-Story Synthesis for Reach University — index, method, and how this changes once RAG/KAG lands
Seven recurrent themes pulled by hand from the reach-edu funder corpus (539 files across 57 funders), each framed as a fundraising story with its aligned funder cluster and cited proof points. This is the starter the operator asked for while proper retrieval (remote filesystem + SurrealDB vector/graph) is still a few days out — and an honest note on what synthesis looks like now vs. once RAG/KAG is real.
narratives/pre-rag-synthesis/README.md -
Pipeline Building & Automation — Scroll-Deck Outline
What Lossless will boot up for Reach next. Boost-and-relief for the current fundraise team, then widening the aperture to new donors, new grants, and a map of the philanthropic landscape.
narratives/pipeline-building-automation.md -
Reach Education Hub — `/` Index Page Brainstorm
Working doc on what the hub homepage communicates, who it serves, and the order of the scroll. Brainstorm, not a spec.
sitemap/Page__Index.md -
Deck Collections — a menu/aggregation layer above single-deck convergence
Everything dididecks has built so far (calmstorm, chroma) operates inside ONE deck: converging on a single narrative through variants and versions. reach-edu-hub needs the layer above that — a curated menu of several DISTINCT decks, each its own narrative (a 'strategy'). This doc names that layer 'deck collections', fixes the conceptual model (a collection groups peer decks; a variant is an alternate design of the same deck — different axis entirely), specifies the near-term reach instantiation (a Strategies collection of ~5, possibly more, decks), codifies the per-deck authoring loop (LLM-authored narrative markdown → Claude designs the deck Scroll-UI-first → register → drop into the existing dididecks variant/version workflow only if needed), and proposes how the concept graduates into the shared @dididecks/shell so it's reusable across client-sites.
explorations/Deck-Collections-A-Menu-Layer-Above-Single-Deck-Convergence.md -
Exporting the Strategy Decks to Google Slides
The seven strategy decks live as code — Astro Scroll-UI sections, not slides in any format Google Slides understands. Getting them into Slides for a stakeholder who wants to open, present, or lightly edit them in the tool she already knows is a real pipeline question, not a five-minute export. This names the actual path: what format has to exist first, what's proven prior art from calmstorm-decks, and what reach-edu-hub is missing today to make it clean.
explorations/Exporting-Strategy-Decks-to-Google-Slides.md -
Codify the deck design system & component library — author DESIGN.md, showcase it on /design-system, and refactor every kept element onto theme/mode tokens
Building six strategy decks produced a real, reusable design system — deck-primitives.css (a 15-class component vocabulary) plus a set of recurring section compositions (cover, stat slide, field template, two-column contrast, numbered flow, accent callout, tier cards, ask/close). None of it is documented or shown on /design-system, and there is no DESIGN.md. This plan codifies the system: author a DESIGN.md per the maintain-design-md (Google Stitch) spec, add the deck primitives + patterns to the /design-system page, and — the gating discipline — promote an element into the documented system ONLY once it reads the Tier-2 semantic + --fx-* tokens and works in light/dark/vibrant with no hardcoded colors. That last bar is what 'requires refactoring': the strategy decks are already token-driven, but the older story/automation/homepage sections hardcode dark:/vibrant: triples and must be reconciled (or explicitly excluded) for one coherent system.
plans/Codify-Deck-Design-System-and-Component-Library.md -
16:9 Export Variant (Play-UI) and the PPT/PDF Pipeline
Plan for the fixed-aspect, no-scroll, no-animation variant of each strategy pitch deck — the Play-UI conversion per the DidiDecks discipline — plus a native-shapes PPT exporter tuned for clean Google Slides import, and PDF via the shell's print route. Written 2026-07-28 while building the Scroll-UI decks, so the conversion is anticipated, not retrofitted.
plans/Sixteen-Nine-Export-Variant-and-PPT-Pipeline.md
self-host-stack 26 docs
-
Watchlist — Interesting Tools Not Yet Sorted
A running catch-all for tools worth a second look, before we know whether they map to a self-host-stack category, a personal-workstation list, or nothing at all.
explorations/Watchlist-Interesting-Tools.md -
Aggregating Historical Calendar Items for Lossless Twenty
Started as 'should we deploy cal.diy' and ended somewhere else entirely — cal.diy deletes the past by design, Twenty's importer already backfills everything, and the thing actually worth building is a one-time ICS backfill that never touches OAuth.
explorations/Aggregate-Historical-Calendar-Items-for-Lossless-Twenty.md -
Creating a Railway service fires a build before you can configure it
The build that starts the instant a service is created runs with no domain, no variables, and the Dockerfile's ARG defaults. Read anything from it and you will draw the wrong conclusion about what Railway does and does not pass to a build.
reminders/Creating-a-Railway-Service-Fires-a-Build-Before-You-Configure-It.md -
Homebase MCP — one connector per client, every tool behind it
A client adds one address to Claude and their agent can move across CRM, wiki, data room, and post planner in a single task — because one plane fronts them all, authenticates them through didi.sh, holds the credentials, and serves our skills as both prompts and resources.
specs/Homebase-MCP-One-Connector-Per-Client.md -
Do we need a sandbox behind homebase?
Homebase federates tools but stores nothing and runs nothing. The missing piece turns out to be two pieces — storage, which is already funded, and compute, which can wait.
explorations/Do-We-Need-a-Sandbox-Behind-Homebase.md -
Replacing Granola with an Open-Source Transcription Stack
Transcription is solved and free. Knowing who was speaking is neither — and it's the half that makes a meeting-notes product feel good.
explorations/Exploring-Diarization-Voice-Transcription-w-OpenSource.md -
Postiz is the heaviest thing we run
Postiz and its dependencies account for more than half the memory in the client projects that have it — and memory is 93% of the Railway bill. Nobody is visibly getting value back.
issues/Postiz-Is-The-Heaviest-Thing-We-Run.md -
Normalize Paths Everywhere — one URL shape for every client + service
Today every tool lives at a raw Railway hostname; the goal is one owned, legible shape — lossless.at/<client>/<service>/… — for humans and agents alike.
issues/Normalize-Paths-Everywhere.md -
Which domain hosts what — lossless.at vs didi.sh
Client-facing apps have landed on both domains by accident of chronology, not decision. Nothing is broken; the next deploy will guess, and guess differently than the last one.
issues/Which-Domain-Hosts-What-lossless-at-vs-didi-sh.md -
railway config pull does not pin database images — read the plan
A pulled Railway IaC config re-declares every postgres() and redis() at the helper's default version. Applying it unchanged proposes a major-version upgrade on live databases.
reminders/Railway-IaC-Pull-Does-Not-Pin-Database-Images.md -
lossless.at path-based homebases + /<client>/<service>/api gateway
decisions/lossless-at-path-based-homebase.md -
Per-Client Self-Host Stacks, Twenty-First, on Railway
One playbook, three tiers: managed client stacks on Railway, a hub page clients actually use, and a per-client remote MCP server that could grow into a full context plane.
explorations/Per-Client-Self-Host-Stacks-Twenty-First-on-Railway.md -
Per-Client Stack Deployment — Twenty First (reach-edu, then palmer-ai)
Stand up Twenty CRM for reach-edu, then palmer-ai, on Railway project-per-client — phase by phase, with a verification gate at every step.
specs/Per-Client-Stack-Deployment-Spec-Twenty-First.md -
Should Hermes Agent Co-Locate on the Same Host as TwentyCRM?
Colocation feels like it should mean 'automatic access' — the evidence says it doesn't, and the real value is elsewhere.
explorations/Hermes-Agent-Colocation-and-Hackability.md -
Sharing One Hermes Agent Instance Across a 3-Person Client Team
Hermes Agent has no shipped multi-user mode — the gap is real, catalogued, and still open upstream.
explorations/Hermes-Agent-Multi-User-Team-Access.md -
An Instantly-Synced Shared Folder for a 3-Person Team
Nextcloud was the first name that came to mind — but the actual ask is pure instant file sync, and that's a different tool's specialty.
explorations/Instantly-Synced-Team-Folder-Nextcloud-vs-Alternatives.md -
self-host-stack/agent-skills/custom-domain-cutover/skill
Point a custom (sub)domain at a Railway service and survive the cutover — DNS records, wildcard overrides, cert issuance, and the stale-cache theater that follows. Use whenever minting a `*.didi.sh` (or any custom) domain for a client hub/app, whenever a freshly-cut domain "doesn't work" on someone's machine while probes say it's live, or whenever the user says "I can't see the subdomain."
agent-skills/custom-domain-cutover/SKILL.md -
self-host-stack/agent-skills/decilehub-interface/readme
agent-skills/decilehub-interface/README.md -
self-host-stack/agent-skills/decilehub-interface/references/connector-setup
agent-skills/decilehub-interface/references/connector-setup.md -
self-host-stack/agent-skills/decilehub-interface/references/pipeline-vocabulary
agent-skills/decilehub-interface/references/pipeline-vocabulary.md -
self-host-stack/agent-skills/decilehub-interface/references/tool-map
agent-skills/decilehub-interface/references/tool-map.md -
self-host-stack/agent-skills/decilehub-interface/skill
Operate a VC firm's Decile Hub from Claude Desktop, claude.ai, or Claude Teams via Decile's native MCP connector — 158 tools across the LP/investor pipeline, deal flow, portfolio, fund admin, data room, and outbound email. Use when someone asks about an LP or a deal ("is X in our pipeline?", "what stage?", "who referred us?"), wants a call or voice memo logged, wants records created or updated, wants a pipeline or portfolio roundup, or wants to send an email, newsletter, PACT, or LPA. Supplies the safety tiering Decile omits (its 158 tools carry zero annotations, so list_people and publish_newsletter look alike), the People-vs-Organizations-vs-Prospects model, where notes actually land, the never-create-a-duplicate rule (there is no merge tool), and the discipline of reporting only what the record supports.
agent-skills/decilehub-interface/SKILL.md -
self-host-stack/agent-skills/decilehub-interface/templates/deal-upsert
agent-skills/decilehub-interface/templates/deal-upsert.md -
self-host-stack/agent-skills/decilehub-interface/templates/lp-upsert
agent-skills/decilehub-interface/templates/lp-upsert.md -
self-host-stack/agent-skills/decilehub-interface/templates/speech-to-text-upsert
agent-skills/decilehub-interface/templates/speech-to-text-upsert.md -
self-host-stack/agent-skills/vc-firm-profile-ingest/skill
Research a VC firm from the open web and land it in BOTH systems in one pass — a Twenty CRM company record with a research note attached, and a cross-linked Outline wiki page in the Venture Firms collection following the house profile template. Use whenever the operator says "create a VC profile", "add <firm> to the CRM and the wiki", "profile <firm>", "research this fund and write it up", "who are they and should we care", or names this skill. Encodes the dedupe-first discipline (98+ companies already exist — never create a second record), the two-call note attachment Twenty requires, the composite link-field shapes that silently fail as plain strings, the Twenty↔Outline join (the wiki page header carries the CRM record UUID), the house page template with its open-questions checklist, and the sourcing hierarchy that keeps contaminated aggregator data out of the record. Client-scoped: collection and workspace IDs below are Palmer AI's.
agent-skills/vc-firm-profile-ingest/SKILL.md
site 4 docs
-
Handoff — site → site-next rebuild kickoff (Phase 0 in progress)
Everything the next agent-session needs to resume the ground-up rebuild cold: the locked decisions, what was installed, what Phase-0 artifacts exist, what remains, and the exact next actions — including the gotchas (graphify under-captures .astro imports; the MCP query server becomes available in the NEXT session).
handoffs/2026-08-04_Rebuild-Kickoff-Handoff.md -
Rebuild Keep/Drop Ledger — site → site-next (Astro 7 + astro-knots + LFM)
The Phase-0 ground truth for the ground-up rebuild: what the current site is made of, what survives into site-next/, what we retire — and the discipline that every retired thing gets its intention captured in context-v before its code is dropped.
decisions/2026-08-03_Rebuild-Keep-Drop-Ledger.md -
Abandoned Intention — The Tube Visual (four-layer branded container)
A retired attempt at a signature 'tube box' framing device — four concentric layered borders wrapping content — explored across three rendering strategies (CSS clip-path, raw SVG, Webkit) and never adopted. Captured here so the design intent survives the code being dropped in the site-next rebuild.
explorations/Abandoned-Intentions-Tube-Visual.md -
Rethink on Client-Focused Landing Pages
Three overlapping mechanisms — `for_clients` frontmatter, MOC files, and the `client-content/` tree — are trying to do the same job and stepping on each other. This is a thinking-out-loud document, not a spec.
explorations/Rethink-on-Client-Focused-Landing-Pages.md
specs 17 docs
-
Churn: An AI content editor for the Internet has been missing.
Content Management Systems are an old paradigm, they are clunky, they are rarely where creatives develop content. HTML and CSS need to marry Content Editors
Churn-Content-Editor-for-the-Web.md -
Markdown-Serve: `md-serve` - a simple server and API for Markdown content rendering on the web
Markdown files have been the lingua franca of web content, on the rise since JAM Stack adoption. Yet, the development experience requires long builds, complex setups, massive content filling developer projects. Why not improve developer experience while making it easier to serve and render them?
Markdown-Serve-an-API-for-Markdown-Content.md -
AI-Powered Link Aggregator for Product Digital Footprint Discovery
Automatically discover and catalog social media profiles, code repositories, blog feeds, and other digital presence links for 1,400+ products in our tooling directory.
AI-Powered-Link-Aggregator-for-Product-Digital-Footprint.md -
An Obsidian Plugin that uses AI to Browserless Search, Perplexity API, follows outline
Extend Perplexed to summarize products
Search-and-Summarize-Obsidian-App.md -
YAML Frontmatter Error Detection and Correction System
Let content teams develop content. Handle frontmatter inconsistencies gracefully for a seamless user experience.
Cases-and-Corrections-for-YAML-Content-Wide.md -
Project Routing Collision Fix
Cleaned route collisions between Client Projects and canonical Projects, yet now need to figure out Client Projects again.
Project-Routing-Fix-Complete-Implementation.md -
AI-Powered Link Aggregator for Product Digital Footprint Discovery
Automatically discover and catalog social media profiles, code repositories, blog feeds, and other digital presence links for 1,400+ products in our tooling directory.
AI-Powered-Link-Aggregator-for-Product-Digital-Footprint 1.md -
A Collaborative Markdown-based Desktop Publisher
Technical specification document outlining implementation details
Create-a-Collaborative-Markdown-based-Desktop-Publisher.md -
Dynamic Webpage to Display Portfolio w Authentication
Dynamically display portfolio information on a branded webpage, with certain types of information only displayed for certain privileges connected to authentication.
Dynamic-Webpage-to-Display-Portfolio-w-Authentication.md -
Self-Updating Product Announcement Watcher
Automatically monitor, collect, and catalog product releases and announcements for 1,400+ tools in our content library without manual intervention.
Self-Updating-Product-Announcement-Watcher.md -
Complete Me: A context-aware, blazing fast markup editor.
Streamlines data entry and development workflows through rigorous, context-aware autocomplete in markup and json.
JSON-Editor-like-Obsidian.md -
Build-Out-WhatsApp-Plugins-Ecosystem-for-Overwhelmed-Professionals
WhatsApp and other messaging apps have become the defacto place where business is done. Why not make it work?
Build-Out-WhatsApp-Plugins-Ecosystem.md -
Salute: An AI design system generator that generates as you code.
The Design System to Engineering Handoff is clunky for most situations. Instead, designers vibe create design systems, and engineers vibe contribute. Managed through MCP
Salute-Design-System-Generator.md -
Maintain a Dynamic Project Viewer
A dynamic project viewer can handle multiple artifacts, file formats, and make it easier for clients to navigate projects.
Maintain-a-Dynamic-Project-Viewer.md -
Churn: An AI content editor for the Internet has been missing.
Content Management Systems are an old paradigm, they are clunky, they are rarely where creatives develop content. HTML and CSS need to marry Content Editors
Was-There-a-Substack-for-Event-Attendees.md -
Clean Specific Issues in YAML One at a Time
Targeted scripts to address specific YAML frontmatter issues for improved content management
Clean-Specific-Issues-in-YAML-One-at-a-Time.md -
Filesystem Observer for Consistent Metadata in Markdown Files
Let content teams develop content. Handle frontmatter inconsistencies gracefully for a seamless user experience.
Filesystem-Observer-for-Consistent-Metadata-in-Markdown-files.md
stenographer 1 doc
studies 3 docs
sync-and-content-version-control 8 docs
-
automerge
The only entry where two people editing the same paragraph is a solved case rather than a second file with a longer name — and it costs you the filesystem.
profiles/Profile__Automerge.md -
git-annex
Content is optional. git tracks which copies exist where, and refuses to drop the last one — the bookkeeping that makes deleting a local file safe.
profiles/Profile__Git-Annex.md -
jujutsu
The storage layer is five pluggable backends, not one — and only two of the five have a shipped implementation you could put in a bucket.
profiles/Profile__Jujutsu.md -
kopia
Its snapshot manifest has the free-text Description field restic lacks, and its policies attach per directory and inherit — the ask's own shape, in the store.
profiles/Profile__Kopia.md -
rclone-ui
The only entry that solves the trigger problem — 5,167 lines of Rust registering jobs with launchd, crontab, and Task Scheduler behind one trait.
profiles/Profile__Rclone-UI.md -
restic
Its on-disk layout is data/<ab>/<sha256> plus snapshots/<id> — which is corpora-builder's unbuilt Phase 4, already shipped and hardened since 2014.
profiles/Profile__Restic.md -
seafile
Git's object model with content-defined chunking underneath and a human-readable description on every commit — and the S3 backend is the paid tier.
profiles/Profile__Seafile.md -
syncthing
Closes a question two Lossless docs left open: a receive-only device does not silently orphan the collaborator's edit — it flags it, counts it, and offers Revert.
profiles/Profile__Syncthing.md
vector-databases 6 docs
-
chroma
The hybrid retrieval in Chroma's docs raises `NotImplementedError` on a laptop — `Collection.search()` is gated behind Cloud.
profiles/Profile__Chroma.md -
lancedb
The database *is* the file format: a `.lance` directory DuckDB, Polars, and Pandas read with no LanceDB process running.
profiles/Profile__LanceDB.md -
milvus
One Milvus deployment is not a process — it is nine roles, three external dependencies, and a C++ ANN core reached through cgo.
profiles/Profile__Milvus.md -
pgvector
About 3k lines of substantive C, and it inherits MVCC, WAL, replication, PITR, and row-level security completely untouched.
profiles/Profile__pgvector.md -
qdrant
Qdrant estimates a filter's cardinality *before* searching, which is why recall doesn't collapse the moment you filter on `tenant_id`.
profiles/Profile__Qdrant.md -
weaviate
The database itself calls OpenAI to embed on write and Cohere to rerank on read — the RAG pipeline lives inside the store, not the app.
profiles/Profile__Weaviate.md