- Windows 10/11 or macOS
- Git installed
- Python 3.12+ installed
- Node.js 18+ installed (for Claude Code)
git clone https://github.com/ShuhanCS/conductscience-inventory.git
cd conductscience-inventory
pip install -r requirements.txt
- Sign up for Claude Max at https://claude.ai (use your ConductScience email)
- Install Claude Code:
npm install -g @anthropic-ai/claude-code
- Launch it once to authenticate:
claude
It will open a browser window to log in with your Claude account.
Ask Shuhan to create your personal WooCommerce API keys. You will receive:
- Staging key + secret — for day-to-day development
- Production key + secret — only if your role requires production writes (most people only need staging)
Your staging key will be scoped to the permissions your role requires (read-only, read-write, etc.).
cp .env.example .env
Open .env and paste in the keys you received. The .env file is gitignored — it never gets committed.
# Check that staging API works
python -c "from shared.config import WOO_STAGING_KEY; print('Staging key loaded' if WOO_STAGING_KEY else 'ERROR: No staging key')"
# Run the inventory status check
python status.py
- Staging first: All development and testing happens on staging. Production writes require approval.
- Never commit
.env: It's gitignored for a reason. If git prompts you to add it, decline.
- Never share your API keys: Each employee has their own. If you suspect a key is compromised, tell Shuhan immediately.
- Read CLAUDE.md: The project CLAUDE.md has all the rules for working with this codebase.
- Log in to https://staging.conductscience.com/wp-admin/
- Go to WooCommerce > Settings > Advanced > REST API
- Click Add key
- Set:
- Description: Employee name + role (e.g., "Jane - Inventory Read/Write")
- User: Select the appropriate WordPress user
- Permissions: Read/Write for most roles, Read only for view-only access
- Click Generate API key
- Send the Consumer Key and Consumer Secret to the employee securely
- Repeat for production if needed (https://conductscience.com/wp-admin/)