Glossary

Plain-language definitions for the concepts, hardware, editors, and labels used throughout :bitForge.

AI and file basics

These are names for tools and formats—not skills you must master before creating a challenge. Start with the everyday meaning and return when you need a reminder.

AI chat tool: An app such as ChatGPT, Gemini, or Claude where you type instructions and receive a response. You can use :bitForge's recommended generation route with the chat tool you already know.
LLM: Short for large language model: the technology that reads your instructions and produces the text or code shown by an AI chat tool. You do not need to understand how the model is built to use it.
Prompt: The instructions you give an AI chat. A useful prompt tells it what to make, who it is for, which limits to follow, and what the response should look like. In Generate, :bitForge builds these instructions from the choices you make.
JSON: A structured way to label and organize information. :bitForge uses it behind the scenes so it can reliably tell the title, difficulty, code, hardware, and teacher notes apart—and check that required pieces are present. Teachers can add the downloaded AI result or paste the complete AI reply without editing this structure.
Markdown: Plain text with simple marks for headings, lists, links, and emphasis. It is useful because people can read it as-is while many tools can also turn it into a formatted document. A file ending in .md contains Markdown.
CSV: A simple table format where each line is a row and commas separate columns. Spreadsheet apps can open it, which makes CSV useful for portable checklists and trackers. A file ending in .csv contains this table data.
API: A way for one piece of software to request something from another. :bitForge's advanced generator can use an AI provider's API to request a challenge without making you copy and paste between tools.
API key: A private access code for a developer API account. It is not the same as your normal ChatGPT or Claude password, and API use may have separate billing. Most teachers do not need one: the recommended :bitForge workflow uses an ordinary AI chat instead.

Python concepts

Sequencing & output

Putting instructions in the correct order and making the micro:bit show, play, or send a result. This is the foundation for reading and writing a program.

Variables, data types & expressions

Storing information under a name, recognizing kinds of data such as numbers and text, and combining values with operators to calculate a result.

Conditionals

Using if, elif, and else to make a program choose what to do. The program checks whether a condition is true before running a set of instructions.

For loops

Repeating instructions a known number of times or once for each item in a collection. A loop variable tracks the current step or item.

While loops & input validation

Repeating while a condition remains true. Input validation checks that a value is acceptable before the program continues.

String methods

Working with text using built-in operations such as changing case, finding characters, splitting text, or replacing part of a string.

Lists & tuples

Keeping several values in an ordered collection. Lists can be changed after creation; tuples are normally used for values that should stay fixed.

Dictionaries

Storing related values as key-and-value pairs so the program can look up information by a meaningful name rather than a numbered position.

Combined patterns

Using several concepts together—for example, a loop containing a conditional that updates a variable—to solve a larger multi-step problem.

Challenge levels

Foundational: Grade-level practice focused on one main concept with a direct, observable result.
Advanced: A more demanding variation that may combine ideas, add constraints, or require more independent problem-solving.

Editors

MakeCode Python: Python used in Microsoft MakeCode. It can switch between text and blocks when the code stays within the blocks-compatible subset.
MicroPython: The Python runtime used by the micro:bit Python Editor. Open MicroPython challenges there rather than in MakeCode; its library names and some commands differ from MakeCode Python.

CSTA mappings

CSTA standard: A learning outcome from the 2026 CSTA PK–12 Computer Science Standards. Challenge mappings are provided as a planning aid and do not represent formal CSTA alignment or endorsement.
MS identifier: The code for a middle-school standard covering grades 6–8. For example, MS-PRO-TR-19 addresses systematic testing, refinement, and documentation.
Future reference: CSTA also publishes Physical Computing and Software Development specialty standards for high school. Some :bitForge challenges relate to those areas, but this grades 6–8 library does not use high-school specialty tags. They may be considered if :bitForge adds a high-school collection in the future.

Components and hardware

LED display: The 5×5 light display built into every micro:bit.
Buttons: The A, B, and touch-logo inputs built into the board. The touch logo requires micro:bit v2.
Speaker / buzzer: The speaker is built into micro:bit v2. A v1 board needs a separately connected buzzer or speaker.
Radio: The wireless radio built into every micro:bit. Radio challenges normally require two boards.
Built-in sensors: Inputs such as temperature, light, acceleration, compass direction, and—on v2—the microphone.
Motor: An external component. Motors require suitable connecting hardware such as a motor driver; never power a motor directly from a micro:bit pin.

Challenge labels

Device tested: The challenge and solution have been manually checked on a physical micro:bit through the :bitForge review workflow.
Blocks-friendly: The MakeCode Python solution stays within code that MakeCode can represent as blocks.
Library: Challenges published by :bitForge. Publication and physical-device testing are separate states.
Saved Work: Complete draft challenges stored in the current browser profile. They do not synchronize across devices and may be lost when browser data is cleared.
Library tag: An organizational label published by :bitForge. A user may hide it locally, but only Admin can change the shared default.
My tag: An organizational label stored only in the current browser. It can be added to Library or Saved Work challenges, backed up as JSON, renamed, or deleted without changing the shared Library.
Draft: A complete challenge in Saved Work that has not been published or verified on physical hardware.
Blueprint: A reviewed deterministic template that Mad Libs uses to create a complete challenge locally without calling an AI service.
Imported challenge: A draft loaded from validated JSON written by a person or produced by any external tool.
Generated challenge: A draft created with the optional OpenAI or Anthropic BYOK generator.
Submission: A draft sent to :bitForge for possible review and inclusion in the Library. Submission does not guarantee publication or verification.