[update] readme, tutorial spec, and add a tutorial catalogue.

Author: vmarcella

README.md

@@ -17,6 +17,7 @@
         1. [Optional dependencies](#opt_deps)
         1. [Linux, Macos, Windows](#bash)
 1. [Getting started](#get_started)
+1. [Tutorials](#tutorials)
 1. [Examples](#examples)
 1. [Planned additions](#plans)
 1. [Releases & Publishing](#publishing)
@@ -110,7 +111,19 @@ If this works successfully, then lambda is ready to work on your system!
 ## Getting started <a name="get_started"></a>
 Coming soon.
 
+## Tutorials <a name="tutorials"></a>
+Start with the tutorials to build features step by step:
+
+- Tutorials index: [docs/tutorials/](./docs/tutorials/)
+- Uniform Buffers: Build a Spinning Triangle: [docs/tutorials/uniform-buffers.md](./docs/tutorials/uniform-buffers.md)
+
 ## Examples <a name="examples"></a>
+Browse example sources:
+
+- Core API examples: [crates/lambda-rs/examples/](./crates/lambda-rs/examples/)
+- Logging examples: [crates/lambda-rs-logging/examples/](./crates/lambda-rs-logging/examples/)
+- Argument parsing examples: [crates/lambda-rs-args/examples/](./crates/lambda-rs-args/examples/)
+
 ### Minimal
 A minimal example of an application with a working window using lambda.
 ```rust

docs/specs/_spec-template.md

@@ -0,0 +1,108 @@
+---
+title: "<short, descriptive title>"
+document_id: "<stable-id, e.g., subsystem-YYYY-MM-DD>"
+status: "draft"              # draft | living | frozen | deprecated
+created: "<UTC ISO-8601>"   # e.g., 2025-10-17T00:00:00Z
+last_updated: "<UTC ISO-8601>"
+version: "0.1.0"
+engine_workspace_version: "2023.1.30"
+wgpu_version: "26.0.1"
+shader_backend_default: "naga"
+winit_version: "0.29.10"
+repo_commit: "<git sha at update>"
+owners: ["lambda-sh"]
+reviewers: ["engine", "rendering"]
+tags: ["spec", "<area>"]
+---
+
+# <Specification Title>
+
+Summary
+- State the problem and the desired outcome in one paragraph.
+- Include a concise rationale for introducing or changing behavior.
+
+## Scope
+
+- Goals
+  - List concrete, testable goals.
+- Non-Goals
+  - List items explicitly out of scope.
+
+## Terminology
+
+- Define domain terms and acronyms on first use (for example, uniform buffer
+  object (UBO)). Use the acronym thereafter.
+
+## Architecture Overview
+
+- Describe components, data flow, and boundaries with existing modules.
+- Include a small ASCII diagram if it materially aids understanding.
+
+## Design
+
+- API Surface
+  - Enumerate public types, builders, functions, and commands.
+  - Use code identifiers with backticks (for example, `RenderCommand`).
+- Behavior
+  - Specify observable behavior, constraints, and edge cases.
+  - Use normative language (MUST/SHOULD/MAY) where appropriate.
+- Validation and Errors
+  - Document validation rules and the layer that enforces them.
+  - Describe error conditions and error types.
+
+## Constraints and Rules
+
+- Platform and device limits that apply (for example, alignments, size caps).
+- Data layout or serialization rules, if any.
+
+## Performance Considerations
+
+- Recommendations
+  - State performance guidance succinctly.
+  - Rationale: Provide a short reason for each recommendation.
+
+## Requirements Checklist
+
+- Functionality
+  - [ ] Feature flags defined (if applicable)
+  - [ ] Core behavior implemented
+  - [ ] Edge cases handled (list)
+- API Surface
+  - [ ] Public types and builders implemented
+  - [ ] Commands/entry points exposed
+  - [ ] Backwards compatibility assessed
+- Validation and Errors
+  - [ ] Input validation implemented
+  - [ ] Device/limit checks implemented
+  - [ ] Error reporting specified and implemented
+- Performance
+  - [ ] Critical paths profiled or reasoned
+  - [ ] Memory usage characterized
+  - [ ] Recommendations documented
+- Documentation and Examples
+  - [ ] User-facing docs updated
+  - [ ] Minimal example(s) added/updated
+  - [ ] Migration notes (if applicable)
+
+For each checked item, include a reference to a commit, pull request, or file
+path that demonstrates the implementation.
+
+## Verification and Testing
+
+- Unit Tests
+  - Describe coverage targets and representative cases.
+  - Commands: `cargo test -p <crate> -- --nocapture`
+- Integration Tests
+  - Describe scenarios and expected outputs.
+  - Commands: `cargo test --workspace`
+- Manual Checks (if necessary)
+  - Short, deterministic steps to validate behavior.
+
+## Compatibility and Migration
+
+- Enumerate breaking changes and migration steps, or state “None”.
+- Note interactions with feature flags or environment variables.
+
+## Changelog
+
+- <YYYY-MM-DD> (v0.1.0) — Initial draft.

docs/tutorials/README.md

@@ -0,0 +1,25 @@
+---
+title: "Tutorials Index"
+document_id: "tutorials-index-2025-10-17"
+status: "living"
+created: "2025-10-17T00:20:00Z"
+last_updated: "2025-10-17T00:20:00Z"
+version: "0.1.0"
+engine_workspace_version: "2023.1.30"
+wgpu_version: "26.0.1"
+shader_backend_default: "naga"
+winit_version: "0.29.10"
+repo_commit: "93c85ccbc3863ecffc73e68fb340c5d45df89377"
+owners: ["lambda-sh"]
+reviewers: ["engine", "rendering"]
+tags: ["index", "tutorials", "docs"]
+---
+
+This index lists tutorials that teach specific engine tasks through complete, incremental builds.
+
+- Uniform Buffers: Build a Spinning Triangle — `docs/tutorials/uniform-buffers.md`
+
+Browse all tutorials in this directory.
+
+Changelog
+- 0.1.0 (2025-10-17): Initial index with uniform buffers tutorial.