project-knowledge

Load architecture.json, conventions.json, patterns.json, and gotchas.json into a queryable project model.

Updated Dec 1, 2025
One-click install
npx skills add https://github.com/Clouder0/dotagent --skill project-knowledge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-knowledge
Source: https://github.com/Clouder0/dotagent/tree/main/.claude/skills/project-knowledge
Command: npx skills add https://github.com/Clouder0/dotagent --skill project-knowledge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pattern to load project architecture and structure knowledge for quick understanding.

Core Features & Use Cases

  • Knowledge files: Architecture, conventions, patterns, gotchas.
  • Guided usage: Read knowledge before making changes.

Quick Start

Read memory/knowledge/codebase/architecture.json to understand project structure.

Frequently Asked Questions about project-knowledge

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

FAQPage Schema
How do I understand my project's architecture and structure?

Load your project architecture by reading knowledge files—architecture.json, conventions.json, patterns.json, and gotchas.json—to build an integrated model of structure, conventions, patterns, and known issues. This creates a queryable reference for onboarding and informed decision-making.

When should I review project architecture before making changes?

Review project architecture at the start of any work—especially before making architectural decisions or connecting components. Understanding conventions, patterns, and gotchas upfront prevents misaligned implementations and saves rework.

What knowledge files document project conventions and patterns?

Project knowledge is stored in four files: architecture.json defines structure, conventions.json captures coding standards, patterns.json documents recurring solutions, and gotchas.json lists known pitfalls and edge cases.

Can I update project knowledge after completing tasks?

Yes. After task completion, you can update knowledge files to document new patterns discovered, architectural changes made, or additional gotchas encountered, keeping the knowledge model current.

How do I query project knowledge to understand component connections?

Load the integrated knowledge model from the four JSON files to produce a queryable representation. This enables you to trace how components connect, understand architectural decisions, and navigate dependencies.

Related Skills