⏯️

When to Use Copressan

Copressan isn't meant to replace natural writing. It is a tool that shines in specific contexts. Let's explore when to use it, and importantly, when not to.

Perfect Uses

Project tracking becomes instantly clearer:

Website Launch{
    status=in development
    priorities{
        user auth
        payment system=urgent
        database setup
    }
    timeline{
        testing->[2 weeks]
        fixes->[1 week]
        launch->[October 1]
    }
}

Quick decision mapping helps clear thinking:

House Choice{
    Option A{
        price=[400k]
        location=downtown
        space=[2] bedrooms
        pros{
            close to work
            new building
            good views
        }
    }
    Option B{
        price=[350k]
        location=suburb
        space=[3] bedrooms
        pros{
            quieter
            bigger yard
            better schools
        }
    }
}

Natural Integration

Copressan works best when embedded within regular writing like so:

Here is our team's current project status.

Development{
    complete{
        frontend
        basic backend
        user testing=[phase 1]
    }
    pending{
        security audit
        performance tests
        documentation
    }
}

This gives us a clear snapshot without breaking the flow of discussion. Another example is this article itself.

Prompting LLMs

Copressan is especially good for prompting, I predict that this will be where people strongly notice its benefits.

Here's an example of prompting an LLM to code a frontend website using Copressan:

Web App{
    type=react
    app{
        name=Weather Dashboard
        features{
            current conditions
            hourly forecast=[24h]
            weekly view=[7 days]
        }
        components{
            header{
                search bar
                location display
                units toggle=[C/F]
            }
            main display{
                temperature
                conditions
                wind speed
                humidity
            }
            charts{
                temperature trend
                precipitation chance
                wind pattern
            }
        }
        style{
            theme=minimal
            colors=[blue, white, gray]
            responsive=true
        }
    }
    requirements{
        mobile friendly
        loading states
        error handling
        api=OpenWeather
    }
}

Here's what makes prompting better in copressan:

Clear component hierarchy
No filler words that might disrupt the model
Low token cost

This is clearer than a paragraph describing all these requirements, and the AI knows exactly what structure to generate for cheaper.

When Not to Use

Copressan isn't suited for:

Emotional or personal messages
Detailed explanations needing context
Narrative writing

Instead of:

Feeling{
    mood=sad
    reason{
        work stress
        tired
        missing home
    }
}

Simply write: "I'm feeling down today because of work stress, exhaustion, and homesickness."

Best Practices

Use Copressan when:

Organizing information hierarchically
Planning projects or events
Taking structured notes
Creating quick reference guides
Mapping out decisions
Summarizing complex data
...and alike

Here are some tips… in Copressan!

Integration Tips{
    methods{
        embed in documents
        use as quick references
        combine with prose
    }
    goal{
        clarity=enhanced
        understanding=quick
        complexity=reduced
    }
}

Let Copressan handle the structured, hierarchical information while natural language carries the narrative and emotion.

Copressan is a tool for clarity, not a replacement for every liguistic expression. Use it when it makes understanding easier, not when it adds unnecessary structure to simple ideas.