Files
community-rule/docs
adilallo d9c475a967 Give finished Rules a print path, folded launch counts, and a two-day follow-up.
Export is PDF, RULE.md, and Print on US Letter, with every shared term, no member names, and a takeaway that points at Ask an organizer. Finished Rules keep type and place so the team can read folded counts without a database, Umami can sit beside the app with no cookies, and the person who holds the pen gets working PDF and RULE.md links 48 hours later.
2026-11-10 18:32:33 -07:00
..
2026-05-24 16:00:11 -06:00

Documentation

User-facing docs. Implementation conventions live in .cursor/rules/.

Canonical references

  • create-flow.md — Custom create-rule wizard: stages, URLs, persistence. Source of truth for product/eng alignment.
  • testing-guide.md — Testing philosophy, layer coverage, and Prisma migration smoke before merge.
  • privacy-policy-facts.md — Periods and hosting facts for the privacy policy counsel will read. Live /privacy stays on the current page until that review.
  • figma-component-registry.md — Figma Community Rule System file ↔ app/components/ (and route-colocated admin UI) map.

Author guides (guides/)

Temporary backend planning

These will be deleted once the backend services are stood up:

Cursor rules

Implementation contracts are enforced by .cursor/rules/*.mdc:

Rule Scope
component-structure.mdc 4-file split (container/view/types/index).
component-props.mdc Lowercase enum prop convention + Figma traceability.
tailwind-styling.mdc Token usage and class composition.
localization.mdc messages/ bundles and useMessages().
testing.mdc Test layout, helpers, required imports.
storybook.mdc Story location and argTypes patterns.
hooks.mdc Custom hook authoring + TSDoc as the API reference.
create-flow.mdc Wizard step / screen registry conventions.
api-routes.mdc API route handler conventions.