القائمة
Form behavior in contracts — validation timing, field semantics, and recovery UX. Use when data entry blocks workflows or causes scenario gaps.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use only when explicitly invoked as lamina-design. Turn an incomplete product idea or brownfield change into a minimum sufficient product behavior graph: actors, entities, operations, workflows, rules, dependencies, decisions, persona perspectives, and distinct risks; then generate an implementation-ready contract.
Use only when explicitly invoked as lamina-init. Turn an incomplete product idea into usable business context and evidence-grounded personas, asking only high-leverage questions and labeling provisional assumptions for later product-graph design.
Product design workflows — domain contracts, implement brief, verify loop. Load via Read or Skill tool when /lamina-* workflows need it.
Use only when explicitly invoked as lamina. Route product design for developers building with AI — design, verify, or direct capability answers.
Use only when explicitly invoked as lamina-verify. Verify a live or brownfield product against its product graph: critical promises, reachable workflows, authority, invariants, state integrity, recovery, accessibility, and contract drift; emit evidence-backed fixes before merge.
Business context UX guidance. Use when bootstrapping Lamina for a project; answering business questions UX work needs; updating context after a pivot or scope change.
| name | lamina-forms |
| description | Form behavior in contracts — validation timing, field semantics, and recovery UX. Use when data entry blocks workflows or causes scenario gaps. |
| metadata | {"lamina":{"id":"forms","problems":["designing data entry forms","validation blocking users","form abandonment and errors"],"related":["lamina-error-handling","lamina-flow-design","lamina-controls-and-menus"],"tags":["audit-default","interaction"]}} |
Specify how data entry behaves in run.json — field semantics, validation timing, and recovery — not CSS or component libraries.
| Concern | Where |
|---|---|
| Fields per screen | surfaces[].fields[] or workflow step notes |
| Validation timing | scenario trigger.when: validation_failed |
| Recoverable vs blocking | scenario category: partial vs failure |
| Data immunity vs integrity | decisions.md + form policy in implement.md |
Data immunity (default for high-volume entry): accept input, flag uncertainty, audit later — never halt batch flow for recoverable format issues.
Bounded controls: match widget semantics to data type in screen spec; allow override when domain requires.
implement.md).datetime-local value has no zone: submit its untouched local components plus the subject/place IANA zone for trusted resolution. Never convert it in the browser and attach another zone afterward.ux (banner/alert).