Frontend Patterns¶
Workflow¶
- Follow the existing framework and design language. For a new modest interface, consider server-rendered HTML or HTMX before a full client framework.
- Define loading, empty, error and success states; make the primary action easy to find and give useful feedback.
- Use semantic HTML, labels, keyboard interaction, visible focus, responsive layouts and appropriate contrast.
- Render untrusted content safely; avoid injecting Markdown or API text into innerHTML without a trusted sanitizer.
- Agree on the API contract and test the critical interaction, authorization boundary and failure recovery.
Completion¶
Return the concrete result, verification evidence and any material unresolved limitation. Keep documentation proportional to the change and preserve human feedback.
Focused references¶
- Detailed examples: load only the section relevant to the task.
Canonical source: skills/frontend-patterns/SKILL.md.