From 7ee1866fe3a4e7fa5f626ca7b6a83efffa400c5c Mon Sep 17 00:00:00 2001 From: Jev Date: Sun, 22 Feb 2026 12:21:39 +0100 Subject: [PATCH] add claude and gitignore --- .../.claude/commands/architect.md | 53 ++++++++++++++++++ {{cookiecutter.project_slug}}/.gitignore | 56 +++++++++++++++++++ 2 files changed, 109 insertions(+) create mode 100644 {{cookiecutter.project_slug}}/.claude/commands/architect.md create mode 100644 {{cookiecutter.project_slug}}/.gitignore diff --git a/{{cookiecutter.project_slug}}/.claude/commands/architect.md b/{{cookiecutter.project_slug}}/.claude/commands/architect.md new file mode 100644 index 0000000..9294aa9 --- /dev/null +++ b/{{cookiecutter.project_slug}}/.claude/commands/architect.md @@ -0,0 +1,53 @@ +--- +description: Create architectural overview +argument-hint: [files or context] +--- + +You are a senior software architect. Before designing anything, identify what +you don't know. Ask me up to 5 clarifying questions — prioritize questions +that would change the architecture. Wait for my answers before proceeding. + +the project documentation is in `docs` folder. +For context, use `docs/user-stories.md` file if available. + + +Once you have enough context, produce a project architecture document `docs/architecture.md` with these sections: + +# Architecture: [Project Name] + +## Problem and context +What problem this solves and for whom. + +## Goals and non-goals +Numbered goals with measurable criteria. Explicit non-goals. + +## System overview +One paragraph. Then a Mermaid component diagram showing the major +components, their responsibilities, and how they communicate. + +## Technology stack +| Component | Technology | Version | Rationale | + +## Module boundaries +For each module: what it owns, its public interface, and what it must NOT +do. Communication patterns between modules (sync/async, events, RPC). + +## Key architectural decisions +For each significant decision: +- **Decision:** What was chosen +- **Alternatives considered:** What else was evaluated +- **Rationale:** Why this option + +## Constraints and conventions +Tech stack rules, naming conventions, forbidden libraries, coding patterns +to follow project-wide. + +## Open questions +Unresolved items that will be decided at feature-design time. + +--- +Rules: +- Keep the document as short as reasonably possible +- Mermaid diagrams only (no images) +- Be specific — version numbers, concrete patterns, not "we will use best practices" +- Flag every assumption with [ASSUMPTION] diff --git a/{{cookiecutter.project_slug}}/.gitignore b/{{cookiecutter.project_slug}}/.gitignore new file mode 100644 index 0000000..c0ae060 --- /dev/null +++ b/{{cookiecutter.project_slug}}/.gitignore @@ -0,0 +1,56 @@ +# Byte-compiled / optimized / DLL files +__pycache__/ +*.py[cod] +*$py.class + +# C extensions +*.so + +# Distribution / packaging +.Python +build/ +dist/ +*.egg-info/ +.eggs/ +*.egg +pip-wheel-metadata/ + +# Virtual environments +.venv/ +venv/ +env/ +ENV/ + +# Installer logs +pip-log.txt +pip-delete-this-directory.txt + +# Unit test / coverage reports +.pytest_cache/ +.coverage +.coverage.* +htmlcov/ +coverage.xml + +# Type checkers / linters +.mypy_cache/ +.pyre/ +.pytype/ +.ruff_cache/ +*_cache/ + +# Jupyter Notebook +.ipynb_checkpoints/ + +# pyenv +.python-version + +# IDEs and editors +.vscode/ +.idea/ +*.swp +*.swo + +# OS files +.DS_Store +Thumbs.db