# Follow the four commandments

1. **Keep it simple:** It’s easy to get carried away with your sample project. Aim to keep it as simple as you can, while still accomplishing the goals you set out in your outline.
2. **Be practical:** The best sample projects show how to “re-implement a cool behavior found in app X”, or “provide a solution to this common question/problem” because you know that is a useful thing that people want to know how to do. Don’t be abstract; be practical.
3. **Remember how it fits in:** As you work on the sample project, always consider how it will fit into a teaching format. Think about the order in which you’ll implement features of the project, what parts will be challenges, etc.

   Remember to keep your project focused on a single learning objective. Don’t let the project distract the student with unnecessary work unrelated to the main topic.
4. **Use the latest and greatest:** You should always use the latest versions of any tools, libraries, OSs, etc. This will give your sample project the longest possible shelf life.


---

# 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://playbook.wednesday.is/communications/content/processes/articles/sample-project/follow-the-four-commandments.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.