astro-knots
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…
A Lossless Group collection · MIT
A shared library of Agent Skills for AI coding agents on Lossless projects. Tool-agnostic — works with Claude Code, pi-coding-agent, OpenAI Codex, and anything following the spec.
Built in public. Methods, tooling, and institutional knowledge developed openly so others can adopt, adapt, critique, and contribute. Frequent commits, occasional churn, skills that evolve as real workflows reveal what works.
./sync-skills.sh ~/.claude/skills Featured
The first 6 of 24 skills. Sorted by status, then alpha. See the full catalog for the rest.
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…
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…
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,…
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…
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,…
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…
Recent
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.
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.
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.