skills.rest
axiomantic
axiomanticOFFICIAL
Explore all skills by this author →
GitHub

project-encyclopedia

Create a structured project encyclopedia with glossary, architecture diagrams, and decision logs.

8|5|Updated Dec 30, 2025
Search Tags:#glossary#knowledge-management#decision-log#project-encyclopedia#architecture-maps#cross-session-context
One-click install
npx skills add https://github.com/axiomantic/spellbook --skill project-encyclopedia
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: project-encyclopedia
Source: https://github.com/axiomantic/spellbook/tree/main/skills/project-encyclopedia
Command: npx skills add https://github.com/axiomantic/spellbook --skill project-encyclopedia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams maintain a cross-session memory of project knowledge by building a persistent glossary, architecture maps, and decision logs that stay useful across sessions.

Core Features & Use Cases

  • Glossary: capture domain terms and definitions to avoid repeated clarification.
  • Architecture maps: generate lightweight diagrams and overviews of project structure.
  • Decisions: log rationale and alternatives to preserve reasoning across sessions.
  • Use Case: On first session or when a codebase overview is requested, produce a concise encyclopedia for current project scope.

Quick Start

Create a project encyclopedia for the current project to capture glossary terms, architecture overview, and decision records for ongoing context.

Frequently Asked Questions about project-encyclopedia

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I maintain project context across sessions for glossary terms and architecture maps?▼

Maintain project context by building a persistent encyclopedia that records glossary terms, architecture maps, and decision logs. This structured knowledge base adapts to your project's language and framework layout, preserving reasoning across sessions.

What is a decision log and when do I need it for software architecture?▼

A decision log preserves rationale and alternatives for architectural choices across sessions. You need it during initial sessions or codebase overviews to ensure past reasoning remains accessible without repeated clarification.

How to generate a codebase overview without losing existing knowledge management data?▼

Generate a codebase overview by applying surgical refresh to update stale sections rather than full regeneration. This workflow respects a 500-1000 line content budget, ensuring existing glossary and architecture maps remain intact while adapting to project scope.

Does the project encyclopedia workflow work with any framework or language layout?▼

Yes, the encyclopedia workflow adapts to your project's specific language, framework, and layout. It conforms to standardized staleness checks and content budgeting regardless of the underlying tech stack structure.

What are the limitations of cross-session context budgeting for architecture maps?▼

Cross-session context budgeting limits the encyclopedia to 500-1000 lines, requiring surgical refresh of stale content rather than full regeneration. This constraint ensures the knowledge base remains concise without overwhelming session context.

Related Skills

Explore More Software Engineering Skills→
BishoniBishoni
27

init-sync

Generates MD and AGENTS.md documentation for scanned codebases and their architectural details.

Community
Advanced
devCharuzudevCharuzu

context-engine

Loads and maintains the company context file at ~/.claude/company.md.

Community
Advanced
MovchanetsMovchanets

ddd-strategic-design

Maps business capabilities into subdomains and bounded contexts with glossary terms and rationale.

Community
Intermediate
xloxn69xloxn69
7

agileflow-adr

Convert discussed architectural decisions into MADR-formatted ADR files.

Community
Basic