> For the complete documentation index, see [llms.txt](https://jig.gitbook.io/sley/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://jig.gitbook.io/sley/examples/typescript.md).
# TypeScript examples
Browse complete TypeScript projects by learning goal, Sley mechanism, and cognitive complexity.
Do not choose by ambition. Choose the smallest project that answers your next question, run it, and change one behavior. Complexity estimates cognitive load, not quality; lower is usually the more useful starting point.
## Start here
| Project | What it teaches | Sley mechanisms | Complexity |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------ | ------------------------------ | ---------: |
| TypeScript Hello World
Read the lesson
| Create one typed node, update shared state, and finish an ordinary leaf. | `node`, `state`, `run` | 1 |
| A Small Typed Workflow
Read the lesson
| Model a small three-step application as explicit topology. | `node`, `link`, `Flow` | 2 |
| Inspect a Compiled Flow
Read the lesson
| Inspect portable compiled topology and an explicit run result. | `compile`, `describe`, `start` | 2.5 |
## Composition and failure
| Project | What it teaches | Sley mechanisms | Complexity |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------- | --------------------------------------- | ---------: |
| Retry and Recovery in TypeScript
Read the lesson
| Retry a complete handler and recover locally after attempts fail. | `retry`, `recover`, `Failure` | 2.5 |
| Concurrent Service Checks
Read the lesson
| Check services concurrently and combine terminal outputs once. | `emit`, `end`, `combine` | 5.5 |
| Concurrent Nested Workers
Read the lesson
| Run a multi-step nested worker concurrently and combine its results. | `nested Flow`, `concurrency`, `combine` | 4 |
| Recovering a Partially Completed Batch
Read the lesson
| Recover a partial batch from settled terminal records. | `ScopeFailure`, `terminals`, `recover` | 6 |
## Agents and integrations
| Project | What it teaches | Sley mechanisms | Complexity |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------- | ------------------------------------------ | ---------: |
| Terminal Chat
Read the lesson
| Type shared state in a one-node loop with deliberate hard termination. | `unlabelled link`, `end`, `maxActivations` | 3.5 |
| Search Agent
Read the lesson
| Type state and branch input across a bounded search loop. | `emit`, `input`, `maxActivations` | 11 |
| MCP Tool Discovery and Execution
Read the lesson
| Discover, validate, and invoke one MCP tool in a linear Flow. | `async handler`, `input`, `validation` | 5.5 |
| Orchestrator and Workers
Read the lesson
| Freeze a dynamic plan, fan sections out, and integrate the results. | `emit`, `input`, `combine` | 4.5 |
| A Bounded Quality Loop
Read the lesson
| Compose benchmarked component loops, integration, and final evaluation. | `nested Flow`, `combine`, `maxActivations` | 7 |
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://jig.gitbook.io/sley/examples/typescript.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.