Skill LibraryPrompt Skill1 DesignsTop Views

Public Service Trust Rails

Create official identity, responsible organization, legal links, semantic forms, error recovery, review/confirmation, and anti-impersonation boundaries for government, public-service, healthcare, education, benefits, permit, and compliance pages.

Skill Uses0

Recorded selections across prompt workflows.

Public Designs1

Ranked by views, then community favorites.

Prompt Lines10

Reusable instruction lines for generation.

Author@Interface Lab

Accessibility

Skill Directive

Description

TagsAccessibility

Skill Prompt

- Use for government, public service, civic service, public healthcare/education, benefits and permit applications, compliance portals, sensitive long forms, official banners, agency identifiers, .gov/.mil/GOV.UK/NHS-style services, legal footer links, and avoiding misleading official endorsement.
- Classify context first: official, government-adjacent, prototype, commercial-non-official, or unknown; when the context is not genuine, do not use government banners, seals, flags, NHS/agency marks, or endorsement-implying copy.
- Identity and responsibility must be inspectable: name the responsible organization, parent agency, or service owner, and expose privacy, accessibility, FOIA/freedom-of-information, oversight/performance, and contact links in the identifier or footer.
- Use the user task as the H1, such as Apply for housing support or Check permit status; do not push the service task below a giant marketing hero, abstract value prop, or decorative motion.
- Form structure comes before layout: DOM and visual order match, related controls use fieldset/legend, and labels, hints, required/optional text, input purpose, and save state stay visible.
- Error recovery appears in two layers: on submit failure, a top error summary lists problems and links to repairable fields/fieldsets while field-adjacent errors show the same fix guidance; long forms move focus to the summary.
- Sensitive or high-cost submissions need review/check-answers; confirmation includes reference number, submitted service, next step, expected timeline, support/contact path, and save/print guidance.
- Frontend implementation defines a PublicServicePageContract: context, domainEvidence, ownerName, parentAgency, officialIdentityAllowed, legalLinks, serviceTaskTitle, formSections, errorSummary, reviewStep, confirmation, and impersonationRiskNotes.
- Use real header/main/footer/form/fieldset/legend/label/button/a semantics; connect hints/errors with aria-describedby, set aria-invalid on invalid fields, make the error summary focusable, and use polite live regions for routine state.
- QA checks official identity, responsible organization, legal links, task title, keyboard focus, error anchors, input preservation, mobile sticky-action occlusion, review/confirmation, and non-official misuse of official marks. Sources: USWDS Banner/Identifier/Form, GOV.UK Error Summary, NHS.UK Error Summary, and WCAG.

Public directive summary shown; Pro unlocks the full prompt.

Layout Info

Designs below are ordered by views. Top items use live previews; the rest stay fast thumbnail cards.

Unlock Pro All Skills

Public Service Trust Rails

More pages using Public Service Trust Rails