recursica-skill-dates-and-currency

Enforces house rules for formatting dates, times, currency, and numeric values in enterprise web applications.

1|Updated May 29, 2026
One-click install
npx skills add https://github.com/borderux/recursica-knowledge --skill recursica-skill-dates-and-currency-borderux
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: recursica-skill-dates-and-currency
Source: https://github.com/borderux/recursica-knowledge/tree/main/skills/design-rules/recursica-skill-dates-and-currency
Command: npx skills add https://github.com/borderux/recursica-knowledge --skill recursica-skill-dates-and-currency-borderux

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Inconsistent date, time, and number formatting across enterprise screens forces users to disambiguate ambiguous dates, do mental arithmetic on timestamps, and misread unaligned figures. This Skill supplies a single set of opinionated house rules so every temporal and numeric value is displayed consistently and unambiguously. ## Core Features & Use Cases - Disambiguated date formatting: Mandates the Jan 7, 2026 format, forbids numeric slash/hyphen dates outside focused inputs, and requires deriving values from Intl.DateTimeFormat rather than slicing toISOString() output. - Time zone and relative time rules: Defines when to state a time zone, when not to localize a time at all, and the one-week threshold for switching between relative (3 days ago) and absolute dates using Intl.RelativeTimeFormat. - Currency and numeric conventions: Right-alignment, fixed two-decimal precision, currency symbols in column headers, digit grouping via Intl.NumberFormat, accounting parentheses, and consistent precision down every column. - Use Case: While building a transactions table, an agent applies these rules to render Jun 24, 2026 dates, right-aligned $-in-header amounts with two decimals, and 5 minutes ago timestamps that switch to absolute dates after one week. ## Quick Start Apply the dates-and-currency house rules to format the dates, timestamps, and money columns in this transactions table.

Frequently Asked Questions about recursica-skill-dates-and-currency

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How should I format dates in an enterprise web app?▼

Use a three-letter month, one-to-two-digit day, and four-digit year, such as Jan 7, 2026. Never display numeric slash-or-hyphen dates outside a focused input, because forms like 01/07/2026 are ambiguous across locales.

Why is toISOString().slice(0, 10) wrong for displaying dates?▼

It produces the prohibited numeric hyphen format and, more seriously, shows the UTC date rather than the reader's local day, so an evening entry can display as the next day. Build the value with Intl.DateTimeFormat in the reader's locale and zone instead.

When should I use relative time versus an absolute date?▼

Use relative time like 5 minutes ago or yesterday for events within the last week, and switch to the absolute date at one week and beyond. Generate relative strings with Intl.RelativeTimeFormat using numeric: auto rather than hand-written strings.

How should currency be displayed in table columns?▼

Right-align currency with exactly two decimal places on every value, and put the currency symbol in the column header rather than each cell. Label the cell when showing a converted currency, and pad accounting parentheses so decimals stay aligned.

Should numbers always be digit-grouped with commas?▼

Group digits once a value reaches four figures, using Intl.NumberFormat or toLocaleString so the separator matches the locale. Never group identifiers such as years, versions, ports, or account numbers, since grouping implies a comparable quantity.

When should a time not be converted to the user's time zone?▼

When the event happened somewhere else and the local time of occurrence matters, such as a security log entry, show the time in the zone where it occurred with a label. Always offer the reader a way to switch it to their own zone.