Skip to content
Documentation

Design-System Legal Documents

FieldValue
TypeSkill Resource
Source~/.copilot/skills/legal/references/design-system-legal-docs.md
DescriptionNot specified

Source Content

Design-System Legal Documents

Use this reference when the output belongs in the MyfreeLawyer design-system legal document system instead of being a plain Markdown draft.

Required sources

Read the repo ADRs before editing legal documents: ADR-030, ADR-030, ADR-018, ADR-031, ADR-031, ADR-031, and ADR-031.

Design-system first rule

If the @dmwd-io/design-system MyfreeLawyer legal components are available, build legal filings with those components instead of freehand Markdown. Use the design-system components to make the structure repeatable, printable, and Storybook-reviewable.

File choice

Use MDX for prose-heavy legal documents. Use TSX when the document is mostly structured component composition. Data belongs in case-files/data/, not in templates.

Component rules

  • Do not import legal components in MDX; the provider supplies them.
  • Import only Meta and matter data from case-files/data/ in MDX.
  • Use bare citation text and update the citation registry when needed.
  • Use LegalCertificateOfService showHeading={false} when a LegalHeader is present.
  • Do not use inline styles for visual mechanics.
  • Do not hand-write Roman numerals in headings when components/CSS generate numbering.
  • Use [FILL IN: specific fact] tokens for unresolved facts.

Document-family mapping

  • Motions use LegalHeader, LegalSection, LegalReliefSought, LegalSignature, LegalCertificateOfService, and often LegalProposedOrder.
  • Orders use LegalProposedOrder or command-language sections.
  • Sworn statements use declarations or affidavit bodies, oath/notary blocks, and fact paragraphs.
  • Exhibits use exhibit appendix, exhibit image, quote, index, and cover components.
  • Discovery uses numbered requests, definitions, instructions, certificate of service, and proportionality notes.

Example files

Use these examples as repeatable structure patterns:

Document typeExample
Motion with proposed orderexamples/design-system-motion.mdx
Proposed order onlyexamples/design-system-proposed-order.mdx
Sworn declarationexamples/design-system-declaration.mdx
Exhibit packetexamples/design-system-exhibit-packet.mdx
Discovery requestexamples/design-system-discovery-request.mdx

Output checks

The Storybook page should render as court-facing prose, not internal notes. Evidence belongs in rear exhibits. Headings should be adoptable findings for motions and neutral fact topics for declarations.