generating-lattice
SolidGenerate 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.
Install
Quality Score: 84/100
Skill Content
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
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'.
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."
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.