Find a prompt. Copy it. Make it yours.

Implement a vertical slice of this feature — thinnest path end-to-end. Rules: - One happy path only — no edge cases yet unless trivial - Real persistence and UI wire-up, not mocks (unless spike labeled) - Tests for the happy path - List follow-up slices explicitly Goal: learn fast with something demoable today.

Explore this repository and draft an AGENTS.md for coding agents. Include only durable facts: - What the product does - Stack and key directories - How to run dev, test, lint - Database/auth conventions - What not to do (destructive migrations, etc.) Exclude secrets and one-off tickets. Keep under 80 lines. Use bullet points.

Draft incident communications from the facts I provide. Produce: 1. Internal Slack update (technical, timeline-focused) 2. External status page update (user impact, workaround, next update time) 3. What not to say yet (unknowns) Calm, factual tone. No ETA unless confident.

Write an architecture decision record for this choice. Sections: 1. Status (proposed) 2. Context and forces 3. Options considered 4. Decision and rationale 5. Consequences (positive, negative, risks) 6. Review date Keep it one to two pages. Link to code or tickets where relevant.

Split this epic into user stories small enough for a 1–3 day PR each. Each story needs: - Title - Acceptance criteria - Dependencies noted - MVP vs follow-up label Vertical slices over horizontal layers. First story should demo something user-visible.

Write empty state copy for this screen. Include: - Title (what's empty) - One sentence of context - Primary action label - Optional secondary action Friendly but concise. No illustrations suggestions unless asked.

Audit this UI for design system consistency. Find: - Hardcoded colors, spacing, radii, typography - One-off components duplicating existing primitives - Dark mode gaps Propose token mappings using existing theme variables. Minimal visual change unless fixing clear bugs.

Write a feature announcement email. Structure: - Subject line options (3) - Preview text - Body: what shipped, who benefits, one concrete example, single CTA - P.S. only if it adds real value Keep under 200 words. No hollow superlatives.

Create an SEO brief for this page topic. Deliver: - Primary intent and target reader - Title tag and meta description (character limits) - H1 and H2 outline - Internal link suggestions - FAQ schema candidates No keyword stuffing. Prefer helpful technical accuracy over volume.