Kinds / Canonical
reminders/
Short corrections born from the same AI mistake made twice.
100 files · 22 projects
Lost in Public28
Reminder of Specification Template and Guidelines for AI Code Assistants
Guidlines and templates only work if you use them.
How to manage gnarly routing with Static Site Generators
Guidlines for how to manage dynamic and static routing with Static Site Generators
Maintain an Environment-based Build System
Build across environments, including different deployments, using environment variables and configuration files.
Fire up the Observer
Ready to automate? Learn how to launch the Observer system for seamless citation and frontmatter processing across your content library.
Implement Client-Specific Content Routing in Astro
Create dynamic routes for client-specific content while maintaining existing general content structure
Maintain Consistent Debugging Conventions
Debugging is a critical part of our development process. We should maintain consistent debugging conventions across all our code.
Ways We Avoid Hard Validation
Prevent build failures and gracefully handle frontmatter inconsistencies.
The Simplified Observer Logic
Clarify and streamline the Observer’s orchestration logic—ensuring every subsystem, expectation, and write operation is perfectly sequenced.
Use Safe Syntax in Mermaid Charts
Assure your Mermaid Charts render by avoiding unsafe characters and syntax while writing technical documentation
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.
Change Role and Implement Prompt
Seamlessly switch roles from product manager to developer and implement prompts with context awareness and precision.
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.
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.
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.
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.
Maintain Consistent Reporting
Master the art of consistent, auditable reporting for every automation, script, and observer in your content pipeline.
Maintain Consistent Reporting Templates
Build trust and clarity with consistent, reusable reporting templates that make every audit, fix, and automation step transparent and repeatable.
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.
Maintain a Scripting Pipeline
Design modular pipelines to detect, clean, and report on markdown files—ensuring every content workflow is robust, maintainable, and auditable.
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.
Map of Relevant Paths
Review this file to ensure code generation is using the correct paths and directory structure in this complex monorepo.
Meticulous Constraints for Every Prompt
Master prompt engineering with essential, actionable constraints—ensuring every code generation task is robust, DRY, and error-resilient.
Read the relevant documentation before guessing.
Illuminate your coding journey by diving into relevant documentation, and transform assumptions into accurate, well-informed decisions.
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.
Respect the framework nuances, read the docs
Brief description of the reminder functionality and purpose
Discuss Spec init starter before Developing Spec
Brief description of the reminder functionality and purpose
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.
lost-in-public/reminders/specification-guidelines-template
astro-knots14
Orient Before You Introduce a Term of Art
A reader who does not yet know what the thing is cannot learn its name. Plain question first, clinical title second — enforce it in the schema.
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.
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.
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 `//`.
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.
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.
Write a Changelog Prior to Meaningful Commits
A quick reference for writing a changelog prior to meaningful commits.
Quirks of Obsidian Flavored Markdown
A quick reference for the quirks of Obsidian Flavored Markdown.
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.
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.
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.
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.
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.
astro-knots/reminders
lossless-monorepo7
No Scripts for Frontmatter Edits
One wrong line in a script becomes a thousand broken docs, and every site and vault that reads them breaks at once. Agents edit by hand.
Gitignored Build Caches Must Ship to Vercel
A cache that is gitignored does not exist on Vercel. On an on-demand route that means live fetches inside the request and a write to a read-only disk.
Submodule pointer bumps belong at wrap-up
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.
Dates are UTC at rest, viewer-local at render
Pseudomonorepo Settings — Fence Each Project from Parent pnpm Workspaces
lossless-monorepo/reminders
ai-labs5
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.
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.
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.
Preferred Stack — uv over pip, and other defaults
ai-labs/reminders
memopop-orchestratorai-labs / memopop-ai5
Every Step Writes Its Output To File
A run's destination folder is decided before the first step, and every step writes its result there as it finishes. Nothing lives only in memory.
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.
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.
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.
memopop-orchestrator/reminders
augment-itai-labs4
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.
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.
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.
augment-it/reminders
self-host-stack4
Submodules detach because .gitmodules never said which branch
The parent pins a raw SHA, so every submodule update lands on a detached HEAD. Declaring branch and update in .gitmodules fixes it once for every clone — but the bulk scripts that promise to fix it are exactly the things that have historically detached submodules AND clobbered their remotes.
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.
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.
self-host-stack/reminders
id-didi-shai-labs3
Dates are UTC at rest, viewer-local at render
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.
id-didi-sh/reminders
content-farm3
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.
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.
content-farm/reminders
cite-widecontent-farm3
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.
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.
cite-wide/reminders