Browse Prompts

Discover AI prompts shared by the community

Tags:

15 prompts available

Sort by:

SEO Optimization

You are an expert full-stack developer and technical SEO specialist. Goal: Review this entire website codebase and upgrade it to world-class SEO, WITHOUT breaking existing design, routing, or core UX. When you find an issue, fix it everywhere that pattern appears, not just in a single file. Do this: 1. Audit & plan - Scan the routing, layouts, templates, and components. - List the main SEO issues you find before making large changes. 2. On-page SEO - Ensure 1 clear `<h1>` per page, with logical heading hierarchy. - Create unique, descriptive `<title>` and `<meta name="description">` for each page/template. - Add meaningful `alt` text to images. - Improve internal links (descriptive anchor text, not “click here”). 3. Technical SEO - Ensure proper `robots.txt` and `sitemap.xml` (or framework equivalents). - Add canonical tags where needed. - Ensure clean, human-readable URLs for important content. - Confirm correct 404/500 handling and status codes. 4. Performance / Core Web Vitals - Optimize image sizes, formats, and lazy loading. - Reduce blocking JS/CSS; remove obvious unused code. - Use framework-idiomatic performance features (code-splitting, caching, etc.). 5. Structured data & social - Add JSON-LD for `WebSite` and `Organization`, plus `Article`/`BlogPosting`/`Product`/`FAQPage` where appropriate. - Add Open Graph and Twitter Card tags with sensible defaults and per-page overrides. 6. Safety & output - Do not add environment-specific URLs (e.g., localhost). - Preserve content meaning; do not invent facts. - When done, output: - A bullet list of key SEO changes (on-page, technical, performance, structured data). - Any breaking changes or trade-offs. - A short TODO list for remaining manual or content tasks.

developmentseofrontend

by Rex

Coding & Development

Code Review Extended Execution

Ok, let's update the code review document to reflect what we've done. Ensure we note what was accomplished, deferred and changed. Then, let's continue solving the remaining problems found in the code review document. Your core guidelines are 1) prioritize modularity 2) focus on documentation and maintainability 3) always ensure we build testing as we go, and use it to confirm things work before we move on to the next thing. Your task is to get as far as possible without user input. When you have reached the point where you cannot continue without user input, I want you to create a document (in a file called docs/development/sprint-xxx-report.md) that documents progress, decisions made, new challenges/questions/open issues that were surfaced, and what your suggested next steps are.

code-review

by Rex

Coding & Development

Update then Execute Code Review Doc

code-review

by Rex

Coding & Development

PRD Extended Execution

Ok, let's update the PRD to reflect what we've done. Ensure we note what was accomplished, deferred and changed. Then, let's continue executing against the PRD. Your core guidelines are 1) prioritize modularity 2) focus on documentation and maintainability 3) always ensure we build testing as we go, and use it to confirm things work before we move on to the next thing. Your task is to get as far as possible without user input. When you have reached the point where you cannot continue without user input, I want you to create a document (in a file called docs/development/sprint-xxx-report.md) that documents progress, decisions made, new challenges/questions/open issues that were surfaced, and what your suggested next steps are.

codingexecutionprd+1 more

by Rex

Coding & Development

Update then Execute the PRD

Ok, let's update the PRD to reflect what we've done. Ensure we note what was accomplished, deferred and changed. Then, let's continue executing against the PRD.

prdplanningexecute

by Rex

Coding & Development

Coding Session Starter Prompt

When we are working together, please follow these git workflow rules: 1. Commit liberally and often - Create git commits whenever you complete a logical unit of work (fixing a bug, adding a feature, refactoring a section, etc.) 2. NEVER push to GitHub without explicit permission - You may stage files (git add) and commit locally (git commit), but ONLY push to remote (git push) when I explicitly say "push to github" or similar. 3. Permission does NOT carry forward - If I say "commit and push" for one change, that permission applies ONLY to that specific commit. Future commits require NEW explicit permission to push. Think of it as: Local commits are safe and encouraged. Remote pushes require explicit approval each time. Understood? Before starting any dev server, always check for and kill existing processes on the target port Never run multiple dev servers for the same project simultaneously - kill old ones before starting new ones Use lsof -ti:[PORT] | xargs kill -9 to clean up ports before starting servers Minimize background processes - only keep necessary dev servers running (one per active project) When debugging, restart the existing server rather than spawning additional ones If starting a new background process, verify no duplicate processes exist first

codingstartstarting+1 more

by Rex

Coding & Development

Proactive Build Errors

When I paste a build error, don’t just fix the one line in the log. Identify the general pattern causing the error and apply a repo-wide fix: reason about all files where this same pattern could appear, and propose changes for every affected file in one pass. Summarize the root cause, list each file you’re changing, and then show the updated code.

debugerror

by Rex

Coding & Development

Extended Autonomous Coding Sprint

Your core guidelines are 1) prioritize modularity 2) focus on documentation and maintainability 3) always ensure we build testing as we go, and use it to confirm things work before we move on to the next thing. Your task is to get as far as possible without user input. When you have reached the point where you cannot continue without user input, I want you to create a document (in a file called docs/development/sprint-xxx-report.md) that documents progress, decisions made, new challenges/questions/open issues that were surfaced, and what your suggested next steps are.

developmentautomationdocumentation+2 more

by Rex

Coding & Development

Modular Development Guidelines

Set clear development principles for AI coding assistants: modularity, documentation, testing, and git workflow.

developmentgit-workflowbest-practices+2 more

by Rex Kirshner

Planning

Product Requirements Document (PRD) Planning

Generate comprehensive product requirements documents with emphasis on modularity, testability, and professional design. Creates structured planning documents that break complex projects into manageable steps.

planningprddocumentation+3 more

by Rex Kirshner

Development

Development Server Port Management

Essential guidelines for managing development server processes and ports. Prevents port conflicts, resource waste, and debugging confusion by ensuring clean process management.

developmentdevopsdebugging+3 more

by Rex Kirshner

Development

TypeScript Build Check Before Push

Ensure TypeScript code quality by running production builds before pushing. Catches type errors early and prevents broken code from reaching the repository.

typescriptbuildtesting+3 more

by Rex Kirshner

Development

AI Context System Feedback

Gather structured feedback from AI assistants about the AI Context System usage. Helps collect real-world insights for continuous improvement of development workflows.

ai-context-systemfeedbackdocumentation+2 more

by Rex Kirshner

Development

GitHub Workflow Rules

Clear git workflow rules for AI coding assistants to prevent unauthorized pushes while encouraging frequent commits. Establishes safe defaults for version control collaboration.

gitgithubversion-control+3 more

by Rex Kirshner

Development

Execution Core Guidelines

Essential coding guidelines for AI assistants to ensure modular, well-documented, and thoroughly tested code. Perfect for setting expectations at the start of development sessions.

developmentbest-practicestesting+3 more

by Rex Kirshner