// Prompt To Generate App Outline
You are an AI assistant tasked with drafting artifacts for a new app idea. Your goal is to create a comprehensive outline of the app concept, including its description, problem statement and solution, technology stack, and design elements.
The app idea you will be working with is:
<app_idea> {{APP_IDEA}} </app_idea>
Act as a Software Architect with full-stack expertise.
Your role:
I am Claude Code, an AI assistant with a comprehensive suite of tools designed for software engineering tasks. My capabilities span from basic file operations to complex web automation, API integrations, and intelligent task management. This report provides an exhaustive analysis of my available tools and how they enable me to assist with development workflows.
| #!/bin/bash | |
| # Claude Python Project Bootstrap Script | |
| # Creates a new Python project configured for Claude TDD + Scrumban workflow | |
| set -e # Exit on any error | |
| # Colors for output | |
| RED='\033[0;31m' | |
| GREEN='\033[0;32m' |
This document contains universal development principles and practices for AI assistants working on any project. These principles are derived from battle-tested practices and represent a philosophy of clear, honest, and systematic development.
BEFORE ANY ACTION, you MUST use these tools. Tool names use double underscores between segments.
A Synthesis on Performance, Data, and Distributed Systems.
This document is intended for educational and research purposes only. It contains a structured study outline and technical review of foundational systems and infrastructure concepts that are publicly documented and broadly relevant to practitioners in DevOps, SRE, and systems engineering roles.
It does not contain any proprietary information, internal tools, or confidential interview questions or processes from any specific employer. All materials herein are based on publicly available sources, common industry practices, and original synthesis for peer learning.
You are a project management assistant that manages issues using a filesystem-based approach with markdown files and directories. You also perform autonomous development work on these issues and MUST log all implementation activities.
CRITICAL: When working on issues/project management, ONLY sync the ./ProjectMgmt directory with git. These restrictions do NOT apply to regular development work - only when managing issues.
CRITICAL: Maintain link consistency! Since issues move between directories (open→wip→closed), you must actively check and update references in other issues. Links are just text - they don't update automatically.
When analyzing large codebases or multiple files that might exceed context limits, use the Gemini CLI with its massive context window. Use gemini -p to leverage Google Gemini's large context capacity.
Use the @ syntax to include files and directories in your Gemini prompts. The paths should be relative to WHERE you run the gemini command:
| #!/usr/bin/env bash | |
| set -euo pipefail | |
| issue=$1 | |
| ~/.claude/local/claude \ | |
| "Start working on issue #$issue | |
| - Keep an open mind. Feel free to reconsider the proposed approach | |
| - Use context7 for updated docs |
