---
name: website-and-form-implementation
description: "Implement a page or lead form with reliable submission, validation and accessible states. Use when the user requests website and form implementation. Select relevant methods for the requested outcome; unrelated tasks do not require this skill."
metadata:
  version: "1.0.0"
---

# Website and Form Implementation

Implement a page or lead form with reliable submission, validation and accessible states.

## OLLIE Runtime integration

Use this capability under the active OLLIE Operator. Read live Workspace Context and tenant bindings for client facts and required inputs. This generic package contains no client configuration. Consume ask-ollie-authority-core for authority, outloop-access-fallback for access and recovery, email-lifecycle-core for communication, and the bootstrapper Runtime Contract for ownership, scheduling and completion. Preserve domain constraints; this Skill creates no competing execution path. Use one method, combine skills, or fill missing steps with authorized tools as the task requires.

External access uses the active Workspace’s approved Outloop capabilities. Never request, read, embed or expose credentials. A service named in a method is a possible dependency, not an access grant. Local file and application work uses the host’s authorized tools.

## Required inputs

- Existing website source
- Content and design direction
- Approved form destination
- Success criteria

## Methods

### Reuse the project conventions

Reuse the project’s routing, styles, components and deployment conventions. Establish one clear primary action and retain the supplied brand assets.

### Design submission states

Specify field validation, duplicate-submission handling and success/error states. Keep provider credentials server-side or behind the approved router.

### Test the submission path

Validate the complete submission path in a test destination, including slow responses, failures, keyboard use and mobile layout. Do not equate a button click with a saved record.

### Deliver source and evidence

Preserve existing analytics consent and data-minimization rules. Deliver source and test evidence; publishing or production integrations require the applicable authorization.

## Completion

Verify findings against source evidence and read back the resulting artifact or authorized change. Report inputs used, methods selected, output location, assumptions and unresolved dependencies. Do not report a plan, queue entry, draft, test fixture or accepted request as a completed external action. Use the task’s requested format; if a tool is unavailable, finish independent work and identify the exact unfulfilled deliverable.

## Test before relying on it

Read [the synthetic evaluation cases](references/evaluation.md) for activation, output and isolation checks. These cases are test instructions, not evidence that a host or provider test has passed.