learningfoundry 0.2.0__tar.gz

learningfoundry-0.2.0/.github/workflows/publish.yml

@@ -0,0 +1,49 @@
+name: Publish to PyPI
+
+on:
+  push:
+    tags:
+      - "v*"
+
+jobs:
+  build:
+    name: Build distribution
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - name: Install build
+        run: pip install build
+
+      - name: Build sdist and wheel
+        run: python -m build
+
+      - name: Upload distribution artifacts
+        uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    name: Publish to PyPI
+    needs: build
+    runs-on: ubuntu-latest
+    environment:
+      name: pypi
+      url: https://pypi.org/p/learningfoundry
+    permissions:
+      id-token: write  # required for OIDC trusted publishing
+    steps:
+      - name: Download distribution artifacts
+        uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1

learningfoundry-0.2.0/.gitignore

@@ -0,0 +1,42 @@
+# macOS only
+.DS_Store
+
+# Python build and test artifacts
+__pycache__
+*.pyc
+*.pyo
+*.pyd
+*.egg-info
+*.egg
+.coverage
+coverage.xml
+htmlcov/
+.pytest_cache/
+dist/
+build/
+
+# Jupyter notebooks
+.ipynb_checkpoints/
+*.ipynb_checkpoints
+
+# Pyve virtual environment
+.pyve/testenv
+.envrc
+.env
+.venv
+
+
+
+
+# Node / SvelteKit
+node_modules/
+.svelte-kit/
+.output/
+.vercel/
+.netlify/
+
+# TypeScript
+*.tsbuildinfo
+
+# project-guide
+docs/project-guide/**/*.bak.*

learningfoundry-0.2.0/.project-guide.yml

@@ -0,0 +1,5 @@
+version: '2.0'
+installed_version: 2.3.9
+target_dir: docs/project-guide
+metadata_file: .metadata.yml
+current_mode: plan_stories

learningfoundry-0.2.0/.pyve/config

@@ -0,0 +1,6 @@
+pyve_version: "1.13.2"
+backend: venv
+venv:
+  directory: .venv
+python:
+  version: 3.14.4

learningfoundry-0.2.0/.tool-versions

@@ -0,0 +1 @@
+python 3.12.13

learningfoundry-0.2.0/CHANGELOG.md

@@ -0,0 +1,23 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+## [0.2.0] - 2026-04-15
+
+### Added
+
+- `.github/workflows/publish.yml` — publishes sdist + wheel to PyPI on `v*` tag push via OIDC trusted publishing
+
+## [0.1.0] - 2026-04-15
+
+### Added
+
+- `src/learningfoundry/__init__.py` with `__version__ = "0.1.0"`
+- `src/learningfoundry/py.typed` PEP 561 marker
+- `src/learningfoundry/cli.py` Click entry point with `--version` flag
+- `src/learningfoundry/__main__.py` enabling `python -m learningfoundry`

learningfoundry-0.2.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

learningfoundry-0.2.0/PKG-INFO

@@ -0,0 +1,13 @@
+Metadata-Version: 2.4
+Name: learningfoundry
+Version: 0.2.0
+Summary: A curriculum engine that turns a YAML curriculum definition into a deployable SvelteKit learning application.
+Author: Pointmatic
+License-Expression: Apache-2.0
+License-File: LICENSE
+Requires-Python: >=3.12
+Requires-Dist: click>=8.1
+Requires-Dist: pydantic>=2.0
+Requires-Dist: pyyaml>=6.0
+Provides-Extra: quizazz
+Requires-Dist: quizazz-builder>=0.1; extra == 'quizazz'

learningfoundry-0.2.0/README.md

@@ -0,0 +1,19 @@
+# learningfoundry
+
+[![License](https://img.shields.io/badge/License-Apache%202.0-blue.svg)](LICENSE)
+
+A curriculum engine that turns a YAML curriculum definition into a deployable SvelteKit learning application — with LLM-generated content, interactive assessments, executable notebooks, and data visualizations — in a single pipeline.
+
+## Installation
+
+```bash
+pip install learningfoundry
+```
+
+## Usage
+
+```bash
+learningfoundry build
+```
+
+<!-- Full usage documentation coming soon. -->

learningfoundry-0.2.0/docs/project-guide/.metadata.yml

@@ -0,0 +1,195 @@
+common:
+  mode_templates_path: "project_guide/templates/project-guide/templates/modes"
+  artifact_templates_path: "project_guide/templates/project-guide/templates/artifacts"
+  spec_artifacts_path: "docs/specs"
+  root_artifacts_path: "."
+  web_root: "docs/site"
+  programming_language: python
+  test_command: pytest
+  test_invocation: "pyve run {{test_command}}"
+  default_code_mode: code_velocity
+
+modes:
+
+  # Default
+  - name: default
+    info: Getting started -- full project lifecycle overview
+    description: Default mode for new projects. Walks through setup, planning, and implementation with links to specific modes.
+    sequence_or_cycle: sequence
+    generation_type: document
+    mode_template: "{{mode_templates_path}}/default-mode.md"
+    next_mode: plan_concept
+
+  # Planning
+  - name: plan_concept
+    info: Generate a high-level concept (problem and solution space)
+    description: Define the problem space (problem statement, pain points, target users, value criteria) and the solution space (solution statement, goals, scope, constraints), and pain point to solution mapping.
+    sequence_or_cycle: sequence
+    generation_type: document
+    mode_template: "{{mode_templates_path}}/plan-concept-mode.md"
+    next_mode: plan_features
+    artifacts: 
+      - file: "{{spec_artifacts_path}}/concept.md"
+        action: create
+  - name: plan_features
+    info: Generate feature requirements (what the project does)
+    description: This is what the project does (functional and presentation requirements, not technical implementation).
+    sequence_or_cycle: sequence
+    generation_type: document
+    mode_template: "{{mode_templates_path}}/plan-features-mode.md"
+    next_mode: plan_tech_spec
+    artifacts:
+      - file: "{{spec_artifacts_path}}/features.md"
+        action: create
+    files_exist:
+      - "{{spec_artifacts_path}}/concept.md"
+  - name: plan_tech_spec
+    info: Generate a technical specification prompt (how it's built)
+    description: This details the requirements for how the project is built (architecture, modules, dependencies, but not code).
+    sequence_or_cycle: sequence
+    generation_type: document
+    mode_template: "{{mode_templates_path}}/plan-tech-spec-mode.md"
+    next_mode: plan_stories
+    artifacts:
+      - file: "{{spec_artifacts_path}}/tech-spec.md"
+        action: create
+      - file: "{{spec_artifacts_path}}/project-essentials.md"
+        action: create
+    files_exist:
+      - "{{spec_artifacts_path}}/concept.md"
+      - "{{spec_artifacts_path}}/features.md"
+  - name: plan_stories
+    info: Generate a user stories prompt
+    description: Based on the concept, features, and technical specification documents, scaffold the project, determine the implementation phases, and breakdown all that into stories.
+    sequence_or_cycle: sequence
+    generation_type: document
+    mode_template: "{{mode_templates_path}}/plan-stories-mode.md"
+    next_mode: project_scaffold
+    artifacts:
+      - file: "{{spec_artifacts_path}}/stories.md"
+        action: create
+    files_exist:
+      - "{{spec_artifacts_path}}/concept.md"
+      - "{{spec_artifacts_path}}/features.md"
+      - "{{spec_artifacts_path}}/tech-spec.md"
+
+  # Post-Release
+  - name: archive_stories
+    info: Archive docs/specs/stories.md and re-render a fresh one for the next phase
+    description: Move the current stories.md to .archive/ under a version-stamped name derived from the latest story, and re-render an empty stories.md from the artifact template preserving the `## Future` section.
+    sequence_or_cycle: sequence
+    generation_type: document
+    mode_template: "{{mode_templates_path}}/archive-stories-mode.md"
+    next_mode: plan_phase
+    artifacts:
+      - file: "{{spec_artifacts_path}}/stories.md"
+        action: archive
+    files_exist:
+      - "{{spec_artifacts_path}}/stories.md"
+  - name: plan_phase
+    info: Generate a feature phase prompt, which includes a mini-concept, features, and technical details
+    description: Based on a specific request from the developer, develop a combined concept, features, and technical specification document that describes the gap to fill, then create a new phase in the stories document, and breakdown all that into stories.
+    sequence_or_cycle: sequence
+    generation_type: document
+    mode_template: "{{mode_templates_path}}/plan-phase-mode.md"
+    next_mode: "{{default_code_mode}}"
+    artifacts:
+      - file: "{{spec_artifacts_path}}/new-phase-{{phase_name}}.md"
+      - file: "{{spec_artifacts_path}}/stories.md"
+        action: modify
+      - file: "{{spec_artifacts_path}}/project-essentials.md"
+        action: modify
+    files_exist:
+      - "{{spec_artifacts_path}}/concept.md"
+      - "{{spec_artifacts_path}}/features.md"
+      - "{{spec_artifacts_path}}/tech-spec.md"
+      - "{{spec_artifacts_path}}/stories.md"
+
+  # Scaffold
+  - name: project_scaffold
+    info: Scaffold the project foundation (LICENSE, headers, manifest, README, CHANGELOG)
+    description: One-time project scaffolding after planning. Creates license, copyright headers, package manifest, README with badges, CHANGELOG, and .gitignore based on decisions made during planning.
+    sequence_or_cycle: sequence
+    generation_type: document
+    mode_template: "{{mode_templates_path}}/project-scaffold-mode.md"
+    next_mode: "{{default_code_mode}}"
+    files_exist:
+      - "{{spec_artifacts_path}}/concept.md"
+      - "{{spec_artifacts_path}}/features.md"
+      - "{{spec_artifacts_path}}/tech-spec.md"
+      - "{{spec_artifacts_path}}/stories.md"
+
+  # Pre-Release
+  - name: document_brand
+    info: Develop and document branding for the project
+    description: Define the canonical source of truth for all descriptive language about the project brand for the project. All consumer files (README.md, docs/index.html, pyproject.toml, features.md) should draw from these definitions.
+    sequence_or_cycle: sequence
+    generation_type: document
+    mode_template: "{{mode_templates_path}}/document-brand-mode.md"
+    artifacts:
+      - file: "{{spec_artifacts_path}}/brand-descriptions.md"
+        action: create
+    files_exist:
+      - "{{spec_artifacts_path}}/concept.md"
+      - "{{spec_artifacts_path}}/features.md"
+  - name: document_landing
+    info: Generate a GitHub landing page and markdown support documentation using MkDocs
+    description: TBD.
+    sequence_or_cycle: sequence
+    generation_type: document
+    mode_template: "{{mode_templates_path}}/document-landing-mode.md"
+    artifacts:
+      - webpage: "{{web_root}}/index.md"
+        action: create
+      - framework: mkdocs
+        action: create
+    files_exist:
+      - "{{spec_artifacts_path}}/concept.md"
+      - "{{spec_artifacts_path}}/features.md"
+      - "{{spec_artifacts_path}}/tech-spec.md"
+      - "{{spec_artifacts_path}}/stories.md"
+      - "{{spec_artifacts_path}}/brand-descriptions.md"
+ 
+  # Code modes
+  - name: code_velocity
+    info: Generate code with velocity
+    description: TBD.
+    sequence_or_cycle: cycle
+    generation_type: code
+    mode_template: "{{mode_templates_path}}/code-velocity-mode.md"
+    files_exist:
+      - "{{spec_artifacts_path}}/stories.md"
+      - "{{root_artifacts_path}}/CHANGELOG.md"
+  - name: code_test_first
+    info: Generate code with a test-first approach
+    description: TBD.
+    sequence_or_cycle: cycle
+    generation_type: code
+    mode_template: "{{mode_templates_path}}/code-test-first-mode.md"
+    files_exist:
+      - "{{spec_artifacts_path}}/stories.md"
+  - name: debug
+    info: Debug code with a test-first approach
+    description: TBD.
+    sequence_or_cycle: cycle
+    generation_type: code
+    mode_template: "{{mode_templates_path}}/debug-mode.md"
+    files_exist:
+      - "{{spec_artifacts_path}}/stories.md"
+
+  # Refactoring modes
+  - name: refactor_plan
+    info: Update planning artifacts (concept, features, tech-spec)
+    description: Rewrite or update existing planning documents because of new features or improvements, including concept, features, and tech-spec. You can also migrate legacy project-guide planning documents--it will preserve information while restructuring into standardized sections.
+    sequence_or_cycle: cycle
+    generation_type: document
+    mode_template: "{{mode_templates_path}}/refactor-plan-mode.md"
+    artifacts:
+      - file: "{{spec_artifacts_path}}/project-essentials.md"
+        action: modify
+  - name: refactor_document
+    info: Update documentation artifacts (README, brand descriptions, landing page, MkDocs)
+    description: Update existing documentation files because of new features or improvements, including README, brand descriptions, landing page, and MkDocs configuration. You can also migrate legacy project-guide documentation--it will preserve information while restructuring into standardized sections.
+    sequence_or_cycle: cycle
+    generation_type: document
+    mode_template: "{{mode_templates_path}}/refactor-document-mode.md"

learningfoundry-0.2.0/docs/project-guide/README.md

@@ -0,0 +1,51 @@
+# Guides Directory
+
+**IMPORTANT: Needs update**
+
+This directory contains documentation for LLM-assisted development workflows and developer reference materials.
+
+## Project Workflow Overview
+
+The LLM creates or improves the following documents **in order**, waiting for developer approval after each one:
+
+| Step | Document | Purpose |
+|------|----------|---------|
+| 1 | `docs/specs/features.md` | What the project does (requirements, not implementation) |
+| 2 | `docs/specs/tech-spec.md` | How the project is built (architecture, modules, dependencies) |
+| 3 | `docs/specs/stories.md` | Step-by-step implementation plan (phases, stories, checklists) |
+
+After all three documents are approved, the LLM proceeds to scaffold the project and implement stories one by one.
+
+## Development Mode – Focused LLM Prompts
+
+Project-Guide provides structured instructions for LLMs to follow when working on projects focused on the subset of tasks that are needed, called a "mode":
+
+- **`project_guide.md`** - Core workflow for LLM-assisted project creation from scratch. Read this at the start of every new project session.
+- **`best_practices_guide.md`** - Diagnostic patterns and anti-patterns for evaluating project quality. Use for occasional audits.
+- **`debug_guide.md`** - Test-driven debugging methodology for fixing bugs in existing projects.
+- **`documentation-setup-guide.md`** - Step-by-step workflow for setting up GitHub Pages documentation with MkDocs and custom landing pages.
+
+## Developer-Focused Guides
+
+The `developer/` subdirectory contains manual setup instructions and troubleshooting guides for human developers:
+
+- Manual service configuration (e.g., Codecov, PyPI trusted publishers)
+- Troubleshooting references
+- One-time setup procedures
+- Production mode workflow and GitHub repository setup
+
+These guides are primarily for manual setup tasks, but LLMs may reference excerpts when providing step-by-step instructions or documenting procedures in stories.
+
+## Usage
+
+**For LLMs:**
+- Consult `go-project_guide.md` at the start of every project session
+
+**???**
+- Reference `debug_guide.md` when bugs are reported
+- Use `documentation-setup-guide.md` when setting up public documentation
+- Check `best_practices_guide.md` when auditing project quality
+
+**For Developers:**
+- Refer to `developer/` guides for manual setup tasks
+- Use these guides as troubleshooting references