Skip to main content
A quick reference for Blitzy-specific terminology. Each entry links to the page where the concept is explained in detail.
Jump to: Platform & UI | Prompt & Generation | Artifacts & Review | Administration

​
Platform & UI

The official collection of workflows, standards, and processes for professional-grade AI-native development. Covers platform features, project lifecycle, administration, prompt engineering, and pull request review protocols. Learn more
One of the two primary UI modes in the Blitzy platform (toggled alongside the Workspace). The Knowledge Base lets you browse, search, and review Technical Specifications organized by repository and branch. Learn more
The primary UI mode in the Blitzy platform for active development. From the Workspace you write prompts, review Agent Action Plans, manage projects, and merge generated code. Toggle to the Knowledge Base for specification review. Learn more

​
Prompt & Generation

The prompt you write to tell Blitzy what code to generate or change. It can range from a brief request to a detailed specification; after submission, Blitzy produces an Agent Action Plan for your review. Learn more
A set of best practices for writing effective prompts that produce high-quality code generation results. Learn more
The process where Blitzy analyzes your existing codebase to understand its architecture, patterns, conventions, and domain terminology. Ingestion produces a Technical Specification and is required for existing codebases (not needed for greenfield projects). Learn more
An optional prompt you provide during ingestion to enrich the Technical Specification with business context, domain terminology, compliance requirements, and architectural decisions that are not visible in the code itself. Learn more
A ready-to-use, structured prompt for common scenarios such as adding features, fixing bugs, refactoring, or onboarding a codebase. Templates are available in the prompt library and can be customized to fit your project. Learn more
Reusable directives you attach to a project that enforce quality and analysis standards during every code generation. Each rule has a name and a description. Rules persist across generations, can be shared with teams, and apply across projects and languages. Learn more
The process where Blitzy compiles and tests generated code in isolated environments before creating a pull request. The depth of validation scales with your environment configuration, from basic build checks to full end-to-end testing with databases and APIs. Learn more

​
Artifacts & Review

A structured implementation plan that Blitzy produces after you submit a generation prompt. It details every file change, dependency, and design decision before any code is written. You review, edit, and approve it as your primary control point for code generation. Learn more
The process of reviewing Blitzy-generated pull requests. Blitzy’s review model is layered: intent is validated at the AAP stage, runtime validation catches build errors, and code-level review focuses on integration and business logic. Learn more
Comprehensive documentation automatically generated alongside your code. It explains architecture decisions, file structure, key components, testing instructions, and next steps, serving as living documentation for your team. Learn more
A living knowledge base that Blitzy generates after ingesting your codebase. It documents architecture, patterns, conventions, domain terminology, and technical constraints across nine structured sections. The spec updates automatically as your code changes. Learn more

​
Administration

A file placed in your repository root (using .gitignore syntax) that permanently excludes files and directories from Blitzy’s analysis. Excluded files do not count toward subscription usage. Learn more
A configuration that tells Blitzy how to build and run your application. Includes setup instructions, toolchain versions, dependency commands, variables (non-sensitive), and secrets (encrypted credentials). Environments are attached to projects and determine the level of runtime validation Blitzy can perform. Learn more
The practice of embedding Blitzy into your existing software development lifecycle, including sprint planning, team roles, and development processes. Blitzy adapts to your workflow rather than replacing it. Learn more