# Tactics

- [Principles](https://docs.leandesignsystem.org/tactics/principles.md): Tactics on the Principles layer describe the methodology’s foundational concepts.
- [Minimum Viable Design System](https://docs.leandesignsystem.org/tactics/principles/minimum-viable-design-system.md): We start with the building blocks we need today and validate them in the the context of ongoing projects at the first opportunity.
- [Design Codification](https://docs.leandesignsystem.org/tactics/principles/design-codification.md): Design Codification is the belief that all aspects shaping digital products should be defined as code, versioned, and collectively owned.
- [Win Friends, not Battles](https://docs.leandesignsystem.org/tactics/principles/win-friends-not-battles.md): Outlining proper Lean Design System etiquette.
- [Infrastructure](https://docs.leandesignsystem.org/tactics/infrastructure.md): Tactics on the Infrastructure layer describe what kind of organizational and technical structures can be derived from the Principles layer.
- [Steady Flow of Truth](https://docs.leandesignsystem.org/tactics/infrastructure/steady-flow-of-truth.md): We set up central repositories for our design system artifacts and establish a steady flow of components and optimizations between them.
- [Radical Modularity](https://docs.leandesignsystem.org/tactics/infrastructure/radical-modularity.md): We keep our interfaces clean and simple. We leverage 3rd party resources to their fullest and steer clear of common pitfalls.
- [A Name and a Place](https://docs.leandesignsystem.org/tactics/infrastructure/a-name-and-a-place.md): Making it official: We give our design system a (working) title and a hub.
- [Behaviors](https://docs.leandesignsystem.org/tactics/actions.md): Tactics on the Behaviors level describe how action can be taken on the individual level at any time. It also describes behaviors that should be actively fostered to ensure steady improvement.
- [Think Systems!](https://docs.leandesignsystem.org/tactics/actions/think-systems.md): We always build and design with systems in mind.
- [Tidy up!](https://docs.leandesignsystem.org/tactics/actions/clean-up.md): By constantly optimizing and simplifying our designs and implementations, we prune away redundancies and imperfections.
- [Canvas!](https://docs.leandesignsystem.org/tactics/actions/canvas.md): By striking a balance between talking and listening, we foster the cross-pollination of ideas.
- [Artifacts](https://docs.leandesignsystem.org/tactics/artifacts.md): Tactics on the Artifacts level describe the actual artifacts organized in the design system’s libraries and repositories.
- [Design Tokens](https://docs.leandesignsystem.org/tactics/artifacts/design-tokens.md): Design Tokens are a great starting point for Design Codification and help us embrace cross-functionality and collective ownership.
- [UI Kit](https://docs.leandesignsystem.org/tactics/artifacts/ui-kits.md): We consolidate our component designs in one central place to enable effortless exploration and prototyping.
- [A Living Handbook](https://docs.leandesignsystem.org/tactics/artifacts/a-living-handbook.md): We articulate and document a shared design system mission.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.leandesignsystem.org/tactics.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.