Create STYLE_GUIDE.md

Generate a comprehensive, actionable development plan for building a responsive web application.

Use this prompt when the codebase has changed since the last FORME.md was written. It performs a diff between the documentation and current code, then produces only the sections that need updating not the entire document from scratch.

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.

Converts a knowledge-anchored dashboard specification into a restrained Diriyah-adjacent interface mockup with exact blank metric zones.

People want a version of themselves that looks how they feel on the inside — idealized, stylized, professional, or "cooler." Profile pictures are identity signals on every platform they use. Paying for a better signal is rational.

People want to practice before risking real money. The simulation sells the hope of being competent enough to invest eventually — and the journal analysis layer sells the hope of becoming the kind of person whose judgment improves over time. If simulation doesn't reflect real market mechanics, it feels like a toy and loses credibility. Slippage, transaction costs, and realistic price impact must be simulated.

—

Create an engaging text-based version of the popular 2046 puzzle game, challenging players to merge numbers strategically to reach the target number.

A skill for generating comprehensive Product Requirements Documents (PRDs) and technical documentation for projects.

Converts a structured security-audit workflow into a tactile national interface mockup with exact blank reporting zones.

—

The gap between "idea" and "first paying customer" is where most solo founders fail — not from lack of effort but from lack of a structured, day-by-day system. A tool that compresses that gap from months to 14 days with templates already customized to their specific idea removes the activation barrier that kills most ventures before they start. The market evolves faster than any fixed playbook. The prompts and templates that worked in 2024 may not work in 2026.