ScamShield is an AI-powered scam and fraud detection platform that helps users identify potentially fraudulent messages, screenshots, and website links. Its tagline is "Know before you trust." and its short explanation is "Check suspicious messages, screenshots, and links before you act."
This document specifies the first version of ScamShield: a professional, mobile-first web application delivering only the frontend foundation and navigation. The audience is ordinary adults — not security analysts — who need to turn a vague "this feels off" into a graded, defensible read before they act on a suspicious message, screenshot, or link.
This first stage deliberately does not build the entire application. It establishes the screens, navigation, component architecture, and states that later stages will extend. No AI API is connected, no payment/subscription functionality is added, and no fake scam detection results are produced.
ScamShield v1 is a frontend-only, mobile-first web application with a responsive desktop layout. It presents a public landing screen, an authenticated dashboard, three checking workspaces (message, screenshot, link), a reserved results structure, a history destination, and a profile/settings screen, tied together by a bottom navigation bar (Home / Check / History / Profile) that becomes a left rail at ≥1024px.
The product is built from reusable components with proper loading, error, and empty states, accessible buttons, labels, and form controls, and a polished, serious security-product appearance. All analysis, OCR, and URL-detection backends remain unconnected in this stage; each checking workspace displays a clear placeholder indicating the analysis engine will be connected in a later development stage, and the results screen is a UI structure only, containing no fabricated detection results.
ScamShield's current delivery is a frontend foundation: the screens, navigation, and component system that a real startup MVP needs, without any live detection capability. Users can move through the product, submit content into the checking workspaces, and see honest, clearly labeled placeholders where analysis will later appear. Nothing in the current version claims to detect, score, or clear anything.
Access is application-owned. Because checks, history, and account preferences must persist to the correct person and be resumable, the product establishes identity on first use through Sign Up and verifies returning users through Login. Both entry surfaces are anonymously reachable; the protected destinations (Dashboard, Check, the three checking workspaces, Results, History, and Profile/Settings) require a verified session. The public Landing/Home screen remains openly reachable and is the entry point for the checking journey.
The following are explicitly out of scope for this stage: connecting any AI API; implementing OCR or AI for screenshots; implementing real URL analysis; adding payment or subscription functionality; generating fake scam detection results; and adding any features not requested. The "Upgrade to Premium" section on the Dashboard is a presentation block only — it does not process payments or change entitlements. The Results screen reserves the structure for risk level, risk score, warning indicators, explanation, recommended action, and a Report Scam button, but displays no invented values.
Future stages will connect the analysis engine and adopt non-guaranteeing language such as "Low Risk", "Suspicious", and "High Risk" rather than asserting that a message is or is not a scam.
FR-1 — Frontend foundation and navigation (explicit). As a Scam Checker, I should be able to use a professional mobile-first web application that delivers only the frontend foundation and navigation, so that later stages can extend it cleanly.
FR-2 — Brand identity (explicit). As a Scam Checker, I should see the ScamShield name and the tagline "Know before you trust." presented in a modern, trustworthy, professional cybersecurity/fintech style, so that the product reads as a serious security tool.
FR-3 — Landing/Home screen content (explicit). As a Scam Checker, I should see the short explanation "Check suspicious messages, screenshots, and links before you act.", a primary button "Check for a Scam", and a secondary button "How It Works", so that I understand the product and can begin.
FR-4 — Dashboard checking options (explicit). As a Scam Checker, I should see three main checking options — Check a Message, Check a Screenshot, and Check a Link — so that I can choose the right check.
FR-5 — Dashboard Recent Checks (explicit). As a Returning User Reviewing History, I should see Recent Checks on the Dashboard as a ruled data table, so that I can return to a prior check.
FR-6 — Dashboard Protection Status (explicit). As a Scam Checker, I should see a Protection Status panel with a circular gauge, so that I can read my protection state at a glance.
FR-7 — Dashboard Upgrade to Premium section (explicit). As a Scam Checker, I should see an Upgrade to Premium section as a bordered inset band, so that I am aware of the future premium offering.
FR-8 — Check Message workspace (explicit). As a Scam Checker, I should be able to paste a suspicious message into a large text input area with the placeholder "Paste a suspicious message here..." and press "Analyze Message", so that I can submit a message for future analysis.
FR-9 — Check Screenshot workspace (explicit). As a Scam Checker, I should be able to upload an image via an upload button or drag-and-drop area, preview the uploaded image, and press "Analyze Screenshot", so that I can submit a screenshot for future analysis.
FR-10 — Check Link workspace (explicit). As a Scam Checker, I should be able to enter a URL and press "Check Link", so that I can submit a link for future analysis.
FR-11 — Results screen structure (explicit). As a Scam Checker, I should see a Results screen UI structure reserved for risk level, risk score, warning indicators, explanation, recommended action, and a Report Scam button, so that results can be displayed once analysis is connected.
FR-12 — Profile/Settings content (explicit). As a Returning User Reviewing History, I should see account information, subscription status, privacy settings, notification settings, and Logout, so that I can review my account and adjust preferences.
FR-13 — Bottom navigation (explicit). As a Scam Checker, I should have a simple mobile-friendly bottom navigation with Home, Check, History, and Profile, so that I can move between destinations.
FR-14 — Responsive desktop layout (explicit). As a Scam Checker, I should be able to use the application on desktop, so that the experience is not limited to mobile.
FR-15 — Self-service enrollment (required_inference). As a Scam Checker, I should be able to create an account through Sign Up before first protected use, so that my checks and preferences persist to me.
FR-16 — Returning verification (required_inference). As a Returning User Reviewing History, I should be able to verify my identity through Login before accessing protected checks, history, dashboard, and settings, so that I can resume my prior state.
FR-17 — No fabricated analysis (explicit). As a Scam Checker, I should never see fake scam detection results, so that I am not misled about the product's current capability.
FR-18 — Non-guaranteeing language (explicit). As a Scam Checker, I should see language such as "Low Risk", "Suspicious", or "High Risk" rather than any claim that something is or is not a scam, so that I am never given a false guarantee of safety.
FR-19 — Security and privacy constraints (explicit). As a Scam Checker, I should be confident that API keys are not exposed in frontend code and that unnecessary personal information is not collected, so that my use of the product is safe.
FR-20 — Component architecture and states (explicit). As a Scam Checker, I should experience a clean, component-based, reusable interface with proper loading, error, and empty states and accessible controls, so that the product feels polished and usable.
The Scam Checker is the primary end user: an ordinary adult who has received something suspicious — a text at 11pm, a link that feels wrong, a screenshot a relative forwarded — and wants to know whether it is risky before acting. They are not a security analyst; they want a tool that reads as engineered, exact, and quietly trustworthy, with zero playful energy.
The Returning User Reviewing History is the same adult returning to the product after prior use. Their work is different from first-time checking: they are not starting a new investigation but resuming, reviewing, and managing.
The creative direction is "Precision instrument calm for a fraud-detection shield", with MARQ by Garmin as the muse. The emotional register is alert but calm, authoritative without menace — instrument-panel seriousness rather than gaming RGB. The product lives on graphite; there is no blue anywhere and no decorative gradients.
| Role | Token | Value |
|---|---|---|
| Background | --bg | #101215 |
| Surface | --surface | #191D22 |
| Text | --text | #F2F0EB |
| Primary (instrument accent) | --primary | #E8A33D |
| Accent (Low Risk / protected / verified) | --accent | #3FBFA8 |
| Muted | --muted | #8A929B |
| Hairline border | --border | rgba(242,240,235,0.10) |
| High Risk (gauge only) | --risk-high | #E0523F |
#E8A33D is the single instrument accent: primary CTA, active nav indicator, focus rings, needle marks, one highlighted metric.#3FBFA8 is reserved strictly for the "Low Risk" / protected state and for verified/privacy confirmations; it never appears as decoration.#8A929B is used for micro-labels, units, timestamps, and secondary copy.#3FBFA8, Suspicious = amber #E8A33D, High Risk = signal red #E0523F (used only inside the risk gauge, never as a page accent).0.04em tracking; sentence case for the hero headline at very large scale with tight 0.96 leading.0.12em tracking.clamp(44px, 9vw, 96px) / screen title clamp(26px, 5vw, 40px) / section title 20px / body 16px / label 12px / micro 11px; line-height 1.05 for display, 1.55 for body.Instrument geometry: circular gauges and bezels, ruled 1px data rows, chamfered 2px-cornered panels (near-sharp, not pill), capsule only for the primary CTA and the bottom-nav active pill. Concentric ring motifs for the risk gauge and the shield mark; hairline dividers between every data row; small tick marks along panel edges suggesting a dial scale. Radii: 2px (panels), 999px (CTA + active nav), 12px (upload dropzone).
Mobile-first single column with a fixed bottom nav (Home / Check / History / Profile) that becomes a left rail at ≥1024px; content max-width 1120px. The Dashboard is a ruled instrument stack: a full-width Protection Status panel with a circular gauge, then three check tiles as a 1-column → 3-column grid, then Recent Checks as a ruled table (not cards), then the Premium block as a bordered inset band. Every screen opens with a condensed uppercase eyebrow, a large title, and a hairline rule. Numbers align right in tabular columns.
No stock people, no illustration for its own sake. The visual language is engineered texture and macro material: brushed titanium grain, sapphire-glass edge highlights, topographic contour lines as a faint background layer, and a single macro shot of a phone screen at an angle with a blurred suspicious message (used as an abstract, unreadable texture — never as a fake result). Diagrams are schematic: a shield outline, a link-chain pictogram, and a message-bubble pictogram, drawn in 1.5px stroke at 24px on a 24px grid, monochrome in muted with amber on active.
The public entry is a full-bleed graphite ground (#101215) with a faint topographic contour layer at 4% opacity. It is left-aligned, not centered:
clamp(44px, 9vw, 96px), stacked across three lines so the word "trust." lands alone and spans nearly the full viewport width.The dominant visual element is an oversized circular instrument gauge anchored to the right edge on desktop (bleeding off the viewport) and reduced to a 180px arc behind the headline block on mobile. Its bezel is brushed-metal grey with a single amber needle at rest and the label "ANALYSIS ENGINE — NOT YET CONNECTED" in 11px uppercase muted beneath it. There is no gradient blob, no centered stack, and no blue button.
This concept recomposes only accepted content, states, and controls — the brand name, tagline, explanation, both CTAs, and the honest "not yet connected" status. It introduces no new behavior, page, or destination.
Interaction Model: Animated Motion Tempo: restrained Hero Dimensionality: dimensional_css
prefers-reduced-motion, leaving the gauge at its resting value and the content fully readable.#F2F0EB on #101215 yields approximately 15:1 contrast. Rationale: a serious security product must be legible under stress.font-size: clamp(...)) to fit, with no other element covering them. Imagery, decoration, and motion may be cropped, bled, rotated, overlapped, or cut as the direction asks, provided they cover no readable text or control. Rationale: accessibility and the direction's own precedence rule.prefers-reduced-motion, leaving the gauge at its resting value. Rationale: accessibility.
Scam & Fraud Detection
Check suspicious messages, screenshots, and links before you act.
Analysis engine — not yet connected
Paste the message, upload a screenshot, or enter the link that made you pause. Nothing else is required to start a check.
In a later development stage, a connected analysis engine may assess content against known scam patterns and provide a graded read: Low Risk, Suspicious, or High Risk. No grading happens yet.
If analysis is connected in a later development stage, it may provide reasoning and a recommended next step. No readout is available yet.
ScamShield is in its foundation stage. No content is graded yet, and no check can declare a message, screenshot, or link safe.
In this first stage no message, screenshot or link is sent for analysis, so no readout is produced. ScamShield never claims that something is or is not a scam — a check returns a graded indication: Low Risk/Suspicious/High Risk. The analysis engine will be connected in a later development stage.

Scam & Fraud Detection
Check suspicious messages, screenshots, and links before you act.
Analysis engine — not yet connected
Paste the message, upload a screenshot, or enter the link that made you pause. Nothing else is required to start a check.
In a later development stage, a connected analysis engine may assess content against known scam patterns and provide a graded read: Low Risk, Suspicious, or High Risk. No grading happens yet.
If analysis is connected in a later development stage, it may provide reasoning and a recommended next step. No readout is available yet.
ScamShield is in its foundation stage. No content is graded yet, and no check can declare a message, screenshot, or link safe.
In this first stage no message, screenshot or link is sent for analysis, so no readout is produced. ScamShield never claims that something is or is not a scam — a check returns a graded indication: Low Risk/Suspicious/High Risk. The analysis engine will be connected in a later development stage.
No comments yet. Be the first!