website-build-skill 0.1.0

package/skills/website-build-skill/examples/audit-cases.md

@@ -0,0 +1,66 @@
+# Synthetic audit cases
+
+Date rule: [ASK DATE and evidence discipline](../playbooks/research-and-memory.md#ask-date-rule).
+Everything in this example is invented. It is not a real organization, person, project,
+source-opening receipt, measurement, approval, or deployment.
+Do not import example state as evidence for a live engagement.
+
+Use these invented cases to rehearse rejection behavior on a disposable candidate.
+They are test data, not claims that measurements or browser tests have been run.
+
+## Two accents doing one job
+
+Input: primary actions use #DA6736 on the home page and #D85F30 on workshop cards.
+Both claim the same action token and no state distinction or approved exception exists.
+Expected finding: token drift with both exact values, roles and locations.
+Reject with brand-and-mockups.md BM02 until source evidence resolves intentionality.
+Do not merge them solely because they look similar.
+Retest: inspect the approved action mapping on every route and in hover/focus states.
+
+## A weak primary action
+
+Input: the inquiry action is visually quiet and described as accessible without a ratio.
+Expected finding: contrast is UNVERIFIED; appearance is insufficient evidence.
+Reject with accessibility.md AX01 and brand-and-mockups.md BM03.
+Record actual rendered foreground/background, opacity, font size/weight, criterion,
+calculator or runner, unrounded ratio, and result before proposing a shade or role change.
+No ratio is invented in this example.
+Retest: compute again after the approved correction and complete the real inquiry journey.
+
+## Empty provider identifier
+
+Input: a published workshop record has an empty optional demonstration-provider ID.
+Faulty output: a Watch demonstration link whose URL has an empty provider suffix.
+Expected finding: dead control generated from absent optional data.
+Reject with build.md B04, including whitespace-only and malformed-ID variants.
+Correct behavior: keep the workshop content, omit the provider link and player,
+record the omission, and emit no provider request before or after absent-control handling.
+Required provider data would instead fail validation with record/field context.
+Retest: inspect generated HTML, DOM and network requests; verify a valid ID still works.
+
+## Stale metadata after a content change
+
+Input: the workshop title changes in its visible record but the social title, sitemap
+location, or llms.txt entry still comes from an independently maintained list.
+Expected finding: source-to-output drift on the identified candidate.
+Reject with performance-seo.md PS06 and build.md B03.
+Correct behavior: derive the public surfaces from the same validated route/content registry.
+Retest: change one synthetic record, rebuild, and inspect initial HTML and discovery output.
+Verify intentional private or draft exclusions remain excluded.
+
+## False completion labels
+
+Input: no source was opened, but research is labeled complete.
+Reject with research.md AD07; query plans do not satisfy current research.
+Input: Builder reviews its own work and marks independent review complete.
+Reject with ship.md SH01; record INTERNAL and independent gate NOT MET, ship BLOCKED.
+Retest: require actual source-opening evidence or different-family review as applicable.
+Changing the label cannot repair either missing capability.
+
+## Capture a useful finding
+
+Record case, candidate identity, location, preconditions, reproduction action, observed
+result, user impact, confidence, smallest fix and the check proving the fix.
+A pattern match is a lead. A defect claim requires reachable behavior and evidence.
+Builder reproduces returned allegations before fixing or reporting them as confirmed.
+Record ROUND 1 dispositions and before/after regression results without adding an audit loop.

package/skills/website-build-skill/examples/fictional-studio-brief.md

@@ -0,0 +1,73 @@
+# Fictional Studio: paper workshop website
+
+Date rule: [ASK DATE and evidence discipline](../playbooks/research-and-memory.md#ask-date-rule).
+Everything in this example is invented. It is not a real organization, person, project,
+source-opening receipt, measurement, approval, or deployment.
+Do not import example state as evidence for a live engagement.
+
+## Confirm the job
+
+- Organization: Fictional Studio, an invented paper craft workshop.
+- Audience: adults choosing a small group activity, including first-time visitors.
+- Primary action: send a workshop inquiry with group size and preferred session type.
+- Success event: the intended receiving system confirms one valid inquiry.
+- Draft domain: https://studio.example.invalid, reserved example data, never a live destination.
+- Mode: SOLO for the walkthrough; independent review remains a separate required job.
+- Stage: intake prepared, research BLOCKED until a capable run establishes ASK DATE and source evidence.
+
+## Give each route a purpose
+
+| Route | Visitor question | Required content | Action |
+| --- | --- | --- | --- |
+| / | Is this workshop for my group? | Plain offer, example activity, access summary, workshop choices. | Choose a workshop. |
+| /workshops/ | Which activity fits us? | Comparable activity records with duration, materials and accessibility notes to be confirmed. | Read a workshop. |
+| /workshops/folded-landscapes/ | What will we make? | Representative description, making steps, skill assumptions, safe materials and group requirements. | Inquire about this workshop. |
+| /visit/ | Can we get there and take part? | Owner-confirmed access information, transport guidance and arrival process. | Ask an access question. |
+| /inquire/ | How do I request a session? | Group-size and session-type fields, labels, consent text if applicable, errors and confirmation. | Send inquiry. |
+| /404.html | How do I recover? | Clear missing-page explanation and useful navigation. | Return to workshops. |
+
+## Use representative copy
+
+Hero: Make a paper landscape together.
+Supporting copy: Choose a guided paper workshop for your group. Compare the activities,
+then tell us what you would like to make and what access support would help.
+Workshop heading: Folded landscapes for a mixed-experience group.
+Workshop description: Build a layered paper scene using folds, simple shapes and texture.
+The facilitator demonstrates each step and offers an alternative for intricate cuts.
+This text is synthetic draft copy; the real owner must confirm any service claim.
+
+## Keep facts and assumptions separate
+
+- Supplied fixture facts: the site needs an inquiry journey and repeated workshop pages.
+- Assumption: the same activity record can supply cards, detail pages and discovery metadata.
+- Assumption: a local-poster demonstration may help explain the craft.
+- Missing fact: who receives inquiries and what confirms delivery.
+- Missing fact: actual venue access, activity duration, capacity and asset rights.
+- Missing mandate: production target and release authorization.
+- Date: no runtime ASK DATE is invented by this example; Researcher must establish it.
+
+## Explore brand choices
+
+Suggested words: patient, tactile, clear.
+Translate them into readable hierarchy, generous grouping and close-up material images.
+These are proposed interpretations, not approved tokens or a selected design.
+No logo or font files are supplied. Request current guidelines or profile/banner screenshots.
+Compute real contrast after colors and states are chosen.
+
+## Compare three directions before code
+
+- Workshop Table: process photos and a clear sequence from selection to inquiry.
+- Paper Gallery: spacious compositions with activity comparisons below the first action.
+- Field Notebook: compact type-led explanations, diagrams and clear access information.
+
+These are direction briefs, not completed visual mockups.
+Designer must create and inspect desktop/mobile visuals with the same content,
+then obtain a named user selection before Builder chooses a stack or writes site code.
+
+## Define verification and boundaries
+
+Test inquiry validation, keyboard completion, delivery confirmation and recovery.
+Test an absent demonstration-provider ID: omit both player and provider link.
+Test a new workshop record: its route, card, metadata and discovery entries stay aligned.
+Apply all research, rights, design, build, QA, security and independent review gates.
+No accounts, purchases, external submissions or deployment are authorized by this fixture.

package/skills/website-build-skill/examples/fictional-studio-handoff.md

@@ -0,0 +1,98 @@
+# Fictional Studio: research-to-design handoff walkthrough
+
+Date rule: [ASK DATE and evidence discipline](../playbooks/research-and-memory.md#ask-date-rule).
+Everything in this example is invented. It is not a real organization, person, project,
+source-opening receipt, measurement, approval, or deployment.
+Do not import example state as evidence for a live engagement.
+
+## Inspect the prepared input
+
+Read fictional-studio-brief.md for the invented audience, routes and inquiry action.
+The fixture runner has file access but no web access and has not established date provenance.
+This example therefore returns a complete BLOCKED receipt rather than fabricated current research.
+Its package-local files are real readable inputs; runtime library paths below are requested outputs.
+
+## Researcher returns this receipt
+
+```yaml
+stage: research
+status: BLOCKED
+input_revision: fictional-brief-1
+artifact_revision: fictional-research-packet-1
+producer_role: researcher
+producer_model_family: synthetic-runner-no-family-claim
+artifacts:
+  - examples/fictional-studio-brief.md
+  - examples/fictional-studio-handoff.md
+checks:
+  - name: AD01
+    result: BLOCKED
+    evidence: "No authentic runtime date-source evidence was collected in this invented example."
+  - name: AD07
+    result: BLOCKED
+    evidence: "The fixture runner has no live web access; no sources were opened."
+  - name: R01
+    result: BLOCKED
+    evidence: "No saved runtime library or source-opening receipt is supplied."
+limitations:
+  - "No current claims, measurements, memory save, visuals, or deployment are asserted."
+  - "Design and implementation must wait for accepted research."
+next_owner: researcher
+changed_assumptions:
+  - "A descriptive workshop brief does not establish asset rights or inquiry delivery."
+framing_reset: "Treat draft direction names as questions to explore, not approved designs."
+```
+
+## Query plan included in the packet
+
+- Implementation: inspect real static and scripted sites, revisions, licenses and derived route behavior.
+- Stack: compare repeated workshop publishing and form delivery without choosing a stack yet.
+- Design: inspect award work from the last two to three years relative to the established ASK DATE.
+- Graphics: verify chosen-tool/tier rights, material photo provenance and destination crops.
+- UI/UX: research inquiry, group-size validation, access questions, error recovery and mobile use.
+- Accessibility: verify current criteria and plan contrast, keyboard and assistive journeys.
+- Performance: verify metric definitions and propose repeatable route budgets.
+- SEO: map useful initial HTML, canonical routes, sitemap and metadata from workshop records.
+- AEO: distinguish truthful answer structure from unsupported citation promises.
+- Security: research form inputs, host headers, URL validation and provider-ID omission.
+- Hosting: compare preview, HTTPS, form endpoint, response headers and rollback behavior.
+- Measurement: identify receiving-property proof for a successful inquiry.
+- Legal: verify exact font, image and intended-use rights; keep uncertain questions visible.
+
+## Unresolved claims included in the packet
+
+| Claim ID | Unknown | Dependent work | Next evidence action |
+| --- | --- | --- | --- |
+| F-RIGHTS | Permission for workshop photographs and fonts. | Final assets and release. | Obtain original asset/license evidence and open current terms. |
+| F-DELIVERY | Inquiry receiver and confirmation behavior. | Stack decision and functional test. | Confirm owner-approved destination, inspect current integration docs, then test within authority. |
+| F-ACCESS | Venue and activity access facts. | Visit copy and structured data. | Obtain owner-approved facts; do not infer them from imagery. |
+| F-HOST | Host capabilities and response coverage. | Header and release configuration. | Open selected host/version documentation and test an authorized preview. |
+
+No source URLs are invented for these unknowns. They remain UNVERIFIED and block reliance.
+
+## Coordinator's acceptance decision
+
+Acceptance: BLOCKED. No scope-to-designer or scope-to-graphics work assignment is released.
+Return the packet to Researcher with the missing tool and saved-library requirements.
+Coordinator may inspect the blocked return to explain the failure; it does not start its own
+scope/design stage or issue a false passing receipt.
+Optional memory status: pending proposal only; there is no durable-save claim.
+
+## Complete the research-to-design transition
+
+After a capable Researcher establishes date provenance and opens current sources,
+it saves all grouped files, all thirteen checklists, claim ledgers, learning and staleness.
+It reads them back, applies AD01 through AD08 and R01 through R06, and issues a new revision.
+Coordinator reopens those artifacts before recording acceptance.
+Only then does scope-to-designer carry the approved brief, accepted library revision,
+named reading files, applicable checks, asset inputs, ownership and unresolved visual choices.
+Designer records its learning/top-up receipt and creates the three real visual directions.
+The selected direction is a user decision, never a value invented by this walkthrough.
+
+## What carries across a SOLO boundary
+
+Preserve the packet and reopen its files in the next role.
+Keep the blocked status, original assumptions and next actions visible.
+Use framing_reset to release attachment to the proposed directions.
+A future team can reuse the same files after freshness checks; worker creation alone
+cannot change the status of this research receipt.