Agent skills for FrontLit.
| Skill | What it does |
|---|---|
frontlit-docs |
Write FrontLit docs, or port an existing docs site (Fumadocs, Docusaurus, Mintlify, Nextra, GitBook, VitePress) to FrontLit and open a pull request |
frontlit-pages |
Write FrontLit landing pages as JSON (frontlit/pages/*.json, frontlit/site.json), validate them and open a pull request |
Any agent that supports skills (Claude Code, Codex, OpenCode, Gemini CLI, Cursor, Copilot…):
npx skills add codelitdev/frontlit-skills --skill frontlit-docs
npx skills add codelitdev/frontlit-skills --skill frontlit-pages
Claude Code plugin:
/plugin marketplace add codelitdev/frontlit-skills
/plugin install frontlit-docs@frontlit
/plugin install frontlit-pages@frontlit
Connect your repository in FrontLit (Settings → Integrations → GitHub) first. Then, in your repository:
Use the frontlit-docs skill to port my existing docs to FrontLit and open a pull request.
Use the frontlit-pages skill to add a pricing page and link it from the header.
Both skills work on the repository's FrontLit site folder (frontlit/ by default): docs in docs/, pages in pages/, header, footer and theme in site.json.
- frontlit-docs:
references/format.mdandscripts/check.mjsmirror FrontLit's Markdown importer and validator. Update them whenever those rules change in the FrontLit repository. - frontlit-pages:
scripts/schema/page.v1.jsonandsite.v1.jsonare copies ofpackages/page-builder/schema/in the FrontLit repository (generated bybun run schema:generatethere). Copy them again whenever block settings change, then, fromplugins/frontlit-pages/skills/frontlit-pages/examples, runnode ../scripts/check.mjs frontlit/pages --fix(the examples must stay valid and canonical) and updatereferences/blocks.md. The import rules inscripts/check.mjsandreferences/format.md(file names, reserved routes, content feeds, link and image checks) mirrorapps/api/src/pages/git-import.ts.