zachdaniel

Usage Rules

IMPORTANT: Consult these usage rules early and often when working with the packages listed below. Before attempting to use any of these packages or to discover if you should use them, review their usage rules to understand the correct patterns, conventions, and best practices.

zachdaniel

# class={classes("bar", foo: true)}

def classes(string) when is_binary(string) do
    string
  end

  def classes({class, condition}) do
    if condition do
      to_string(class)
    end

zachdaniel

```elixir
defmodule Thing do
  use Ash.TypedStruct

  typed_struct do
    field(:name, :string, allow_nil?: false)
  end
end
```

zachdaniel

# get current cmd before executing 
preexec() {
  export PLZ_CURRENT_COMMAND="$1"
}

# so we can provide it to plz
plz() {
  PLZ_FULL_CMD="$PLZ_CURRENT_COMMAND" $HOME/.dotfiles/scripts/plz "$@"
}

zachdaniel

Usage Rules

IMPORTANT: Consult these usage rules early and often when working with the packages listed below. Before attempting to use any of these packages or to discover if you should use them, review their usage rules to understand the correct patterns, conventions, and best practices.

zachdaniel

Usage Rules

IMPORTANT: Consult these usage rules early and often when working with the packages listed below. Before attempting to use any of these packages or to discover if you should use them, review their usage rules to understand the correct patterns, conventions, and best practices.

zachdaniel

action :analyze_sentiment, :atom do
  constraints one_of: [:positive, :negative]

  description """
  Analyzes the sentiment of a given piece of text to determine if it is overall positive or negative.
  """

  argument :text, :string do
    allow_nil? false
    description "The text for analysis"

zachdaniel

GENERAL TASK WORKFLOW

PHASE 1: TASK ANALYSIS (MANDATORY)

Step 1.1: Understand the Request

YOU MUST:

1. Parse what exactly is being asked
2. Identify if this is a feature (use feature.md) or fix (use fix.md)
3. If neither, continue with this workflow
4. Break down into specific, measurable subtasks

zachdaniel

BUG FIX WORKFLOW

THIS IS A MANDATORY WORKFLOW - ALL STEPS MUST BE COMPLETED IN ORDER

PHASE 1: UNDERSTANDING THE BUG (MANDATORY)

Step 1.1: Initial Investigation

REQUIRED ACTIONS:

• Get exact error message/behavior description
• Identify affected module/function using grep/glob

zachdaniel

FEATURE IMPLEMENTATION WORKFLOW

THIS IS A MANDATORY WORKFLOW - NO STEPS CAN BE SKIPPED

PHASE 1: RESEARCH & PLANNING (MANDATORY)

Step 1.1: Initial Research

YOU MUST USE ALL AVAILABLE RESOURCES:

• Check existing usage rules via get_usage_rules MCP tool or CLAUDE.md links
• Use package_docs_search for ALL potentially relevant packages