Skip to content

Standards

Standards are project-level guidelines that define how work should be done. They capture coding conventions, architectural decisions, API patterns, and other reusable knowledge that agents can reference when working on tasks.

Standards are stored as markdown files in .neova/standards/.

Go to Settings → Standards to:

  • Create new standards
  • Edit existing standards
  • Delete standards you no longer need

Each standard has a unique ID (kebab-case) used to reference it in templates.

FieldDescription
idUnique identifier in kebab-case (e.g., api-design).
titleDisplay name shown in the UI.
descriptionShort summary of what the standard covers.
contentFull markdown content with guidelines and examples.

Reference standards in activity templates using replacement fields:

PatternDescription
{standards.key}File path to the standard
{standards.key.title}Display name
{standards.key.description}Short description
{standards.key.content}Full markdown content

Example:

Follow these API guidelines:
{standards.api-design.content}

When the template renders, the replacement field is replaced with the full content of your api-design standard.

Common standards you might create:

StandardPurpose
coding-styleCode formatting, naming conventions, file organization
api-designREST conventions, error handling, versioning
testingTest coverage requirements, testing patterns
securitySecurity guidelines, input validation, authentication
architectureSystem design decisions, component boundaries

Standards are stored as markdown files in .neova/standards/:

---
id: api-design
title: API Design Guidelines
description: REST API conventions and patterns for this project.
---
## Endpoints
- Use plural nouns for resources (`/users`, not `/user`)
- Use kebab-case for multi-word paths (`/user-profiles`)
## Response Format
Always return JSON with consistent structure:
\`\`\`json
{
"data": { ... },
"meta": { "timestamp": "..." }
}
\`\`\`
## Error Handling
Return appropriate HTTP status codes...