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/STRUCTURE.md

Codebase Structure

Core Sections (Required)

1) Top-Level Map

List only meaningful top-level directories and files.

| Path | Purpose | Evidence | |------|---------|----------| | [path/] | [purpose] | [source] |

2) Entry Points

  • Main runtime entry: [FILE]
  • Secondary entry points (worker/cli/jobs): [FILES or NONE]
  • How entry is selected (script/config): [NOTE]

3) Module Boundaries

| Boundary | What belongs here | What must not be here | |----------|-------------------|------------------------| | [module/layer] | [responsibility] | [forbidden logic] |

4) Naming and Organization Rules

  • File naming pattern: [kebab/camel/Pascal + examples]
  • Directory organization pattern: [feature/layer/domain]
  • Import aliasing or path conventions: [RULE]

5) Evidence

  • [path/to/root-tree-source]
  • [path/to/entry-config]
  • [path/to/key-module]

Extended Sections (Optional)

Add only when repository complexity requires it:

  • Subdirectory deep maps by feature/layer
  • Middleware/boot order details
  • Generated-vs-source layout boundaries
  • Monorepo workspace-level structure maps