Step 14 of 14, updated

From here

You have used each part of ShotScript once. The reference pages say everything about each part.

You'll learn what you built, and where to read next.

What you built

shot map shows the whole project, one line per file, with its declaration and the first line of its doc:

$ shot map
Shot project .: 16 files in 4 folders

EventBus/              module EventBus           Topics with listeners, on one side
  Types.shot           types
Init/
  Client.shot          client script
  Server.shot          server script
Stats/                 server module Stats       Numbers about the whole game
  Types.shot           types                     imports Reason
Wallet/                class Wallet              implements Purse   [Rules, Extend] The coins one player owns.
  Bank.shot            server module Bank
  Coins.shot           module Coins
  Purse.shot           interface Purse           What every kind of wallet has
  Shop.shot            split module Shop         Client -> ShopClient, Server -> ShopServer
  ShopClient.shot      client module ShopClient
  ShopServer.shot      server module ShopServer
  VipWallet.shot       class VipWallet           extends Wallet   A wallet that doubles every pickup
  Whole.shot           func Whole                Rounds down, and never below 0
  Types.shot           types                     public Reason; public Entry
  BuyRequest.instance  RemoteEvent

Next: shot outline <folder or name>, shot find <name>, shot show <Name.Member>, shot docs

The reference behind each step

Every form, every error and what each check doesn't cover:

Files: folders, one declaration per file, paths, use, plain .luau files and bookmarks.
Types: what every file of a folder sees, and imports.
Classes: class properties, generic classes, inheritance in other folders, and WalletClass.
Doc comments: sections, how to write a system's Rules, and the backtick check.
Modules and Funcs.
Interfaces: every message the promise check gives.
Server and client: split modules, and diffsource funcs for one name on both sides.
Remotes: remote signatures, and what can't cross the network.
Events: events on another bus, events several systems publish, event names kept in data.
Match, Start order, Owned fields and Invariants.
Scenarios: the whole world API, data stores, rejoining players, time skips.

What this guide left out

Uses: which other systems a system may use, and every link it didn't declare.
Id kinds: kinds of string id, like product ids, checked wherever they are written.
Saved data lock: the shape each saved section promises to old saves.
Adopt: shot's tools on an existing game mirrored to disk as plain Luau.
Compiled: what every kind of file compiles to.
Luau tips: type checker traps and their fixes.
Rules: every error shot check gives, its cause and the fix.
The shot command: every shot command; shot docs <name> reads a doc in the terminal.

Outside roblox

System projects run on your computer: one .ssp file, a program shot run runs, a window shot open opens.

One-file projects, Getting started, Running a project, Checked paths and ProcessService.
The objects: a page for every class and datatype a System project can use.
The window: the editor, its Run button, Output and History.
Try it

Run shot outline Wallet on your finished project and read it top to bottom. It is the whole Wallet system: its Rules and Extend, and every member with its doc and line.