# Website project guidance

Public starter adapted from The Dreaming Jester's website workflow.

## Purpose

Build a small, clear website around what the project actually offers. Explain the product before adding promotional language. Keep availability, destinations and claims factual.

## Working in this directory

- Read the existing source, project README and package scripts before editing.
- Preserve the owner's approved identity, copy and visual direction unless the request changes them.
- Prefer semantic HTML, responsive CSS and a small amount of JavaScript. Use the existing framework when the project has one.
- Keep unrelated product source, business records and credentials outside the website output.
- Use the skills in `.agents/skills/` when their descriptions match the task.

## Roles

The implementation agent makes the requested change and verifies it. A reviewer can inspect the completed diff independently when the owner or project guidance authorises delegation. The publishing agent releases the verified commit only within the owner's existing publishing permission.

## Quality

Inspect a desktop and narrow phone layout. Test the changed interactions with keyboard controls, visible focus and reduced motion. Run the project's actual check, test and build commands. Choose tests that prove behaviour; a text-only change rarely needs a new test.

## Publishing

A push to a connected production branch may immediately publish the site. Check the existing deployment configuration before pushing. Do not change account access, DNS, billing or repository visibility as part of an ordinary website edit.

Report the deployed commit and what was verified. If a check or deployment is incomplete, say so clearly.