Drop in a screenshot and convert it to clean code (HTML/Tailwind/React/Vue)
Python
Update CLAUDE.md
Abi Raja31dc6cafd25d
diff --git a/CLAUDE.md b/CLAUDE.mdindex cd20d10b..e3b00e64 100644--- a/CLAUDE.md+++ b/CLAUDE.md@@ -1,12 +1,25 @@-# Coding Standards+# Project Agent Instructions-- For Python function, do not add docstrings.-- Ensure a trailing newline to any file that doesn't end with one-- Use type hints in Python to improve code readability and catch potential type-related errors early.-- We use poetry in the backend python project+Python environment:-# Testing+- Always use the backend Poetry virtualenv (`backend-py3.10`) for Python commands.+- Preferred invocation: `cd backend && poetry run <command>`.+- If you need to activate directly, use Poetry to discover it in the current environment:+ - `cd backend && poetry env activate` (then run the `source .../bin/activate` command it prints)-- Frontend tests: `yarn test` (from frontend directory) or `npm run test:frontend` (from root)-- Backend tests: `poetry run pytest` (from backend directory) or `npm run test:backend` (from root)-- Run all tests: `npm test` (from root directory)+Testing policy:++- Always run backend tests after every code change: `cd backend && poetry run pytest`.+- Always run type checking after every code change: `cd backend && poetry run pyright`.+- Type checking policy: no new warnings in changed files (`pyright`).++## Frontend++- Frontend: `cd frontend && yarn lint`++If changes touch both, run both sets.++## Prompt formatting++- Prefer triple-quoted strings (`"""..."""`) for multi-line prompt text.+- For interpolated multi-line prompts, prefer a single triple-quoted f-string over concatenated string fragments.