Enforce consistent Astro site conventions for Lossless Group projects.
npx skills add https://github.com/lossless-group/lossless-agent-skills --skill astro-knots
Please help me install this Agent Skill. Skill: astro-knots Source: https://github.com/lossless-group/lossless-agent-skills/tree/main/astro-knots Command: npx skills add https://github.com/lossless-group/lossless-agent-skills --skill astro-knots
This Skill eliminates inconsistent tech choices, duplicated context work, and avoidable production bugs (like auth bypasses from misconfigured prerendering) that occur when teams build Astro sites for Lossless projects without shared, enforced conventions.
Use the astro-knots skill to scaffold a new Lossless Astro site following the approved tech hierarchy and deploy configuration.
High-intent search queries and answers about installing and using this skill.
To scaffold an Astro site with consistent frontend conventions, enforce an HTML and CSS-first tech hierarchy, avoiding React or Angular, while applying standardized rules for auth-gated routes and pseudomonorepo context sharing to prevent common production misconfigurations.
The best frontend conventions for maintaining multiple Astro sites involve enforcing a lean HTML and CSS-first stack, standardizing deploy workflows for Vercel and GitHub Pages, and aligning LFM integration to eliminate duplicated context work across the project portfolio.
Prerendering causes auth bypasses in Astro sites when auth-gated routes are statically generated without proper production guardrails, allowing unauthorized access; enforcing strict configuration rules during site scaffolding prevents these costly security misconfigurations.
You cannot use React or JSX in an Astro site following these frontend conventions, as the enforced tech hierarchy mandates a strict HTML and CSS-first approach to keep sites lean, fast, and accessible for AI agents.
To configure LFM integration and pseudomonorepo context for an Astro project, apply codified production guardrails that standardize dependency selection and context sharing across the portfolio, ensuring aligned documentation and avoiding duplicated setup work.
thec3ukEnforce global tech stack standards across code files during generation, review, and refactoring.
boomNDSDeploy Next.js apps to Vercel with production and preview workflows.
lossless-groupNormalize directives, Obsidian callouts, and Markdoc tags into a unified component AST.
wjyugutouAutomate UI code review against Web Interface Guidelines for accessibility and consistency.
