OverviewHistoryStatsSecurity
npx skills add ...
Documentation
SKILL.md
npx skills add jmsktm/claude-settings --skill knowledge-base-builder
Build and maintain AI-accessible knowledge bases for projects
npx skills add jmsktm/claude-settings --skill knowledge-base-builder
The Knowledge Base Builder skill helps you create, structure, and maintain knowledge bases that AI agents can effectively query and utilize. It transforms scattered information—from project documentation to tribal knowledge—into organized, accessible knowledge that improves AI performance and team productivity.
This skill guides you through knowledge extraction, organization, structuring, and maintenance. It understands different knowledge formats (documentation, code comments, decision logs, schemas), helps you choose appropriate storage (markdown files, knowledge graphs, databases), and ensures knowledge remains current and useful.
Use this skill when starting new projects, onboarding AI to complex systems, preserving institutional knowledge, or improving AI agent effectiveness through better context.
| Action | Command/Trigger |
|---|---|
| Build new knowledge base | "Build knowledge base for [project]" |
| Extract from codebase | "Extract knowledge from codebase" |
| Organize project docs | "Organize project knowledge" |
| Create knowledge graph | "Create knowledge graph for [domain]" |
| Update knowledge base | "Update knowledge base with [new info]" |
| Audit knowledge | "Audit knowledge base health" |
| Structure documentation | "Structure documentation for [project]" |
Start with Purpose: Define what the knowledge base should accomplish
Structure for Discovery: Make information findable
Write for AI and Humans: Both will consume this
Keep It Current: Stale knowledge is worse than no knowledge
Make It Accessible: Knowledge must be reachable
Use Multiple Formats: Different knowledge needs different formats
Preserve Context: Don't just document "what", document "why"
Link Generously: Connect related concepts
Good knowledge base entries should:
| Tool | Best For | Format |
|---|---|---|
| Markdown files | Human-readable docs | .md files in repo |
| Memory MCP | AI-accessible relationships | Knowledge graph |
| Code comments | Implementation context | JSDoc, inline comments |
| OpenAPI/GraphQL | API contracts | YAML/JSON schemas |
| Mermaid | Visual diagrams | Diagram-as-code |
| Notion | Collaborative docs | Rich text, databases |
# Architecture
## Overview
[High-level system description]
## System Components
- **Component 1**: [Purpose and responsibility]
- **Component 2**: [Purpose and responsibility]
## Data Flow
[How data moves through the system]
## Key Design Decisions
1. **[Decision]**: [Rationale]
2. **[Decision]**: [Rationale]
## Technology Stack
- Frontend: [Technologies]
- Backend: [Technologies]
- Database: [Technologies]
- Infrastructure: [Technologies]
## Integration Points
- [External service 1]: [How we integrate]
- [External service 2]: [How we integrate]
## Security Considerations
[Security architecture and patterns]
## Scalability & Performance
[How system scales, performance characteristics]# Architecture Decision Records
## ADR-001: [Decision Title]
**Date**: YYYY-MM-DD
**Status**: Accepted | Proposed | Deprecated
**Context**:
[What is the issue we're trying to solve?]
**Decision**:
[What we decided to do]
**Consequences**:
- Positive: [Benefits]
- Negative: [Trade-offs]
- Neutral: [Other impacts]
**Alternatives Considered**:
1. [Alternative 1]: [Why rejected]
2. [Alternative 2]: [Why rejected]
---
## ADR-002: [Next Decision]
[...]# [Component Name]
## Purpose
[What this component does and why it exists]
## Location
`/path/to/component`
## Dependencies
- [Dependency 1]: [Why needed]
- [Dependency 2]: [Why needed]
## API
### Functions
- `functionName(params)`: [Description]
### Types
\`\`\`typescript
interface ComponentProps {
// ...
}
\`\`\`
## Usage
\`\`\`typescript
// Example usage
\`\`\`
## Related Components
- [Component A]: [Relationship]
- [Component B]: [Relationship]
## Known Issues
- [Issue 1]: [Workaround]Project
- name
- description
- status (active, maintenance, deprecated)
- tech_stack
Component
- name
- type (service, module, function)
- location (file path)
- purpose
- status
Person
- name
- role
- expertise_areas
- current_focus
Decision
- title
- date
- status
- context
- choice
- rationale
Process
- name
- type (workflow, procedure, standard)
- steps
- triggers
- outputs
Dependency
- name
- version
- purpose
- critical (boolean)Project --depends_on--> Dependency
Project --contains--> Component
Component --uses--> Component
Component --implements--> Decision
Person --owns--> Component
Person --made--> Decision
Decision --supersedes--> Decision
Component --documented_in--> Document
Process --governs--> Component// Create entities
await memory.create_entities({
entities: [
{
name: "id8labs-app",
entityType: "Project",
observations: [
"Next.js 14+ application",
"Uses Supabase for backend",
"Deployed on Vercel",
"Monorepo structure"
]
},
{
name: "authentication-module",
entityType: "Component",
observations: [
"Located in /src/features/auth",
"Handles user authentication via Supabase Auth",
"Supports magic link and OAuth",
"Implements RLS policies"
]
}
]
});
// Create relationships
await memory.create_relations({
relations: [
{
from: "id8labs-app",
to: "authentication-module",
relationType: "contains"
},
{
from: "authentication-module",
to: "Supabase Auth",
relationType: "uses"
}
]
});