Rabbit Holes

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.

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.

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.

How an Astro splash site for a pseudomonorepo aggregates each child submodule's changelog/ and context-v/ into one feed — with provenance, without runtime dependencies on the GitHub API, and without auth token plumbing in CI. The deliberate-sync model: a human runs `pnpm rollup:sync`, content lands in src/rollup/, gets committed, deploys like any other static asset.

Step-by-step playbook for standing up a private, gated, two-surface fundraise/teaser deck workspace from scratch. Captures the patterns proven on sites/calmstorm-decks during the week of 2026-04-30 → 2026-05-03, written as instructions for the next site rather than as a retrospective. Use this when initializing a new client deck site under astro-knots/sites/.

Architecture for a hard-gated, multi-opportunity promotion surface inside mpstaton-site. Each opportunity gets a hub page that conditionally surfaces deck and memo materials behind real authentication, optimised for AI-assisted variant iteration in 3-5 minute cycles.

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.

A specification for a named, versioned extended markdown flavor that codifies our existing rendering capabilities, incorporates features from GFM, Obsidian, MDX, and directive-based systems, and defines a wish list for future development — all backed by a shared remark/rehype package.

A per-site swap script that lets a development branch consume @lossless-group/lfm from the local workspace while every deployable branch consumes the canonical JSR build — so production deploys can never accidentally ship a workspace link.

A quick reference for writing a changelog prior to meaningful commits.

Implementation blueprint for embeddable, theme-aware interactive polls on Astro SSG sites — covering data model, storage progression from flat-file to database, real-time mechanics, live-meeting authoring motions, vote integrity, and Svelte + GSAP UI contracts.

Implementation blueprint for embeddable, theme-aware interactive polls on Astro SSG sites — covering Session/Poll data model, Astro DB on Turso storage, DB→markdown materialization for archive, live-meeting authoring motions, and Svelte + GSAP UI contracts. v0.0.1 ships four templates and one live session.

A reader UI for publishing book-length content as a sequenced series of chapters on the FullStack VC site. The wrapper provides chapter sequencing, navigation, and reading affordances; all content-level features (callouts, citations, image directives, wikilinks) stay in the Lossless Flavored Markdown plugin where they belong.

A quick reference for the quirks of Obsidian Flavored Markdown.

Professionals have a stack of tools and technologies they use to get their work done. This display should show the tools and technologies in a way that is easy to browse and understand, helping others learn about the tools and technologies used in the industry — built on markdown + JSON, no database, in the spirit of AI-friendliness.

Conventions for the two reference pages every Astro-Knots site ships — Brand Kit (brand experience essentials) and Design System (component catalog) — including scope split, URL standardization, theme/mode integration contract, and maintenance motions.

Implementation blueprint for dual-axis theme and mode control using Tailwind CSS v4 custom properties, with runtime utilities and Vitest verification.

Step-by-step guide for scaffolding a new Astro site in the astro-knots monorepo, from empty directory to working markdown rendering.

You can prompt your AI Assistant via chat, but it's hard to manage a complex series of tasks that way. Even harder to retrace your steps or share your work. Thus, this recurring prompt.

A specification for a mobile-first, image-heavy portfolio site with dark and vibrant modes, carousel-driven galleries, tiered pricing cards, WhatsApp CTA, and SEO landing pages — all managed through markdown content and deployable independently from the Astro-Knots pseudomonorepo.

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.

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.

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.

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.

All tags in YAML frontmatter must use Train-Case — capitalize each word, hyphens between words, no spaces, no underscores, no all-lowercase.

Step-by-step implementation guide for adding a build-time GitHub content fetcher to mpstaton-site that pulls context-v documents from multiple repos.

A build-time content fetcher that pulls context-v documents (Specs, Blueprints, Prompts, Reminders) from multiple GitHub repositories, enabling lossless.group and mpstaton.com to render current project documentation without manual copying or submodules.

A slides-only Astro site that stays consistnent with relevant Context Vigilance files fed into AI Assistant context.

A scalable, consistent architecture for Open Graph metadata optimized for the messaging-first share economy.

A citation and reference management system for Astro sites using hex codes as stable identifiers that convert to sequential integers at render time.

Blueprint for implementing syntax-highlighted code blocks across astro-knots sites using Shiki with the tokyo-night theme and reusable wrapper components.

Architecture blueprint for Dark Matter's CSS and Tailwind v4 theming system, defining named brand colors, derived scales, semantic tokens, and three display modes.

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.

Prompt plan for creating a tabbed Partner with Us page showcasing different LP types including corporate investors, family offices, fund of funds, and institutional managers.

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.

A reminder that Astro-Knots is organized like a monorepo but functions as a collection of independent Astro projects for convenient pattern porting.

A quick reference for the preferred technology stack: HTML/CSS first, Astro for SSG, Svelte for interactivity, Tailwind for styling, and no React.

Specification for a media coverage section with article display components, sidebar layout, and links to relevant press coverage of portfolio companies.

A simplified, Astro-Knots-specific blueprint for rendering extended markdown across sites, starting with Hypernova and Dark-Matter as first adopters.

Patterns and tradeoffs for managing markdown content that lives outside an Astro project but must be available at build time, with strategies for Vercel deployment.

Prompt for introducing features and UI components to the Hypernova site, including team pages, responsive design patterns, and branded exports.

We have developed a number of great patterns, components, and utilities that we use on a regular basis. To start with a robust set of included functionality, we cloned The Water Foundation site (twf_site), but now need to strip out any code that is not directly related to the Hypernova brand and desired site functionality.

Dynamically display portfolio information on a branded webpage, with certain types of information only displayed for certain privileges connected to authentication.

Organizations increasingly deliver and maintain multiple products, each necessitating its own changelog. However, as an organization its good to display those changelogs in a unified way, so that users can easily see the changes across all products and the team can feel motivation from organization-wide progress.

With AI Code Assistants on the rise, maintaining a rigorous test suite is more important than ever. Maintaining a test suite that catches regressions and ensures the website is performing as expected is a must.

As website content grows more numerous, across different audiences and different contexts, dynamically generated OpenGraph images can amplify shares and referral marketing while not bogging down the team with the need to create and maintain a separate image for each piece of content.

Design and implementation patterns for consistent jumbotron popdown menus in the Lossless UI.

A tiered pattern for protecting privileged or confidential content across astro-knots sites, from simple passcodes to full OAuth integration.

A pattern enabling Astro sites to fetch confidential content from a private GitHub repository at runtime, keeping sensitive documents out of static assets.

A comprehensive specification for building presentation slide systems in Astro-Knots sites with RevealJS, Three.js, and full theme/mode integration.

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.