Skip to content
Skip to contents
Skip to reading controls

Search skills⌘K

Setting the file. One moment.

This file

Type

Size

Lines

Position

github
/
github/awesome-copilot

STRUCTURE · Acquire Codebase Knowledge · github/awesome-copilot · Skills Docs

Repo No. 28 · Acquire Codebase Knowledge

↖Back to the cover

Skills

Credited skills

Agentic Workflows
Code Review
Create Canvas Extension

200 skills · 702 min

Skill 01 · Acquire Codebase Knowledge

Subchapter 1.9

STRUCTURE

assets/templates/STRUCTURE.mdMarkdown1 KBView on GitHub

Codebase Structure

Core Sections (Required)

1Up to skill 1Acquire Codebase Knowledge

On this page

Codebase Structure
Core Sections (Required)
1) Top-Level Map
2) Entry Points
3) Module Boundaries
4) Naming and Organization Rules
5) Evidence
Extended Sections (Optional)

This file

Number: 1.9
Position: 9 of 10
Type: Markdown
Size: 1 KB

Nearby

Previous STACK
Next TESTING

Source

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

AssetSTACK AssetTESTING

assets/templates/STRUCTURE.md

(opens in a new tab)

Raw file(opens in a new tab)

github/awesome-copilot(opens in a new tab)