<essential_principles>

# Good - concise
fields :id, :name, :email, :created_at

# Only use singular when needed
field :full_name do |user|
  "#{user.first_name} #{user.last_name}"
end

</essential_principles>

<quick_reference>

fields :email, :name, :created_at end

Usage

UserBlueprint.render(user) # JSON string UserBlueprint.render_as_hash(user) # Ruby Hash

</pattern>

<pattern name="computed-field">
```ruby
field :full_name do |user|
  "#{user.first_name} #{user.last_name}"
end

# With options access
field :display_name do |user, options|
  options[:admin] ? user.admin_name : user.public_name
end

Usage

UserBlueprint.render(user, view: :extended)

</pattern>

<pattern name="conditional-field">
```ruby
field :salary, if: ->(field_name, user, options) { options[:show_salary] }
field :age, unless: ->(field_name, user, options) { user.hide_age? }

</quick_reference>

1. Create a new blueprint
2. Understand a specific concept (views, associations, transformers, etc.)
3. Debug a blueprint issue
4. Something else

For option 2, specify the concept and I'll load the relevant reference.

After reading, apply the knowledge to the user's specific situation.

<reference_index>

Core Concepts:

• fields-and-identifiers.md - Fields, identifiers, computed fields, field options
• views.md - Views, include/exclude, view inheritance
• associations.md - Nested blueprints, polymorphic associations

Advanced:

• configuration.md - Global config, JSON generators, field sorting
• transformers-and-extractors.md - Custom transformers and extractors
• conditionals-and-defaults.md - Conditional fields, defaults, nil handling

Troubleshooting:

• anti-patterns.md - Common mistakes and how to fix them

</reference_index>

<workflows_index>

Workflow	Purpose
create-blueprint.md	Create a new blueprint with proper structure
</workflows_index>