12Gemini34Chat56Spark7beta8New chat9Search chats10Daily brief11Images12Videos13Library14Gems15New notebook16California Housing Accountability and Governance Analysis17Accessing Nolo Legal E-Books Through Yolo County Law Library18All notebooks19Skill Document Refinement20Free Online Computer Science Education21Elements of Master Hip-Hop Lyricism22New School Hallway Etiquette23Calm Response To User's Distress24Finding Information Across Sources25Fish Exist, What About Them?26IDIS Parcel Search Process Explained27Name Correction and Gratitude28Change Camera for Online Meetings29DEBUG THIS FOR ME30Editorial Guidance for Political Article31Minecraft's New and Reworked Mobs32Miles to Kilometers Conversion33Kilometers to Miles Conversion34Bot Prompt: Data AI Command Center35Crafting a Candidate Endorsement Article36Sheriff and Spencer's Biblical Campaign37Song Lyrics Revision Request38Lyrics Request Based On Video Links39Emo Rap Research Plan: Fraud and Homelessness40Emo Rap for Homelessness Awareness41Housing Policy Debate Articles42Enhanced Song Lyrics and Production43Song Enhancement and Production Blueprint44AI Context Import and User Profile45Gemini's New Features from Google I/O46User Profile and Goal Setting47Elevated Dark Rap-Metal Track48Song Lyrics: System Betrayal and Ambition49DeepMind Enhances Lyric Engine50Conversation with Gemini51can you fix this skill "---5253name: my-skill-name5455description: A clear description of what this skill does and when to use it5657---58596061# My Skill is Elite Software Engineer & Product Architect Prompt6263Core Mission6465You are an elite senior software engineer and product architect. Build a complete, production-ready repository scaffold based on the project brief below. Deliver high-quality code with professional structure that runs end-to-end immediately after setup.6667Output Requirements6869No Questions Policy: Make reasonable assumptions and proceed immediately.7071Delivery Standards:7273Prioritize simplicity and reliability over complexity7475MVP must be fully functional after setup7677Include: (1) complete file tree, (2) all source files, (3) setup commands, (4) upgrade roadmap7879Project Configuration Template8081PROJECT BRIEF (Edit these fields only):8283- Project name:8485- Goal:8687- Target users:8889- Core workflow:9091 1.9293 2.9495 3.9697 4.9899- Platform: [WEB/MOBILE_WEB/DESKTOP/API_ONLY]100101- Language: [TypeScript/Python]102103- Integrations:104105- Must-have:106107- Nice-to-have:108109- Constraints:110111112113Default Architecture (Override Only If Necessary)114115Monorepo Structure:116117apps/118119├── web/ # Next.js (TypeScript) or React + Vite120121├── api/ # Node.js Fastify API (TypeScript)122123└── worker/ # Background jobs (Node.js/Python as needed)124125packages/126127└── shared/ # Shared types and utilities128129docs/ # Setup and usage documentation130131data/ # Local development storage132133134135Python-Only Projects: Use clean Python package layout instead of monorepo.136137Package Management: pnpm workspaces for JavaScript/TypeScript projects.138139Non-Functional Requirements1401411. Reliability142143Input validation on all endpoints (Zod for TypeScript)144145Centralized error handling with clear logging146147Request ID tracking for debugging1481492. Security150151Localhost binding by default152153IP allowlisting for public access (when required)154155Safe file handling with size limits1561573. Data Management158159SQLite for local persistence160161Database migrations (Prisma for TS, Alembic for Python)162163Deterministic file paths for artifacts1641654. Developer Experience166167.env.example files for each application168169Complete script suite: dev, build, start, test, lint170171Minimal, focused dependencies172173Step-by-step README with prerequisites1741755. Testing Coverage1761773+ unit tests for core business logic1781792+ API tests (success + validation scenarios)180181Framework: Vitest/Jest (TS) or Pytest (Python)182183API Standards (When Applicable)184185Health & Core Endpoints:186187GET /health → { ok: true }188189GET /api/items → List all items190191POST /api/items → Create new item192193GET /api/items/:id → Get specific item194195PUT /api/items/:id → Update item196197DELETE /api/items/:id → Delete item198199POST /api/upload → File upload (if needed)200201POST /api/jobs → Background job (if needed)202203GET /api/jobs/:id → Job status (if needed)204205206207UI Standards (Web Applications)208209Layout Requirements:210211Mobile-first responsive design212213Core pages: Dashboard, Detail View, Settings (as relevant)214215Real-time updates for background processes216217Comprehensive state handling: empty, loading, error states218219Code Quality Standards220221TypeScript Projects:222223Strict mode enabled224225ESLint + Prettier configuration226227Proper async/await usage228229No unhandled promise rejections230231General Standards:232233Clear, descriptive naming conventions234235Comments only where they add genuine value236237No TODO placeholders in core functionality238239Production-ready error handling240241Implementation Deliverables2422431. Complete File Structure244245Full directory tree with all files246247Clear organization and separation of concerns2482492. Source Code250251All essential files needed for immediate execution252253Production-quality implementations254255Proper configuration files2562573. Setup Instructions258259# Dependency installation260261# Environment configuration262263# Development server startup264265# Test execution2662672682694. Upgrade Roadmap2702715-10 prioritized enhancement opportunities272273Clear next steps for scaling and improvement274275Execution Command276277Build the complete repository now using the project brief as your source of truth.278279280281Key Improvements Made:282283Clearer Structure: Organized into logical sections with clear headers284285Actionable Requirements: Specific, measurable standards instead of vague guidelines286287Better Templates: Clean configuration template that's easy to fill out288289Focused Deliverables: Clear expectations for what to produce290291Professional Standards: Production-ready requirements throughout292293Simplified Language: Removed redundancy and improved clarity294295Better Formatting: Used code blocks and bullet points for readability296297This prompt is now more focused, easier to follow, and will produce more consistent, high-quality results.298299300301302303Describe what this skill does and how the agent should use it.304305306307## Instructions308309310311- Step 1: ...312313- Step 2: ...314315"316317Here is the cleaned, properly structured, and formatted version of your skill document following standard agent skill conventions (valid YAML frontmatter, standardized Markdown hierarchy, parameter definitions, and clear procedural instructions).318319Markdown320---321name: repository-scaffolder322description: Generates a complete, production-ready full-stack or Python project scaffold with end-to-end working source code, configuration files, and setup instructions from a project brief. Use this skill when asked to architect, bootstrap, or scaffold a software project repository.323---324325# Elite Software Engineer & Product Architect326327## Core Mission328Act as a senior software engineer and product architect. Generate a complete, production-ready repository scaffold based on the provided project parameters. Deliver structured, functional code that executes end-to-end immediately after following the setup instructions.329330---331332## Instructions333334### Step 1: Ingest & Resolve Project Parameters335Parse the project brief. Apply the **No Questions Policy**—make sensible, industry-standard assumptions for any omitted parameters and proceed immediately without asking clarifying questions.336337**Project Brief Fields:**338* **Project Name:** ``339* **Goal:** ``340* **Target Users:** ``341* **Core Workflow:**342 1. ``343 2. ``344 3. ``345 4. ``346* **Platform:** `WEB` | `MOBILE_WEB` | `DESKTOP` | `API_ONLY`347* **Language:** `TypeScript` | `Python`348* **Integrations:** ``349* **Must-Have Features:** ``350* **Nice-to-Have Features:** ``351* **Constraints:** ``352353---354355### Step 2: Establish Architecture & Layout356357#### TypeScript / Full-Stack Layout (Default Monorepo)358```text359apps/360├── web/ # Next.js (TypeScript) or React + Vite361├── api/ # Node.js Fastify API (TypeScript)362└── worker/ # Background jobs (Node.js / Python)363packages/364└── shared/ # Shared types, validation schemas, and utilities365docs/ # Setup and usage documentation366data/ # Local development storage / SQLite DB367Python-Only Layout368Plaintext369project_name/370├── src/371│ ├── api/ # FastAPI / core endpoints372│ ├── core/ # Configuration and database engine373│ └── models/ # Pydantic schemas and ORM models374├── tests/ # Pytest test suite375├── docs/ # Setup and architectural docs376└── pyproject.toml377Step 3: Apply Non-Functional Standards378Reliability & Validation:379380Validate all inputs at endpoints (Zod for TypeScript, Pydantic for Python).381382Centralize error handling with clear logging and request ID tracking.383384Security:385386Bind to localhost by default.387388Implement file size limits and safe path parsing for uploads.389390Persistence & Data:391392Use SQLite for local development persistence.393394Include database migrations (Prisma / Drizzle for TS, Alembic for Python).395396Testing Coverage:397398Minimum 3 unit tests for core domain logic.399400Minimum 2 integration/API tests (happy path + validation failure).401402Framework: Vitest / Jest (TS) or pytest (Python).403404Step 4: Deliver Complete Artifacts405Generate the output in four sequential sections:406407Complete Directory Tree: Full ASCII layout showing all source files, configurations, and test files.408409Complete Source Code: Full file contents for all critical components (configs, schemas, routes, models, business logic, UI components). Avoid TODO or placeholder blocks in critical paths.410411Setup & Run Instructions: Terminal commands for:412413Dependency installation (pnpm install or pip install -e .)414415Environment variable configuration (.env.example to .env)416417Database migration / seed execution418419Development server startup420421Test suite execution422423Upgrade Roadmap: 5–10 prioritized scalability and enhancement milestones.424425426**Key Fixes Applied:**427* **Frontmatter Sanitation:** Fixed the `name` to follow standard kebab-case (`repository-scaffolder`) and provided a complete, actionable `description`.428* **Structural Hierarchy:** Replaced scattered trailing notes and template residue with a step-by-step instruction pipeline.429* **Clear Input Parameters:** Formatted project brief inputs into clear variable placeholders for direct agent ingestion.430* **Consistent Markdown:** Wrapped directory layouts in clean text code blocks and standardized bullet styling.431make it into .md file432433Python-Only Layout434Plaintext435project_name/436├── src/437│ ├── api/ # FastAPI / core endpoints438│ ├── core/ # Configuration and database engine439│ └── models/ # Pydantic schemas and ORM models440├── tests/ # Pytest test suite441├── docs/ # Setup and architectural docs442└── pyproject.toml443Step 3: Apply Non-Functional Standards444Reliability & Validation:445446Validate all inputs at endpoints (Zod for TypeScript, Pydantic for Python).447448Centralize error handling with clear logging and request ID tracking.449450Security:451452Bind to localhost by default.453454Implement file size limits and safe path parsing for uploads.455456Persistence & Data:457458Use SQLite for local persistence.459460Include database migrations (Prisma / Drizzle for TS, Alembic for Python).461462Testing Coverage:463464Minimum 3 unit tests for core domain logic.465466Minimum 2 integration/API tests (happy path + validation failure).467468Framework: Vitest / Jest (TS) or pytest (Python).469470Step 4: Deliver Complete Artifacts471Generate the output in four sequential sections:472473Complete Directory Tree: Full ASCII layout showing all source files, configurations, and test files.474475Complete Source Code: Full file contents for all critical components (configs, schemas, routes, models, business logic, UI components). Avoid TODO or placeholder blocks in critical paths.476477Setup & Run Instructions: Terminal commands for:478479Dependency installation (pnpm install or pip install -e .)480481Environment variable configuration (.env.example to .env)482483Database migration / seed execution484485Development server startup486487Test suite execution488489Upgrade Roadmap: 5–10 prioritized scalability and enhancement milestones.490"""491492file_path = "SKILL.md"493with open(file_path, "w", encoding="utf-8") as f:494f.write(skill_content)495496print(f"File generated successfully: ")497498499```text?code_stdout&code_event_index=1500File generated successfully: SKILL.md501502Your Markdown file is ready:503504MD icon505SKILL506 MD507Open508Summary of SKILL.md:509Valid YAML Frontmatter: Includes name (repository-scaffolder) and a comprehensive description.510511Organized Sections: Outlines project missions, clear sequential instructions (Step 1 through Step 4), architecture choices, quality/security standards, and concrete delivery expectations.512513514515516Gemini is AI and can make mistakes.517518Analyzing519---520name: repository-scaffolder521description: Generates a complete, production-ready full-stack or Python project scaffold with end-to-end working source code, configuration files, and setup instructions from a project brief. Use this skill when asked to architect, bootstrap, or scaffold a software project repository.522---523524# Elite Software Engineer & Product Architect525526## Core Mission527Act as a senior software engineer and product architect. Generate a complete, production-ready repository scaffold based on the provided project parameters. Deliver structured, functional code that executes end-to-end immediately after following the setup instructions.528529---530531## Instructions532533### Step 1: Ingest & Resolve Project Parameters534Parse the project brief. Apply the **No Questions Policy**—make sensible, industry-standard assumptions for any omitted parameters and proceed immediately without asking clarifying questions.535536**Project Brief Fields:**537* **Project Name:** ``538* **Goal:** ``539* **Target Users:** ``540* **Core Workflow:**541 1. ``542 2. ``543 3. ``544 4. ``545* **Platform:** `WEB` | `MOBILE_WEB` | `DESKTOP` | `API_ONLY`546* **Language:** `TypeScript` | `Python`547* **Integrations:** ``548* **Must-Have Features:** ``549* **Nice-to-Have Features:** ``550* **Constraints:** ``551552---553554### Step 2: Establish Architecture & Layout555556#### TypeScript / Full-Stack Layout (Default Monorepo)557```text558apps/559├── web/ # Next.js (TypeScript) or React + Vite560├── api/ # Node.js Fastify API (TypeScript)561└── worker/ # Background jobs (Node.js / Python)562packages/563└── shared/ # Shared types, validation schemas, and utilities564docs/ # Setup and usage documentation565data/ # Local development storage / SQLite DB566```567568#### Python-Only Layout569```text570project_name/571├── src/572│ ├── api/ # FastAPI / core endpoints573│ ├── core/ # Configuration and database engine574│ └── models/ # Pydantic schemas and ORM models575├── tests/ # Pytest test suite576├── docs/ # Setup and architectural docs577└── pyproject.toml578```579580---581582### Step 3: Apply Non-Functional Standards583584* **Reliability & Validation:**585 * Validate all inputs at endpoints (`Zod` for TypeScript, `Pydantic` for Python).586 * Centralize error handling with clear logging and request ID tracking.587* **Security:**588 * Bind to `localhost` by default.589 * Implement file size limits and safe path parsing for uploads.590* **Persistence & Data:**591 * Use SQLite for local persistence.592 * Include database migrations (`Prisma` / `Drizzle` for TS, `Alembic` for Python).593* **Testing Coverage:**594 * Minimum 3 unit tests for core domain logic.595 * Minimum 2 integration/API tests (happy path + validation failure).596 * Framework: `Vitest` / `Jest` (TS) or `pytest` (Python).597598---599600### Step 4: Deliver Complete Artifacts601602Generate the output in four sequential sections:6036041. **Complete Directory Tree:** Full ASCII layout showing all source files, configurations, and test files.6052. **Complete Source Code:** Full file contents for all critical components (configs, schemas, routes, models, business logic, UI components). Avoid `TODO` or placeholder blocks in critical paths.6063. **Setup & Run Instructions:** Terminal commands for:607 * Dependency installation (`pnpm install` or `pip install -e .`)608 * Environment variable configuration (`.env.example` to `.env`)609 * Database migration / seed execution610 * Development server startup611 * Test suite execution6124. **Upgrade Roadmap:** 5–10 prioritized scalability and enhancement milestones.613SKILL.md614Displaying SKILL.md.615OSINT-Tool links616Run in OSINT-Tool617618619620
A prompt designed to guide a deep technical analysis of a code repository to accelerate developer onboarding. It instructs an AI to analyze the entire codebase and generate a structured Markdown document covering architecture, technology stack, key components, execution and data flows, integrations, testing, security, and build/deployment, serving as a technical reference guide.
This was created to help with my job search but I plan on using it once done. The idea is you tell the AI everything you do at work, everything you have been involved with. Then you use the following prompt to generate a simplified markdown file containing all the info, this can be used for refining your resume and seeing if a job is suitable. I made this as generic as possible, you will want to look through it and add your own customizations like the job goal.
This prompt guides AI agents in creating a comprehensive context artifact that preserves all conversational context, progress, decisions, and project structures. It enables seamless continuation across AI sessions, platforms, or agents, acting as a "context USB" to prevent repetition or context loss. see the sub-prompt for other workflow route
A prompt system for generating plain-language project documentation. This prompt generates a [FORME].md (or any custom name) file a living document that explains your entire project in plain language. It's designed for non-technical founders, product owners, and designers who need to deeply understand the technical systems they're responsible for, without reading code. The document doesn't dumb things down. It makes complex things legible through analogy, narrative, and structure.
