generating-lattice

Solid

Generate and maintain lat.md/ knowledge graphs with bidirectional source code anchoring. Docs link to code via [[src/file#symbol]] wiki links; code links back to docs via @lat: comments. lat check validates both directions, catching drift when either side changes. Use when user says "lat.md", "lattice", "knowledge graph", "document this codebase", "add back-links", or wants cross-referenced architecture docs anchored to source code symbols.

Data & Documents 148 stars 5 forks Updated today MIT

Install

View on GitHub

Quality Score: 84/100

Stars 20%
72
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Generating Lattice Generate and maintain `lat.md/` knowledge graphs — structured, cross-referenced markdown anchored to source code symbols. The output is validated by the `lat` CLI, which catches documentation drift whenever code or docs change. **The core mechanism is bidirectional linking:** - **Top-down** (docs → code): `[[src/auth.js#getValidToken]]` wiki links in `lat.md/` files point to specific symbols in source. When a symbol is renamed or deleted, `lat check` catches the broken link. - **Bottom-up** (code → docs): `// @lat: [[auth#Token Refresh]]` comments in source point back to the concept they implement. When a section is renamed or removed, `lat check` catches the dangling reference. Without both directions, the lattice is a static essay that drifts silently. With both, `lat check` enforces consistency. **Dependency:** Requires the **tree-sitting** skill. Its AST scan is the input that makes LLM-assisted authoring token-efficient — read the tree to understand API surfaces, then selectively read source files only where design rationale lives. ## Installation ```bash npm install -g lat.md lat --version # verify (requires Node.js 22+) ``` The `lat` CLI provides `lat check` (validation), `lat search` (semantic search), `lat section` (browsing), `lat refs` (reference lookup), and `lat mcp` (agent integration). ## Generation Pipeline ### Phase 1: Structural Scan Get the symbol inventory from tree-sitting. Nothing is written to disk — the scan run...

Details

Author
oaustegard
Repository
oaustegard/claude-skills
Created
10 months ago
Last Updated
today
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

lattice-init

Guided setup and upgrade-check experience for Lattice projects -- scans the repository, detects existing configuration and outdated conventions, suggests refiners and available upgrades in priority order, and creates or reconciles the .lattice/ config. Bridges the gap between installing skills and getting first value, and between upgrading Lattice and adopting its newest conventions. Use when the user says 'lattice init', 'set up lattice', 'initialize lattice', 'get started with lattice', 'configure lattice for this project', 'check for lattice upgrades', or 'upgrade lattice conventions'.

190 Updated 4 days ago
techygarg
AI & Automation Listed

artifact-lint

Scans a project's generated-artifact surface (08-Generated/ + promoted folders) and runs five graph-integrity checks — orphan, sibling duplicate, stale draft, displaced content, version chain — reading the horizontal-lineage frontmatter (parent_artifact / sibling_topic / supersedes) so duplicate, orphaned, stale, or displaced generated content is surfaced for operator approval instead of silently accumulating. Read-and-recommend only — no automatic file moves or deletes. Triggers: "lint the generated artifacts", "check 08-Generated for duplicates", "scan for orphaned artifacts", "find stale drafts", "run artifact lint", "are there duplicate generated artifacts", "check the artifact lineage graph", "version-chain check the generated folder."

0 Updated today
cody-hutson
AI & Automation Listed

llms-txt

Generate and maintain llms.txt -- the curated markdown map a website, docs directory, repo, or knowledge vault publishes at its root so agents can orient in one fetch. Fires on three branches: creating one ("add llms.txt", "make my site/docs/repo agent-readable", GEO/AEO asks); refreshing an existing llms.txt after content changed (minimal diff, stable ordering); and checking one ("is my llms.txt valid or stale?"). Whole-repo release packaging is burnish's job -- it routes here for this one artifact; compiling sources into a knowledge vault is wiki-it's job. llms-txt maps content that already exists.

0 Updated 1 months ago
lroolle