Micro-Tool Website Playbook

When working with zod, reference the local source under:
`$(opensrc path zod)`
Do not guess API names. Search the source first, then implement.

Build a form validation module using zod.

Before coding:
1. Search `$(opensrc path zod)/src` for the correct schema API and .parse() patterns.
2. Note which files/functions you used as reference.
3. Implement only the minimal validation function.
4. Keep the diff small.
5. Tell me which source files you looked at.

When working with [library/tool], reference the local source under:
`reference/repos/github.com/company/project`.
Do not guess API names. Search the source first, then implement.

Build [feature]. We use [library/tool].

Before coding:
1. Search `reference/repos/github.com/company/project` for the correct API and patterns.
2. Identify the files/functions/examples you used as reference.
3. Implement only the minimal service function and one calling route/component.
4. Keep the diff small.
5. Explain which source files you referenced.

Always Use:
- astro, tailwind-4-docs, web-design-guidelines (these 3 skills every project)
- DESIGN.md for this project's visual design

Install MCPs for your tech stack before starting.
Start new sessions frequently.
Always use git — commit after each working milestone.

I have initialized a new AstroJS project. Use the astro-docs MCP,
tailwind-4-docs skill, and web-design-guidelines skill.
Also use @DESIGN.md. Keep the design like Vercel.

Name: [Your Tool Name]
Domain: [yourdomain.com]

Create a [describe your tool]. My competitor is [URL] — go to this
website, analyze it, identify weaknesses, and build a better version.
Do not copy the competitor's design or UI.
Use MPA architecture for best SEO.

Do the on-page SEO of this website for:
Main Keyword: [your keyword]
Supporting Keywords: [comma-separated list from Ahrefs]

Also add proper OG meta tags. Write 600 words about the tool
on the home page for SEO.

Add an SEO-friendly FAQ section using JSON-LD structured data
for these questions:
[paste questions from Ahrefs "Questions" tab + Google "People Also Ask"]

Use FAQ JSON-LD schema with @type: FAQPage and Question/Answer pairs.

Create these pages as separate MPA routes for best SEO:
- Privacy Policy
- Terms & Conditions
- About Us
- Contact Us

Make them visible and linked in the home page footer and header.
This should be a multi-page application (MPA) for best SEO.

https://yoursite.pages.dev/*
  X-Robots-Tag: noindex

CRITICAL CONTEXT COMPRESSION: Summarize our entire session up to this point.
Include: 1) The overarching goal, 2) Key technical decisions made,
3) Files modified and current state, and 4) The exact next steps required.
Format as a dense, context-rich prompt I can paste into a new session to
instantly resume. Output ONLY the summary prompt, nothing else.

We are building using an agentic engineering workflow.

Rules:
1. Keep the change small and reviewable.
2. Search existing code before creating new abstractions.
3. If using a package/framework, reference its source or official repo before guessing APIs.
4. Build the minimal working version first.
5. After it works, run a code-structure cleanup pass.
6. Run relevant tests/typechecks.
7. Summarize what changed, what was tested, and what needs human judgment.

Task: [describe the feature or fix here]