What this prompt does
This prompt designs an interactive financial reporting and statement interface for your product. You provide [product_name], [product_type], [report_types], [data_granularity], [user_roles], [compliance_needs], and [framework], and it designs a report dashboard, a P&L statement, a balance sheet, a cash flow statement, interactive drill-down and export features, and [framework] implementation notes — all under finance-specific design rules.
The structure works because financial professionals judge a reporting tool's credibility by its formatting before they trust a single number. The prompt bakes in the right conventions: right-aligned tabular figures, negatives in parentheses, visually distinct totals, and context-aware color (a cost decrease shows green, not red). It builds hierarchical, expandable statements with period comparison and drill-down to underlying transactions at your [data_granularity], and ties compliance details like audit-trail annotations to your [compliance_needs].
When to use it
- You're building a financial reporting tool and need P&L, balance sheet, and cash flow views designed properly.
- Finance users need to drill from a summary number down to the underlying transactions.
- You need period comparison (vs. prior period, budget, or prior year) with proper variance columns.
- Your
[compliance_needs]require GAAP-style formatting and an audit trail with line-item annotations. - You want export to PDF, Excel (formulas preserved), and CSV designed in from the start.
- You need
[framework]guidance for virtualized tables handling thousands of line items.
Example output
You get a finance-grade interface design: a report dashboard with a quick-metrics row (revenue, net income, cash, burn rate) and period/comparison selectors; a hierarchical, expandable P&L with variance columns and context-aware color; a balance sheet with composition bars, trend mini-charts, and inline ratios; a cash flow statement with a waterfall chart and runway projection; interactive drill-down modals, inline commenting, and a custom report builder; PDF/Excel/CSV export; and [framework] notes covering virtualized tables, locale-aware number formatting, and print stylesheets.
Pro tips
- List your exact
[report_types]so the prompt designs the specific statements you need, not generic placeholders. - Set
[data_granularity]to match how deep drill-down should go (transaction level, by department or project). - Use
[compliance_needs]to drive audit-trail features like line-item annotations and before/after history. - Keep the formatting rules — right-aligned figures, parentheses for negatives, distinct totals — they are what finance users trust.
- Match
[framework](including any grid or charting libraries) so the virtualization and formatting advice fits your stack. - Confirm the context-aware variance coloring with your users; favorable vs. unfavorable isn't always higher-is-better.
