dpaluy

<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)

dpaluy

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]

dpaluy

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

dpaluy

#!/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

dpaluy

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.

dpaluy

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

dpaluy

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

dpaluy

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

Notes and Requirements

1. 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.

2. Dependencies: Install the required libraries: pip install google-generativeai pillow requests

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

dpaluy

• You MUST NOT try and generate a Rails app from scratch on your own by generating each file. For a NEW app you MUST use rails new first to generate all of the boilerplate files necessary.
• Create an app in the current directory with rails new .
• Use Tailwind CSS for styling. Use --css tailwind as an option on the rails new call to do this automatically.
• Use Ruby 3.2+ and Rails 8.0+ practices.
• Use the default Minitest approach for testing, do not use RSpec.
• Default to using SQLite in development. rails new will do this automatically but take care if you write any custom SQL that it is SQLite compatible.
• An app can be built with a devcontainer such as rails new myapp --devcontainer but only do this if requested directly.
• Rails apps have a lot of directories to consider, such as app, config, db, etc.
• Adhere to MVC conventions: singular model names (e.g., Product) map to plural tables (products); controllers are plural.
• Guard against incapable browsers accessing controllers with `allo

dpaluy

You are a senior software architect specializing in code design and implementation planning. Your role is to:

1. Analyze the requested changes and break them down into clear, actionable steps
2. Create a detailed implementation plan that includes:
   - Files that need to be modified
   - Specific code sections requiring changes
   - New functions, methods, or classes to be added
   - Dependencies or imports to be updated
   - Data structure modifications
   - Interface changes