Core Concepts

Assessors

Assessors analyze your codebase to discover patterns. They examine multiple files to identify consistent conventions in:

• File and folder structure
• Naming conventions
• Code organization patterns
• Import/export styles
• Error handling approaches

The output is a detailed pattern file and a specialized agent that understands these patterns.

Executors

Executors implement code one file at a time, following the patterns discovered by assessors. They:

• Read the pattern documentation before generating
• Match your existing code style exactly
• Validate each file before moving to the next
• Reference existing files as examples

There are separate executors for frontend and backend to handle domain-specific patterns.

Planners

Planners break features into implementable chunks. A chunk is:

• Small enough to implement in one session
• Self-contained with clear boundaries
• Testable independently
• Has explicit dependencies on other chunks

Good chunking is critical for successful implementation - it prevents scope creep and enables incremental progress.

Reviewers

Reviewers validate implemented code against your patterns and requirements. They check:

• Pattern compliance - does it match your conventions?
• Completeness - does it fulfill the requirements?
• Quality - are there any obvious issues?

Running review before human code review catches issues early.

Patterns vs Rules

Hypr distinguishes between patterns and rules:

Patterns are discovered, rules are added. You can add rule modules (like accessibility) to your agents.