FICTIONAL PRACTICE PROJECT: Cedar Desk Repair FAQ

Purpose: make a local, offline-readable FAQ page for a fictional desk-repair business. No real business or customer data is involved.

Approved facts:
- Business name: Cedar Desk Repair (fictional).
- Service: inspection and repair of freestanding office desks.
- Service area: the fictional Harbor District.
- Appointments: Tuesday–Friday, 10:00–16:00, by arrangement.
- To request an estimate, customers would describe the issue and provide desk dimensions. This practice page collects nothing.
- Price: quote after inspection; no fixed price has been approved.
- Warranty: not yet decided. Display “Warranty details: ask before booking.”

Create exactly one index.html with inline CSS and no JavaScript or external assets. Include a clearly visible fictional-practice label, page title, brief introduction, and five question-and-answer sections covering service, area, appointments, estimates and warranty. Use semantic headings, readable contrast and a narrow-screen layout. No forms, tracking, booking links, fabricated contact information or external network requests.

Keep this project-brief.txt unchanged. Create review-notes.txt listing changed files, checks actually performed, checks not run and remaining questions. Work only in this practice folder. No deployment, account connection, paid service, package installation or system-setting changes. Local file preview is enough. Any actual later publication requires a separate decision and verified real business facts.


PROMPT TEMPLATE
Read project-brief.txt in the selected practice folder. First confirm the folder path, list existing files and summarize relevant project instructions. Explain a short plan and stop before editing.

After I approve that plan, create the local FAQ page exactly to the brief. Edit only index.html and review-notes.txt. Preserve all existing unrelated files and instruction files. Use plain HTML with inline CSS, no JavaScript, dependencies, forms, tracking or external assets. Do not connect accounts, deploy, publish, install software or access anything outside the practice folder.

Show the changed files and explain their diff. Check all five required answers against the brief, including unknown price and warranty. Report actual checks separately from suggested/manual checks. Do not claim browser preview, accessibility compliance or tests passed unless supported by what you actually did. If a command or permission request exceeds this scope, explain the need before proceeding. Provide a local file path I can open and a concise review checklist.


Original synthetic practice material from https://aiandcompanies.com/workflows/getting-started-with-codex-and-claude-code-cli/