import type { GetDailyHoroscopeResponse, GetMonthlyHoroscopeResponse, GetWeeklyHoroscopeResponse } from '../types/index.js';
import { RoxyDataElement } from '../utils/base-element.js';
type HoroscopeData = GetDailyHoroscopeResponse | GetWeeklyHoroscopeResponse | GetMonthlyHoroscopeResponse;
/**
 * Daily, weekly, or monthly horoscope card. Pass `data` from
 * /astrology/horoscope/{sign}/{daily|weekly|monthly}.
 *
 * @remarks
 * A horoscope reads as prose end to end, but it is not one: the card has a real
 * data spine and `hide-readings` keeps all of it. The sign and its glyph, the
 * period and date, the energy meter, the sky strip (Moon sign, Moon phase and the
 * transits this reading was derived from), the lucky number, colour, days and
 * compatible signs, and the monthly key dates all stay. The overview paragraph,
 * the love, career, health, finance and advice sections, and the week-by-week
 * focus and advice go. The two prose blocks each carry their own heading, so each
 * goes whole rather than leaving one over nothing.
 */
export declare class RoxyHoroscopeCard extends RoxyDataElement<HoroscopeData> {
    static styles: import("lit").CSSResult[];
    period: 'daily' | 'weekly' | 'monthly';
    protected renderData(d: HoroscopeData): import("lit").TemplateResult<1>;
    /**
     * The sky behind the reading (daily only): where the Moon is, what phase it is in, and the transits the forecast was derived from. A daily horoscope that hides its transits is a fortune cookie; showing them is what makes this one auditable.
     */
    private renderSky;
    /** Monthly arc: the week-by-week focus and the dated events (lunations, retrogrades, ingresses) the month turns on. */
    private renderMonth;
}
declare global {
    interface HTMLElementTagNameMap {
        'roxy-horoscope-card': RoxyHoroscopeCard;
    }
}
export {};
//# sourceMappingURL=horoscope-card.d.ts.map