AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

acquire-codebase-knowledge

Use this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like "map this codebase", "document this architecture", "onboard me to this repo", or "create codebase docs". Do not trigger for routine feature implementation, bug fixes, or narrow code edits unless the user asks for repository-level discovery.

Original source
github
License
MIT
Pinned revision
5269f7ea2d6c3a9bfda5ed878b6726cf509121fd

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read github--acquire-codebase-knowledge at revision 5269f7ea2d6c3a9bfda5ed878b6726cf509121fd, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 10

assets/templates/ARCHITECTURE.md

Architecture

Core Sections (Required)

1) Architectural Style

  • Primary style: [layered/feature/event-driven/other]
  • Why this classification: [short evidence-backed rationale]
  • Primary constraints: [2-3 constraints that shape design]

2) System Flow

[entry] -> [processing] -> [domain logic] -> [data/integration] -> [response/output]

Describe the flow in 4-6 steps using file-backed evidence.

3) Layer/Module Responsibilities

| Layer or module | Owns | Must not own | Evidence | |-----------------|------|--------------|----------| | [name] | [responsibility] | [non-responsibility] | [file] |

4) Reused Patterns

| Pattern | Where found | Why it exists | |---------|-------------|---------------| | [singleton/repository/adapter/etc] | [path] | [reason] |

5) Known Architectural Risks

  • [Risk 1 + impact]
  • [Risk 2 + impact]

6) Evidence

  • [path/to/entrypoint]
  • [path/to/main-layer-files]
  • [path/to/data-or-integration-layer]

Extended Sections (Optional)

Add only when needed:

  • Startup or initialization order details
  • Async/event topology diagrams
  • Anti-pattern catalog with refactoring paths
  • Failure-mode analysis and resilience posture