Imported from pinchiguillo/cf_wrangler_Bootstrap (AGENTS.md). Install upstream with npx skills add pinchiguillo/cf_wrangler_Bootstrap. Copyright stays with the author.

Repository Guidelines

Project Structure & Module Organization

This repository is currently minimal: the top level contains only .codex, and there is no application source tree, test suite, or build configuration yet. Keep new code organized from the start:

• src/ for application code
• tests/ for automated tests
• docs/ for design notes and operational documentation
• assets/ for static files such as images or fixtures

Prefer small, focused modules. Mirror source paths in tests where possible, for example src/auth/session.py with tests/auth/test_session.py.

Build, Test, and Development Commands

There are no project commands configured yet. Before adding features, introduce the runtime and its standard entry points, then document them here. Recommended baseline commands:

• make setup to install dependencies
• make test to run the full test suite
• make lint to run formatting and static checks
• make dev to start a local development server

If you do not add a Makefile, provide equivalent commands in README.md and keep them consistent with this guide.

Coding Style & Naming Conventions

Use 4-space indentation for code and Markdown lists. Prefer descriptive names over abbreviations.

• Python files and modules: snake_case
• Classes: PascalCase
• Constants: UPPER_SNAKE_CASE
• Test files: test_<unit>.py

Adopt automated formatting as soon as the language stack is chosen. For Python, use black and ruff; for JavaScript or TypeScript, use prettier and eslint.

Testing Guidelines

Every new feature should ship with tests. Place tests under tests/ and name them after the behavior they verify. Keep unit tests fast and deterministic; isolate external services behind mocks or fixtures.

Run the full suite before opening a pull request. If a change cannot be tested automatically, document the manual verification steps in the PR.

Commit & Pull Request Guidelines

This directory is not currently a Git repository, so there is no local commit history to infer conventions from. Use short, imperative commit messages such as Add initial session model or Document local setup.

Pull requests should include:

• a clear summary of the change
• linked issue or task reference when available
• test evidence or manual verification notes
• screenshots only for UI changes

Repository Notes

Do not assume hidden infrastructure or tooling exists in this folder. When introducing new build, test, or deployment workflows, update this file in the same change.