David Paluy dpaluy

Global Development Principles

FUNDAMENTAL RULE: VERIFY EVERYTHING, ASSUME NOTHING

Before taking ANY action in ANY language or framework:

VERIFY the actual state of the codebase - read it, don't assume it
CHECK that files, functions, modules, and dependencies actually exist
READ the source code to understand actual implementations
CONFIRM exports, imports, and APIs match what you're trying to use
TEST your understanding with small verification steps

<Example: add this to your workflow>

SubTasks

Review the subtask. If anything is unclear, ask follow up questions
Upon subtask is completed, Run linter and tests and ensure they pass
Create a git commit
Declare "task is completed ✅"

Task Definition of Done (DoD)

I've got a personal finance app called Maybe Finance and want to produce more personal finance articles. Here's where that is on our site: @https://maybefinance.com/articles First, do keyword research and come up with 10 keywords and article ideas based on that research.

Let's narrow that down to the 5 most impactful and realistic opportunties. Here's our sitemap of existing content so we don't duplicate anything. @https://maybefinance.com/sitemap.xml]

Poll CI Status: $ARGUMENTS

Use this command when you need to wait for all GitHub checks on a pull-request to complete and then branch into success or failure flows.

Parameters (space-separated)

Pos	Name	Example	Purpose
1	`pr_id`	`123`	Pull-request number to monitor
2	`interval`	`15`	(optional, default 15 s) seconds between status polls
3	`timeout`	`600`	(optional, default 600 s) maximum wait in seconds

Instructions

The user will provide a task.
The task involves working with Git repositories in your current working directory.
Wait for all terminal commands to be completed (or terminate them) before finishing.

Git instructions

If completing the user's task requires writing or modifying files:

Do not create new branches.
Use git to commit your changes.
If pre-commit fails, fix issues and retry.

AGENTS.md spec

Containers often contain AGENTS.md files. These files can appear anywhere in the container's filesystem. Typical locations include /, ~, and in various places inside of Git repos.
These files are a way for humans to give you (the agent) instructions or tips for working within the container.
Some examples might be: coding conventions, info about how code is organized, or instructions for how to run or test code.
AGENTS.md files may provide instructions about PR messages (messages attached to a GitHub Pull Request produced by the agent, describing the PR). These instructions should be respected.
Instructions in AGENTS.md files:
- The scope of an AGENTS.md file is the entire directory tree rooted at the folder that contains it.
- For every file you touch in the final patch, you must obey instructions in any AGENTS.md file whose scope includes that file.
Instructions about code style, structure, naming, etc. apply only to code within the AGENTS.md file's scope, unless the f

gemini-2.0-flash-exp for iamge editing via API

Notes and Requirements

API Key: Replace 'YOUR_API_KEY' with your actual Google AI API key. You can obtain this from the Google Cloud Console after enabling the Gemini API.
Dependencies: Install the required libraries: pip install google-generativeai pillow requests

google-generativeai: The official Python library for the Google Gemini API.

	module CredentialsDemo
	class Application < Rails::Application
	creds = credentials[Rails.env.to_sym]
	.with_indifferent_access
	.transform_keys(&:upcase)
	.transform_values(&:to_s)
	ENV.merge! creds.merge(ENV)
	end
	end

	#!/usr/bin/env bash
	set -euo pipefail

	################################################################################
	# VARIABLES – adjust only if you really need something different
	################################################################################
	NODE_VERSION="22.12.0" # must match Dockerfile
	PNPM_VERSION="latest" # use a specific version if you prefer
	PARALLEL_JOBS="$(nproc)" # bundler / compile jobs

	You are in "Planner Mode". Deeply reflect upon the changes being asked and analyze existing code to map the full scope of changes needed.
	## Clarification Questions (If Necessary):
	- If, after this comprehensive, tool-based exploration, critical details essential for planning are still missing, ask up to three concise, high-value questions. These questions must arise from gaps identified during your exploration.

	Once answered, draft a comprehensive plan of action and ask me for approval on that plan. Once approved, summarize the final plan that can be implemented by a Code mode.
	You are not allowed to EDIT any file. You can READ any file