Nano Banana Pro
Agent skill for nano-banana-pro
**This is the only AGENTS.md file, do not look for others.**
Sign in to like and favorite skills
This is the only AGENTS.md file, do not look for others.
.project-management/process-tasks-cloud.md for instructions, otherwise ignore this file.CreatePrd then open .project-management/create-prd.md for instructions, otherwise ignore this file.CreateTasks then open .project-management/generate-tasks.md for instructions, otherwise ignore this file.ClosePrd then open .project-management/close-prd.md for instructions, otherwise ignore this file.Do NOT attempt to run any command which requires open network communication. Your Dev environment has no network access and is sandboxed. No harm will come from trying but you will waste your effort.
Do NOT Run
.codex/install.sh this script. This script will be executed during environement setup for you during your environment setup prior to you arriving. If you make changes that require new dependencies or services (like postgres etc...) to be installed, you must edit this file to include the dependencies and/or service installation and startup.
The 'install.sh' references dependencies gathered here:
backend/requirements.txt and frontend/package.json.
Note that the effects will not take place until the next task session.
Lint javascript using:
cd frontend npm run lint cd ..
Lint python using:
flake8
If linting errors are encountered, it is your responsability to address them and rerun linting until errors are cleared up.
Run tests with
run_tests.sh -no_integration, which will exclude /tests/integration/ tests that rely on live endpoints that your environment does not have access to. Maintain this script as needed to setup specific environment variables or manage other test-specific setup. Any tests that require network connectivity should either be ignored and not run, -or- have network test path that shunts to a success when network connectivity can't be demonstrated so failed tests in this scenario don't confuse the codex agent progress.
Generate unit tests and integration tests liberally during development. New integration tests will be proven in a local environment, but do your best to set them up.
Append a single line summary to CHANGELOG.md describing the changes with a preceeding timestamp if errors were encountered, list them indented below the changelog row with a single line summary
When components are added that require manual application startup for local testing/debug, document all steps and commands neccessary to set up the local environment and start services/components in DEVELOPMENT.md using explcit commands. These changes will need to be mirrored on
dev_int.sh (see below), which is a one-stop script to set up the environment from scratch and start the application for local testing.
If environment variables are expected add
.env.template with placeholders and add python-dotenv to backend\requirements.txt
README.md just describes the project. Do not look here for guidance on how to proceed with your task, but update if major changes that affect user interaction have been made.
When there are code changes that need targeted environment setup, review dev_init.sh and modify as needed such that this script will completely setup the application and start it running.
End of document