Style Cards

Customize how micro-agents generate code to match your team's conventions

Style Cards

Style Cards customize how micro-agents generate code to match your team's conventions, project patterns, and preferences. They influence naming conventions, formatting, documentation style, and architectural patterns.

What Are Style Cards?

A Style Card is a configuration profile that tells micro-agents how to write code for your project. Instead of getting generic output, agents produce code that follows your team's established patterns.

Style Cards can be scoped to:

  • User - Personal preferences applied across all projects
  • Project - Team-wide conventions for a specific project
  • Task - Overrides for specific issues or tasks

Key Configuration Areas

Naming Conventions

Control how variables, functions, classes, and files are named:

| Element | Options | |---------|---------| | Variables | camelCase, snake_case, PascalCase, kebab-case | | Functions | camelCase, snake_case, PascalCase | | Classes | PascalCase, camelCase | | Constants | UPPER_SNAKE, camelCase | | Files | kebab-case, snake_case, camelCase |

Formatting

Define code formatting rules:

  • Indent style - 2 spaces, 4 spaces, or tabs
  • Line length - Maximum characters per line
  • Brace style - Same line or new line
  • Quote style - Single or double quotes
  • Semicolons - Required or omitted
  • Trailing commas - Included or excluded

Documentation

Set documentation expectations:

  • Doc style - JSDoc, docstring, Javadoc, or XML doc
  • Function docs - Required or optional
  • Class docs - Required or optional
  • Include examples - Whether to add usage examples

Architecture Patterns

Guide structural decisions:

  • Preferred design patterns (MVC, Repository, etc.)
  • Error handling approach (try/catch, Result types, etc.)
  • State management preferences
  • API design conventions

Creating a Style Card

  1. Navigate to Engineering Intelligence > Style Cards
  2. Click New Style Card
  3. Fill in the configuration sections
  4. Set the scope (User, Project, or Task)
  5. Save and activate the card

Using Predefined Templates

Elixion provides predefined style card templates for common setups:

  • TypeScript React - Modern React with TypeScript conventions
  • Python FastAPI - Python backend with FastAPI patterns
  • Go Microservice - Go service with standard patterns
  • Java Spring - Java with Spring Boot conventions

Select a template as your starting point and customize it to match your team's preferences.

Assigning to Projects

Style Cards can be assigned to specific projects so that all agents working on that project follow the same conventions:

  1. Open the style card you want to assign
  2. Click Assign to Project
  3. Select the target project
  4. The card will be active for all agent work in that project

Exporting Configuration

You can export your style card configuration as JSON for backup, sharing, or version control. Use the Export option from the style card menu.


Next: AI Agents Overview - Learn about the agents that use Style Cards