Which kind of Dotkernel application a repo is — API, Admin, Frontend, Light, or Queue — or a project derived from one of them.
Detected by dotkernel-application-variants and by session-start.sh, since conventions differ by variant.
Command
A .md file under .claude/commands/ with frontmatter (description, optional argument-hint, allowed-tools) that defines a /dk-* slash command.
Invoked explicitly by name, unlike a skill.
dot-maker
dotkernel/dot-maker, a Composer tool (composer make …) that scaffolds new modules, entities, services, handlers and more to Dotkernel's file structure and naming pattern.
Feature doc
A markdown file written by /dk-document describing what a feature does, why, and how to exercise it — the part of a change a cleared session can't reconstruct from src/ alone.
See Feature Documentation.
Frontmatter
The YAML block at the top of a SKILL.md or command .md file (name, description, etc.) that Claude Code reads to decide whether and how to load the file.
Guard
A hook that blocks a tool call outright rather than just reporting on it — guard-protected-paths.sh and guard-bash.sh.
Hook
A bash script registered in settings.json against a lifecycle event (SessionStart/PreToolUse/PostToolUse) that runs automatically when that event fires.
See Hooks.
Permission tier
One of deny, ask, or allow in settings.json's permissions block, governing whether a path or command is blocked outright, prompted for approval, or runs without a prompt.
See Permissions.
SKILL.md
The file every skill directory must contain — frontmatter plus an instructional body — that Claude Code loads into context when the skill fires.
Skill
A packaged set of instructions under .claude/skills/ that Claude Code auto-loads based on its description: frontmatter matching the current task, with no central routing table.
See Skills.
Subagent
A separately-invoked agent defined under .claude/agents/, used to keep bulk review work out of the main conversation's context.
Dotboost ships one: dotkernel-reviewer.