Development

Intent context defines what the user wants to get out of the model. For example, a system prompt usually serves as high-level instructions for how the user wants the model to behave. Most of the “prompting” done in Cursor is intent context. “Turn that button from blue to green” is an example of stated intent; it is prescriptive.

State context describes the state of the current world. Providing Cursor with error messages, console logs, images, and chunks of code are examples of context related to state. It is descriptive, not prescriptive.

Together, these two types of context work in harmony by describing the current state and desired future state, enabling Cursor to make useful coding suggestions.

1. Sequential schemes are suited to ordered data that progress from low to high. Lightness steps dominate the look of these schemes, with light colors for low data values to dark colors for high data values.

X TYPES OF COLOR SCHEMES 1. Sequential schemes are suited to ordered data that progress from low to high. Lightness steps dominate the look of these schemes, with light colors for low data values to dark colors for high data values. 2. Diverging schemes put equal emphasis on mid-range critical values and extremes at both ends of the data range. The critical class or break in the middle of the legend is emphasized with light colors and low and high extremes are emphasized with dark colors that have contrasting hues.

3. Qualitative schemes do not imply magnitude differences between legend classes, and hues are used to create the primary visual differences between classes. Qualitative schemes are best suited to representing nominal or categorical data.

The appearance and robustness of a color scheme is in part a product of what else goes on the map and the background over which you are trying to show your colors. Small differences in the color of linework or the presence of other map items (like labels) really has a big impact on the appearance of a color scheme, so be sure to try these options here before settling on a final color scheme. Overlay cities and roads for a first look at how well text and symbols can be read with the area colors you select. Though the examples we have chosen are highways and cities, they should give you a good idea of how other linework or typography will function on the map. We have also provided a grayscale DEM so you can see what happens to your colors when you combine them with other underlying map data: Generally speaking, colors become harder to distinguish and you will need to user fewer classes of data.

TIP: Try turning off the county borders or making them white; notice a big difference? Try changing the background surrounding the map to see how colors are changed by their surroundings.

Choosing the number of data classes is an important part of map design. Increasing the number of data classes will result in a more "information rich" map by decreasing the amount of data generalization. However, too many data classes may overwhelm the map reader with information and distract them from seeing general trends in the distribution. In addition, a large numbers of classes may compromise map legibility—more classes require more colors that become increasingly difficult to tell apart. Many cartographers advise that you use five to seven classes for a choropleth map. Isoline maps, or choropleth maps with very regular spatial patterns, can safely use more data classes because similar colors are seen next to each other, making them easier to distinguish.