Skip to content

armgit / ARES

Public Imported from GitHub
0

ARES - authorized red-team engagement automation with dashboard, campaign scope, module orchestration, OPSEC controls, encrypted vault, and reporting.

feat(ui): elevate platform to startup-grade enclave with dragon-scale mesh, interactive showcases, and UX fixes

Mafifrizic0e9f26cebaf
diff --git a/.agents/skills/design-taste-frontend/SKILL.md b/.agents/skills/design-taste-frontend/SKILL.md
new file mode 100644
index 0000000..b72132f
--- /dev/null
+++ b/.agents/skills/design-taste-frontend/SKILL.md
@@ -0,0 +1,1206 @@
+---
+name: design-taste-frontend
+description: Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.
+---
+
+# tasteskill: Anti-Slop Frontend Skill
+
+> Landing pages, portfolios, and redesigns. Not dashboards, not data tables, not multi-step product UI.
+> Every rule below is **contextual**. None of it fires automatically. First read the brief, then pull only what fits.
+
+---
+
+## 0. BRIEF INFERENCE (Read the Room Before Anything Else)
+
+Before touching code or tweaking dials, **infer what the user actually wants**. Most LLM design output is bad because the model jumps to a default aesthetic instead of reading the room.
+
+### 0.A Read these signals first
+1. **Page kind** - landing (SaaS / consumer / agency / event), portfolio (dev / designer / creative studio), redesign (preserve vs overhaul), editorial / blog.
+2. **Vibe words** the user used - "minimalist", "calm", "Linear-style", "Awwwards", "brutalist", "premium consumer", "Apple-y", "playful", "serious B2B", "editorial", "agency-y", "glassy", "dark tech".
+3. **Reference signals** - URLs they linked, screenshots they pasted, products they named, brands they're competing with.
+4. **Audience** - B2B procurement panel vs. design-conscious consumer vs. recruiter scanning a portfolio. The audience picks the aesthetic, not your taste.
+5. **Brand assets that already exist** - logo, color, type, photography. For redesigns, these are starting material, not optional input (see Section 11).
+6. **Quiet constraints** - accessibility-first audiences, public-sector, regulated industries, trust-first commerce, kids' products. These constraints OVERRIDE aesthetic preference.
+
+### 0.B Output a one-line "Design Read" before generating
+Before any code, state in one line: **"Reading this as: \<page kind> for \<audience>, with a \<vibe> language, leaning toward \<design system or aesthetic family>."**
+
+Example reads:
+- *"Reading this as: B2B SaaS landing for technical buyers, with a Linear-style minimalist language, leaning toward Tailwind utilities + Geist + restrained motion."*
+- *"Reading this as: solo designer portfolio for hiring managers, with an editorial / kinetic-type language, leaning toward native CSS + scroll-driven animation + custom typography."*
+- *"Reading this as: redesign of a public-sector service site, with a trust-first language, leaning toward GOV.UK Frontend or USWDS."*
+
+### 0.C If the brief is ambiguous, ask one question, do not guess
+Ask exactly **one** clarifying question - never a multi-question dump - and only when the design read genuinely diverges. Example: *"Should this feel closer to Linear-clean or Awwwards-experimental?"*
+
+If you can confidently infer from context, **do not ask**. Just declare the design read and proceed.
+
+### 0.D Anti-Default Discipline
+Do not default to: AI-purple gradients, centered hero over dark mesh, three equal feature cards, generic glassmorphism on everything, infinite-loop micro-animations everywhere, Inter + slate-900. These are the LLM defaults. Reach past them deliberately based on the design read.
+
+---
+
+## 1. THE THREE DIALS (Core Configuration)
+
+After the design read, set three dials. Every layout, motion, and density decision below is gated by these.
+
+* **`DESIGN_VARIANCE: 8`** - 1 = Perfect Symmetry, 10 = Artsy Chaos
+* **`MOTION_INTENSITY: 6`** - 1 = Static, 10 = Cinematic / Physics
+* **`VISUAL_DENSITY: 4`** - 1 = Art Gallery / Airy, 10 = Cockpit / Packed Data
+
+**Baseline:** `8 / 6 / 4`. Use these unless the design read overrides them. Do not ask the user to edit this file - overrides happen conversationally.
+
+### 1.A Dial Inference (design read → dial values)
+| Signal | VARIANCE | MOTION | DENSITY |
+|---|---|---|---|
+| "minimalist / clean / calm / editorial / Linear-style" | 5-6 | 3-4 | 2-3 |
+| "premium consumer / Apple-y / luxury / brand" | 7-8 | 5-7 | 3-4 |
+| "playful / wild / Dribbble / Awwwards / experimental / agency" | 9-10 | 8-10 | 3-4 |
+| "landing page / portfolio / marketing site (default)" | 7-9 | 6-8 | 3-5 |
+| "trust-first / public-sector / regulated / accessibility-critical" | 3-4 | 2-3 | 4-5 |
+| "redesign - preserve" | match existing | +1 | match existing |
+| "redesign - overhaul" | +2 | +2 | match existing |
+
+### 1.B Use-Case Presets
+| Use case | VARIANCE | MOTION | DENSITY |
+|---|---|---|---|
+| Landing (SaaS, mainstream) | 7 | 6 | 4 |
+| Landing (Agency / creative) | 9 | 8 | 3 |
+| Landing (Premium consumer) | 7 | 6 | 3 |
+| Portfolio (Designer / studio) | 8 | 7 | 3 |
+| Portfolio (Developer) | 6 | 5 | 4 |
+| Editorial / Blog | 6 | 4 | 3 |
+| Public-sector service | 3 | 2 | 5 |
+| Redesign - preserve | match | match+1 | match |
+| Redesign - overhaul | +2 | +2 | match |
+
+### 1.C How the Dials Drive Output
+Use these (or user-overridden values) as global variables. Cross-references throughout this document refer to these exact variable names - never invent aliases like `LAYOUT_VARIANCE` or `ANIM_LEVEL`.
+
+---
+
+## 2. BRIEF → DESIGN SYSTEM MAP
+
+Once you have the design read (Section 0) and dials (Section 1), pick the right foundation. Do not invent CSS for things that have an official package. Do not pretend an aesthetic trend is an official system.
+
+### 2.A When to reach for a real design system (use official packages)
+| Brief reads as… | Reach for | Why |
+|---|---|---|
+| Microsoft / enterprise SaaS / dashboards | `@fluentui/react-components` or `@fluentui/web-components` | Official Fluent UI, Microsoft tokens, accessibility done |
+| Google-ish UI, Material-flavored product | `@material/web` + Material 3 tokens | Official, theme-able via Material Theming |
+| IBM-style B2B / enterprise analytics | `@carbon/react` + `@carbon/styles` | Official Carbon, mature data-density patterns |
+| Shopify app surfaces | `polaris.js` web components / Polaris React | Required for Shopify admin UI |
+| Atlassian / Jira-style product | `@atlaskit/*` + `@atlaskit/tokens` | Official Atlassian DS |
+| GitHub-style devtool / community page | `@primer/css` or `@primer/react-brand` | Official Primer; Brand variant for marketing |
+| Public-sector UK service | `govuk-frontend` | Legally / regulatorily expected |
+| US public-sector / trust-first | `uswds` | Same |
+| Fast local-business / agency MVP | Bootstrap 5.3 | Boring, fast, works |
+| Modern accessible React foundation | `@radix-ui/themes` | Primitives + polished theme |
+| Modern SaaS where you own the components | shadcn/ui (`npx shadcn@latest add ...`) | You own the code, easy to customise; never ship default state |
+| Tailwind-based modern SaaS / AI marketing | Tailwind v4 utilities + `dark:` variant | Default for indie + small team builds |
+
+**Honesty rule:** if the brief reads as one of the systems above, install and use the **official** package. Do not recreate its CSS by hand. Do not import a system's tokens but then override 90% of them.
+
+**One system per project.** Do not mix Fluent React with Carbon in the same tree. Do not import shadcn/ui components into a Material 3 app.
+
+### 2.B When the brief is an aesthetic, not a system
+For these directions, there is **no single official package**. Build with native CSS + Tailwind + a maintained component library. Be honest in code comments about what is borrowed inspiration vs. official material.
+
+| Aesthetic | Honest implementation |
+|---|---|
+| Glassmorphism / "frosted glass" | `backdrop-filter`, layered borders, highlight overlays. Provide solid-fill fallback for `prefers-reduced-transparency`. |
+| Bento (Apple-style tile grids) | CSS Grid with mixed cell sizes. No single library owns this. |
+| Brutalism | Native CSS, monospace, raw borders. No library. |
+| Editorial / magazine | Serif type, asymmetric grid, generous whitespace. No library. |
+| Dark tech / hacker | Mono + accent neon, terminal motifs. No library. |
+| Aurora / mesh gradients | SVG or layered radial gradients. No library. |
+| Kinetic typography | Native CSS animations, scroll-driven animations, GSAP for hijacks. No library. |
+| **Apple Liquid Glass** | Apple documents this for Apple platforms only. **There is no official `liquid-glass.css`.** Web implementations are approximations using `backdrop-filter` + layered borders + highlights. Label clearly as approximation. |
+
+---
+
+## 3. DEFAULT ARCHITECTURE & CONVENTIONS
+
+Unless the design read picks a real design system (Section 2.A), these are the defaults:
+
+### 3.A Stack
+* **Framework:** React or Next.js. Default to Server Components (RSC).
+ * **RSC SAFETY:** Global state works ONLY in Client Components. In Next.js, wrap providers in a `"use client"` component.
+ * **INTERACTIVITY ISOLATION:** Any component using Motion, scroll listeners, or pointer physics MUST be an isolated leaf with `'use client'` at the top. Server Components render static layouts only.
+* **Styling:** **Tailwind v4** (default). Tailwind v3 only if the existing project demands it.
+ * For v4: do NOT use `tailwindcss` plugin in `postcss.config.js`. Use `@tailwindcss/postcss` or the Vite plugin.
+* **Animation:** **Motion** (the library formerly known as Framer Motion). Import from `motion/react` (`import { motion } from "motion/react"`). The `framer-motion` package still works as a legacy alias - prefer `motion/react` in new code.
+* **Fonts:** Always use `next/font` (Next.js) or self-host with `@font-face` + `font-display: swap`. Never link Google Fonts via `<link>` in production.
+
+### 3.B State
+* Local `useState` / `useReducer` for isolated UI.
+* Global state ONLY for deep prop-drilling avoidance - Zustand, Jotai, or React context.
+* **NEVER** use `useState` to track continuous values driven by user input (mouse position, scroll progress, pointer physics, magnetic hover). Use Motion's `useMotionValue` / `useTransform` / `useScroll`. `useState` re-renders the React tree on every change and collapses on mobile.
+
+### 3.C Icons
+* **Allowed libraries (priority order):** `@phosphor-icons/react`, `hugeicons-react`, `@radix-ui/react-icons`, `@tabler/icons-react`.
+* **Discouraged:** `lucide-react`. Acceptable only when the user explicitly asks for it or the project already depends on it.
+* **NEVER hand-roll SVG icons.** If a glyph is missing, install a second library or compose from primitives - do not draw icon paths from scratch.
+* **One family per project.** Do not mix Phosphor with Lucide in the same component tree.
+* **Standardize `strokeWidth` globally** (e.g. `1.5` or `2.0`).
+
+### 3.D Emoji Policy
+Discouraged by default in code, markup, and visible text. Replace symbols with icon-library glyphs. **Override:** allow emojis only when the user explicitly asks for a playful / chat-style / social-native vibe - and even then use them sparingly with intent.
+
+### 3.E Responsiveness & Layout Mechanics
+* Standardize breakpoints (`sm 640`, `md 768`, `lg 1024`, `xl 1280`, `2xl 1536`).
+* Contain page layouts using `max-w-[1400px] mx-auto` or `max-w-7xl`.
+* **Viewport Stability:** NEVER use `h-screen` for full-height Hero sections. ALWAYS use `min-h-[100dvh]` to prevent layout jumping on mobile (iOS Safari address bar).
+* **Grid over Flex-Math:** NEVER use complex flexbox percentage math (`w-[calc(33%-1rem)]`). ALWAYS use CSS Grid (`grid grid-cols-1 md:grid-cols-3 gap-6`).
+
+### 3.F Dependency Verification (mandatory)
+Before importing ANY 3rd-party library, check `package.json`. If the package is missing, output the install command first. **Never** assume a library exists.
+
+---
+
+## 4. DESIGN ENGINEERING DIRECTIVES (Bias Correction)
+
+LLMs default to clichés. Override these defaults proactively. Each rule has a context-aware override path.
+
+### 4.1 Typography
+* **Display / Headlines:** Default `text-4xl md:text-6xl tracking-tighter leading-none`.
+* **Body / Paragraphs:** Default `text-base text-gray-600 leading-relaxed max-w-[65ch]`.
+* **Sans font choice:**
+ * **Discouraged as default:** `Inter`. Pick `Geist`, `Outfit`, `Cabinet Grotesk`, `Satoshi`, or a brand-appropriate serif first.
+ * **Override:** Inter is acceptable when the user explicitly asks for a neutral / standard / Linear-style feel, or when the brief is a public-sector / accessibility-first site.
+* **Pairings to know:** `Geist` + `Geist Mono`, `Satoshi` + `JetBrains Mono`, `Cabinet Grotesk` + `Inter Tight`, `GT America` + `IBM Plex Mono`.
+
+* **SERIF DISCIPLINE (VERY DISCOURAGED AS DEFAULT):**
+ * Serif is **very discouraged as the default font for any project.** "It feels creative / premium / editorial" is NOT a reason to reach for serif. The agent's default mental model that "creative brief = serif" is the single most-tested AI tell in production rounds.
+ * **Serif is only acceptable when ONE of these is explicitly true:**
+ - The brand brief literally names a serif font, OR
+ - The aesthetic family is genuinely editorial / luxury / publication / manuscript / heritage / vintage AND you can articulate why this specific serif fits this specific brand
+ * For everything else (creative agency, design studio, modern brand, premium consumer, portfolio, lifestyle), **default sans-serif display** (Geist Display, ABC Diatype, Söhne Breit, Cabinet Grotesk Display, Migra Sans, GT Walsheim, Inter Display, PP Neue Montreal). Sans display fonts are not "boring" — they are the default for the same reason black is the default in fashion.
+ * **EMPHASIS RULE (related):** When you want to emphasize a word within a headline (the kinetic "and `spatial` design" type move), use **italic or bold of the SAME font**. Do NOT inject a random serif word into a sans headline (or vice versa) just to add visual interest. Mixed-family emphasis is amateur. Italic/bold emphasis in the same family is the right move.
+ * **Specifically BANNED as defaults:** `Fraunces` and `Instrument_Serif` (the two LLM-favorite display serifs).
+ * **If a serif is justified** (rare, per the above), rotate from this pool, do NOT reuse the same serif across consecutive projects: PP Editorial New, GT Sectra Display, Cardinal Grotesque, Reckless Neue, Tiempos Headline, Recoleta, Cormorant Garamond, Playfair Display, EB Garamond, IvyPresto, Migra, Editorial Old, Saol Display, Söhne Breit Kursiv, Domaine Display, Canela, Schnyder, Tobias, NB Architekt, ITC Galliard.
+
+* **ITALIC DESCENDER CLEARANCE (mandatory):** When italic is used in display type and the word contains a descender letter (`y g j p q`), `leading-[1]` or `leading-none` will clip the descender. Use `leading-[1.1]` minimum and add `pb-1` or `mb-1` reserve on the wrapping element. Audit every italic word in display headlines before shipping.
+
+### 4.2 Color Calibration
+* Max 1 accent color. Saturation < 80% by default.
+* **THE LILA RULE:** The "AI Purple / Blue glow" aesthetic is discouraged as a default. No automatic purple button glows, no random neon gradients. Use neutral bases (Zinc / Slate / Stone) with high-contrast singular accents (Emerald, Electric Blue, Deep Rose, Burnt Orange, etc.).
+* **Override:** if the brand or brief explicitly asks for purple / violet / lila, embrace it. But execute with intent: consistent palette, harmonised neutrals, restrained gradients. Not generic AI gradient slop.
+* **One palette per project.** Do not fluctuate between warm and cool grays within the same project.
+* **COLOR CONSISTENCY LOCK (mandatory):** Once an accent color is chosen for a page, it is used on the WHOLE page. A warm-grey site does not suddenly get a blue CTA in section 7. A rose-accented site does not get a teal status badge in the footer. Pick one accent, lock it, audit every component before shipping.
+
+* **PREMIUM-CONSUMER PALETTE BAN (mandatory, second-most-recurring AI-tell):**
+ * For premium-consumer briefs (cookware, wellness, artisan, luxury, heritage craft, DTC home goods, etc.) the LLM default is **warm beige/cream + brass/clay/oxblood/ochre + espresso/ink dark text**. Concretely banned hex families as default backgrounds and accents:
+ - Backgrounds: `#f5f1ea`, `#f7f5f1`, `#fbf8f1`, `#efeae0`, `#ece6db`, `#faf7f1`, `#e8dfcb` (all "warm paper / cream / chalk / bone")
+ - Accents: `#b08947`, `#b6553a`, `#9a2436`, `#9c6e2a`, `#bc7c3a`, `#7d5621` (all "brass / clay / oxblood / ochre")
+ - Text: `#1a1714`, `#1a1814`, `#1b1814` (all "espresso / warm near-black")
+ * This palette is BANNED as the default reach for premium-consumer briefs. Every premium-consumer site you have ever shipped uses this exact palette. The brand becomes invisible.
+ * **Default alternatives (rotate, do not reuse):**
+ - **Cold Luxury:** silver-grey + chrome + smoke (think Tesla, Apple Watch Hermes-without-the-leather)
+ - **Forest:** deep green + bone + amber accent (think Filson, Patagonia premium)
+ - **Black and Tan:** true off-black + warm tan, sharp contrast, no beige
+ - **Cobalt + Cream:** saturated blue against a single neutral, no brass
+ - **Terracotta + Slate:** warm rust against cool grey, no brass
+ - **Olive + Brick + Paper:** muted olive plus brick-red accent
+ - **Pure monochrome + single saturated pop:** off-white + off-black + one bright accent (electric blue, emerald, hot pink, etc.)
+ * **Palette-rotation rule:** if the previous premium-consumer project you generated used the beige+brass family, this one MUST use a different family. Do not ship the same warm-craft palette twice in a row.
+ * **Override:** the beige+brass+espresso palette is acceptable ONLY when the brand brief explicitly names those colors, or when the brand identity is genuinely vintage / artisan / warm-craft AND you can articulate why this specific palette fits this specific brand. Default-reaching for it because "this is a cookware brief" is banned.
+
+### 4.3 Layout Diversification
+* **ANTI-CENTER BIAS:** Centered Hero / H1 sections are avoided when `DESIGN_VARIANCE > 4`. Force "Split Screen" (50/50), "Left-aligned content / right-aligned asset", "Asymmetric white-space", or scroll-pinned structures.
+* **Override:** centered hero is OK for editorial / manifesto / launch-announcement briefs where the message itself is the design.
+
+### 4.4 Materiality, Shadows, Cards
+* Use cards ONLY when elevation communicates real hierarchy. Otherwise group with `border-t`, `divide-y`, or negative space.
+* When a shadow is used, tint it to the background hue. No pure-black drop shadows on light backgrounds.
+* For `VISUAL_DENSITY > 7`: generic card containers are banned. Data metrics breathe in plain layout.
+* **SHAPE CONSISTENCY LOCK (mandatory):** Pick ONE corner-radius scale for the page and stick to it. Options: all-sharp (radius 0), all-soft (radius 12-16px), all-pill (full radius for interactive). Mixed systems are allowed only when there is a documented rule (e.g. "buttons are full-pill, cards are 16px, inputs are 8px") and that rule is followed everywhere. Round buttons in a square layout, or square cards on a pill-button page, is broken design.
+
+### 4.5 Interactive UI States
+LLMs default to "static successful state only." Always implement full cycles:
+* **Loading:** Skeletal loaders matching the final layout's shape. Avoid generic circular spinners.
+* **Empty States:** Beautifully composed; indicate how to populate.
+* **Error States:** Clear, inline (forms), or contextual (toasts only for transient).
+* **Tactile Feedback:** On `:active`, use `-translate-y-[1px]` or `scale-[0.98]` to simulate a physical push.
+* **BUTTON CONTRAST CHECK (mandatory, a11y):** Before shipping any button, verify the button text is readable against the button background. White button + white text, `bg-white` CTA with `text-white` label, transparent button against the page background with no border → all banned. Audit every CTA: contrast ratio WCAG AA min (4.5:1 for body, 3:1 for large text 18px+). Same rule applies to ghost buttons over photographic backgrounds (use a backdrop, scrim, or stroke).
+* **CTA BUTTON WRAP BAN (mandatory):** Button text MUST fit on one line at desktop. If a label like "VIEW SELECTED WORK" wraps to 2 or 3 lines, the button is broken. Fix by EITHER shortening the label (3 words max for primary CTAs, ideally 1-2) OR widening the button (do not artificially constrain `max-width` on CTAs). Wrapped CTAs at desktop are a Pre-Flight Fail.
+* **NO DUPLICATE CTA INTENT (mandatory):** Two CTAs with the same intent on one page is a Pre-Flight Fail. Examples of same intent: "Get in touch" + "Contact us" + "Let's talk" + "Start a project" + "Start something" + "Reach out" = all "contact" intent → pick ONE label and use it everywhere on the page (nav, hero, footer). Same for "Try free" + "Get started" + "Sign up free" (all "signup" intent) and "View work" + "See selected work" + "Browse projects" (all "portfolio" intent). One label per intent.
+* **FORM CONTRAST CHECK (mandatory, a11y):** Form inputs, placeholder text, focus rings, helper text, and error text all pass WCAG AA contrast against the section background. Light placeholders on a near-white form, white form on white page section, form labels grayer than 4.5:1 contrast → all banned. Audit every form before shipping.
+
+### 4.6 Data & Form Patterns
+* Label ABOVE input. Helper text optional but present in markup. Error text BELOW input. Standard `gap-2` for input blocks.
+* No placeholder-as-label. Ever.
+
+### 4.7 Layout Discipline (Hard Rules. Failing any of these is shipping broken work)
+
+* **Hero MUST fit in the initial viewport.** Headline max 2 lines on desktop, subtext max **20 words** AND max 3-4 lines, CTAs visible without scroll. If the copy is too long: reduce font scale OR cut copy. If you cannot describe the value-prop in 20 words of subtext, the value-prop is unclear, not the rule too tight. Never let the hero overflow and force scroll to find the CTA.
+* **Hero font-scale discipline.** Plan font size and image size *together*. If the hero asset is large and the headline is more than 6 words, do not start at `text-7xl/text-8xl`. Default sensible range: `text-4xl md:text-5xl lg:text-6xl` for most heroes; `text-6xl md:text-7xl` only when the headline is 3-5 words. A 4-line hero headline is always a font-size error, never a copy-length error.
+* **HERO TOP PADDING CAP (mandatory):** Hero top padding max `pt-24` (≈6rem) at desktop. More than that means the hero content floats halfway down the viewport and reads as a layout bug, not as intentional space. If your hero needs more breathing room, increase font scale or asset size, not top padding.
+* **HERO STACK DISCIPLINE (max 4 text elements).** The hero is a single moment, not a feature list. Allowed text elements, max 4 in total:
+ 1. Eyebrow (small uppercase label) OR brand strip OR neither - pick zero or one
+ 2. Headline (max 2 lines, see above)
+ 3. Subtext (max 20 words, max 4 lines)
+ 4. CTAs (1 primary + max 1 secondary)
+ - **BANNED in the hero:** tiny tagline below CTAs ("Works with GitHub, GitLab, and self-hosted Git"), trust micro-strip ("Used by engineering teams at..."), pricing teaser ("Free for solo, $10/user for teams"), feature bullet list, social-proof avatar row. All of those move to dedicated sections directly below the hero.
+ - If you have an eyebrow AND a tagline below CTAs in the same hero, drop the tagline. If you have a brand strip AND a tagline, drop the tagline. One small text element per hero, max.
+* **"Used by" / "Trusted by" logo wall belongs UNDER the hero, never inside it.** The hero is for the value prop and primary CTA. The logo wall is a separate section directly below. Do not stuff trust logos into the same flex row as the hero copy.
+* **Navigation MUST render on a single line on desktop.** If items don't fit at `lg` (1024px), condense labels, drop secondary items, or move to a hamburger. A two-line nav at desktop is broken design.
+* **Navigation height cap: 80px max desktop, default 64-72px.** No huge "agency" nav bars that eat 15% of the viewport.
+* **Bento grids MUST have rhythm, not one-sided repetition.** Do not stack 6 left-image / right-text rows. Vary the composition: alternate full-width feature rows, asymmetric tile sizes, vertical breaks.
+* **BENTO CELL COUNT RULE (mandatory):** A bento grid has EXACTLY as many cells as you have content for. 3 items → 3 cells (1+2 split, or 2+1, or asymmetric trio). 5 items → 5 cells (2+3, 3+2, hero+4, etc.). If your grid has an empty cell in the middle or at the end, you planned wrong. Re-shape the grid; do not paste a blank tile.
+* **Section-Layout-Repetition Ban.** Once you use a layout family for a section (e.g., 3-column-image-cards, full-width-quote, split-text-image), that family can appear at most ONCE on the page. "Selected commissions" must not look like "What we do." A landing page with 8 sections must use at least 4 different layout families.
+* **ZIGZAG ALTERNATION CAP (mandatory).** Alternating "left-image + right-text" then "left-text + right-image" zigzag layout = banal. Max 2 sections in a row with this image+text-split pattern. The 3rd consecutive image+text split is a Pre-Flight Fail. Break the pattern with a full-width section, a vertical-stack section, a bento grid, a marquee, or a different layout family.
+* **EYEBROW RESTRAINT (mandatory, the #1 violated rule in production tests).** An "eyebrow" is the small uppercase wide-tracking label sitting above a section headline (e.g. `FOUR COLORWAYS`, `SELECTED WORK`, `THE HARDWARE`, `Git-native task management`). Typical CSS signature: `text-[11px] uppercase tracking-[0.18em]`, `font-mono text-[10.5px] uppercase tracking-[0.22em]`. Every AI-built site puts an eyebrow above EVERY section header, producing the same templated rhythm. Hard rule:
+ - **Maximum 1 eyebrow per 3 sections.** Hero counts as 1. So a page with 9 sections may use at most 3 eyebrows total.
+ - If section A has an eyebrow, the next 2 sections cannot have one.
+ - **Pre-Flight Check is mechanical:** count instances of `uppercase tracking` (or similar small-caps mono labels above headlines) across all section components. If count > ceil(sectionCount / 3), the output fails.
+ - **What to do instead of an eyebrow:** drop it entirely. The headline alone is enough. If you need to categorize a section, the section's location on the page already categorizes it; no label needed.
+* **SPLIT-HEADER BAN (mandatory).** The pattern "left big headline + right small explainer paragraph" as a section header (left col-span-7/8, right col-span-4/5 with a small body paragraph floating in the right column) is **banned as default**. Sections should have ONE focused message. If you genuinely need both a headline and an explainer paragraph, stack them vertically (headline on top, body below, max-width 65ch). Reach for the split-header pattern only when there is a real compositional reason (e.g., the right column carries a visual or interactive element, not just filler text).
+* **Bento Background Diversity (mandatory).** Bento and feature-grid sections cannot be 6 white-on-white cards with text inside. At least 2-3 cells in any multi-cell grid need real visual variation: a real image, a brand-appropriate gradient (not AI-purple), a pattern, a tinted background. A cream-on-cream bento with only typography inside reads as boring AI default, even when the rest of the page is good.
+* **Mobile collapse must be explicit per section.** For every multi-column layout, declare the `< 768px` fallback in the same component. No "it'll work, Tailwind handles it" assumptions.
+
+### 4.8 Image & Visual Asset Strategy
+
+Landing pages and portfolios are **visual products**. Text-only pages with fake-screenshot divs are slop.
+
+**Priority order for visual assets:**
+1. **Image-generation tool first.** If ANY image-gen tool is available in the environment (`generate_image`, MCP image tool, IDE-integrated gen, OpenAI image tools, etc.) you MUST use it to create section-specific assets: hero photography, product shots, texture backgrounds, mood images. Generate at the right aspect ratio for the section. Do not skip this step because hand-rolled CSS feels faster.
+2. **Real web images second.** When no gen tool is available, use real photography sources. Acceptable defaults:
+ * `https://picsum.photos/seed/{descriptive-seed}/{w}/{h}` for placeholder photography (seed should describe the section, e.g. `marrow-cookware-kitchen`)
+ * Actual stock or brand URLs when the brief provides them
+ * Open-license sources (Unsplash via direct URL, Pexels) if explicitly allowed
+3. **Last resort: tell the user.** If neither is possible, do NOT fill the page with hand-rolled SVG illustrations or div-based "fake screenshots." Instead, leave clearly-labeled placeholder slots (`<!-- TODO: hero product photo, 1600x1200 -->`) and at the end of the response say: *"This page needs real images at: \[list of placements\]. Please generate or provide them."*
+
+**Even minimalist sites need real images.** A pure-text page is not minimalism. It is incomplete work. Even an editorial Linear-style site needs at least 2-3 real images (hero, one product/lifestyle shot, one supporting image). Generate B&W minimalist photography if the brief is restrained; do not skip images entirely because the dial is low.
+
+**Real company logos for social proof.** When the brief calls for a "Trusted by / Used by / Customers" logo wall, do NOT default to plain text wordmarks (`<span>Acme Co</span>` styled in a row). Use real SVG logos:
+* **Source: Simple Icons** (`https://cdn.simpleicons.org/{slug}/ffffff` for any color, or `simple-icons` npm package). Covers most known brands.
+* **Alternative: devicon** for tech-stack logos (`@svgr/cli` or CDN).
+* **Make-up the brand name? Then make-up an SVG mark too.** Generate a simple monogram (one letter in a circle, two-letter ligature, abstract glyph) rendered as an inline `<svg>` matching the page style. Plain text wordmarks for invented brand names look generic.
+* **Always** ensure logos render in both light and dark mode (white-on-dark, black-on-light, or single-color theme variable).
+* **LOGO-ONLY rule (mandatory):** logo wall = logos and nothing else. Do NOT print industry / category labels below each logo (no `Vercel` + `hosting` underneath, no `Stripe` + `payments`, no `Cloudflare` + `infra`). The logo is the credibility, the label adds nothing the user does not already know. Optional: brand name as alt-text for screen readers, optional link to the brand's site. That is it.
+
+**Hand-rolled illustrations:**
+* SVG icons from libraries: fine (see Section 3.C).
+* Hand-rolled decorative SVGs (custom illustrations, logos, marks): **strongly discouraged**, never as default. Acceptable only when:
+ - The brief explicitly calls for it ("draw me an SVG logo")
+ - It's a single, simple geometric mark (a square, a circle, a wordmark in display type)
+ - You're confident in the output quality
+
+**Div-based fake screenshots are banned.** A "hand-built product preview" rendered with `<div>` rectangles, fake task lists, fake dashboards, fake terminal windows is a Tell. If you need to show a product:
+* Use a real screenshot URL if one exists
+* Generate one via image tool
+* Use a real component preview (an actual mini-version of the UI inside the page)
+* Or skip the preview entirely and use editorial photography
+
+**Hero needs a real visual.** Text + gradient blob is not a hero - it's a placeholder.
+
+### 4.9 Content Density
+
+Landing pages live on the **first impression**, not the full read. Cut ruthlessly.
+
+* **Default content shape per section:** short headline (≤ 8 words) + short sub-paragraph (≤ 25 words) + one visual asset OR one CTA. Anything more must be justified by the section's job.
+* **No data-dump sections.** A 20-row publication table, a 30-row award list, a giant pricing matrix on a marketing page = wrong layout. Use:
+ - Top 3-5 highlights + "View full list" link
+ - Marquee / carousel for breadth
+ - Different page entirely if the data is the product
+* **Long lists need a different UI component, not a longer list.** Default `<ul>` with bullets / `divide-y` rows is the lazy choice. If you have > 5 items, reach for one of these instead:
+ - 2-column split with grouped items
+ - Card grid with image + label per item
+ - Tabs / accordion if items are categorisable
+ - Horizontal scroll-snap pills
+ - Carousel for breadth-heavy lists (testimonials, logos, capabilities)
+ - Marquee for "lots-of-things-that-don't-need-individual-attention"
+ A spec sheet with 10 rows + a hairline under every row is the WORST default. Either group rows into 2-3 chunks with sparse dividers, or move to a card-per-spec layout.
+* **Spec sheets specifically (the Marrow-cookware pattern).** A long product specification table with `border-b` on every row is the AI default for cookware / hardware / apparel / artisan-goods briefs. Banned. Concrete alternatives:
+ - **2-col card grid:** each spec gets its own card with the spec name, the value (large display number), and a one-line "why it matters" body. Cards arranged 2-col on desktop, 1-col mobile.
+ - **Scroll-snap horizontal pills:** each spec is a pill, user can flick through.
+ - **Grouped chunks:** group 10 specs into 3 logical clusters (e.g. "Materials", "Cooking", "Warranty"), each cluster gets ONE soft divider and a cluster heading.
+ - **Featured-vs-rest:** 3-4 hero specs visualised as large display tiles, the rest collapsed under a "View full specifications" disclosure.
+
+* **COPY SELF-AUDIT (mandatory before ship):** Before declaring any task done, re-read every visible string on the page (headlines, subheads, eyebrows, button labels, body copy, captions, alt text, footer text, error messages). Flag any string that is:
+ - **Grammatically broken** ("free on its past", "two plans but one is honest", "to put it on the table" out of context)
+ - **Has unclear referents** ("we plan to stay that way" without prior context)
+ - **Sounds like AI hallucination** (cute-but-wrong wordplay, forced metaphors that don't track, "elegant nothing" phrases)
+ - **Reads like an LLM trying to sound thoughtful** (passive-aggressive humility, fake-craftsman labels, mock-poetic micro-meta)
+ Rewrite every flagged string. If unsure whether a string makes sense, replace it with a plain functional sentence. AI-generated cute copy is worse than boring copy.
+* **Fake-precise numbers are flagged.** Numbers like `92%`, `4.1×`, `48k`, `5.8 mm`, `13.4 lb` either:
+ - Come from real data (brief, brand guidelines, public metrics) - fine
+ - Are explicitly labeled as mock (`<!-- mock -->`, "example", "sample data") - fine
+ - Are AI-invented spec aesthetics - banned. Don't fake engineering precision the brand doesn't claim.
+* **One copy register per page.** Don't mix technical mono ("47 tasks · 0.6 ctx-switches/day"), editorial prose, and marketing punch in the same composition unless the brand voice explicitly calls for it.
+
+### 4.10 Quotes & Testimonials
+
+* **Max 3 lines** of quote body. Never 6. If the original quote is longer → cut it. A landing-page quote is a snippet, not the full review.
+* For very small font sizes (e.g. footer-style testimonials), the line cap can stretch slightly. Spirit: "fits in a glance."
+* **No em-dashes inside the quote text** as design flourish (long pauses, kinetic em-dashes, em-dash-bullets). See Section 9.G - em-dash is completely banned.
+* Attribution: name + role + (optionally) company. Never name only ("- Sarah").
+* Quote marks: use real typographic quotes ( " " ) or none at all. Not straight ASCII ( " ).
+
+### 4.11 Page Theme Lock (Light / Dark Mode Consistency)
+
+The page has ONE theme. Sections do not invert.
+
+* If the page is dark mode, ALL sections are dark mode. No light-mode-warm-paper section sandwiched between dark sections (or vice versa). The user must not feel they walked into a different website mid-scroll.
+* The exception: if the brief explicitly calls for a "Color Block Story" or "Theme Switch on Scroll" device AND that is a deliberate composition (one full theme switch with a strong transition, not random alternation), it is allowed once per page.
+* Default behaviour: pick light, dark, or auto (`prefers-color-scheme`) at the page level and lock it. Section-level background tints within the same theme family are fine (`bg-zinc-950` next to `bg-zinc-900`); flipping to `bg-amber-50` in the middle of a `bg-zinc-950` page is broken.
+* When using a design system with built-in theming (Radix Themes, shadcn/ui with `<Theme>`), set the theme ONCE in `layout.tsx` or the page root. Do not let individual sections override.
+
+---
+
+## 5. CONTEXT-AWARE PROACTIVITY
+
+These are tools, not defaults. Use them when the design read calls for them. **None of these fire automatically.**
+
+* **Liquid Glass / Glassmorphism:** Appropriate for premium consumer, Apple-adjacent, luxury brand, or media-overlay vibes. Inappropriate for dashboards, public-sector, or "boring B2B." When used, go beyond `backdrop-blur`: add a 1px inner border (`border-white/10`) and a subtle inner shadow (`shadow-[inset_0_1px_0_rgba(255,255,255,0.1)]`) for physical edge refraction. Provide a solid-fill fallback under `prefers-reduced-transparency`.
+* **Magnetic Micro-physics:** Use when `MOTION_INTENSITY > 5` AND the brief reads premium / playful / agency. Implement EXCLUSIVELY with Motion's `useMotionValue` / `useTransform` outside the React render cycle. Never `useState`. See Section 3.B.
+* **Perpetual Micro-Interactions** (Pulse, Typewriter, Float, Shimmer, Carousel): Use when `MOTION_INTENSITY > 5` AND the section actively benefits from motion (status indicators, live feeds, AI-feel). **Not every card needs an infinite loop.** If a section is informational, leave it still. Apply Spring Physics (`type: "spring", stiffness: 100, damping: 20`) - no linear easing.
+* **"Motion claimed, motion shown."** If `MOTION_INTENSITY > 4`, the page must actually move: entry transitions on hero, scroll-reveal on key sections, hover physics on CTAs, at minimum. A static page that claims `MOTION_INTENSITY: 7` is broken. Conversely, if you cannot ship working motion in the available scope, drop the dial to 3 and ship a clean static page. Never half-build motion that breaks (cut-off ScrollTriggers, jumpy enters, missing cleanups).
+* **MOTION MUST BE MOTIVATED (mandatory).** Before adding any animation, ask: "what does this animation communicate?" Valid answers: hierarchy (drawing attention to the right thing), storytelling (revealing content in sequence that matches a narrative), feedback (acknowledging a user action), state transition (showing something changed). Invalid answer: "it looked cool". GSAP everywhere because GSAP is available is amateur. Each ScrollTrigger, each marquee, each pinned section needs a reason. If you cannot articulate the reason in one sentence, drop the animation.
+* **MARQUEE MAX-ONE-PER-PAGE (mandatory).** Horizontal scrolling text marquees ("logos endlessly scrolling", "manifesto scrolling sideways", "kinetic word strip") are appropriate at most ONCE per page. Two or more marquees on the same page reads as lazy filler. Pick the one section where the marquee actually serves the content; the others get a different layout.
+* **GSAP Sticky-Stack Pattern (when scroll-stack is used).** A "card stack on scroll" must be a REAL sticky-stack, not a sequential reveal list. See Section 5.A below for the canonical code skeleton. Common failure: trigger fires halfway through scroll instead of pinning at viewport top. Fix: `start: "top top"` not `start: "top center"` or `"top 80%"`.
+* **GSAP Horizontal-Pan Pattern (when horizontal scroll-hijack is used).** See Section 5.B below for the canonical skeleton. Common failure: animation starts before the section is pinned, so the user sees half a slide. Same fix: `start: "top top"`, pin the wrapper, scrub the inner track.
+
+### 5.A Sticky-Stack - Canonical Skeleton
+
+```tsx
+"use client";
+import { useRef, useEffect } from "react";
+import { gsap } from "gsap";
+import { ScrollTrigger } from "gsap/ScrollTrigger";
+import { useReducedMotion } from "motion/react";
+
+gsap.registerPlugin(ScrollTrigger);
+
+export function StickyStack({ cards }: { cards: React.ReactNode[] }) {
+ const ref = useRef<HTMLDivElement>(null);
+ const reduce = useReducedMotion();
+
+ useEffect(() => {
+ if (reduce || !ref.current) return;
+ const ctx = gsap.context(() => {
+ const cardEls = gsap.utils.toArray<HTMLElement>(".stack-card");
+ cardEls.forEach((card, i) => {
+ if (i === cardEls.length - 1) return;
+ ScrollTrigger.create({
+ trigger: card,
+ start: "top top", // pin at viewport top
+ endTrigger: cardEls[cardEls.length - 1],
+ end: "top top",
+ pin: true,
+ pinSpacing: false,
+ });
+ gsap.to(card, {
+ scale: 0.92,
+ opacity: 0.55,
+ ease: "none",
+ scrollTrigger: {
+ trigger: cardEls[i + 1],
+ start: "top bottom",
+ end: "top top",
+ scrub: true,
+ },
+ });
+ });
+ }, ref);
+ return () => ctx.revert();
+ }, [reduce]);
+
+ return (
+ <div ref={ref} className="relative">
+ {cards.map((card, i) => (
+ <div
+ key={i}
+ className="stack-card sticky top-0 min-h-[100dvh] flex items-center justify-center"
+ >
+ {card}
+ </div>
+ ))}
+ </div>
+ );
+}
+```
+
+Critical points: `start: "top top"`, `pin: true`, every card except the last is pinned, the scale/opacity transform is driven by the NEXT card's scroll trigger (so previous card shrinks as next one arrives).
+
+### 5.B Horizontal-Pan - Canonical Skeleton
+
+```tsx
+"use client";
+import { useRef, useEffect } from "react";
+import { gsap } from "gsap";
+import { ScrollTrigger } from "gsap/ScrollTrigger";
+import { useReducedMotion } from "motion/react";
+
+gsap.registerPlugin(ScrollTrigger);
+
+export function HorizontalPan({ children }: { children: React.ReactNode }) {
+ const wrap = useRef<HTMLDivElement>(null);
+ const track = useRef<HTMLDivElement>(null);
+ const reduce = useReducedMotion();
+
+ useEffect(() => {
+ if (reduce || !wrap.current || !track.current) return;
+ const ctx = gsap.context(() => {
+ const distance = track.current!.scrollWidth - window.innerWidth;
+ gsap.to(track.current, {
+ x: -distance,
+ ease: "none",
+ scrollTrigger: {
+ trigger: wrap.current,
+ start: "top top", // pin starts when section top hits viewport top
+ end: () => `+=${distance}`, // scroll distance = track width minus viewport
+ pin: true,
+ scrub: 1,
+ invalidateOnRefresh: true,
+ },
+ });
+ }, wrap);
+ return () => ctx.revert();
+ }, [reduce]);
+
+ return (
+ <section ref={wrap} className="relative overflow-hidden">
+ <div ref={track} className="flex h-[100dvh] items-center">
+ {children}
+ </div>
+ </section>
+ );
+}
+```
+
+Critical points: `start: "top top"`, `pin: true`, `end: "+=${distance}"` (scroll length = horizontal travel needed), `scrub: 1`. The wrapper is pinned, the inner track slides horizontally as the user scrolls vertically.
+
+### 5.C Scroll-Reveal Stagger - Canonical Skeleton (lighter alternative)
+
+For simple "items appear as they enter viewport" (no pinning), prefer Motion's `whileInView` over GSAP - lighter, no ScrollTrigger needed:
+
+```tsx
+"use client";
+import { motion, useReducedMotion } from "motion/react";
+
+export function RevealStagger({ items }: { items: string[] }) {
+ const reduce = useReducedMotion();
+ return (
+ <ul className="grid gap-6">
+ {items.map((item, i) => (
+ <motion.li
+ key={item}
+ initial={reduce ? false : { opacity: 0, y: 24 }}
+ whileInView={{ opacity: 1, y: 0 }}
+ viewport={{ once: true, amount: 0.3 }}
+ transition={{
+ duration: 0.6,
+ delay: i * 0.06,
+ ease: [0.16, 1, 0.3, 1],
+ }}
+ >
+ {item}
+ </motion.li>
+ ))}
+ </ul>
+ );
+}
+```
+
+Use this for: feature lists, testimonial grids, logo walls, anything that just needs "enter on scroll." Save GSAP for actual pin/scrub work.
+
+### 5.D Forbidden Animation Patterns
+
+* **`window.addEventListener("scroll", ...)`** is banned. It runs on every scroll frame, jank-prone, no batching. Use Motion's `useScroll()`, GSAP's `ScrollTrigger`, IntersectionObserver, or CSS `scroll-driven animations` (`animation-timeline: view()`).
+* **Custom scroll progress calculations using `window.scrollY`** in React state. Same reason. Re-renders on every frame.
+* **`requestAnimationFrame` loops that touch React state.** Use motion values (`useMotionValue` + `useTransform`) instead.
+* **Layout Transitions:** Use Motion's `layout` and `layoutId` props for visible state changes (re-ordering lists, expanding modals, shared elements between routes). Do not wrap static content in `layout` props "for safety" - it costs measurement work.
+* **Staggered Orchestration:** Use `staggerChildren` (Motion) or CSS cascade (`animation-delay: calc(var(--index) * 100ms)`) for reveal moments where sequence matters. For `staggerChildren`, parent (`variants`) and children MUST share the same Client Component tree.
+
+---
+
+## 6. PERFORMANCE & ACCESSIBILITY GUARDRAILS
+
+### 6.A Hardware Acceleration
+* Animate ONLY `transform` and `opacity`. Never animate `top`, `left`, `width`, `height`.
+* Use `will-change: transform` sparingly - only on elements that will actually animate.
+
+### 6.B Reduced Motion (mandatory)
+* **Any motion above `MOTION_INTENSITY > 3` MUST honor `prefers-reduced-motion`.** This is non-negotiable.
+* In Motion: wrap with `useReducedMotion()` and degrade to static.
+* In CSS: gate animations behind `@media (prefers-reduced-motion: no-preference)` or provide an override block under `@media (prefers-reduced-motion: reduce)` that disables.
+* Infinite loops, parallax, scroll-hijack, and magnetic physics MUST collapse to static / instant under reduced motion.
+
+### 6.C Dark Mode (mandatory for any consumer-facing page)
+* Design for **both modes from the start**. Never ship light-only or dark-only without explicit user instruction.
+* Use Tailwind `dark:` variant OR CSS variables for tokens. Pick one strategy per project.
+* **Do not prescribe specific dark-mode colors here.** The brief decides. Maintain visual hierarchy, brand identity, and WCAG AA contrast (AAA for body) across both modes.
+* Respect `prefers-color-scheme: dark`. Default to system preference unless the brand insists on one mode.
+
+### 6.D Core Web Vitals Targets
+* **LCP** < 2.5s. Hero image must be `next/image priority` or preloaded.
+* **INP** < 200ms. Heavy work off main thread.
+* **CLS** < 0.1. Reserve space for images, fonts, embeds.
+* Run Lighthouse before declaring a page done.
+
+### 6.E DOM Cost
+* Apply grain / noise filters EXCLUSIVELY to fixed, `pointer-events-none` pseudo-elements (e.g., `fixed inset-0 z-[60] pointer-events-none`). NEVER on scrolling containers - continuous GPU repaints destroy mobile FPS.
+* Be aware of bundle size. Motion is not tiny. Three.js is large. Lazy-load anything that's not above-the-fold.
+
+### 6.F Z-Index Restraint
+NEVER spam arbitrary `z-50` or `z-10`. Use z-index strictly for systemic layer contexts (sticky navbars, modals, overlays, grain). Document the z-index scale in a project constants file.
+
+---
+
+## 7. DIAL DEFINITIONS (Technical Reference)
+
+### DESIGN_VARIANCE (Level 1-10)
+* **1-3 (Predictable):** Symmetrical CSS Grid (12-col, equal fr-units), equal paddings, centered alignment.
+* **4-7 (Offset):** `margin-top: -2rem` overlaps, varied image aspect ratios (4:3 next to 16:9), left-aligned headers over center-aligned data.
+* **8-10 (Asymmetric):** Masonry layouts, CSS Grid with fractional units (`grid-template-columns: 2fr 1fr 1fr`), massive empty zones (`padding-left: 20vw`).
+* **MOBILE OVERRIDE:** For levels 4-10, asymmetric layouts above `md:` MUST collapse to strict single-column (`w-full`, `px-4`, `py-8`) on viewports `< 768px`.
+
+### MOTION_INTENSITY (Level 1-10)
+* **1-3 (Static):** No automatic animations. CSS `:hover` and `:active` states only. `prefers-reduced-motion` is the default mode anyway.
+* **4-7 (Fluid CSS):** `transition: all 0.3s cubic-bezier(0.16, 1, 0.3, 1)`. `animation-delay` cascades for load-ins. Focus on `transform` and `opacity`.
+* **8-10 (Advanced Choreography):** Complex scroll-triggered reveals, parallax, scroll-driven animation (CSS `animation-timeline` or GSAP ScrollTrigger). Use Motion hooks. **NEVER use `window.addEventListener('scroll')`** - it is a hard ban, not a "prefer-not." See Section 5.D for the allowed alternatives.
+
+### VISUAL_DENSITY (Level 1-10)
+* **1-3 (Art Gallery):** Lots of white space. Huge section gaps (`py-32` to `py-48`). Expensive, clean.
+* **4-7 (Daily App):** Standard web app spacing (`py-16` to `py-24`).
+* **8-10 (Cockpit):** Tight paddings. No card boxes; 1px lines separate data. Mandatory: `font-mono` for all numbers.
+
+---
+
+## 8. DARK MODE PROTOCOL
+
+Dual-mode by default. Never assume light-only unless the brief is print-emulating editorial.
+
+### 8.A Token Strategy (pick one, stick to it)
+* **Tailwind `dark:` variant** (default for utility-first projects): every color utility paired with its dark variant (`bg-white dark:bg-zinc-950`, `text-gray-900 dark:text-gray-100`).
+* **CSS variables** (for shadcn/ui, Radix Themes, or component libraries with theming): define semantic tokens (`--surface`, `--surface-elevated`, `--text-primary`, `--accent`) and swap values under `[data-theme="dark"]` or `@media (prefers-color-scheme: dark)`.
+
+### 8.B Do Not Prescribe Specific Colors Here
+The brief and brand decide. This skill enforces only:
+* **Contrast** - WCAG AA minimum for body text, AAA target for hero copy.
+* **Hierarchy parity** - visual hierarchy that works in light must work in dark. If a CTA pops in light, it pops in dark.
+* **Brand fidelity** - primary brand color stays recognisable. Don't desaturate the brand into a dark mode.
+* **No pure `#000000` and no pure `#ffffff`** - use off-black (zinc-950, near-black warm gray) and off-white. Pure values kill depth.
+
+### 8.C Default Mode
+Respect `prefers-color-scheme` unless the brand insists. Add a manual toggle if either mode would lose key brand expression.
+
+### 8.D Test in Both Modes Before Finishing
+Open the page in both modes during development. Do not ship a page you've only seen in one mode.
+
+---
+
+## 9. AI TELLS (Forbidden Patterns)
+
+Avoid these signatures unless the brief explicitly asks for them.
+
+### 9.A Visual & CSS
+* **NO neon / outer glows** by default. Use inner borders or subtle tinted shadows.
+* **NO pure black (`#000000`).** Off-black, zinc-950, or charcoal.
+* **NO oversaturated accents.** Desaturate to blend with neutrals.
+* **NO excessive gradient text** for large headers.
+* **NO custom mouse cursors.** Outdated, accessibility-hostile, perf-hostile.
+
+### 9.B Typography
+* **AVOID Inter as default.** See Section 4.1. Override path exists.
+* **NO oversized H1s** that just scream. Control hierarchy with weight + color, not raw scale.
+* **Serif constraints:** Serif for editorial / luxury / publication. Not for dashboards.
+
+### 9.C Layout & Spacing
+* **Mathematically perfect** padding and margins. No floating elements with awkward gaps.
+* **NO 3-column equal feature cards.** The generic "three identical cards horizontally" feature row is banned. Use 2-column zig-zag, asymmetric grid, scroll-pinned, or horizontal-scroll alternative.
+
+### 9.D Content & Data ("Jane Doe" Effect)
+* **NO generic names.** "John Doe", "Sarah Chan", "Jack Su" → use creative, realistic, locale-appropriate names.
+* **NO generic avatars.** No SVG "egg" or Lucide user icons → use believable photo placeholders or specific styling.
+* **NO fake-perfect numbers.** Avoid `99.99%`, `50%`, `1234567`. Use organic, messy data (`47.2%`, `+1 (312) 847-1928`).
+* **NO startup-slop brand names.** "Acme", "Nexus", "SmartFlow", "Cloudly" → invent contextual, premium names that sound real.
+* **NO filler verbs.** "Elevate", "Seamless", "Unleash", "Next-Gen", "Revolutionize" → concrete verbs only.
+
+### 9.E External Resources & Components
+* **NO hand-rolled SVG icons.** Use Phosphor / HugeIcons / Radix / Tabler. Lucide on explicit request only.
+* **Hand-rolled decorative SVGs strongly discouraged** as default (see Section 4.8).
+* **NO div-based fake screenshots.** Never build a fake product UI out of `<div>` rectangles to simulate a screenshot. Use real images, generated images, or skip the preview.
+* **NO broken Unsplash links.** Use `https://picsum.photos/seed/{descriptive-string}/{w}/{h}`, or generated photo placeholders, or actual assets.
+* **shadcn/ui customization:** Allowed, but NEVER in default state. Customize radii, colors, shadows, typography to the project aesthetic.
+* **Production-Ready Cleanliness:** Code visually clean, memorable, meticulously refined.
+
+### 9.F Production-Test Tells (banned outright)
+
+These patterns came out of real LLM-generated landing-page tests. They are the signatures the model defaults to when it tries to "look designed." Treat them as hard bans unless the brief explicitly calls for one.
+
+**Hero & top-of-page**
+* **NO version labels in the hero.** `V0.6`, `v2.0`, `BETA`, `INVITE-ONLY PREVIEW`, `EARLY ACCESS`, `ALPHA` - banned as default eyebrows. Only acceptable when the brief is explicitly about a product launch / preview status.
+* **NO "Brand · No. 01"-style sub-eyebrows.** "Marrow · No. 01 · The 6-quart" type micro-meta lines. Skip them.
+
+**Section numbering & micro-labels**
+* **NO section-number eyebrows.** `00 / INDEX`, `001 · Capabilities`, `002 · Featured commission`, `06 · how it works`, `05 · The honest table` - banned. Eyebrows should name the topic in plain language, not enumerate.
+* **NO `01 / 4`-style pagination on images or bento tiles.** If the user can count, they don't need the label.
+* **NO `Scroll · 001 Capabilities`-style scroll cues.** A simple arrow or "Scroll" is enough; no section-number prefix.
+* **NO "Index of Work, 2018 - 2026"-style range labels** as eyebrows. Just say what the section is.
+
+**Separators & dots**
+* **The middle-dot (`·`) is rationed.** Maximum 1 per line in metadata strips. Do NOT use it as the default separator for everything ("foo · bar · baz · qux · quux"). If you need a separator family, prefer line breaks, hairlines, or columns.
+* **NO decorative colored status dots on every list/nav/badge.** A colored dot before "ONE Q4 SLOT OPEN" or before every nav link, or every task row - banned by default. Acceptable only when the dot conveys actual semantic state (a server status, an availability flag) and is used sparingly.
+
+**Em-dashes & typography flourishes**
+* **NO em-dash (`—`) as a design element OR anywhere else.** See Section 9.G below for the complete, non-negotiable ban. The em-dash character is forbidden in headlines, eyebrows, pills, body copy, quotes, attribution, captions, button text, and alt text. Use the regular hyphen (`-`).
+* **NO `<br>`-broken-and-italicized headlines** as a default "design move." "for thirty\<br\>*years.*" type splits. Headlines should read naturally first, get clever only when the brief demands it.
+* **NO vertical rotated text** ("INDEX OF WORK, 2018 - 2026" rotated 90°). Agency-portfolio cliché. Use it only when the brief is explicitly agency / Awwwards / experimental AND it serves a real composition purpose.
+* **NO crosshair / hairline grid lines as decoration.** Vertical and horizontal lines drawn just to make the page "feel designed" - banned. Use them only when they organize real content.
+
+**Fake product previews**
+* **NO div-based fake product UI in the hero** (fake task list, fake terminal, fake dashboard built from styled divs). It is the #1 LLM-design Tell. Use a real screenshot, a generated image, a real component preview, or none at all.
+* **NO fake version footers** ("v0.6.2-rc.1", "last sync 4s ago · main") inside fake screenshots. Adds nothing, screams AI.
+
+**Marketing-copy Tells**
+* **NO "Quietly in use at" / "Quietly trusted by"** social-proof headers. Use natural language: "Trusted by", "Used at", "Customers include", or skip the heading entirely if the logos speak.
+* **NO "From the field" / "Field notes" / "Currently on the bench" / "On our desks" / "Loose plates" style poetic labels** on quote, blog, or sidebar sections. Reads as performative-craftsman. Use plain functional labels ("Testimonials", "Latest writing", "Now working on") or skip the label.
+* **NO "We respect the French ones"-style** mock-humble industry-references in body copy. Cute and AI-y.
+* **NO weather / locale strips** ("LIS 14:23 · 18°C") in headers/footers unless the brief is explicitly about a place / time-zone-distributed studio.
+* **NO micro-meta-sentences under eyebrows.** Sentences like *"Each of these is a feature we ship today, not a roadmap promise. The list will stay short on purpose."* sitting under a section heading are clutter. Eyebrow + Headline + Body is enough.
+* **NO generic step labels.** "Stage 1 / Stage 2 / Stage 3", "Step 1 / Step 2 / Step 3", "Phase 01 / Phase 02 / Phase 03", "Pass One / Pass Two / Pass Three". Banned. The actual step content is the label. If you must show progression, use the verb-noun directly ("Install", "Configure", "Ship") not "Stage 1: Install".
+
+**Pills, labels and version stamps**
+* **NO pills/labels/tags overlaid on images.** No `<span>` overlays on photos with tags like `Brand · 02`, `PLATE · BRAND`, `Field notes - journal`. Either let the image speak alone, or add a caption directly below (outside the image).
+* **NO photo-credit captions as decoration.** Strings like `Field study no. 12 · Ines Caetano`, `Plate 03 · House archive`, `Frame XII · 35mm` under stock/picsum images are pretentious. Photo credit is allowed ONLY when there is a real photographer being credited for a real photo (with permission). Otherwise: skip the caption or use a one-line functional caption ("The 6-quart, in Sage.").
+* **NO version footers on marketing pages.** Footer strings like `v1.4.2`, `Build 0048`, `last sync 4s ago · main` are CLI / devtool fixtures, not landing-page content. Banned on marketing/landing/portfolio pages.
+* **NO "Reservation 412 of 800"-style live-stock counters** as decoration. Only if the brief is explicitly a limited-run waitlist with real data.
+
+**Decoration text strips**
+* **NO decoration text strip at hero bottom.** Patterns like `BRAND. MOTION. SPATIAL.`, `TYPE / FORM / MOTION`, `DESIGN · BUILD · SHIP`, `ESTD. 2018 · LISBON · BRAND. MOTION. SPATIAL.` as a small mono-caps strip across the bottom of the hero are an agency-portfolio cliché. Banned by default. Only acceptable when the strip carries real, navigable links (sticky bottom nav) or real status info (cookie banner, build info on a docs site).
+* **NO floating top-right sub-text in section headings.** Pattern: section has a giant left-aligned headline; in the top-right corner of the same section header there is a small explainer paragraph floating with no clear alignment to anything else. That floater is the Tell. Either put the sub-text directly under the headline, or build a clean 2-column header (left: headline, right: aligned body), but not a tiny corner paragraph.
+
+**Lists, dividers and scoring**
+* **NO `border-t` + `border-b` on every row of a long list / spec table.** Pick one (bottom-border between rows OR top-border above the group) and use it sparsely. A 10-row spec table with hairlines under each row is the laziest layout - see Section 4.9 for alternative UI components.
+* **NO scoring/progress bars with filled background tracks** as comparison visuals. If you need to show "X out of Y" comparisons, prefer a number + small icon, or a tiny inline bar WITHOUT a background track. Big filled `bg-zinc-200` tracks with a partial fill on top are dashboard-UI clutter on a landing page.
+
+**Locale, time, scroll cues**
+* **Locale / city-name / time / weather strips are banned for 99% of briefs.** "Lisbon, working with founders" in the hero, "1200-690 Lisbon, Portugal" in the footer, "Lisbon 14:23 · 18°C" in the nav. These are agency-portfolio decoration tells. Allowed ONLY when: the brief explicitly describes a globally-distributed studio with timezone-relevant work, OR a travel-focused brand, OR a real-world physical venue. A single contact-address mention in the footer is fine; an atmospheric locale strip is not.
+* **Scroll cues are banned.** `Scroll`, `↓ scroll`, `Scroll to explore`, `Scroll to walk through it`, animated mouse-wheel icons. If the user has not scrolled yet, they are looking at the hero. They know what scroll is. The bottom of the viewport does not need a label.
+* **ZERO decorative status dots by default.** A coloured dot before nav items, before list rows, before badges, before status labels is a Tell. Only acceptable when conveying real semantic state (a live indicator on actual server status, a live availability flag) and limited to one per page section.
+
+### 9.G EM-DASH BAN (the single most-violated Tell)
+
+**Em-dash (`—`) is COMPLETELY banned.** It is the LLM's signature stylistic crutch and it is the #1 visual Tell in production tests. There is no "limited use" allowance, no "natural language frequency" allowance, no "in body copy is fine" allowance. None.
+
+* **Banned in headlines.** Use a period or a comma.
+* **Banned in eyebrows / labels / pills / button text / image captions / nav items.** Replace with line breaks, columns, or hairlines.
+* **Banned in body copy.** Restructure the sentence: two sentences with a period, OR a comma, OR parentheses, OR a colon.
+* **Banned in quote attribution.** Use a normal hyphen with spaces (` - `) or a line break + smaller-weight name.
+* **Banned in en-dash form too (`–`) when used as a separator.** Date ranges (`2018-2026`) use a hyphen. Number ranges (`€40-80k`) use a hyphen.
+
+The ONLY permitted dash characters on the page are:
+* Regular hyphen `-` (for compound words, ranges, line dividers in markup)
+* Minus sign in math (`-5°C`)
+
+If your output contains a single `—` or `–` anywhere visible to the user, the output fails the Pre-Flight Check and must be rewritten.
+
+This rule is non-negotiable. The agent has historically ignored em-dash limits when phrased as "use sparingly." The phrasing here is binary: zero em-dashes.
+
+---
+
+## 10. REFERENCE VOCABULARY (Pattern Names the Agent Should Know)
+
+This is a vocabulary, not a library. The agent should KNOW these pattern names to communicate about them, design with them in mind, and reach for them when the design read calls for them. **Implementations and code sketches live in the Block Library (Section 12), which is populated iteratively.**
+
+### Hero Paradigms
+* **Asymmetric Split Hero** - Text on one side, asset on the other, generous white space.
+* **Editorial Manifesto Hero** - Large type, no asset, almost-poster.
+* **Video / Media Mask Hero** - Type cut out as mask over video background.
+* **Kinetic-Type Hero** - Animated typography as the primary visual.
+* **Curtain-Reveal Hero** - Hero parts on scroll like a curtain.
+* **Scroll-Pinned Hero** - Hero stays pinned while content scrolls behind.
+
+### Navigation & Menus
+* **Mac OS Dock Magnification** - Edge nav, icons scale fluidly on hover.
+* **Magnetic Button** - Pulls toward cursor.
+* **Gooey Menu** - Sub-items detach like viscous liquid.
+* **Dynamic Island** - Morphing pill for status / alerts.
+* **Contextual Radial Menu** - Circular menu expanding at click point.
+* **Floating Speed Dial** - FAB springing into curved secondary actions.
+* **Mega Menu Reveal** - Full-screen dropdown, stagger-fade content.
+
+### Layout & Grids
+* **Bento Grid** - Asymmetric tile grouping (Apple Control Center).
+* **Masonry Layout** - Staggered grid, no fixed row height.
+* **Chroma Grid** - Borders / tiles with subtle animating gradients.
+* **Split-Screen Scroll** - Two halves sliding in opposite directions.
+* **Sticky-Stack Sections** - Sections that pin and stack on scroll.
+
+### Cards & Containers
+* **Parallax Tilt Card** - 3D tilt tracking mouse coordinates.
+* **Spotlight Border Card** - Borders illuminate under cursor.
+* **Glassmorphism Panel** - Frosted glass with inner refraction.
+* **Holographic Foil Card** - Iridescent rainbow shift on hover.
+* **Tinder Swipe Stack** - Physical card stack, swipe-away.
+* **Morphing Modal** - Button expands into its own dialog.
+
+### Scroll Animations
+* **Sticky Scroll Stack** - Cards stick and physically stack.
+* **Horizontal Scroll Hijack** - Vertical scroll → horizontal pan.
+* **Locomotive / Sequence Scroll** - Video / 3D sequence tied to scrollbar.
+* **Zoom Parallax** - Central background image zooming on scroll.
+* **Scroll Progress Path** - SVG line drawing along scroll.
+* **Liquid Swipe Transition** - Page transition like viscous liquid.
+
+### Galleries & Media
+* **Dome Gallery** - 3D panoramic gallery.
+* **Coverflow Carousel** - 3D carousel with angled edges.
+* **Drag-to-Pan Grid** - Boundless draggable canvas.
+* **Accordion Image Slider** - Narrow strips expanding on hover.
+* **Hover Image Trail** - Mouse leaves popping image trail.
+* **Glitch Effect Image** - RGB-channel shift on hover.
+
+### Typography & Text
+* **Kinetic Marquee** - Endless text bands reversing on scroll.
+* **Text Mask Reveal** - Massive type as transparent window to video.
+* **Text Scramble Effect** - Matrix-style decoding on load / hover.
+* **Circular Text Path** - Text curving along spinning circle.
+* **Gradient Stroke Animation** - Outlined text with running gradient.
+* **Kinetic Typography Grid** - Letters dodging the cursor.
+
+### Micro-Interactions & Effects
+* **Particle Explosion Button** - CTA shatters into particles on success.
+* **Liquid Pull-to-Refresh** - Reload indicator like detaching droplets.
+* **Skeleton Shimmer** - Shifting light reflection across placeholders.
+* **Directional Hover-Aware Button** - Fill enters from cursor's exact side.
+* **Ripple Click Effect** - Wave from click coordinates.
+* **Animated SVG Line Drawing** - Vectors drawing themselves in real time.
+* **Mesh Gradient Background** - Organic lava-lamp blobs.
+* **Lens Blur Depth** - Background UI blurred to focus foreground action.
+
+### Animation Library Choice
+* **Motion (`motion/react`)** - default for UI / Bento / state-change motion.
+* **GSAP + ScrollTrigger** - for full-page scrolltelling and scroll hijacks. Isolate in dedicated leaf components with `useEffect` cleanup.
+* **Three.js / WebGL** - for canvas backgrounds and 3D scenes. Same isolation rule.
+* **NEVER mix GSAP / Three.js with Motion in the same component tree.** They fight over the same frames.
+
+---
+
+## 11. REDESIGN PROTOCOL
+
+This skill handles **greenfield builds AND redesigns**. Misclassifying the mode is the single biggest source of bad redesign output.
+
+### 11.A Detect the Mode (first action)
+* **Greenfield** - no existing site, or full overhaul approved. Dial baseline from Section 1.
+* **Redesign - Preserve** - modernise without breaking the brand. Audit first, extract brand tokens, evolve gradually.
+* **Redesign - Overhaul** - new visual language on top of existing content. Treat as greenfield for visuals; preserve content and IA.
+
+If ambiguous, ask **once**: *"Should this redesign preserve the existing brand, or are we starting visually from scratch?"*
+
+### 11.B Audit Before Touching
+Document the current state before proposing changes:
+* **Brand tokens** - primary / accent colors, type stack, logo treatment, radii.
+* **Information architecture** - page tree, primary nav, key conversion paths.
+* **Content blocks** - what exists, what's doing work, what's filler.
+* **Patterns to preserve** - signature interactions, recognisable hero, copy voice.
+* **Patterns to retire** - AI-slop tells, broken layouts, dead links, generic stock imagery, perf traps.
+* **Dial reading of the existing site** - infer current `DESIGN_VARIANCE` / `MOTION_INTENSITY` / `VISUAL_DENSITY`. That's your starting point, not the baseline.
+* **SEO baseline** - current ranking pages, meta titles, structured data, OG cards. **SEO migration is the #1 redesign risk.**
+
+### 11.C Preservation Rules
+* **Do not change information architecture** unless asked. Keep page slugs, anchor IDs, primary nav labels stable for SEO and muscle memory.
+* **Extract brand colors before applying Section 4.2.** A brand that is already purple stays purple - apply the LILA RULE's override.
+* **Preserve copy voice** unless asked for a rewrite. Visual modernisation ≠ content rewrite.
+* **Honor existing accessibility wins.** Do not regress focus states, alt text, keyboard nav, contrast.
+* **Respect existing analytics events.** Do not rename buttons, form fields, section IDs that downstream tracking depends on.
+
+### 11.D Modernisation Levers (priority order)
+Apply in order - stop when the brief is satisfied:
+1. **Typography refresh** - biggest visual lift per unit of risk.
+2. **Spacing & rhythm** - increase section padding, fix vertical rhythm.
+3. **Color recalibration** - desaturate, unify neutrals, keep brand accent.
+4. **Motion layer** - add `MOTION_INTENSITY`-appropriate micro-interactions to existing components.
+5. **Hero & key-section recomposition** - restructure top-of-funnel using Section 10 vocabulary.
+6. **Full block replacement** - only when the existing block is unsalvageable.
+
+### 11.E Decision Tree: Targeted Evolution vs Full Redesign
+* IA, content, and SEO sound → **targeted evolution** (Levers 1-4). ~70% of value at ~40% of risk.
+* Visual debt is structural (broken IA, no design system, broken mobile) → **full redesign** with strict content preservation.
+* Brand itself is changing → **greenfield**.
+
+### 11.F What Never Changes Silently
+Never modify without explicit user approval:
+* URL structure / route slugs.
+* Primary nav labels.
+* Form field names or order (breaks analytics + autofill).
+* Brand logo or wordmark.
+* Existing legal / consent / cookie copy.
+
+---
+
+## 12. THE BLOCK LIBRARY (Contract - Implementations Land Here Iteratively)
+
+The Reference Vocabulary (Section 10) names patterns. The Block Library implements them with real props, real motion specs, and real code sketches.
+
+**Status:** schema defined here. Blocks will be added iteratively. Do not freelance new blocks without following this schema.
+
+### 12.A File Location
+```
+skills/taste-skill/blocks/
+ hero/
+ asymmetric-split.md
+ editorial-manifesto.md
+ kinetic-type.md
+ ...
+ feature/
+ bento-grid.md
+ sticky-scroll-stack.md
+ zig-zag.md
+ ...
+ social-proof/
+ pricing/
+ cta/
+ footer/
+ navigation/
+ portfolio/
+ transition/
+```
+
+### 12.B Required Frontmatter
+```yaml
+---
+name: asymmetric-split-hero
+category: hero
+dial_compatibility:
+ variance: [6, 10]
+ motion: [3, 10]
+ density: [2, 5]
+when_to_use: "Landing pages with one strong asset and one strong message. Default hero for SaaS, agency, premium consumer."
+not_for: "Editorial / manifesto launches where the message IS the design."
+stack: ["react", "next", "tailwind", "motion"]
+---
+```
+
+### 12.C Required Body Sections
+1. **Visual sketch** - short ASCII or description of the layout.
+2. **Props API** - the component's interface.
+3. **Code sketch** - minimal working implementation (Server Component default, Client island for motion).
+4. **Mobile fallback** - explicit collapse rules for `< 768px`.
+5. **Motion variants** - one variant per `MOTION_INTENSITY` band (1-3, 4-7, 8-10). Reduced-motion fallback explicit.
+6. **Dark-mode notes** - token strategy specific to this block.
+7. **Anti-patterns** - common ways this block goes wrong.
+8. **References** - links to real examples in production.
+
+### 12.D Block-Library Discipline
+* One block per file. No multi-block files.
+* Every block must work standalone (drop it into a page, it renders).
+* Every block must pass the Pre-Flight Check (Section 14).
+* Blocks that depend on a design system from Section 2.A live under `blocks/<category>/<name>--<system>.md` (e.g. `feature/bento-grid--material.md`).
+
+---
+
+## 13. OUT OF SCOPE
+
+This skill is NOT for:
+* Dashboards / dense product UI / admin panels (use Fluent, Carbon, Atlassian, or Polaris from Section 2.A).
+* Data tables (use TanStack Table or AG Grid).
+* Multi-step forms / wizards (use Form-specific patterns; this skill won't make them better).
+* Code editors (use Monaco / CodeMirror with their official skinning).
+* Native mobile (use Apple HIG / Material directly).
+* Realtime collab UIs (presence, cursors, OT-aware - different problem class).
+
+If the brief is one of the above, **say so explicitly**, point to the right tool, and only apply this skill's marketing-page / about-page / landing-page parts to the surfaces where they apply.
+
+---
+
+## 14. FINAL PRE-FLIGHT CHECK
+
+Run this matrix before outputting code. This is the last filter.
+
+**THIS IS NOT OPTIONAL. Run every box. If any box fails, the output is not done.**
+
+- [ ] **Brief inference** declared (Section 0.B one-liner)?
+- [ ] **Dial values** explicit and reasoned from the brief, not silently using baseline?
+- [ ] **Design system** chosen from Section 2 if applicable, or aesthetic labeled honestly?
+- [ ] **Redesign mode** detected and audit performed (if applicable, Section 11)?
+- [ ] **ZERO em-dashes (`—`) anywhere on the page.** Headlines, eyebrows, pills, body, quotes, attribution, captions, buttons, alt text. Zero. (Section 9.G - non-negotiable.)
+- [ ] **Page Theme Lock**: ONE theme (light, dark, or auto) for the whole page. No section flips to inverted mode mid-page (Section 4.11)?
+- [ ] **Color Consistency Lock**: one accent color used identically across all sections (Section 4.2)?
+- [ ] **Shape Consistency Lock**: one corner-radius system applied consistently (Section 4.4)?
+- [ ] **Button Contrast Check**: every CTA text is readable against its background (no white-on-white, WCAG AA 4.5:1)?
+- [ ] **CTA Button Wrap**: no CTA label wraps to 2+ lines at desktop?
+- [ ] **Form Contrast Check**: form inputs, placeholders, focus rings, labels all pass WCAG AA against the section background?
+- [ ] **Serif discipline**: if a serif is used, it is NOT Fraunces or Instrument_Serif (or it is, with explicit brand justification)? Different serif from your previous project?
+- [ ] **Premium-consumer palette check**: if the brief is premium-consumer (cookware / wellness / artisan / luxury), the palette is NOT the AI-default beige+brass+oxblood+espresso family? Different family from your previous premium-consumer project?
+- [ ] **Italic descender clearance**: every italic word with `y g j p q` has `leading-[1.1]` min + `pb-1` reserve?
+- [ ] **Hero fits the viewport**: headline ≤ 2 lines, subtext ≤ 20 words AND ≤ 4 lines, CTA visible without scroll, font scale planned around image?
+- [ ] **Hero top padding**: max `pt-24` at desktop, hero content does not float halfway down the viewport?
+- [ ] **Hero stack discipline**: max 4 text elements in hero (eyebrow OR brand strip, headline, subtext, CTAs)? No tiny tagline below CTAs, no trust micro-strip in hero?
+- [ ] **EYEBROW COUNT (mechanical)**: count instances of `uppercase tracking` micro-labels above section headlines across all components. Count ≤ ceil(sectionCount / 3)? Hero counts as 1.
+- [ ] **Split-Header Ban**: no "left big headline + right small explainer paragraph" pattern as a section header (vertical stack instead)?
+- [ ] **Zigzag Alternation Cap**: no 3+ consecutive sections with the same image+text-split layout?
+- [ ] **No Duplicate CTA Intent**: no two CTAs with the same intent ("Get in touch" + "Let's talk" both on page = Fail)?
+- [ ] **Logo wall = logo only**: no industry / category labels printed below logos?
+- [ ] **Bento Background Diversity**: at least 2-3 bento cells have real visual variation (image, gradient, pattern), not all white-on-white text cards?
+- [ ] **"Used by / Trusted by" logo wall** lives UNDER the hero, not inside it, uses REAL SVG logos (Simple Icons / devicon) or generated SVG marks, NOT plain text wordmarks?
+- [ ] **Copy Self-Audit**: every visible string re-read, no grammatically-broken or AI-hallucinated phrases ("free on its past" type) shipped?
+- [ ] **Motion motivated**: every animation can be justified in one sentence (hierarchy / storytelling / feedback / state transition), no GSAP-for-show?
+- [ ] **Marquee max-one-per-page**: no two horizontal marquees on the same page?
+- [ ] **Navigation on ONE line** at desktop, height ≤ 80px?
+- [ ] **Section-Layout-Repetition** check: no two sections share the same layout family (at least 4 different families across 8 sections)?
+- [ ] **Bento has rhythm AND exact cell count** (N items → N cells, no empty cells in middle or at end)?
+- [ ] **Long lists use the right UI component** (not default `<ul>` with `divide-y` for > 5 items - see Section 4.9 alternatives)?
+- [ ] **Real images used** (gen-tool first, then Picsum-seed, then explicit placeholder slots) - NO div-based fake screenshots, NO hand-rolled decorative SVGs, NO pure-text minimalism?
+- [ ] **No pills/labels overlaid on images** (no `Plate · Brand`, no `Field notes - journal`)?
+- [ ] **No photo-credit captions as decoration** (`Field study no. 12 · Ines Caetano`)?
+- [ ] **No version footers** (`v1.4.2`, `Build 0048`) on marketing pages?
+- [ ] **No micro-meta-sentences** under eyebrows ("Each of these is a feature we ship today...")?
+- [ ] **No decoration text strip at hero bottom** (`BRAND. MOTION. SPATIAL.`)?
+- [ ] **No floating top-right sub-text** in section headings?
+- [ ] **No scoring/progress bars with filled background tracks** as comparison visuals?
+- [ ] **No locale / city-name / time / weather strips** unless brief is genuinely globally-distributed or place-focused?
+- [ ] **No scroll cues** (`Scroll`, `↓ scroll`, `Scroll to explore`)?
+- [ ] **No version labels in hero** (V0.6, BETA, INVITE-ONLY) unless the brief is a launch?
+- [ ] **No section-numbering eyebrows** (`00 / INDEX`, `001 · Capabilities`, `06 · how it works`)?
+- [ ] **No decorative dots** (zero by default, only for real semantic state)?
+- [ ] **No `border-t` + `border-b` on every row** of long lists / spec tables?
+- [ ] **Content density** sane: no 20-row data tables, no fake-precise specs without justification, ≤ 25-word sub-paragraphs by default?
+- [ ] **Quotes ≤ 3 lines** of body, attribution clean (no em-dash)?
+- [ ] **Motion claimed = motion shown**: if `MOTION_INTENSITY > 4`, page actually animates, not just claimed?
+- [ ] **GSAP sticky-stack / horizontal-pan** implemented per Section 5.A / 5.B canonical skeleton (`start: "top top"`, `pin: true`, correct scrub)?
+- [ ] **No `window.addEventListener('scroll')`** - using Motion `useScroll()` / ScrollTrigger / IntersectionObserver / CSS scroll-driven animations only?
+- [ ] **Reduced motion** wrapped for everything `MOTION_INTENSITY > 3`?
+- [ ] **Dark mode** tokens defined and tested in both modes?
+- [ ] **Mobile collapse** explicit (`w-full`, `px-4`, `max-w-7xl mx-auto`) for high-variance layouts?
+- [ ] **Viewport stability**: `min-h-[100dvh]`, never `h-screen`?
+- [ ] **`useEffect` animations** have strict cleanup functions?
+- [ ] **Empty / loading / error** states provided?
+- [ ] **Cards omitted** in favor of spacing where possible?
+- [ ] **Icons** from an allowed library only (Phosphor / HugeIcons / Radix / Tabler), no hand-rolled SVG paths?
+- [ ] **Motion** isolated in client-leaf components with `'use client'` at the top, memoized?
+- [ ] **No AI Tells** from Section 9 (Inter as default, AI-purple, three-equal cards, Jane Doe, Acme, "Quietly in use at")?
+- [ ] **Core Web Vitals** plausibly hit (LCP < 2.5s, INP < 200ms, CLS < 0.1)?
+- [ ] **One design system** per project (no Material + shadcn mixed)?
+
+If a single checkbox cannot be honestly ticked, the page is not done. Fix it before delivering.
+
+---
+
+# APPENDICES - Real Source-Backed Reference Material
+
+The sections below are vendored reference content. They give the agent real install commands, real canonical doc links, and real working starter snippets for each design system named in Section 2. Use them to ground decisions in production reality, not training-data fiction.
+
+## Appendix A - Install Commands per Design System
+
+```bash
+# Material Web (Material 3)
+npm install @material/web
+
+# Fluent UI React (v9)
+npm install @fluentui/react-components
+
+# Fluent UI Web Components (framework-free)
+npm install @fluentui/web-components @fluentui/tokens
+
+# IBM Carbon
+npm install @carbon/react @carbon/styles
+
+# Radix Themes
+npm install @radix-ui/themes
+
+# shadcn/ui (open code, owned components)
+npx shadcn@latest init
+npx shadcn@latest add button card badge separator input
+
+# Primer CSS (GitHub product/devtool UI)
+npm install --save @primer/css
+
+# Primer Brand (GitHub marketing UI)
+npm install @primer/react-brand
+
+# GOV.UK Frontend
+npm install govuk-frontend
+
+# USWDS (US Web Design System)
+npm install uswds
+
+# Atlassian Design System (Atlaskit)
+yarn add @atlaskit/css-reset @atlaskit/tokens @atlaskit/button @atlaskit/badge @atlaskit/section-message @atlaskit/card
+
+# Bootstrap 5.3
+npm install bootstrap
+
+# Shopify Polaris Web Components (Shopify apps only)
+# Add this to your app HTML head:
+# <meta name="shopify-api-key" content="%SHOPIFY_API_KEY%" />
+# <script src="https://cdn.shopify.com/shopifycloud/polaris.js"></script>
+```
+
+## Appendix B - Canonical Sources (read these before reinventing)
+
+### Material Web
+- https://github.com/material-components/material-web
+- https://material-web.dev/theming/material-theming/
+- https://m3.material.io/develop/web
+
+### Fluent UI
+- https://fluent2.microsoft.design/get-started/develop
+- https://fluent2.microsoft.design/components/web/react/
+- https://github.com/microsoft/fluentui
+- https://learn.microsoft.com/en-us/fluent-ui/web-components/
+
+### Carbon
+- https://carbondesignsystem.com/
+- https://github.com/carbon-design-system/carbon
+- https://carbondesignsystem.com/developing/react-tutorial/overview/
+- https://carbondesignsystem.com/developing/web-components-tutorial/overview/
+
+### Shopify Polaris
+- https://shopify.dev/docs/api/app-home/web-components
+- https://github.com/Shopify/polaris-react
+- https://polaris-react.shopify.com/components
+
+### Atlassian
+- https://atlassian.design/get-started/develop
+- https://atlassian.design/components/button/examples
+- https://atlaskit.atlassian.com/packages/design-system/button/example/disabled
+- https://atlassian.design/tokens/design-tokens
+
+### Primer
+- https://primer.style/
+- https://github.com/primer/css
+- https://github.com/primer/brand
+
+### GOV.UK
+- https://design-system.service.gov.uk/components/button/
+- https://design-system.service.gov.uk/styles/layout/
+- https://github.com/alphagov/govuk-frontend
+
+### USWDS
+- https://designsystem.digital.gov/documentation/developers/
+- https://designsystem.digital.gov/components/button/
+- https://designsystem.digital.gov/components/card/
+- https://github.com/uswds/uswds
+
+### Bootstrap
+- https://getbootstrap.com/docs/5.3/layout/grid/
+- https://getbootstrap.com/docs/5.3/components/card/
+
+### Tailwind
+- https://tailwindcss.com/docs/dark-mode
+- https://tailwindcss.com/blog/tailwindcss-v4
+
+### Radix
+- https://www.radix-ui.com/themes/docs/components/theme
+- https://www.radix-ui.com/themes/docs/components/card
+- https://github.com/radix-ui/themes
+
+### shadcn/ui
+- https://ui.shadcn.com/docs
+- https://ui.shadcn.com/docs/components/card
+- https://github.com/shadcn-ui/ui
+
+### Native CSS / W3C standards
+- https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/Properties/backdrop-filter
+- https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/At-rules/@media/prefers-color-scheme
+- https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/At-rules/@media/prefers-reduced-motion
+- https://developer.mozilla.org/en-US/docs/Web/CSS/Guides/Grid_layout
+- https://developer.mozilla.org/en-US/docs/Web/CSS/Guides/Scroll-driven_animations
+- https://drafts.csswg.org/scroll-animations-1/
+
+### Apple Liquid Glass (Apple platforms only)
+- https://developer.apple.com/design/human-interface-guidelines/materials
+- https://developer.apple.com/documentation/TechnologyOverviews/liquid-glass
+- https://developer.apple.com/documentation/TechnologyOverviews/adopting-liquid-glass
+- https://developer.apple.com/documentation/SwiftUI/Material
+
+---
+
+## Appendix C - Apple Liquid Glass: Honest Web Approximation
+
+Do **not** treat random CSS snippets as official Apple Liquid Glass.
+
+### What is official
+Apple documents Liquid Glass inside Apple's Human Interface Guidelines and Developer Documentation for **Apple platforms**. It is a dynamic material used across Apple platform UI. Apple's native implementation belongs to Apple platform APIs and system components, **not a public web CSS package**.
+
+Relevant official docs:
+- Apple Human Interface Guidelines → Materials
+- Apple Developer Documentation → Liquid Glass
+- Apple Developer Documentation → Adopting Liquid Glass
+- SwiftUI → Material
+
+### What is NOT official
+There is no `liquid-glass.css` from Apple for normal websites.
+
+A web approximation can use:
+- `backdrop-filter`
+- transparent backgrounds
+- layered borders
+- highlight overlays
+- gradients
+- motion
+- strong contrast fallbacks
+
+But that is **web glassmorphism / frosted-glass approximation**, not official Apple Liquid Glass. Label it as such in comments.
+
+### Safer web approximation skeleton
+
+```css
+.liquid-glass-web-approx {
+ position: relative;
+ isolation: isolate;
+ overflow: hidden;
+ border-radius: 999px;
+ border: 1px solid rgb(255 255 255 / .32);
+ background:
+ linear-gradient(135deg, rgb(255 255 255 / .30), rgb(255 255 255 / .08)),
+ rgb(255 255 255 / .12);
+ backdrop-filter: blur(24px) saturate(180%) contrast(1.05);
+ -webkit-backdrop-filter: blur(24px) saturate(180%) contrast(1.05);
+ box-shadow:
+ inset 0 1px 0 rgb(255 255 255 / .48),
+ inset 0 -1px 0 rgb(255 255 255 / .12),
+ 0 18px 60px rgb(0 0 0 / .18);
+}
+
+.liquid-glass-web-approx::before {
+ content: "";
+ position: absolute;
+ inset: 0;
+ z-index: -1;
+ border-radius: inherit;
+ background:
+ radial-gradient(circle at 20% 0%, rgb(255 255 255 / .55), transparent 34%),
+ linear-gradient(90deg, rgb(255 255 255 / .18), transparent 42%, rgb(255 255 255 / .14));
+ pointer-events: none;
+}
+
+.liquid-glass-web-approx::after {
+ content: "";
+ position: absolute;
+ inset: 1px;
+ border-radius: inherit;
+ border: 1px solid rgb(255 255 255 / .14);
+ pointer-events: none;
+}
+
+@media (prefers-color-scheme: dark) {
+ .liquid-glass-web-approx {
+ border-color: rgb(255 255 255 / .18);
+ background:
+ linear-gradient(135deg, rgb(255 255 255 / .16), rgb(255 255 255 / .04)),
+ rgb(15 23 42 / .42);
+ box-shadow:
+ inset 0 1px 0 rgb(255 255 255 / .22),
+ 0 18px 60px rgb(0 0 0 / .42);
+ }
+}
+
+@media (prefers-reduced-transparency: reduce) {
+ .liquid-glass-web-approx {
+ background: rgb(255 255 255 / .96);
+ backdrop-filter: none;
+ -webkit-backdrop-filter: none;
+ }
+}
+```
+
+**Important:** `prefers-reduced-transparency` has uneven browser support; test it. Always provide enough contrast even without blur.
+
+---
+
+**End of appendices.** Install commands above are reality anchors. The Apple Liquid Glass skeleton is a labeled approximation, not an Apple-issued package. For canonical docs per design system, consult the system's official docs (links in Section 2 plus Appendix B).
diff --git a/.gitignore b/.gitignore
index fb62f0e..615fe66 100644
--- a/.gitignore
+++ b/.gitignore
@@ -59,3 +59,4 @@ evidence/
logs/
frontend/*.tsbuildinfo
file
+scratch/
diff --git a/README.md b/README.md
index c293173..304cdd7 100644
--- a/README.md
+++ b/README.md
@@ -1,638 +1,469 @@
<div align="center">
-<img src="frontend/public/brand/ares-logo.png" alt="ARES" width="460">
+<img src="frontend/public/brand/ares-logo.png" alt="ARES Logo" width="480">
-# ARES
+# ARES™
+### Autonomous Adversary Emulation & Continuous Security Validation Platform
-### Automated Red Team Engagement System
+**The open-core platform empowering enterprise red teams, MSSPs, and security operations centers to safely simulate advanced threat actors, discover deterministic attack paths, and continuously validate defensive posture with zero collateral risk.**
-ARES is an authorized red-team engagement framework for scoped campaigns,
-module orchestration, OPSEC-aware execution, encrypted credential handling,
-and professional report generation.
+<br>
-[![Python](https://img.shields.io/badge/Python-3.11%2B-3776AB?style=for-the-badge&logo=python&logoColor=white)](https://python.org)
-[![FastAPI](https://img.shields.io/badge/API-FastAPI-009688?style=for-the-badge&logo=fastapi&logoColor=white)](https://fastapi.tiangolo.com)
-[![React](https://img.shields.io/badge/Dashboard-React-61DAFB?style=for-the-badge&logo=react&logoColor=111111)](https://react.dev)
-[![License](https://img.shields.io/badge/License-MIT-22C55E?style=for-the-badge)](LICENSE)
-[![Status](https://img.shields.io/badge/Unit%20Suite-passing-22C55E?style=for-the-badge)](tests/)
+[![Version](https://img.shields.io/badge/Release-v6.0--Enterprise-red?style=for-the-badge&logo=shield)](releases/)
+[![Python](https://img.shields.io/badge/Engine-Python%203.12%2B-3776AB?style=for-the-badge&logo=python&logoColor=white)](https://python.org)
+[![FastAPI](https://img.shields.io/badge/Backend-FastAPI%20Async-009688?style=for-the-badge&logo=fastapi&logoColor=white)](https://fastapi.tiangolo.com)
+[![React](https://img.shields.io/badge/Frontend-React%2019%20%7C%20Vite-61DAFB?style=for-the-badge&logo=react&logoColor=111111)](https://react.dev)
+[![MITRE](https://img.shields.io/badge/Coverage-MITRE%20ATT%26CK-FF6F00?style=for-the-badge)](docs/modules.md)
+[![Security](https://img.shields.io/badge/Security-Zero--Trust%20Enclave-22C55E?style=for-the-badge)](docs/security-model.md)
+[![License](https://img.shields.io/badge/License-MIT-blue?style=for-the-badge)](LICENSE)
+[![Unit Suite](https://img.shields.io/badge/Tests-128%20Passing-22C55E?style=for-the-badge)](tests/)
-**Built for labs, internal security teams, and authorized engagements only.**
+<br>
+
+[**Platform Showcase**](#-platform-showcase--control-surfaces) • [**Why ARES?**](#-why-enterprises-choose-ares) • [**Competitive Matrix**](#-market-comparison-matrix) • [**Architecture**](#-system-architecture--data-pipeline) • [**MITRE Matrix**](#-adversary-techniques--mitre-attck-matrix) • [**Quickstart**](#-quickstart-up-and-running-in-60-seconds) • [**Zero-Trust Security**](#-enterprise-security-model--compliance) • [**Documentation**](docs/)
</div>
---
-## What ARES Is
+## ⚡ Executive Summary
-ARES turns a red-team or security-validation engagement into a structured,
-auditable workflow:
+Traditional penetration testing is fundamentally flawed: it is expensive, episodic, point-in-time, and leaves organizations blind to newly introduced misconfigurations and emerging adversary tradecraft. Meanwhile, automated vulnerability scanners overwhelm SOC teams with thousands of hypothetical CVEs without demonstrating exploitability or multi-stage lateral attack paths.
-1. Create a campaign.
-2. Define explicit scope.
-3. Select modules from the catalog.
-4. Validate parameters with dry-run mode.
-5. Execute authorized checks.
-6. Store evidence and credentials safely.
-7. Review findings, graph data, and OPSEC risk.
-8. Generate branded reports.
-9. Clean up test campaigns from the dashboard.
+**ARES bridges this gap.** Built from the ground up for modern enterprise infrastructure, ARES delivers an **autonomous, goal-directed adversary emulation platform** that models real-world threat actors. By combining hard kernel-level scope firewalls, adaptive OPSEC noise profiling, an interactive directed acyclic graph (DAG) attack solver, and 60+ weaponized techniques mapped to MITRE ATT&CK, ARES allows security teams to prove vulnerability exploitability, locate shortest compromise paths to Active Directory Crown Jewels, and generate executive-ready deliverables with zero operational downtime.
-ARES is designed for the part of an engagement where authorization already
-exists and the operator needs discipline, repeatability, reporting, and guardrails.
+---
-## Demo Video
+## 🎯 Why Enterprises Choose ARES
-[![ARES Kerberoast Active Directory Lab](https://img.youtube.com/vi/jsw_qoCxkps/maxresdefault.jpg)](https://www.youtube.com/watch?v=jsw_qoCxkps)
+```
+ THE ARES ADVANTAGE
+ ┌─────────────────────────┐ ┌─────────────────────────┐ ┌─────────────────────────┐
+ │ STRICT SCOPE ENCLAVE │ │ AUTONOMOUS DAG ENGINE │ │ ZERO-TRUST ARCHITECTURE │
+ │ Hard kernel CIDR egress │ │ Computes shortest paths │ │ Memory-only JWT tokens, │
+ │ whitelisting prevents │───│ to Domain Admins & Crown│───│ AES-256 encrypted vault,│
+ │ any collateral impact. │ │ Jewels deterministically│ │ strict HMAC-CSRF checks.│
+ └─────────────────────────┘ └─────────────────────────┘ └─────────────────────────┘
+ │
+ ▼
+ ┌─────────────────────────┐
+ │ INSTANT EXECUTIVE SUITE │
+ │ Branded PDF, HTML, JSON │
+ │ deliverables with zero │
+ │ native GTK dependencies │
+ └─────────────────────────┘
+```
-This demo shows ARES running a guided Kerberoast workflow inside an isolated Active Directory lab, including SPN enumeration, Kerberoast execution, telemetry, findings, and dashboard reporting.
+### Core Value Pillars
-## What ARES Is Not
+1. **🛡️ Zero-Collateral Scope Governance**: Every campaign runs inside an isolated cryptographic boundary. Hard target IP and CIDR validations at the network socket layer guarantee that no packet ever touches out-of-scope infrastructure.
+2. **🧠 Autonomous Goal-Directed Planning**: Operators set high-level objectives (e.g. `domain_admin`, `full_compromise`, `cloud_audit`), and the ARES decision engine autonomously synthesizes multi-stage execution paths using graph heuristics and optional LLM agents (Claude / OpenAI / local Ollama).
+3. **🕸️ Multi-Vector Attack Graph (DAG)**: Ingest BloodHound collections or map active domain sessions in real time. The built-in graph engine calculates shortest attack paths, highlights chokepoints, and simulates lateral pivot feasibility.
+4. **🔐 Defense-in-Depth Security Model**: Engineered for zero-trust environments. Database-authoritative sessions, memory-only short-lived JWT access tokens, HttpOnly rotating refresh credentials, and AES-256-GCM encrypted local vaults protect harvested hashes and sensitive client evidence.
+5. **📑 Automated Deliverables Pipeline**: One-click generation of branded, audit-ready compliance deliverables in PDF, HTML, Markdown, and JSON formats. Features automated headless browser PDF rendering on Windows/Linux without external GTK dependencies.
-ARES is not:
+---
-- A C2 framework.
-- An implant or beacon framework.
-- A phishing framework.
-- An initial-access toolkit.
-- A tool for testing systems without written authorization.
+## 📊 Market Comparison Matrix
-Do not use ARES against systems you do not own or have explicit permission to
-assess.
+| Operational Capability | Traditional Manual Pentest | Legacy Vulnerability Scanners | ARES Autonomous Platform |
+| :--- | :---: | :---: | :---: |
+| **Testing Frequency** | Annual / Semi-Annual | Scheduled Daily / Weekly | **Continuous / On-Demand** |
+| **Exploitability Validation** | Manual & Labor Intensive | ❌ Theoretical CVE Matching | **Deterministic Multi-Stage Proof** |
+| **Multi-Hop Attack Paths** | Manual Drawing | ❌ None | **Real-Time Interactive DAG** |
+| **Scope Enclave & Egress Firewall** | Operator Discipline Only | Network Firewalls Only | **Hard Socket-Level CIDR Enforcement** |
+| **Active Directory Lateral Paths** | Slow Script Execution | ❌ No Active Paths | **Native BloodHound & Kerberos Suite** |
+| **Credential Security & Storage** | Loose Flat Files / Cleartext | Vulnerability Logs | **AES-256-GCM Encrypted Vault** |
+| **OPSEC & Telemetry Throttling** | Manual Jitter Scripts | High Network Noise | **Adaptive Noise Profiles & Governor** |
+| **Delivery Time for Reports** | 1–2 Weeks Post-Engagement | Raw Data Dumps | **Instant Multi-Format Artifacts** |
+| **Deployment Footprint** | External Consultants | Bulky Cloud Agents | **Air-Gapped Local / Self-Hosted** |
---
-## Start Here: Fast Path
+## 🖥️ Platform Showcase & Control Surfaces
-For the complete first-run walkthrough, use [QUICKSTART.md](QUICKSTART.md).
-The short Windows PowerShell path is:
+The ARES Platform features a high-performance, responsive operator dashboard engineered with dark-tech aesthetics, low cognitive load, and audited operational control.
```powershell
-git clone https://github.com/Mafifrizi/ARES.git
-Set-Location .\ARES
+# Launch local development environment
+.\.venv\Scripts\ares.exe dashboard dev --no-reload
+```
-py -3.12 -m venv .venv
-.\.venv\Scripts\python.exe -m pip install -U pip
-.\.venv\Scripts\python.exe -m pip install -e ".[dev,pdf]"
+---
-Set-Location frontend
-& "C:\Program Files\nodejs\npm.cmd" ci
-Set-Location ..
+### 1. 🛡️ Operator Enclave & Zero-Trust Gateway
-$env:ARES_PDF_BROWSER = "C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"
-.\.venv\Scripts\ares.exe doctor --pdf-smoke
+*Autonomous entry barrier designed specifically for authorized offensive operators and security personnel.*
-.\.venv\Scripts\ares.exe dashboard dev --no-reload
-```
+<div align="center">
+
+![ARES Operator Enclave & Zero-Trust Authentication Gateway](docs/assets/screenshots/login-enclave.png)
+
+*ARES Operator Enclave featuring live Dragon-Scale Hexagonal Mesh visualizer and defense-in-depth security boundary.*
+
+</div>
-Configure `ARES_SECRET_KEY`, `ARES_ENCRYPTION_KEY`, and
-`ARES_DEFAULT_ADMIN_PASSWORD` before first login. Open
-`http://127.0.0.1:5173/dashboard/`, log in as `admin` with the
-`ARES_DEFAULT_ADMIN_PASSWORD` value, create a campaign/scope, run a module,
-review findings, then generate, download, or delete reports from the Report
-Library.
+- **The Problem Solved**: Eliminates unauthorized operator access, token replay attacks, and token leakage to local browser storage.
+- **Key Capabilities**:
+ - Live **Dragon-Scale Hexagonal Mesh Canvas**: Low-overhead hardware-accelerated canvas visualizing DAG lattice density while responding dynamically to operator proximity.
+ - **Memory-Only Token Isolation**: Short-lived JWTs reside strictly in memory; refresh credentials use host-only, HttpOnly cookies with one-time rotation.
+ - **HMAC Double-Submit CSRF Protection**: Constant-time verification on all state-mutating requests (`X-ARES-CSRF`).
+ - **Cryptographic Brute-Force Shield**: Enforces exponential backoff and IP-based rate limiting on authentication attempts.
---
-## Why It Exists
+### 2. 📊 Executive Command Center & Telemetry
-Offensive security work can become messy fast: scattered scripts, loose notes,
-untracked evidence, unclear scope, repeated manual validation, and reports that
-take longer than the test.
+*Real-time operational command console providing instant posture visibility across active campaigns.*
-ARES focuses on the operational layer:
+<div align="center">
+
+![ARES Executive Command Center & Telemetry](docs/assets/screenshots/dashboard-overview.png)
-| Problem | ARES Approach |
-| --- | --- |
-| "What campaign is this finding from?" | Campaign-scoped storage and reports. |
-| "Can this module run safely?" | Parameter validation, dry-run mode, OPSEC levels. |
-| "Are we inside scope?" | Scope-first campaign model and backend validation. |
-| "Where did this credential come from?" | Encrypted credential vault and campaign audit trail. |
-| "How do we explain results?" | MITRE-aware findings and branded report generation. |
-| "How do we avoid UI clutter?" | Campaign and API-key delete flows with backend cleanup. |
-| "How do we test the app after changes?" | Local validation lab script. |
+*Executive Command Center displaying real-time telemetry, confirmed findings by severity, and operational health.*
+
+</div>
+
+- **The Problem Solved**: Aggregates scattered offensive metrics into a single real-time operational pane without requiring manual status queries.
+- **Key Capabilities**:
+ - **Unified Scope Context**: Switch seamlessly between `Scope: Global / All` (enterprise-wide telemetry) and specific engagement campaigns (`AD Lab Simulation`).
+ - **Finding Severity Breakdown**: Live counters for Critical, High, Medium, Low, and Informational findings with CVSS v3 score tracking.
+ - **Telemetry & Worker Health**: Monitor background task queue depth, execution error rates, and active worker statuses in real time.
+ - **Audited Activity Stream**: Immutable event log tracking every module dispatch, credential discovery, and lateral progression.
---
-## Core Features
+### 3. 🎯 Scoped Campaign & Target Boundary Management
-### Operator Dashboard
+*Zero-collateral target governance enforcing hard CIDR whitelist boundaries and encrypted evidence isolation.*
-ARES has two dashboard serving modes:
+<div align="center">
-- Local development: run the launcher from the repository root and open the
- Vite dashboard at `http://127.0.0.1:5173/dashboard/`.
-- Production/static serving: after the frontend assets are built, FastAPI
- serves the compiled dashboard at `/dashboard`.
+![ARES Scoped Campaign & Target Boundary Management](docs/assets/screenshots/dashboard-campaigns.png)
-Recommended local development command:
+*Campaign Management interface showing target scopes, CIDR boundaries, noise controls, and encrypted credential vault.*
-```bash
-ares dashboard dev --no-reload
-```
+</div>
-Windows virtualenv example:
+- **The Problem Solved**: Prevents catastrophic out-of-scope scanning and eliminates unencrypted credential files on operator laptops.
+- **Key Capabilities**:
+ - **Hard CIDR Whitelists**: Network-level boundary enforcement. The engine intercepts and drops any request targeting unapproved IP addresses or subnets.
+ - **Noise Profiles & Jitter**: Configure engagement throttle levels (`Stealth`, `Low Noise`, `Aggressive`) with randomized delay distributions.
+ - **AES-256 Encrypted Enclave Vault**: Harvested NTLM hashes, Kerberos tickets, and service credentials are encrypted at rest with AES-256-GCM.
+ - **Clean Teardown Workflows**: Single-click campaign deletion that securely cleans up all associated database rows, graph vertices, and temporary artifacts.
-```powershell
-.\.venv\Scripts\ares.exe dashboard dev --no-reload
-```
+---
-Dashboard preview:
-
-![ARES dashboard overview](docs/assets/screenshots/dashboard-overview.png)
-
-Dashboard shell:
-
-- The left sidebar routes between the major dashboard pages.
-- The topbar menu button collapses and expands the sidebar.
-- Topbar quick search is client-side navigation over the currently loaded
- dashboard context: page names/routes, campaigns, modules, reports, and
- templates. It is not a server-backed global search across unloaded historical
- data.
-- The notification bell is the status surface. There is no separate topbar
- status pill labeled `Offline` or `Live`.
-- The notification badge counts unread notifications only. Opening the drawer
- marks visible notifications as read; individual dismiss and clear-all actions
- remove notifications from the current session. The frontend stores only
- notification state, not bodies, tokens, API keys, stack traces, or raw
- payloads.
-- The topbar also shows the signed-in identity and logout action.
-- Page headers provide context, and page tabs switch the visible content for
- the current section.
-
-Dashboard areas:
-
-| Page | Purpose |
-| --- | --- |
-| Overview | Health, operator telemetry metrics, and campaign summary. Overview has no variation tabs. |
-| Campaigns | `List`, `Scope`, and `Findings` tabs for campaign creation, inspection, compare/restore/dry-run actions, and cleanup. |
-| Modules | `Catalog`, `Run Panel`, and `Results` tabs for browsing modules, filling backend-generated parameter forms, and reviewing execution output. |
-| Reports | `Generate` and `Library` tabs for authenticated campaign report creation, listing, download, per-report delete, and Delete all / Clear library cleanup. |
-| Graph | `Entities`, `Attack Paths`, and `Ingest` tabs for graph review and BloodHound/SharpHound import. |
-| Templates | `Templates` and `Plan Builder` tabs for selecting built-in plans and generating reviewable execution stages. |
-| Strategy | `Objective`, `Active`, and `Result` tabs for authorized goal-based planning and state review. |
-| Security | `Account`, `API Keys`, and `Audit` tabs for password changes, API key lifecycle, audit output, and user review. |
-| EDR/OPSEC | `Knowledge Base` and `Report Outcome` tabs for defensive telemetry and controlled outcome records. |
-| Live | `Stream` and `Buffer` tabs for campaign WebSocket feedback and buffered event review. |
-
-Recommended dashboard workflow:
-
-1. Start in `Campaigns` and create a campaign with a name, client, targets,
- and scope CIDRs.
-2. Use `Modules` to search for a module, pick the campaign, fill the generated
- parameters, and run it in dry-run mode first. The page shows a running state
- while execution is in progress and surfaces scope or validation errors in the
- result panel.
-3. Use `Graph` only after a campaign exists. To ingest BloodHound or
- SharpHound data, enter a JSON file or directory path that is local to the
- machine running the ARES API, then click `Ingest`.
-4. Use `Templates` when you want a repeatable plan. Select a built-in template,
- optionally provide JSON parameters, and click `Generate Plan`. This creates
- a structured execution plan for review; it does not silently execute modules.
-5. Use `Strategy` for goal-based planning. Select a campaign, choose a goal
- such as `domain_admin`, provide explicit authorization notes, and click
- `Engage`. RBAC and backend authorization checks still apply.
-6. Use `Reports` to generate HTML, PDF, Markdown, or JSON output for a campaign.
- PDF generation writes the PDF artifact directly; HTML is generated only when
- you choose the HTML format. Report evidence is rendered as readable tables
- and key-value rows where possible instead of unformatted report objects.
- Report evidence is redacted by default; include sensitive evidence only
- intentionally and only with authorized access. The Library tab supports
- Download, per-report Delete, and Delete all / Clear library cleanup.
- Successful deletes remove rows and update the artifact count without a page
- reload.
-7. Use `Security` for account administration. API keys are for scripts and
- integrations; the Security Audit panel reports dependency-audit status for
- the ARES environment, not findings from a target network.
-8. Use `EDR/OPSEC` to record controlled bypass outcomes and review historical
- telemetry. This page stores defensive-validation data; it does not generate
- payloads or bypass logic.
-
-Common page inputs and outputs:
-
-| Area | What you provide | What ARES returns | Use it when |
-| --- | --- | --- | --- |
-| Templates | Template name plus optional JSON parameters. | A reviewable execution plan with stages and module IDs. | You want a consistent plan for a common engagement type. |
-| Strategy | Campaign, goal, and authorization notes. | Active engagement state and strategy events. | You want ARES to plan toward an authorized objective while preserving RBAC checks. |
-| Security Audit | No target input; team-lead access only. | Dependency-audit snapshot, scanner status, and environment warnings. | You want to verify the ARES runtime dependencies and security posture. |
-| EDR/OPSEC | Technique ID, EDR vendor, version, outcome, campaign, and notes. | Historical success-rate telemetry and outcome records. | You want to track defensive visibility and tune OPSEC decisions from controlled tests. |
-| Graph Ingest | Campaign plus local BloodHound/SharpHound JSON path. | Campaign graph nodes, links, and attack-path candidates. | You already collected BloodHound-style data and want it mapped into ARES. |
-
-Telemetry note:
-
-The Overview telemetry panel combines live process metrics with database-backed
-aggregates for module runs, confirmed findings, and discovered hosts. Queue
-depth and worker health remain process-local and reset on restart; campaign
-findings, credentials, module-run records, and graph snapshots remain durable.
-
-Graph data is hydrated from campaign records and a sanitized persisted graph
-snapshot. BloodHound/SharpHound imports are available to later graph requests;
-credential secrets are never included in graph or API payloads.
-
-Planning modes:
-
-| Mode | Where to use it | Requires LLM key? | What it does |
-| --- | --- | --- | --- |
-| Template plan | `Templates` page | No | Builds a deterministic plan from a named template such as `internal_pentest`. It is for review and does not execute modules by itself. |
-| AI planner module | `Modules` page, module `ai.autonomous_planner` | Yes, unless using local Ollama | Reads campaign context and asks Claude, OpenAI, or a local Ollama model to produce a proposed execution plan with reasoning, confidence, and OPSEC warnings. |
-| Strategy engagement | `Strategy` page | Usually yes | Starts a background goal-based strategy loop for an existing campaign. It uses AI planning and OPSEC checks, then sends progress events to the `Live` page. |
-| Internal scorer | CLI / engine internals | No | Ranks possible next modules from local campaign/session state. This is AI-style scoring, not an external LLM call. |
-
-The ARES API key created in the `Security` page is not an OpenAI, Anthropic,
-or Ollama key. It authenticates scripts and integrations to the ARES API.
-LLM provider keys are configured separately in the ARES server environment.
-Creating an ARES API key opens the `Save your key` modal. The full secret is
-shown once, the `Copy` button changes to `Copied` after a successful copy, and
-`Done` closes the modal and clears the in-memory new-key state. The key list
-shows metadata and a prefix only; the full secret cannot be retrieved later.
-
-See [docs/dashboard-guide.md](docs/dashboard-guide.md).
-
-### Campaign System
-
-- Explicit campaign scope.
-- Campaign-specific findings, hosts, credentials, loot, reports, and graph data.
-- Team-lead-only campaign deletion for lab cleanup.
-- Vault restore after restart.
-- Campaign diff and CVSS summary.
-
-### Module Orchestration
-
-- 60+ built-in modules across AD, Windows, Linux, cloud, network, credential,
- lateral movement, EDR/OPSEC, exfil exposure checks, persistence review, and AI
- planning.
-- Backend-driven module parameter schema.
-- Dry-run default in the dashboard.
-- OPSEC levels for module risk.
-- High-noise and sensitive modules remain guarded by authorization and
- confirmation checks.
-- MITRE ATT&CK metadata for reporting.
-
-See [docs/modules.md](docs/modules.md).
-
-### Security Controls
-
-- Database-authoritative JWT access with one refresh-token family per login,
- one-time rotation, strict replay-family revocation, and no JWT role authority.
-- Same-origin browser sessions with memory-only access tokens, host-only
- HttpOnly refresh cookies, strict Origin checks, and constant-time CSRF
- validation. Refresh credentials are never returned in JSON or browser storage.
-- Current-device and all-device logout plus immediate epoch revocation after
- password, role, or activation security events.
-- API key lifecycle with revoked-key removal from dashboard lists.
-- RBAC roles: team lead, operator, recon, reporter.
-- Encrypted data handling for sensitive credential material.
-- Backend validation for scope, params, paths, and auth.
-- Rate limiting for sensitive flows.
-- Security headers and audit visibility.
-
-See [docs/security-model.md](docs/security-model.md).
-
-Production requires one exact HTTPS `ARES_BROWSER_ORIGIN`. Browser auth is
-same-origin and CORS remains noncredentialed; use API keys for automation.
-Backend and frontend cookie-transport changes must be deployed atomically,
-existing sockets drained, and existing users asked to sign in again. No schema
-revision beyond `0009` is required for this transport change.
-
-### User Roles And Accounts
-
-ARES creates the first `admin` account automatically when the user table is
-empty. That bootstrap account is assigned the `team_lead` role and uses the
-password provided in `ARES_DEFAULT_ADMIN_PASSWORD`. Change that password after
-the first login.
-
-Bootstrap happens only when the user table is empty. Changing
-`ARES_DEFAULT_ADMIN_PASSWORD` after an `admin` user already exists does not
-reset that user's password. For local development, either change the password
-from the `Security` page after logging in or recreate the local database if you
-intend to discard existing local data.
-
-Local development reset warning: this deletes local dashboard data in
-`ares.db`. Do not use it on real or shared deployments.
+### 4. ⚡ Modular Adversary Orchestration (60+ Modules)
-```powershell
-New-Item -ItemType Directory -Force ".\_db_backup" | Out-Null
-if (Test-Path ".\ares.db") {
- Copy-Item ".\ares.db" ".\_db_backup\ares.db.before-reset" -Force
-}
-Remove-Item ".\ares.db" -Force -ErrorAction SilentlyContinue
-```
+*Extensive catalog of weaponized adversary techniques aligned with the MITRE ATT&CK enterprise matrix.*
-Roles are assigned when a `team_lead` creates a user:
-
-| Role | Intended use | Practical access |
-| --- | --- | --- |
-| `team_lead` | Engagement lead or local administrator. | Full API access, user registration, security audit, campaign deletion, high-noise authorization, and normal operator work. |
-| `operator` | Day-to-day operator account. | Campaign workflows, module execution, reports, graph, artifacts, and standard validation flows. Cannot register users. |
-| `recon` | Low-risk review/recon identity. | Read-heavy access. The internal module permission matrix marks enumeration, fingerprint, and network modules as recon-safe, but the main dashboard execution endpoints are still operator-gated. |
-| `reporter` | Report reviewer or stakeholder account. | Read-only access to campaign/report/graph-style data. No module execution and no user administration. |
-
-Create additional users through `POST /auth/register` while logged in as
-`team_lead`. Browser login is cookie/CSRF protected; follow the browser-session
-example in [docs/api-reference.md](docs/api-reference.md) instead of posting a
-password directly to the backend origin.
-
-Valid role values are exactly `team_lead`, `operator`, `recon`, and `reporter`.
-Passwords must be at least 12 characters and include uppercase, lowercase,
-number, and special-character content. The current dashboard lists users in the
-Security page, but role assignment is done at account creation time through
-`POST /auth/register`.
-
-### Reporting
-
-- HTML, Markdown, and JSON report output.
-- PDF output through WeasyPrint when available, with an Edge/Chrome/Chromium
- browser fallback for local environments that do not have WeasyPrint native
- libraries installed.
-- On Windows, use Python 3.12.x from a normal non-Administrator PowerShell for
- dashboard PDF export. If auto-detection needs help, set the fallback for the
- current PowerShell session:
-
- ```powershell
- $env:ARES_PDF_BROWSER = "C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"
- .\.venv\Scripts\ares.exe doctor --pdf-smoke
- ```
-
-- WeasyPrint on Windows needs native GTK/Pango libraries in addition to the pip
- package; run `ares doctor --pdf-smoke` to verify the active PDF backend.
-- ARES branding in generated reports with footer-safe page spacing.
-- Findings, readable evidence tables, severity, timeline, MITRE, and
- remediation-oriented sections.
-- Authenticated report download through the dashboard.
-- Report Library cleanup through per-report Delete and Delete all / Clear
- library actions.
-- Sensitive report evidence is redacted by default. Include raw hashes,
- secrets, or other sensitive evidence only for authorized internal review,
- never in public demos or shared reports.
-
-### Validation Lab
-
-ARES includes a local validation harness for checking the app after changes.
-
-It validates:
-
-- Health endpoint.
-- Login and current profile.
-- Campaign input validation.
-- Local campaign create/list/delete.
-- Module dry-run validation.
-- Module API parameter validation.
-- Report generation and listing.
-- API key create/list/delete/list-after-delete.
-
-See [docs/validation-lab.md](docs/validation-lab.md).
+<div align="center">
----
+![ARES Modular Adversary Orchestration](docs/assets/screenshots/dashboard-modules-catalog.png)
+
+*Module Catalog with MITRE ATT&CK categorization, dynamic parameter generation, and dry-run safety modes.*
+
+</div>
-## Quickstart
-
-Use [QUICKSTART.md](QUICKSTART.md) as the complete source of truth for the
-first-run path from clone to report. The universal order is:
-
-1. Clone the repo.
-2. Create `.venv`.
-3. Install `.[dev,pdf]`.
-4. Run `npm ci` in `frontend/`.
-5. Configure `ARES_SECRET_KEY`, `ARES_ENCRYPTION_KEY`, and
- `ARES_DEFAULT_ADMIN_PASSWORD`.
-6. Set `$env:ARES_PDF_BROWSER = "C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"`
- on Windows when using Edge PDF fallback.
-7. Run `.\.venv\Scripts\ares.exe doctor --pdf-smoke`.
-8. Start `.\.venv\Scripts\ares.exe dashboard dev --no-reload`.
-9. Log in, create a campaign/scope, run a module, review findings, and manage
- reports from the Report Library.
-
-Optional module families are installed only when needed, for example `.[ad]`,
-`.[cloud]`, `.[windows]`, or `.[full]`. For AD users with source/local
-Impacket already importable, use `.[ad-support]` for the remaining direct AD
-support libraries; see [QUICKSTART.md](QUICKSTART.md) for the full decision
-path. For AD usernames on Windows, prefer UPN format such as
-`[email protected]`; avoid `LAB\alice` unless NTLM/MD4 support is known to work.
+- **The Problem Solved**: Replaces unvalidated, unreliable GitHub scripts with typed, reproducible, and auditable adversary modules.
+- **Key Capabilities**:
+ - **Comprehensive Vector Coverage**: 60+ modular techniques covering Active Directory (`ad.kerberoast`, `ad.adcs`, `ad.enum_users`), Windows (`windows.uac_bypass`), Linux, Cloud (AWS, Azure, GCP), and Network infrastructure.
+ - **Dynamic Typed Schemas**: UI forms are generated dynamically from Python Pydantic models with strict validation.
+ - **Dry-Run Safety Engine**: Validate target responsiveness, parameters, and expected outcome before transmitting offensive traffic.
+ - **Role-Gated Execution**: Operator and Team Lead permissions required for execution; sensitive high-noise modules require explicit confirmation.
---
-## Developer Setup
+### 5. 🕸️ Multi-Vector Attack Graph & Objective Replay
-Backend:
+*Interactive directed acyclic graph (DAG) solver visualizing enterprise attack paths and privilege escalation chains.*
-```bash
-python3.12 -m venv .venv
-source .venv/bin/activate
-python -m pip install -e ".[dev,pdf]"
-python -m pytest tests/unit -q
-```
+<div align="center">
-Windows PowerShell:
+![ARES Multi-Vector Attack Graph & Objective Replay](docs/assets/screenshots/dashboard-graph.png)
-```powershell
-py -3.12 -m venv .venv
-.\.venv\Scripts\python.exe -m pip install -e ".[dev,pdf]"
-.\.venv\Scripts\python.exe -m pytest tests/unit -q --tb=short --timeout=60 --timeout-method=thread
-```
+*Multi-Vector Attack Graph mapping enterprise entities, sessions, and deterministic paths to Domain Admin.*
-Frontend:
+</div>
-```bash
-cd frontend
-npm ci
-npm run build
-```
+- **The Problem Solved**: Translates raw vulnerability data into actionable, visual compromise paths that executives and engineers can understand immediately.
+- **Key Capabilities**:
+ - **Shortest Path Algorithms**: Deterministically calculates the fewest hops required to compromise Domain Controllers or cloud root credentials.
+ - **Native BloodHound / SharpHound Ingest**: Directly import BloodHound JSON archives into the ARES graph engine for unified analysis.
+ - **Interactive Entity Inspection**: Explore relationships between users, groups, computers, ACLs, and active Kerberos sessions with fluid navigation.
+ - **Objective Replay**: Re-simulate historical attack chains to verify defensive patch efficacy.
-Production build assets are served by FastAPI from `frontend/dist` at
-`/dashboard`.
+---
-Platform notes:
+### 6. 📑 Automated Report Engine & Evidence Library
-- Windows: use normal non-Administrator PowerShell and
- `.\.venv\Scripts\python.exe`. The Windows release path for the dashboard,
- PDF browser fallback, and Windows AD/Impacket lab modules is Python 3.12.x.
-- Linux, Kali, and macOS: use `source .venv/bin/activate`.
-- The package metadata allows Python 3.10-3.12, but the tested release path for
- the dashboard and Windows AD/Impacket lab modules is Python 3.12.x.
-- Keep one project virtual environment per OS instead of copying `.venv`
- directories between machines. Use Python 3.12.x for release validation.
-- Optional AD, cloud, container, Windows, and PDF dependencies are not required
- for the core dashboard to start.
+*Instant deliverable generation producing branded, audit-ready compliance reports across multiple standard formats.*
----
+<div align="center">
-## Module Ecosystem
+![ARES Automated Report Engine & Evidence Library](docs/assets/screenshots/dashboard-reports.png)
-ARES modules are grouped by operational purpose:
+*Report Engine and Artifact Library supporting multi-format exports with synchronized real-time lifecycle management.*
-| Category | Examples | Purpose |
-| --- | --- | --- |
-| Active Directory | `ad.enum_users`, `ad.kerberoast`, `ad.adcs` | Domain enumeration and authorized AD path validation. |
-| Credential | `credential.crack`, `credential.pass_spray` | Credential workflow and offline validation. |
-| Lateral | `lateral.winrm`, `lateral.wmiexec`, `lateral.psexec` | Approved lateral movement validation. |
-| Windows | `windows.registry_enum`, `windows.uac_bypass` | Windows endpoint posture review. |
-| Linux | `linux.kernel_suggester`, `linux.container` | Linux and container posture review. |
-| Cloud | `cloud.aws`, `cloud.azure`, `cloud.gcp` | Cloud identity and control-plane review. |
-| Network | `network.dns_enum`, `network.http_fingerprint` | Network and service discovery inside scope. |
-| EDR/OPSEC | `edr.bypass_adaptive`, `opsec.coverage_predictor` | Defensive visibility and OPSEC decision support. |
-| AI | `ai.autonomous_planner` | Goal-based planning from campaign context. |
+</div>
-High-noise modules require careful authorization and should be tested first in
-dry-run mode.
+- **The Problem Solved**: Eliminates the 40+ hours typically spent manually writing, formatting, and redacting pentest reports.
+- **Key Capabilities**:
+ - **Multi-Format Export**: One-click generation of **PDF**, **HTML**, **Markdown**, and **JSON** deliverables.
+ - **Automated Headless PDF Engine**: Integrated fallback using Microsoft Edge / Chromium headless mode for clean PDF export without complex GTK dependencies on Windows.
+ - **Automated Evidence Redaction**: Automatically redacts sensitive raw passwords and private keys in customer deliverables while retaining audit proofs.
+ - **Synchronized Report Library**: Authenticated artifact repository with instant downloads, per-report deletion, and real-time UI state synchronization.
---
-## ARES SDK Surface
+### 7. 🧠 Autonomous Strategy & AI Planner
-ARES exposes a public SDK import path for module authors and local
-integrations:
+*Goal-directed autonomous engine that plans, prioritizes, and executes complex attack chains while respecting OPSEC limits.*
-```python
-from ares.sdk import BaseModule, ExecutionContext, ModuleResult
-```
+<div align="center">
-Current SDK surface:
+![ARES Autonomous Strategy & AI Planner](docs/assets/screenshots/dashboard-strategy.png)
-- Module contracts: `BaseModule`, module metadata, generated parameter schemas,
- `ExecutionContext`, findings, validation results, dry-run behavior, OPSEC
- metadata, and report-ready outputs.
-- Frontend API client: typed dashboard calls under `frontend/src/api` for auth,
- campaigns, modules, reports, graph, security, EDR/OPSEC, and live workflows.
-- Documentation: [docs/module-development.md](docs/module-development.md) and
- [docs/module_sdk.md](docs/module_sdk.md) describe how to build and test ARES
- modules without bypassing scope validation, RBAC, or audit controls.
+*Autonomous Strategy Console for goal-based campaign planning and adaptive containment governance.*
-`ares.sdk` is the preferred import path for new code. The older
-`ares.modules.sdk` import path remains available so existing local modules keep
-working.
+</div>
+
+- **The Problem Solved**: Coordinates multi-module attack chains autonomously without requiring constant manual operator intervention.
+- **Key Capabilities**:
+ - **Goal-Directed Execution Engine**: Define high-level objectives (`domain_admin`, `full_compromise`, `cloud_audit`), and let the engine chain techniques.
+ - **Plug-and-Play AI Planners**: Integrate with Anthropic Claude, OpenAI, or local Ollama models to analyze engagement context and propose optimal next steps.
+ - **Adaptive Containment Governor**: Continuously evaluates defensive telemetry and noise thresholds, automatically slowing down or aborting aggressive actions when detection risk peaks.
---
-## Architecture
-
-```text
-Browser Dashboard
- |
- v
-FastAPI Server -> RBAC, auth, validation, rate limits
- |
- v
-ARES Engine -> module registry, execution context, OPSEC checks
- |
- v
-Modules -> AD, cloud, network, credential, EDR, reporting
- |
- v
-Database -> campaigns, findings, vault records, API keys, audit data
+## 🎛️ Control Surfaces Breakdown
+
+| Surface | Core Responsibility | Available Sub-Tabs | Primary Operators |
+| :--- | :--- | :--- | :--- |
+| **Overview** | Executive health, telemetry counters, finding severity metrics. | Single Pane | All Stakeholders |
+| **Campaigns** | Scope whitelisting, noise profiles, encrypted credential vault. | `List`, `Scope`, `Findings` | Team Lead, Operator |
+| **Modules** | 60+ module catalog, parameter input forms, execution console. | `Catalog`, `Run Panel`, `Results` | Operator |
+| **Reports** | Deliverable builder, evidence packages, Report Library lifecycle. | `Generate`, `Library` | Operator, Reporter |
+| **Graph** | DAG entity exploration, shortest attack paths, BloodHound ingest. | `Entities`, `Attack Paths`, `Ingest` | Operator, Recon |
+| **Templates** | Repeatable engagement playbooks and multi-stage workflow plans. | `Templates`, `Plan Builder` | Team Lead, Operator |
+| **Strategy** | Goal-directed autonomous engine, AI planner integration. | `Objective`, `Active`, `Result` | Team Lead, Operator |
+| **Security** | Operator credentials, API key lifecycle, dependency audit checks. | `Account`, `API Keys`, `Audit` | Team Lead |
+| **EDR/OPSEC** | Defensive telemetry, bypass tracking, detection evasion rules. | `Knowledge Base`, `Report Outcome` | Operator |
+| **Live** | Real-time WebSocket event streams and buffered telemetry logs. | `Stream`, `Buffer` | Operator |
+
+---
+
+## 🏗️ System Architecture & Data Pipeline
+
+ARES follows a strict defense-in-depth architecture separating presentation, execution orchestration, security governance, and persistent cryptographic storage:
+
+```mermaid
+flowchart TB
+ subgraph Client["Presentation Layer (Operator Enclave)"]
+ UI["React 19 Dashboard<br>(Vite + TypeScript)"]
+ Mesh["Dragon-Scale Hexagonal Mesh<br>(Canvas 2D Engine)"]
+ WSClient["WebSocket Client<br>(Real-Time Telemetry Stream)"]
+ end
+
+ subgraph Gateway["Zero-Trust Security Gateway"]
+ FastAPI["FastAPI Async Engine<br>(Uvicorn Backend)"]
+ AuthGuard["Auth & Session Guard<br>(Memory-Only JWT + HttpOnly Refresh)"]
+ CSRF["HMAC Double-Submit CSRF<br>(X-ARES-CSRF Validation)"]
+ RateLimit["Rate Limiting & Brute-Force Shield"]
+ end
+
+ subgraph Core["ARES Core Engine & Governance"]
+ ScopeFirewall["Scope Egress Firewall<br>(Strict CIDR & IP Whitelist)"]
+ Governor["OPSEC Noise Governor<br>(Adaptive Jitter & Throttling)"]
+ Orchestrator["Module Execution Orchestrator<br>(Worker Thread Pool)"]
+ AutoPlanner["Autonomous Strategy Engine<br>(DAG Heuristics / AI Planner)"]
+ end
+
+ subgraph Storage["Cryptographic Persistence Layer"]
+ DB[(SQLite / PostgreSQL<br>Alembic Versioned)]
+ Vault[(AES-256-GCM Vault<br>Encrypted Credentials & Hashes)]
+ GraphEngine["Attack Graph DAG Engine<br>(BloodHound Ingest & Shortest Path)"]
+ end
+
+ subgraph Deliverables["Reporting Pipeline"]
+ PDFGen["Headless Chromium / Edge Engine<br>(Automated PDF Generation)"]
+ Artifacts["Evidence Library<br>(HTML, Markdown, JSON)"]
+ end
+
+ UI -->|HTTPS / REST| AuthGuard
+ WSClient -->|WSS / Ticket Barrier| AuthGuard
+ AuthGuard --> CSRF --> RateLimit --> FastAPI
+ FastAPI --> ScopeFirewall
+ ScopeFirewall --> Orchestrator
+ Orchestrator --> Governor
+ Orchestrator --> AutoPlanner
+ Orchestrator --> Storage
+ Storage --> GraphEngine
+ FastAPI --> Deliverables
```
-Important design boundaries:
+---
-- The frontend improves UX but does not replace backend enforcement.
-- Module forms are generated from backend metadata.
-- Sensitive data stays behind authentication.
-- Reports require authenticated download through the dashboard or API.
-- Report Library delete actions are authenticated and update visible rows and
- artifact counts after success.
-- Local validation flows use localhost by default.
+## ⚔️ Adversary Techniques & MITRE ATT&CK Matrix
-See [docs/architecture.md](docs/architecture.md) and
-[docs/engine_design.md](docs/engine_design.md).
+ARES implements 60+ modular adversary techniques natively mapped to the MITRE ATT&CK Enterprise Framework:
----
+```
+┌──────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
+│ MITRE ATT&CK MATRIX COVERAGE │
+├─────────────────────┬─────────────────────┬─────────────────────┬─────────────────────┬──────────────────────────┤
+│ DISCOVERY │ CREDENTIAL ACCESS │ LATERAL MOVEMENT │ PRIVILEGE ESCALATION│ DEFENSE EVASION / CLOUD │
+├─────────────────────┼─────────────────────┼─────────────────────┼─────────────────────┼──────────────────────────┤
+│ • T1087 User Enum │ • T1558.003 Kerberoast│ • T1021.002 SMB/RPC │ • T1548.002 UAC Byps│ • T1070 Indicator Removal│
+│ • T1069 Group Enum │ • T1558.004 AS-REP │ • T1021.006 WinRM │ • T1068 Token Privs │ • T1562 Impair Defenses │
+│ • T1046 Port/Net │ • T1003 LSASS Dump │ • T1550 Use Ticket │ • T1053 Scheduled │ • T1078 Cloud IAM Enum │
+│ • T1018 Host Disc │ • T1649 ADCS ESC1-8 │ • T1071 App Layer │ • T1055 Injection │ • T1580 Cloud Discovery │
+│ • T1082 System Info │ • T1110 Pass Spray │ • T1021.001 RDP │ • T1134 Access Token│ • T1526 Cloud Hierarchy │
+└─────────────────────┴─────────────────────┴─────────────────────┴─────────────────────┴──────────────────────────┘
+```
-## Documentation
-
-| Document | Description |
-| --- | --- |
-| [docs/README.md](docs/README.md) | Central documentation portal and subsystem sitemap. |
-| [QUICKSTART.md](QUICKSTART.md) | First engagement walkthrough. |
-| [docs/dashboard-guide.md](docs/dashboard-guide.md) | Dashboard page-by-page guide. |
-| [docs/modules.md](docs/modules.md) | Module catalog and safe workflows. |
-| [docs/api-reference.md](docs/api-reference.md) | API endpoints and request/response examples. |
-| [docs/security-model.md](docs/security-model.md) | Security controls and threat model. |
-| [docs/validation-lab.md](docs/validation-lab.md) | Local validation harness. |
-| [docs/module-development.md](docs/module-development.md) | Build new modules. |
-| [docs/module_sdk.md](docs/module_sdk.md) | Module SDK reference. |
-| [docs/github-publish-guide.md](docs/github-publish-guide.md) | GitHub push and release checklist. |
-| [docs/community-posts.md](docs/community-posts.md) | Facebook, Discord, and release announcement drafts. |
+- **Active Directory Lab Suites**: Full SPN discovery, Kerberoasting (`ad.kerberoast`), AS-REP Roasting, ADCS Certificate Template abuse (ESC1 through ESC8), DCSync account replication, and BloodHound data generation.
+- **Endpoint Posture Checkers**: Windows UAC Bypass methods, registry key persistence inspection, Linux container breakouts, and Sudo privilege enumeration.
+- **Cloud Control Plane**: Multi-cloud identity auditing across AWS IAM, Azure Active Directory / Entra ID role assignments, and GCP IAM bindings.
---
-## Project Status
+## 🚀 Quickstart: Up and Running in 60 Seconds
-Current local verification:
+### Prerequisites
+- **Python**: 3.11 or 3.12 (Python 3.12 recommended for Windows).
+- **Node.js**: v18+ (tested on Node v20 LTS).
+- **OS**: Windows 11/10 (PowerShell), Linux (Ubuntu/Debian/Kali), or macOS.
-```text
-unit suite passed
-frontend build passed
-validation lab passed
-ares doctor dependency display and local-env isolation covered by tests
-PDF report visual QA passed through browser fallback and Poppler render checks
-```
+### Fast Path (PowerShell on Windows)
-Runtime features confirmed locally:
+```powershell
+# 1. Clone the repository
+git clone https://github.com/Mafifrizi/ARES.git
+Set-Location .\ARES
-- Production/static dashboard loads from FastAPI at `/dashboard` after frontend
- assets are built; local Vite dev mode uses `http://127.0.0.1:5173/dashboard/`.
-- Health endpoint returns connected DB.
-- Login, password change, API key lifecycle, and campaign cleanup work.
-- Report generation, authenticated download, and Report Library delete/Delete
- all cleanup work.
-- PDF report layout, footer branding, and evidence rendering work.
-- Overview telemetry records API-triggered module runs in the current process.
-- Campaign delete removes stored child data and updates the UI immediately.
+# 2. Setup isolated Python virtual environment
+py -3.12 -m venv .venv
+.\.venv\Scripts\python.exe -m pip install -U pip
+.\.venv\Scripts\python.exe -m pip install -e ".[dev,pdf]"
+
+# 3. Install frontend dependencies
+Set-Location frontend
+& "C:\Program Files\nodejs\npm.cmd" ci
+Set-Location ..
+
+# 4. Configure local Edge PDF rendering engine & verify doctor status
+$env:ARES_PDF_BROWSER = "C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"
+.\.venv\Scripts\ares.exe doctor --pdf-smoke
+
+# 5. Launch development server (Frontend + Backend proxy)
+.\.venv\Scripts\ares.exe dashboard dev --no-reload
+```
+
+Open your browser to **`http://127.0.0.1:5173/dashboard/`**.
+- **Initial Operator**: `admin`
+- **Initial Password**: Configured via `ARES_DEFAULT_ADMIN_PASSWORD` in `.env` (default: `Admin123456!`)
---
-## Responsible Use
+## 🔐 Enterprise Security Model & Compliance
-ARES is dual-use software. Use it only for:
+ARES was designed for environments with the most stringent compliance and confidentiality requirements:
-- Owned lab environments.
-- Internal security validation.
-- Authorized red-team engagements.
-- Training environments with permission.
+### Defense-in-Depth Authentication
+- **Memory-Only Access Tokens**: Short-lived JWTs (15-minute lifespan) exist purely within in-memory React state and are never written to `localStorage` or `sessionStorage`.
+- **Rotating Refresh Family**: Long-lived refresh credentials are bound to strict, host-only, HttpOnly cookies (`ares_refresh`) with one-time rotation and automatic reuse revocation.
+- **HMAC CSRF Barrier**: State-changing endpoints mandate valid `X-ARES-CSRF` headers matched against cryptographically secure cookie tokens.
-Do not use ARES for unauthorized access, persistence, data theft, or testing
-systems outside approved scope.
+### Role-Based Access Control (RBAC)
+ARES enforces strict RBAC permissions across all API endpoints and UI controls:
-If you discover a security issue in ARES, follow [SECURITY.md](SECURITY.md).
+| Role | Operational Scope | Administrative Authority |
+| :--- | :--- | :--- |
+| **`team_lead`** | Complete platform authority: campaign creation/deletion, user provisioning, security audits, high-noise module overrides. | Full |
+| **`operator`** | Day-to-day operations: execute authorized modules, review findings, explore attack graph, generate reports. | Standard |
+| **`recon`** | Read-heavy reconnaissance: execute safe discovery and network fingerprinting modules. Execution of disruptive modules is blocked. | Read-Heavy |
+| **`reporter`** | Stakeholder review: read-only access to campaign analytics, findings, attack graphs, and generated deliverables. | Read-Only |
---
-## Contributing
+## 🛠️ Extensible Developer SDK
-Contributions are welcome when they improve safety, clarity, module quality,
-operator experience, tests, documentation, or defensive validation workflows.
+Build custom adversary modules, integrate proprietary attack tools, or extend telemetry parsers using the clean `ares.sdk` interface:
-Start here:
+```python
+from ares.sdk import BaseModule, ExecutionContext, ModuleResult
+
+class CustomKerberoastModule(BaseModule):
+ id = "custom.ad.kerberoast"
+ name = "Custom SPN Extraction & Kerberoasting"
+ description = "Extracts SPNs from targeted Active Directory domain controllers."
+ category = "active_directory"
+ mitre_techniques = ["T1558.003"]
+ opsec_level = "medium"
+
+ def run(self, ctx: ExecutionContext) -> ModuleResult:
+ # Hard scope validation is enforced automatically by ctx
+ target_ip = ctx.params.get("target_ip")
+
+ if ctx.is_dry_run:
+ return ModuleResult.ok("Dry-run validated: target inside approved scope.")
+
+ # Execute check inside scope boundary
+ hashes = self._extract_spn_hashes(target_ip)
+
+ # Save captured hash to AES-256 encrypted campaign vault
+ ctx.vault.store_credential(
+ cred_type="kerberos_hash",
+ target=target_ip,
+ secret=hashes
+ )
+
+ return ModuleResult.ok(f"Extracted {len(hashes)} SPN hashes.", data={"count": len(hashes)})
+```
-- [CONTRIBUTING.md](CONTRIBUTING.md)
-- [docs/module-development.md](docs/module-development.md)
-- [docs/module_sdk.md](docs/module_sdk.md)
+See [docs/module-development.md](docs/module-development.md) for full developer documentation.
-Before opening a PR:
+---
-```bash
-pytest tests/unit -q
-cd frontend && npm run build
-```
+## 📚 Documentation Sitemap
-Do not commit `.env`, `.venv`, local databases, reports with real client data,
-API keys, tokens, screenshots that expose secrets, or database-adoption backups.
-Persistent databases are Alembic-managed. Existing
-unversioned generation-6/7 databases require the explicit verified adoption
-workflow; startup never stamps them automatically. See
-[`docs/database-migrations.md`](docs/database-migrations.md) before upgrading a
-deployment. Revision `0009` deliberately resets existing bearer sessions into
-revoked rollout families; plan an atomic backend/frontend maintenance window
-and require users to sign in again.
+Comprehensive documentation is available in the [`docs/`](docs/) directory:
+
+- [**Documentation Portal & Subsystem Index**](docs/README.md)
+- [**Quickstart Engagement Guide**](QUICKSTART.md)
+- [**Dashboard Surface-by-Surface Manual**](docs/dashboard-guide.md)
+- [**Adversary Module Catalog & Schemas**](docs/modules.md)
+- [**API Endpoint Reference & Payloads**](docs/api-reference.md)
+- [**Enterprise Security & Threat Model**](docs/security-model.md)
+- [**Validation Lab & Test Harness**](docs/validation-lab.md)
+- [**Module Authoring SDK Guide**](docs/module-development.md)
---
-## License
+## ⚖️ Responsible Use & Legal Disclaimer
+
+> [!IMPORTANT]
+> **ARES is a dual-use software framework designed exclusively for authorized cybersecurity research, internal enterprise resilience validation, and professional red-team engagements with explicit written permission.**
+
+- **Do NOT** execute ARES against any network, host, or cloud infrastructure without prior written authorization from the system owners.
+- Unauthorized system access or testing violates national and international cybercrime legislation (e.g. Computer Fraud and Abuse Act 18 U.S.C. § 1030).
+- The creators and maintainers of ARES assume no liability for misuse, damages, or regulatory violations caused by this software.
-ARES is released under the [MIT License](LICENSE).
+To report security vulnerabilities in ARES, please follow our [Security Policy](SECURITY.md).
---
+## 📄 License
+
+ARES is distributed under the open-source **[MIT License](LICENSE)**.
+
+<br>
+
<div align="center">
-**ARES - scoped, auditable, OPSEC-aware red-team engagement automation.**
+**ARES — Enterprise-Grade Autonomous Adversary Emulation.**
+*Continuous Security Validation. Zero Collateral Risk.*
</div>
diff --git a/docs/assets/screenshots/dashboard-campaigns.png b/docs/assets/screenshots/dashboard-campaigns.png
index 826fd2b..2b6447d 100644
Binary files a/docs/assets/screenshots/dashboard-campaigns.png and b/docs/assets/screenshots/dashboard-campaigns.png differ
diff --git a/docs/assets/screenshots/dashboard-graph.png b/docs/assets/screenshots/dashboard-graph.png
new file mode 100644
index 0000000..4b729dc
Binary files /dev/null and b/docs/assets/screenshots/dashboard-graph.png differ
diff --git a/docs/assets/screenshots/dashboard-modules-catalog.png b/docs/assets/screenshots/dashboard-modules-catalog.png
index 32bbef9..7f1db11 100644
Binary files a/docs/assets/screenshots/dashboard-modules-catalog.png and b/docs/assets/screenshots/dashboard-modules-catalog.png differ
diff --git a/docs/assets/screenshots/dashboard-overview.png b/docs/assets/screenshots/dashboard-overview.png
index e5d69e7..9f8452c 100644
Binary files a/docs/assets/screenshots/dashboard-overview.png and b/docs/assets/screenshots/dashboard-overview.png differ
diff --git a/docs/assets/screenshots/dashboard-reports.png b/docs/assets/screenshots/dashboard-reports.png
index 9401894..c61ce98 100644
Binary files a/docs/assets/screenshots/dashboard-reports.png and b/docs/assets/screenshots/dashboard-reports.png differ
diff --git a/docs/assets/screenshots/dashboard-strategy.png b/docs/assets/screenshots/dashboard-strategy.png
new file mode 100644
index 0000000..5711a09
Binary files /dev/null and b/docs/assets/screenshots/dashboard-strategy.png differ
diff --git a/docs/assets/screenshots/login-enclave.png b/docs/assets/screenshots/login-enclave.png
new file mode 100644
index 0000000..97fd62a
Binary files /dev/null and b/docs/assets/screenshots/login-enclave.png differ
diff --git a/frontend/src/features/auth/AuthProvider.tsx b/frontend/src/features/auth/AuthProvider.tsx
index 07273ee..edb16e8 100644
--- a/frontend/src/features/auth/AuthProvider.tsx
+++ b/frontend/src/features/auth/AuthProvider.tsx
@@ -117,7 +117,9 @@ export function AuthProvider({ children }: { children: ReactNode }) {
if (!ownsProviderLifecycle(loginLifecycle)) {
throw new Error("Session changed");
}
- resetLocalSession();
+ clearTokens();
+ queryClient.clear();
+ clearDashboardSession();
if (!ownsProviderLifecycle(loginLifecycle)) {
throw new Error("Session changed");
}
diff --git a/frontend/src/features/auth/LoginPage.tsx b/frontend/src/features/auth/LoginPage.tsx
index ed0575e..5464feb 100644
--- a/frontend/src/features/auth/LoginPage.tsx
+++ b/frontend/src/features/auth/LoginPage.tsx
@@ -1,13 +1,16 @@
-import { KeyRound } from "lucide-react";
+import { Activity, AlertCircle, Eye, EyeOff, GitGraph, Loader2, ShieldCheck } from "lucide-react";
import { FormEvent, useState } from "react";
import { Navigate, useNavigate } from "react-router-dom";
+import { SecurityMeshCanvas } from "./SecurityMeshCanvas";
import { useAuth } from "./authContext";
-const brandLogoPath = "/dashboard/brand/ares-logo.png";
+const brandMarkPath = "/dashboard/brand/ares-mark.png";
export function LoginPage() {
const [username, setUsername] = useState("");
const [password, setPassword] = useState("");
+ const [showPassword, setShowPassword] = useState(false);
+ const [isSubmitting, setIsSubmitting] = useState(false);
const [error, setError] = useState("");
const { login, user } = useAuth();
const navigate = useNavigate();
@@ -18,83 +21,229 @@ export function LoginPage() {
async function submit(event: FormEvent) {
event.preventDefault();
+ if (isSubmitting) return;
setError("");
+ setIsSubmitting(true);
try {
await login(username, password);
- navigate("/");
+ navigate("/", { replace: true });
} catch (exc) {
- setError(exc instanceof Error ? exc.message : "Login failed");
+ setError(exc instanceof Error ? exc.message : "Authentication failed");
+ setIsSubmitting(false);
}
}
return (
- <div className="min-h-screen flex flex-col items-center justify-center bg-zinc-950 px-4 text-zinc-100">
- <div className="w-full max-w-sm">
- {/* Brand Header */}
- <div className="mb-8 text-center">
+ <div className="min-h-[100dvh] w-full bg-[#09090b] text-[#f4f4f5] grid lg:grid-cols-12 selection:bg-red-700 selection:text-white">
+
+ {/* Left Column */}
+ <div className="hidden lg:flex lg:col-span-7 flex-col justify-between p-12 xl:p-16 border-r border-[#1a1a1f] bg-[#0b0b0e] relative overflow-hidden">
+ {/* The mesh IS the animation — purposeful: visualises the live attack graph */}
+ <SecurityMeshCanvas className="opacity-70" />
+
+ {/* Single ambient glow — draws eye toward centre of mesh */}
+ <div className="pointer-events-none absolute left-1/3 top-1/2 -translate-x-1/2 -translate-y-1/2 h-[32rem] w-[32rem] rounded-full bg-red-900/[0.06] blur-[80px] animate-ares-breathe" />
+
+ {/* Brand header */}
+ <div className="relative z-10 flex items-center justify-between animate-login-enter" style={{ animationDelay: "0ms" }}>
+ <div className="flex items-center gap-3">
+ <img
+ className="h-9 w-9 object-contain rounded-md border border-zinc-800 bg-zinc-900/60 p-1 shadow-inner"
+ src={brandMarkPath}
+ alt="ARES"
+ />
+ <div>
+ <div className="flex items-center gap-2">
+ <h1 className="text-base font-semibold text-white tracking-tight">ARES Dashboard</h1>
+ <span className="text-[10px] uppercase font-mono px-1.5 py-0.5 rounded border border-red-800/40 bg-red-950/40 text-red-400 font-medium">Enterprise</span>
+ </div>
+ <p className="text-[11px] text-zinc-400 font-mono">Autonomous Adversary Emulation Platform</p>
+ </div>
+ </div>
+ <div className="hidden xl:inline-flex items-center gap-2 px-2.5 py-1 rounded-full bg-zinc-900/80 border border-zinc-800 text-[11px] text-zinc-400 font-mono">
+ <span className="h-1.5 w-1.5 rounded-full bg-emerald-500 animate-pulse" />
+ <span>ENCLAVE v6.0</span>
+ </div>
+ </div>
+
+ {/* Value proposition */}
+ <div className="relative z-10 max-w-lg space-y-6 my-auto py-12">
+ <div className="animate-login-enter" style={{ animationDelay: "80ms" }}>
+ <div className="inline-flex items-center gap-1.5 px-2.5 py-0.5 rounded-full bg-red-950/40 border border-red-800/30 text-[11px] font-mono text-red-400 mb-3">
+ <span>Continuous Security Validation</span>
+ </div>
+ <h2 className="text-3xl font-semibold text-zinc-100 tracking-tight leading-tight">
+ Autonomous adversary emulation for modern enterprise security.
+ </h2>
+ <p className="text-sm text-zinc-400 leading-relaxed mt-3">
+ Coordinate multi-vector attack chains, stress-test defensive barriers across enterprise enclaves, and validate detection posture with complete audit fidelity.
+ </p>
+ </div>
+
+ <div className="pt-2 grid gap-3 text-xs">
+ {/* Pillar — hover translate communicates interactivity, red accent on hover ties to ARES brand */}
+ <div
+ className="flex items-start gap-3.5 p-3.5 rounded-lg border border-zinc-800/80 bg-zinc-900/30 backdrop-blur-sm hover:border-red-900/40 hover:bg-zinc-900/50 transition-all duration-200 group cursor-default hover:translate-x-1 animate-login-enter"
+ style={{ animationDelay: "180ms" }}
+ >
+ <div className="p-1.5 rounded-md bg-zinc-900 border border-zinc-800 text-zinc-400 group-hover:border-red-900/50 group-hover:text-red-500 transition-colors mt-0.5 shrink-0">
+ <GitGraph size={15} />
+ </div>
+ <div className="flex-1 min-w-0">
+ <strong className="text-zinc-200 block text-xs font-medium">Multi-Vector Attack Graph</strong>
+ <span className="text-zinc-400 text-[11px] leading-relaxed block mt-0.5">
+ Interactive DAG execution chains with deterministic objective replay and BloodHound ingest.
+ </span>
+ </div>
+ </div>
+
+ <div
+ className="flex items-start gap-3.5 p-3.5 rounded-lg border border-zinc-800/80 bg-zinc-900/30 backdrop-blur-sm hover:border-red-900/40 hover:bg-zinc-900/50 transition-all duration-200 group cursor-default hover:translate-x-1 animate-login-enter"
+ style={{ animationDelay: "260ms" }}
+ >
+ <div className="p-1.5 rounded-md bg-zinc-900 border border-zinc-800 text-zinc-400 group-hover:border-red-900/50 group-hover:text-red-500 transition-colors mt-0.5 shrink-0">
+ <Activity size={15} />
+ </div>
+ <div className="flex-1 min-w-0">
+ <strong className="text-zinc-200 block text-xs font-medium">Adaptive OPSEC Controls</strong>
+ <span className="text-zinc-400 text-[11px] leading-relaxed block mt-0.5">
+ Real-time telemetry, noise profiling, and automated containment governor.
+ </span>
+ </div>
+ </div>
+
+ <div
+ className="flex items-start gap-3.5 p-3.5 rounded-lg border border-zinc-800/80 bg-zinc-900/30 backdrop-blur-sm hover:border-red-900/40 hover:bg-zinc-900/50 transition-all duration-200 group cursor-default hover:translate-x-1 animate-login-enter"
+ style={{ animationDelay: "340ms" }}
+ >
+ <div className="p-1.5 rounded-md bg-zinc-900 border border-zinc-800 text-zinc-400 group-hover:border-red-900/50 group-hover:text-red-500 transition-colors mt-0.5 shrink-0">
+ <ShieldCheck size={15} />
+ </div>
+ <div className="flex-1 min-w-0">
+ <strong className="text-zinc-200 block text-xs font-medium">Zero-Trust Ticket Barrier</strong>
+ <span className="text-zinc-400 text-[11px] leading-relaxed block mt-0.5">
+ Cryptographically verified WebSocket sessions, memory-only JWT tokens, and immutable audit logs.
+ </span>
+ </div>
+ </div>
+ </div>
+ </div>
+
+ {/* Enterprise Enclave Status Footer */}
+ <div className="relative z-10 flex items-center justify-between text-[11px] text-zinc-500 font-mono border-t border-zinc-800/60 pt-4 mt-auto">
+ <div className="flex items-center gap-2">
+ <span className="h-2 w-2 rounded-full bg-emerald-500 animate-pulse"></span>
+ <span className="text-zinc-400">Zero-Trust Enclave Active</span>
+ </div>
+ <span className="text-zinc-500">v6.0.0-PROD</span>
+ </div>
+ </div>
+
+ {/* Right Column */}
+ <div className="col-span-12 lg:col-span-5 flex flex-col justify-center items-center p-6 sm:p-10 relative overflow-hidden">
+ {/* Background breathing glow — communicates the system is live, not dormant */}
+ <div className="pointer-events-none absolute inset-0 flex items-center justify-center overflow-hidden">
+ <div className="h-[28rem] w-[28rem] rounded-full bg-red-900/[0.04] blur-[90px] animate-ares-breathe" />
+ </div>
+
+ {/* Mobile brand */}
+ <div className="lg:hidden text-center mb-8 relative z-10 animate-login-enter">
<img
- className="mx-auto mb-4 h-12 w-auto object-contain"
- src={brandLogoPath}
+ className="h-10 w-10 object-contain rounded-md border border-zinc-800 bg-zinc-900/60 p-1 mx-auto mb-3"
+ src={brandMarkPath}
alt="ARES"
/>
- <h1 className="text-xl font-semibold tracking-tight text-zinc-100">ARES Dashboard</h1>
- <p className="mt-1.5 text-sm text-zinc-400">
- Sign in with your operator credentials
- </p>
+ <div className="text-xl font-semibold text-white tracking-tight">ARES Enclave</div>
+ <p className="text-xs text-zinc-400 mt-1">Autonomous Adversary Emulation</p>
</div>
- {/* Form Card */}
- <div className="rounded-xl border border-zinc-800 bg-zinc-900/50 p-6 shadow-sm">
+ {/* Auth card */}
+ <div
+ className="relative z-10 w-full max-w-sm rounded-xl border border-zinc-800/80 bg-[#111114]/95 backdrop-blur-md p-7 shadow-2xl animate-login-enter transition-all duration-200"
+ style={{ animationDelay: "140ms" }}
+ >
+ <div className="mb-6">
+ <div className="inline-flex items-center gap-1.5 px-2 py-0.5 rounded bg-zinc-900 border border-zinc-800 text-[10px] text-zinc-400 font-mono mb-3">
+ <span className="h-1.5 w-1.5 rounded-full bg-emerald-500 animate-pulse" />
+ <span>ZERO-TRUST GATEWAY</span>
+ </div>
+ <h2 className="text-lg font-semibold text-white tracking-tight">Operator Authentication</h2>
+ <p className="text-xs text-zinc-400 mt-1">Sign in with authorized enclave credentials</p>
+ </div>
+
<form onSubmit={(event) => void submit(event)} className="space-y-4">
<div>
- <label className="block text-xs font-medium text-zinc-300 mb-1.5">
- Username
- <input
- className="mt-1 block w-full rounded-md border border-zinc-800 bg-zinc-950 px-3 py-2 text-sm text-zinc-100 placeholder-zinc-500 transition-colors focus:border-zinc-500 focus:outline-none focus:ring-1 focus:ring-zinc-500"
- placeholder="operator"
- value={username}
- onChange={(e) => setUsername(e.target.value)}
- autoComplete="username"
- required
- />
+ <label className="block text-xs font-medium text-zinc-300 mb-1.5" htmlFor="operator-username">
+ Username / Operator ID
</label>
+ <input
+ id="operator-username"
+ className="block w-full rounded-md border border-zinc-800 bg-[#09090b] px-3 py-2 text-sm text-white placeholder-zinc-600 transition-all duration-150 focus:border-red-800/60 focus:outline-none focus:ring-1 focus:ring-red-800/40 disabled:opacity-50"
+ placeholder="operator"
+ value={username}
+ onChange={(e) => setUsername(e.target.value)}
+ autoComplete="username"
+ disabled={isSubmitting}
+ required
+ />
</div>
<div>
- <label className="block text-xs font-medium text-zinc-300 mb-1.5">
+ <label className="block text-xs font-medium text-zinc-300 mb-1.5" htmlFor="operator-password">
Password
+ </label>
+ <div className="relative">
<input
- className="mt-1 block w-full rounded-md border border-zinc-800 bg-zinc-950 px-3 py-2 text-sm text-zinc-100 placeholder-zinc-500 transition-colors focus:border-zinc-500 focus:outline-none focus:ring-1 focus:ring-zinc-500"
- type="password"
+ id="operator-password"
+ className="block w-full rounded-md border border-zinc-800 bg-[#09090b] pl-3 pr-10 py-2 text-sm text-white placeholder-zinc-600 transition-all duration-150 focus:border-red-800/60 focus:outline-none focus:ring-1 focus:ring-red-800/40 disabled:opacity-50"
+ type={showPassword ? "text" : "password"}
value={password}
onChange={(e) => setPassword(e.target.value)}
autoComplete="current-password"
+ placeholder="••••••••••••"
+ disabled={isSubmitting}
required
/>
- </label>
+ <button
+ type="button"
+ className="absolute inset-y-0 right-0 flex items-center pr-3 text-zinc-500 hover:text-zinc-200 transition-colors disabled:pointer-events-none"
+ onClick={() => setShowPassword((v) => !v)}
+ disabled={isSubmitting}
+ aria-label={showPassword ? "Hide password" : "Show password"}
+ >
+ {showPassword ? <EyeOff size={15} /> : <Eye size={15} />}
+ </button>
+ </div>
</div>
{error && (
- <div className="rounded-md border border-red-900/50 bg-red-950/30 px-3 py-2 text-xs text-red-400">
- {error}
+ <div className="rounded-md border border-red-700/30 bg-red-700/10 px-3 py-2 text-xs text-red-400 flex items-start gap-2 animate-login-enter">
+ <AlertCircle size={14} className="mt-0.5 shrink-0" />
+ <span>{error}</span>
</div>
)}
<button
- className="w-full mt-2 flex items-center justify-center gap-2 rounded-md bg-zinc-100 px-4 py-2 text-sm font-medium text-zinc-900 transition-colors hover:bg-white active:bg-zinc-200 focus:outline-none focus:ring-2 focus:ring-zinc-400 focus:ring-offset-2 focus:ring-offset-zinc-900"
+ className="w-full mt-2 flex items-center justify-center gap-2 rounded-md bg-zinc-100 hover:bg-white active:scale-[0.98] px-4 py-2.5 text-sm font-semibold text-zinc-950 transition-all duration-150 shadow-sm hover:shadow-[0_0_20px_rgba(255,255,255,0.10)] focus:outline-none focus:ring-2 focus:ring-zinc-400 focus:ring-offset-2 focus:ring-offset-[#111114] disabled:opacity-50 disabled:cursor-not-allowed"
type="submit"
+ disabled={isSubmitting}
>
- <KeyRound size={15} className="text-zinc-700" />
- Login
+ {isSubmitting ? (
+ <>
+ <Loader2 size={15} className="animate-spin text-zinc-900" />
+ <span>Signing in...</span>
+ </>
+ ) : (
+ <span>Sign in</span>
+ )}
</button>
</form>
- </div>
- {/* Subtle Footer */}
- <div className="mt-6 text-center">
- <p className="text-xs text-zinc-500">
- ARES Automated Red Team Engagement System
- </p>
+ <div className="mt-6 border-t border-zinc-800/60 pt-4 text-center">
+ <p className="text-[11px] text-zinc-500 leading-relaxed">
+ Restricted security gateway. All access attempts are cryptographically verified and audited.
+ </p>
+ </div>
</div>
</div>
</div>
diff --git a/frontend/src/features/auth/SecurityMeshCanvas.tsx b/frontend/src/features/auth/SecurityMeshCanvas.tsx
new file mode 100644
index 0000000..90377f9
--- /dev/null
+++ b/frontend/src/features/auth/SecurityMeshCanvas.tsx
@@ -0,0 +1,168 @@
+import { useEffect, useRef } from "react";
+
+interface SecurityMeshCanvasProps {
+ className?: string;
+}
+
+/**
+ * SecurityMeshCanvas — ARES Dragon Scale Grid
+ *
+ * Renders a tiled hexagonal grid (dragon scales). At rest the scales are barely
+ * visible — a ghostly crimson lattice. A slow diagonal breathing wave drifts
+ * across the grid, keeping it alive. When the operator moves the cursor over
+ * the panel the scales beneath react, glowing bright crimson, as if the dragon
+ * is aware of the operator's presence.
+ *
+ * Motivation for every animation:
+ * • Hex grid — dragon scales, the ARES identity made literal
+ * • Breathing wave — the system is live, not dormant
+ * • Mouse proximity — the dragon reacts to the operator approaching
+ */
+export function SecurityMeshCanvas({ className = "" }: SecurityMeshCanvasProps) {
+ const canvasRef = useRef<HTMLCanvasElement>(null);
+
+ useEffect(() => {
+ const canvas = canvasRef.current;
+ if (!canvas) return;
+
+ if (typeof navigator !== "undefined" && navigator.userAgent.includes("jsdom")) return;
+
+ let ctx: CanvasRenderingContext2D | null = null;
+ try { ctx = canvas.getContext("2d"); } catch { return; }
+ if (!ctx) return;
+
+ let animId: number;
+ let W = 0;
+ let H = 0;
+ const dpr = window.devicePixelRatio || 1;
+ const mouse = { x: -9999, y: -9999 };
+
+ // ── Hex geometry (flat-top orientation) ──────────────────────────────────
+ // R = circumradius (center → corner)
+ // HH = hex height flat-to-flat = √3 × R
+ // COL = horizontal distance between centers = R × 1.5 (columns overlap by R/2)
+ // ROW = vertical distance between centers in same column = HH
+ // Odd columns are offset down by HH/2
+ const R = 24;
+ const HH = Math.sqrt(3) * R;
+ const COL = R * 1.5;
+ const ROW = HH;
+
+ // Six corner offsets for a flat-top hex (angles 0°, 60°, …, 300°)
+ const OFFSETS = Array.from({ length: 6 }, (_, i) => {
+ const a = (Math.PI / 3) * i;
+ return [Math.cos(a), Math.sin(a)] as [number, number];
+ });
+
+ interface Hex { cx: number; cy: number }
+ let hexes: Hex[] = [];
+
+ const buildHexes = () => {
+ hexes = [];
+ const cols = Math.ceil(W / COL) + 3;
+ const rows = Math.ceil(H / ROW) + 3;
+ for (let c = -1; c < cols; c++) {
+ const cx = c * COL;
+ const yOff = c % 2 === 0 ? 0 : HH / 2;
+ for (let r = -1; r < rows; r++) {
+ hexes.push({ cx, cy: r * ROW + yOff });
+ }
+ }
+ };
+
+ const updateSize = () => {
+ const rect = canvas.getBoundingClientRect();
+ W = rect.width;
+ H = rect.height;
+ canvas.width = Math.max(1, Math.floor(W * dpr));
+ canvas.height = Math.max(1, Math.floor(H * dpr));
+ ctx!.setTransform(1, 0, 0, 1, 0, 0);
+ ctx!.scale(dpr, dpr);
+ buildHexes();
+ };
+
+ updateSize();
+
+ // ── Interaction handlers ──────────────────────────────────────────────────
+ const onMouseMove = (e: MouseEvent) => {
+ const rect = canvas.getBoundingClientRect();
+ mouse.x = e.clientX - rect.left;
+ mouse.y = e.clientY - rect.top;
+ };
+ const onMouseLeave = () => { mouse.x = -9999; mouse.y = -9999; };
+
+ window.addEventListener("resize", updateSize);
+ const parent = canvas.parentElement;
+ parent?.addEventListener("mousemove", onMouseMove);
+ parent?.addEventListener("mouseleave", onMouseLeave);
+
+ // ── Render constants ──────────────────────────────────────────────────────
+ const MOUSE_R = 140; // radius of mouse-proximity glow
+ const DRAW_R = R - 1; // slightly smaller so gaps show between scales
+
+ let t = 0;
+
+ const render = () => {
+ if (document.hidden) { animId = requestAnimationFrame(render); return; }
+ t += 0.006; // breathing speed — slow, subliminal
+
+ ctx!.clearRect(0, 0, W, H);
+
+ for (const { cx, cy } of hexes) {
+ // Skip hexes well outside the canvas
+ if (cx < -R * 2 || cx > W + R * 2 || cy < -R * 2 || cy > H + R * 2) continue;
+
+ // ── Mouse proximity glow (dragon reacts to operator) ──────────────
+ const dx = cx - mouse.x;
+ const dy = cy - mouse.y;
+ const distM = Math.hypot(dx, dy);
+ const mouse_t = distM < MOUSE_R ? 1 - distM / MOUSE_R : 0;
+
+ // ── Breathing wave (diagonal drift = direction of dragon's attention) ─
+ // Wave travels diagonally top-left → bottom-right
+ const wave_t = Math.sin(t + cx * 0.012 + cy * 0.009) * 0.5 + 0.5;
+
+ // Combined intensity
+ const glow = Math.max(mouse_t * 0.9, wave_t * 0.13);
+
+ // ── Draw hex path ─────────────────────────────────────────────────
+ ctx!.beginPath();
+ for (let i = 0; i < 6; i++) {
+ const px = cx + DRAW_R * OFFSETS[i][0];
+ const py = cy + DRAW_R * OFFSETS[i][1];
+ i === 0 ? ctx!.moveTo(px, py) : ctx!.lineTo(px, py);
+ }
+ ctx!.closePath();
+
+ // Fill — barely there at rest, deep crimson near cursor
+ ctx!.fillStyle = `rgba(180, 15, 15, ${glow * 0.11})`;
+ ctx!.fill();
+
+ // Border — the scale edge, always visible but dim at rest
+ const border = 0.14 + glow * 0.5;
+ ctx!.strokeStyle = `rgba(220, 38, 38, ${border})`;
+ ctx!.lineWidth = 0.75;
+ ctx!.stroke();
+ }
+
+ animId = requestAnimationFrame(render);
+ };
+
+ animId = requestAnimationFrame(render);
+
+ return () => {
+ cancelAnimationFrame(animId);
+ window.removeEventListener("resize", updateSize);
+ parent?.removeEventListener("mousemove", onMouseMove);
+ parent?.removeEventListener("mouseleave", onMouseLeave);
+ };
+ }, []);
+
+ return (
+ <canvas
+ ref={canvasRef}
+ className={`pointer-events-none absolute inset-0 h-full w-full ${className}`}
+ aria-hidden="true"
+ />
+ );
+}
diff --git a/frontend/src/features/dashboard/DashboardPages.tsx b/frontend/src/features/dashboard/DashboardPages.tsx
index e6504e4..4a5419a 100644
--- a/frontend/src/features/dashboard/DashboardPages.tsx
+++ b/frontend/src/features/dashboard/DashboardPages.tsx
@@ -1,8 +1,10 @@
import {
+ Activity,
AlertTriangle,
Bell,
Boxes,
CheckCircle2,
+ ChevronDown,
Copy,
Database,
Download,
@@ -26,7 +28,8 @@ import {
TrendingUp,
UserCog,
type LucideIcon,
- Workflow
+ Workflow,
+ X
} from "lucide-react";
import {
ChangeEvent,
@@ -341,6 +344,8 @@ export function DashboardShell({ children }: { children: ReactNode }) {
const [searchTerm, setSearchTerm] = useState("");
const [searchOpen, setSearchOpen] = useState(false);
const [notificationsOpen, setNotificationsOpen] = useState(false);
+ const [operatorMenuOpen, setOperatorMenuOpen] = useState(false);
+ const [telemetryOpen, setTelemetryOpen] = useState(false);
const [readNotificationIds, setReadNotificationIds] = useState<string[]>([]);
const [deletedNotificationIds, setDeletedNotificationIds] = useState<string[]>([]);
const health = useQuery({ queryKey: ["health"], queryFn: api.health });
@@ -353,6 +358,7 @@ export function DashboardShell({ children }: { children: ReactNode }) {
queryFn: () => api.reports(selectedCampaignId),
enabled: Boolean(selectedCampaignId)
});
+ const telemetrySnapshot = telemetry.data as TelemetrySnapshot | undefined;
useCampaignEventSocket({
campaignId: liveCampaignId,
@@ -583,8 +589,11 @@ export function DashboardShell({ children }: { children: ReactNode }) {
<div className="sidebar-brand">
<img className="sidebar-mark" src={brandMarkPath} alt="" aria-hidden="true" />
<div className="min-w-0">
- <div className="sidebar-title">ARES</div>
- <div className="sidebar-subtitle">Security dashboard</div>
+ <div className="sidebar-title flex items-center gap-1.5">
+ <span>ARES</span>
+ <span className="text-[9px] uppercase font-mono px-1 py-0.5 rounded border border-red-800/40 bg-red-950/40 text-red-400 font-semibold tracking-wider">v6.0</span>
+ </div>
+ <div className="sidebar-subtitle">Adversary Emulation Suite</div>
</div>
</div>
<nav className="sidebar-nav" aria-label="Dashboard navigation">
@@ -594,10 +603,14 @@ export function DashboardShell({ children }: { children: ReactNode }) {
<div className="grid gap-1">
{group.items.map((item) => {
const Icon = item.icon;
+ const count = item.to === "/campaigns" ? (campaigns.data ?? []).length : item.to === "/modules" ? (modules.data ?? []).length : null;
return (
<NavLink key={item.to} to={item.to} end={item.to === "/"} className="nav-link" title={sidebarCollapsed ? item.label : undefined}>
<Icon size={16} />
<span>{item.label}</span>
+ {count !== null && count > 0 && !sidebarCollapsed ? (
+ <span className="nav-count-badge font-mono">{count}</span>
+ ) : null}
</NavLink>
);
})}
@@ -616,14 +629,36 @@ export function DashboardShell({ children }: { children: ReactNode }) {
onClick={() => setSidebarCollapsed((value) => !value)}
type="button"
>
- <Menu size={17} />
+ <Menu size={16} />
</button>
+
+ <div className="topbar-scope-wrap" title="Active campaign engagement scope">
+ <select
+ className="topbar-scope-select"
+ aria-label="Active campaign scope"
+ value={selectedCampaignId}
+ onChange={(e) => {
+ setSelectedCampaignId(e.target.value);
+ if (e.target.value) {
+ writeDashboardSession("ares.dashboard.campaigns.tab", "Scope");
+ }
+ }}
+ >
+ <option value="">Scope: Global / All</option>
+ {(campaigns.data ?? []).map((c) => (
+ <option key={c.id} value={c.id}>
+ {c.name || c.id.slice(0, 12)}
+ </option>
+ ))}
+ </select>
+ </div>
+
<div className="topbar-search-wrap">
<label className="topbar-search" aria-label="Dashboard search">
- <Search size={16} />
+ <Search size={15} />
<input
aria-label="Search dashboard"
- onBlur={() => window.setTimeout(() => setSearchOpen(false), 120)}
+ onBlur={() => window.setTimeout(() => setSearchOpen(false), 140)}
onChange={(event) => {
setSearchTerm(event.target.value);
setSearchOpen(true);
@@ -641,6 +676,7 @@ export function DashboardShell({ children }: { children: ReactNode }) {
placeholder="Search campaigns, modules, reports"
value={searchTerm}
/>
+ <span className="search-kbd-badge">/</span>
</label>
{searchOpen && (
<div className="search-results" role="listbox">
@@ -653,7 +689,7 @@ export function DashboardShell({ children }: { children: ReactNode }) {
</button>
))
) : (
- <div className="search-empty">No matches</div>
+ <div className="search-empty">No matches found</div>
)
) : (
<div className="search-empty">Type to search dashboard</div>
@@ -663,6 +699,60 @@ export function DashboardShell({ children }: { children: ReactNode }) {
</div>
</div>
<div className="topbar-right">
+ {/* Telemetry Operational Status */}
+ <div className="relative">
+ <button
+ className="topbar-status-btn"
+ type="button"
+ aria-label="System operational status"
+ aria-expanded={telemetryOpen}
+ onClick={() => setTelemetryOpen((v) => !v)}
+ title="System operational health and telemetry status"
+ >
+ <span className={`status-dot ${health.isSuccess && !telemetry.isError ? "online" : "warning"}`} />
+ <span className="status-title">{health.isSuccess ? "Operational" : "Connecting"}</span>
+ <span className="status-pill-count font-mono">
+ {telemetrySnapshot ? `${metricNumber(telemetrySnapshot.modules, "total")} runs` : "v6.0"}
+ </span>
+ </button>
+
+ {telemetryOpen && (
+ <aside className="telemetry-popover" aria-label="Enclave telemetry quick view">
+ <div className="telemetry-popover-header">
+ <div className="flex items-center gap-2">
+ <Activity size={15} className="text-emerald-400" />
+ <strong>Enclave Subsystem Health</strong>
+ </div>
+ <button className="icon-button icon-button-small" onClick={() => setTelemetryOpen(false)} aria-label="Close telemetry view" type="button">
+ <X size={13} />
+ </button>
+ </div>
+ <div className="telemetry-popover-grid">
+ <div className="popover-stat">
+ <span>Worker Pool</span>
+ <strong>{metricNumber(telemetrySnapshot?.workers, "active")} active</strong>
+ </div>
+ <div className="popover-stat">
+ <span>Task Queue</span>
+ <strong>{metricNumber(telemetrySnapshot?.queue, "depth")} queued</strong>
+ </div>
+ <div className="popover-stat">
+ <span>Module Error Rate</span>
+ <strong>{telemetrySnapshot ? `${formatRate(metricNumber(telemetrySnapshot.modules, "error_rate"))}` : "0%"}</strong>
+ </div>
+ <div className="popover-stat">
+ <span>Live Ingest</span>
+ <div className="mt-0.5 flex items-center gap-1.5">
+ <span className={`h-1.5 w-1.5 rounded-full ${liveConnected ? "bg-emerald-400" : "bg-zinc-500"}`} />
+ <strong className="!mt-0 text-zinc-100">{liveConnected ? "Connected" : "Standby"}</strong>
+ </div>
+ </div>
+ </div>
+ </aside>
+ )}
+ </div>
+
+ {/* Notifications */}
<button
className="icon-button has-badge"
aria-expanded={notificationsOpen}
@@ -670,7 +760,7 @@ export function DashboardShell({ children }: { children: ReactNode }) {
onClick={toggleNotifications}
type="button"
>
- <Bell size={16} />
+ <Bell size={15} />
{unreadNotificationCount > 0 ? <span>{unreadNotificationCount}</span> : null}
</button>
{notificationsOpen && (
@@ -690,7 +780,7 @@ export function DashboardShell({ children }: { children: ReactNode }) {
<div className="notification-item-header">
<strong>{item.title}</strong>
<button className="icon-button icon-button-small" aria-label={`Dismiss ${item.title}`} onClick={() => deleteNotification(item.id)} type="button">
- <Trash2 size={14} />
+ <Trash2 size={13} />
</button>
</div>
<p>{item.detail}</p>
@@ -702,19 +792,60 @@ export function DashboardShell({ children }: { children: ReactNode }) {
)}
</aside>
)}
- <span className="user-chip">
- <span className="user-chip-avatar">{user.username.slice(0, 1).toUpperCase()}</span>
- <span className="user-chip-copy">
- <strong>{user.username}</strong>
- <small>{formatRole(user.role)}</small>
- </span>
- </span>
- <button className="btn btn-topbar" onClick={() => void logout()}>
- <LogOut size={16} /> Logout
- </button>
- <button className="btn btn-topbar" onClick={() => void logoutAll()}>
- <LogOut size={16} /> Logout all devices
- </button>
+
+ {/* Consolidated Operator Menu */}
+ <div className="operator-menu-wrap">
+ <button
+ className="operator-trigger"
+ type="button"
+ aria-expanded={operatorMenuOpen}
+ onClick={() => setOperatorMenuOpen((v) => !v)}
+ aria-label="Operator clearance menu"
+ >
+ <span className="operator-avatar">{user.username.slice(0, 1).toUpperCase()}</span>
+ <div className="operator-info">
+ <strong>{user.username}</strong>
+ <small>{formatRole(user.role)}</small>
+ </div>
+ <ChevronDown size={13} className={`chevron-indicator ${operatorMenuOpen ? "open" : ""}`} />
+ </button>
+
+ {operatorMenuOpen && (
+ <div className="operator-dropdown" role="menu">
+ <div className="operator-dropdown-header">
+ <div className="operator-dropdown-title">Operator Clearance</div>
+ <div className="operator-dropdown-badge">{formatRole(user.role)}</div>
+ <div className="operator-dropdown-sub">Signed in as {user.username}</div>
+ </div>
+ <div className="operator-dropdown-actions">
+ <button
+ className="operator-action-item"
+ role="menuitem"
+ onClick={() => {
+ setOperatorMenuOpen(false);
+ void logout();
+ }}
+ type="button"
+ >
+ <LogOut size={14} />
+ <span>Logout</span>
+ </button>
+ <button
+ className="operator-action-item danger"
+ role="menuitem"
+ onClick={() => {
+ setOperatorMenuOpen(false);
+ void logoutAll();
+ }}
+ type="button"
+ >
+ <ShieldAlert size={14} />
+ <span>Logout all devices</span>
+ </button>
+ </div>
+ </div>
+ )}
+ </div>
</div>
</header>
<div className="content-shell">{children}</div>
@@ -747,7 +878,7 @@ export function OverviewPage() {
<div className="highlight-list">
<HighlightRow label="Active campaigns" value={String(activeCampaigns)} tone="low" detail="available engagements" />
<HighlightRow label="Findings" value={String(findings)} tone={findings > 0 ? "medium" : "low"} detail="confirmed observations" />
- <HighlightRow label="Runtime" value={telemetry.isSuccess ? "Online" : "Pending"} tone={telemetry.isSuccess ? "low" : "medium"} detail="telemetry feed" />
+ <HighlightRow label="Runtime" value={telemetry.isSuccess ? "Operational" : "Pending"} tone={telemetry.isSuccess ? "low" : "medium"} detail="telemetry stream" />
</div>
</section>
<section className="panel p-4">
@@ -756,10 +887,10 @@ export function OverviewPage() {
<span>{formatMetric(monthlyTotal)}</span>
<small>{monthlyData?.label ?? "Security signals this cycle"}</small>
</div>
- {monthlyStats.isPending ? <p className="text-sm text-slate-500">Loading monthly activity...</p> : null}
- {monthlyStats.isError ? <p className="text-sm text-slate-500">Monthly activity unavailable.</p> : null}
+ {monthlyStats.isPending ? <p className="text-sm text-zinc-400">Loading monthly activity...</p> : null}
+ {monthlyStats.isError ? <p className="text-sm text-zinc-400">Monthly activity unavailable.</p> : null}
{!monthlyStats.isPending && !monthlyStats.isError && monthlyTotal === 0 ? (
- <p className="text-sm text-slate-500">No monthly activity yet</p>
+ <p className="text-sm text-zinc-400">No monthly activity yet</p>
) : null}
{!monthlyStats.isPending && !monthlyStats.isError && monthlyTotal > 0 && monthlySeries.some((value) => value.count > 0) ? (
<SparklineBars values={monthlySeries} />
@@ -903,7 +1034,7 @@ export function CampaignsPage() {
<textarea className="field min-h-20" required placeholder="Scope CIDRs" value={scope} onInvalid={setRequiredMessage} onChange={(e) => { clearValidationMessage(e); setCreateWarning(""); setScope(e.target.value); }} />
{createWarning && <p className="notice notice-danger">{createWarning}</p>}
<button className="btn btn-primary" disabled={create.isPending} type="submit">
- <ListChecks size={16} /> Create
+ Create Campaign
</button>
</form>
<DataPanel title="Create Error" data={create.error} />
@@ -920,10 +1051,10 @@ export function CampaignsPage() {
<CampaignScopeSummary campaign={detail.data ?? campaigns.data?.find((item) => item.id === selected)} loading={detail.isFetching} />
<div className="mt-3 flex flex-wrap gap-2">
<button className="btn" disabled={!selected} onClick={() => restore.mutate()}>
- <ShieldCheck size={16} /> Restore Vault
+ Restore Vault
</button>
<button className="btn" disabled={!selected} onClick={() => run.mutate()}>
- <Play size={16} /> Dry Run Plan
+ Dry Run Plan
</button>
<button
className="btn btn-danger"
@@ -934,7 +1065,7 @@ export function CampaignsPage() {
}
}}
>
- <Trash2 size={16} /> Delete
+ Delete
</button>
<input className="field max-w-xs" placeholder="Compare campaign ID" value={otherId} onChange={(e) => setOtherId(e.target.value)} />
</div>
@@ -943,9 +1074,8 @@ export function CampaignsPage() {
<DataPanel title="Campaign Detail Error" data={detail.error} />
<DataPanel title="CVSS Error" data={cvss.error} />
<DataPanel title="Campaign Diff Error" data={diff.error} />
- <DataPanel title="Campaign Detail" data={detail.data} />
- <DataPanel title="CVSS Summary" data={cvss.data} />
- <DataPanel title="Diff" data={diff.data} />
+ {cvss.data && <CvssScoreCard data={cvss.data} />}
+ {diff.data && <CampaignDiffCard data={diff.data} />}
</>
)}
{activeTab === "Findings" && (
@@ -994,11 +1124,11 @@ function ExecutionChainsPanel({
<strong>{stage.title}</strong>
{stage.final_goal && <span className="badge badge-low">Final goal</span>}
</div>
- <span className="text-xs font-medium text-slate-500">
+ <span className="text-xs font-medium text-zinc-400">
{stage.uses_previous_output ? "Uses prior output" : "Starts from campaign inputs"}
</span>
</div>
- <p className="mt-2 text-sm text-slate-600">{stage.purpose}</p>
+ <p className="mt-2 text-sm text-zinc-300">{stage.purpose}</p>
{stage.module_ids.length > 0 && (
<div className="mt-3 flex flex-wrap items-center gap-2">
<strong className="text-sm">Run</strong>
@@ -1016,7 +1146,7 @@ function ExecutionChainsPanel({
))}
</div>
)}
- <div className="mt-3 grid gap-1 text-xs text-slate-500">
+ <div className="mt-3 grid gap-1 text-xs text-zinc-400">
<span><strong>Inputs:</strong> {stage.required_inputs.join(", ") || "none"}</span>
<span><strong>Produces:</strong> {stage.produces.join("; ") || "none"}</span>
<span><strong>Next:</strong> {stage.next_action}</span>
@@ -1157,7 +1287,7 @@ export function ModulesPage() {
<div className="flex items-start justify-between gap-3">
<div>
<div className="font-bold">{item.id}</div>
- <div className="text-sm text-slate-600">{item.description}</div>
+ <div className="text-sm text-zinc-400">{item.description}</div>
</div>
<span className={opsecBadge(item.opsec_level)}>{item.opsec_level || "n/a"}</span>
</div>
@@ -1199,7 +1329,7 @@ export function ModulesPage() {
eyebrow={selected ? selected.id : "Select module"}
action={selected ? <span className={opsecBadge(selected.opsec_level)}>{selected.opsec_level || "n/a"}</span> : null}
/>
- {selected?.description && <p className="text-sm text-slate-600">{selected.description}</p>}
+ {selected?.description && <p className="text-sm text-zinc-300">{selected.description}</p>}
{selected && (selected.capability_flags?.length || selected.supported_modes?.length) ? (
<div className="mt-2 flex flex-wrap gap-1">
{(selected.capability_flags ?? []).map((flag) => <span className="badge" key={flag}>{flag}</span>)}
@@ -1358,6 +1488,11 @@ export function ReportsPage() {
: current
);
setLibraryError("");
+ const activePayload = (generate.data ?? lastGenerateResult?.payload) as { filename?: string } | undefined;
+ if (activePayload?.filename === item.filename) {
+ generate.reset();
+ setLastGenerateResult(null);
+ }
},
onError: (error) => {
setLibraryError(readableError(error, "Report could not be deleted."));
@@ -1371,11 +1506,26 @@ export function ReportsPage() {
(current) => current ? { ...current, reports: [] } : current
);
setLibraryError("");
+ generate.reset();
+ setLastGenerateResult(null);
},
onError: (error) => {
setLibraryError(readableError(error, "Report library could not be cleared."));
}
});
+
+ // Auto-clear stale generate result if the report file was deleted from library
+ useEffect(() => {
+ if (reports.isSuccess && (generate.data || lastGenerateResult?.payload)) {
+ const activePayload = (generate.data ?? lastGenerateResult?.payload) as { filename?: string } | undefined;
+ const activeFilename = activePayload?.filename;
+ if (activeFilename && !reportItems.some((r) => r.filename === activeFilename)) {
+ generate.reset();
+ setLastGenerateResult(null);
+ }
+ }
+ }, [reports.isSuccess, reportItems, generate.data, lastGenerateResult]);
+
const deleteDisabled = deleteReport.isPending || clearReports.isPending;
return (
<Page
@@ -1429,6 +1579,10 @@ export function ReportsPage() {
<DataPanel
title={generateIssue ? "Generate Error" : "Generate Result"}
data={generate.error ?? generate.data ?? persistedGenerateResult?.payload}
+ onClear={() => {
+ generate.reset();
+ setLastGenerateResult(null);
+ }}
/>
</section>
)}
@@ -1463,7 +1617,7 @@ export function ReportsPage() {
<tbody>
{reportItems.map((item) => (
<tr key={item.filename}>
- <td className="font-medium text-slate-900">{item.filename}</td>
+ <td className="font-medium text-zinc-100 font-mono text-sm">{item.filename}</td>
<td><span className="badge">{item.format}</span></td>
<td>{formatBytes(item.size_bytes)}</td>
<td>{formatReportDate(item.modified_at)}</td>
@@ -1578,7 +1732,7 @@ export function TemplatesPage() {
{selected ? (
<div className="preview-card mt-3">
<div className="font-bold">{selected.name}</div>
- <p className="mt-1 text-sm text-slate-600">{selected.description}</p>
+ <p className="mt-1 text-sm text-zinc-300">{selected.description}</p>
<div className="mt-2 flex flex-wrap gap-2">
<span className="badge">{selected.stages ?? 0} stages</span>
<span className="badge">{selected.modules ?? 0} modules</span>
@@ -1599,7 +1753,7 @@ export function TemplatesPage() {
}}
/>
</label>
- <p className="mt-1 text-xs text-slate-500">JSON object. Leave {"{}"} for defaults.</p>
+ <p className="mt-1 text-xs text-zinc-400">JSON object. Leave {"{}"} for defaults.</p>
{(warning || !paramsValid) && (
<p className="notice notice-danger mt-2">
{warning || "Global parameters must be a valid JSON object."}
@@ -1882,8 +2036,8 @@ export function SecurityPage() {
<div className="profile-row mb-3">
<span className="profile-avatar-light">{user?.username?.slice(0, 1).toUpperCase() ?? "A"}</span>
<div>
- <div className="font-semibold text-slate-950">{user?.username}</div>
- <div className="text-xs text-slate-500">{formatRole(user?.role)}</div>
+ <div className="font-semibold text-zinc-100">{user?.username}</div>
+ <div className="text-xs text-zinc-400">{formatRole(user?.role)}</div>
</div>
</div>
<form className="grid gap-2" onSubmit={(event) => {
@@ -1923,13 +2077,13 @@ export function SecurityPage() {
{(keys.data ?? []).map((key) => (
<div className="key-row" key={key.id}>
<div className="min-w-0">
- <div className="font-semibold text-slate-950">{key.name ?? "Unnamed API key"}</div>
- <div className="mt-1 flex flex-wrap gap-2 text-xs font-semibold text-slate-600">
+ <div className="font-semibold text-zinc-100">{key.name ?? "Unnamed API key"}</div>
+ <div className="mt-1 flex flex-wrap gap-2 text-xs font-semibold text-zinc-400">
<span className="font-mono">{apiKeyVisibleIdentifier(key)}</span>
{key.scopes ? <span className="badge">Scope: {key.scopes}</span> : null}
{apiKeyOwnerLabel(key) ? <span>Owner: {apiKeyOwnerLabel(key)}</span> : null}
</div>
- <div className="mt-1 flex flex-wrap gap-2 text-xs text-slate-500">
+ <div className="mt-1 flex flex-wrap gap-2 text-xs text-zinc-400">
{key.created_at ? <span>Created: {formatDateTime(key.created_at)}</span> : null}
{key.expires_at ? <span>Expires: {formatDateTime(key.expires_at)}</span> : <span>No expiry</span>}
</div>
@@ -1963,15 +2117,15 @@ export function SecurityPage() {
>
<div className="mb-4 flex flex-wrap items-start justify-between gap-3">
<div>
- <h2 className="text-lg font-bold text-slate-950" id="api-key-dialog-title">Save your key</h2>
- <p className="mt-1 text-sm text-slate-600">Copy this secret key now and store it somewhere safe.</p>
+ <h2 className="text-lg font-bold text-zinc-100" id="api-key-dialog-title">Save your key</h2>
+ <p className="mt-1 text-sm text-zinc-400">Copy this secret key now and store it somewhere safe.</p>
</div>
{generatedApiKey.prefix ? <span className="badge font-mono">{generatedApiKey.prefix}</span> : null}
</div>
- <p className="mb-4 rounded-md border border-amber-200 bg-amber-50 p-3 text-sm font-semibold text-amber-900">
+ <p className="mb-4 rounded-md border border-amber-500/30 bg-amber-500/10 p-3 text-sm font-semibold text-amber-200">
This secret key is shown only once. After you close this dialog, ARES will not show the full key again.
</p>
- <label className="block text-sm font-semibold text-slate-800">
+ <label className="block text-sm font-semibold text-zinc-300">
Secret key
<div className="mt-2 grid gap-2 sm:grid-cols-[1fr_auto]">
<input
@@ -1989,11 +2143,11 @@ export function SecurityPage() {
</div>
</label>
{copyStatus === "manual" && (
- <p className="mt-2 rounded-md border border-slate-200 bg-slate-50 p-3 text-sm text-slate-700">
+ <p className="mt-2 rounded-md border border-zinc-700 bg-zinc-900 p-3 text-sm text-zinc-300">
Clipboard access was blocked. The key field is selected; press Ctrl+C to copy it manually.
</p>
)}
- {generatedApiKey.note ? <p className="mt-3 text-sm text-slate-600">{generatedApiKey.note}</p> : null}
+ {generatedApiKey.note ? <p className="mt-3 text-sm text-zinc-400">{generatedApiKey.note}</p> : null}
<div className="mt-5 flex justify-end">
<button className="btn btn-primary" onClick={closeGeneratedKeyModal} type="button">Done</button>
</div>
@@ -2056,7 +2210,7 @@ export function EdrPage() {
<strong>{formatRate(stats.data?.success_rate)}</strong>
</div>
</div>
- <p className="mt-3 text-sm text-slate-600">{String(stats.data?.message ?? "No historical sample loaded yet.")}</p>
+ <p className="mt-3 text-sm text-zinc-400">{String(stats.data?.message ?? "No historical sample loaded yet.")}</p>
</section>
<DataPanel title="Stats Details" data={stats.data} />
<DataPanel title="Stats Error" data={stats.error} />
@@ -2433,6 +2587,12 @@ function formatReportDate(value: number): string {
return new Date(timestamp).toLocaleString();
}
+function formatReportTime(value: number): string {
+ if (!Number.isFinite(value)) return "n/a";
+ const timestamp = value > 10_000_000_000 ? value : value * 1000;
+ return new Date(timestamp).toLocaleTimeString([], { hour: "2-digit", minute: "2-digit", second: "2-digit" });
+}
+
function TelemetryPanel({ snapshot, loading, confirmedFindings }: { snapshot?: TelemetrySnapshot; loading: boolean; confirmedFindings: number }) {
const total = metricNumber(snapshot?.modules, "total");
const success = metricNumber(snapshot?.modules, "success");
@@ -2461,7 +2621,15 @@ function TelemetryPanel({ snapshot, loading, confirmedFindings }: { snapshot?: T
<SectionHeader
title="Telemetry Report"
description={loading ? "Waiting for metrics." : `Last sample: ${formatTimestamp(snapshot?.timestamp)}`}
- action={<span className={snapshot ? "badge badge-low" : "badge badge-medium"}>{snapshot ? "online" : "pending"}</span>}
+ action={
+ <div className="telemetry-live-status" title="Real-time telemetry ingestion pipeline">
+ <span className={`status-indicator-dot ${snapshot ? "active" : "pending"}`} />
+ <span className="status-indicator-text">{snapshot ? "Ingestion Active" : "Awaiting Data"}</span>
+ {snapshot?.timestamp ? (
+ <span className="status-indicator-time font-mono">{formatReportTime(snapshot.timestamp)}</span>
+ ) : null}
+ </div>
+ }
/>
<div className="telemetry-chart" aria-label="Runtime telemetry chart">
@@ -2472,14 +2640,14 @@ function TelemetryPanel({ snapshot, loading, confirmedFindings }: { snapshot?: T
</div>
<div className="mini-stat-grid mt-4">
- <MiniStat title="Module runs" value={formatMetric(total)} detail={`${success} success / ${failed} failed`} icon={<Database size={16} />} />
- <MiniStat title="Findings" value={formatMetric(findings)} icon={<ShieldAlert size={16} />} />
- <MiniStat title="Queue" value={formatMetric(queueDepth)} detail={`${activeWorkers} active workers`} icon={<Layers size={16} />} />
- <MiniStat title="Throughput" value={throughputValue} detail={latencyDetail} icon={<TrendingUp size={16} />} />
+ <MiniStat title="Module runs" value={formatMetric(total)} detail={`${success} success / ${failed} failed`} />
+ <MiniStat title="Findings" value={formatMetric(findings)} />
+ <MiniStat title="Queue" value={formatMetric(queueDepth)} detail={`${activeWorkers} active workers`} />
+ <MiniStat title="Throughput" value={throughputValue} detail={latencyDetail} />
</div>
<div className="telemetry-footer">
- <span><Target size={14} /> Scope: {snapshot?.campaign_id ? `campaign ${snapshot.campaign_id}` : "global"}</span>
+ <span>Scope: {snapshot?.campaign_id ? `campaign ${snapshot.campaign_id}` : "global"}</span>
<span>{hostsAvailable ? `${hostsDiscovered} discovered / ${hostsOwned ?? 0} owned hosts` : "Host ownership unavailable"}</span>
<span>{workerTotal === 0 ? "no worker sample" : unhealthyWorkers === 0 ? "workers healthy" : `${unhealthyWorkers} unhealthy workers`}</span>
</div>
@@ -2505,27 +2673,143 @@ function TelemetryBar({ label, value, tone = "ok" }: { label: string; value: num
);
}
-function DataPanel({ title, data }: { title: string; data: unknown }) {
+function CvssScoreCard({ data }: { data?: Record<string, unknown> }) {
+ if (!data) return null;
+ const score = data.base_score ?? data.score ?? data.overall;
+ const severity = String(data.severity ?? (typeof score === "number" && score >= 9 ? "critical" : typeof score === "number" && score >= 7 ? "high" : typeof score === "number" && score >= 4 ? "medium" : "low")).toLowerCase();
+ const vector = data.vector_string ?? data.vector;
+ return (
+ <section className="panel p-4 cvss-card">
+ <div className="flex items-start justify-between gap-4 mb-3">
+ <div>
+ <div className="text-[11px] font-semibold text-zinc-400 uppercase tracking-wider">Risk Assessment</div>
+ <h3 className="text-base font-semibold text-white">CVSS Metrics</h3>
+ </div>
+ <span className={`badge status-${severity} font-semibold uppercase text-xs px-2.5 py-1`}>
+ {severity}
+ </span>
+ </div>
+ <div className="grid grid-cols-1 sm:grid-cols-3 gap-3 mb-3">
+ <div className="bg-[#18181c] border border-[#27272a] rounded-lg p-3">
+ <div className="text-[11px] text-zinc-400">Base Score</div>
+ <div className="text-2xl font-bold font-mono text-white mt-1">{score !== undefined ? String(score) : "N/A"}</div>
+ </div>
+ <div className="bg-[#18181c] border border-[#27272a] rounded-lg p-3 sm:col-span-2">
+ <div className="text-[11px] text-zinc-400">Vector String</div>
+ <div className="text-xs font-mono text-zinc-300 mt-1.5 break-all">{vector ? String(vector) : "Vector string not calculated"}</div>
+ </div>
+ </div>
+ <details className="advanced-details">
+ <summary className="text-xs text-zinc-400 hover:text-zinc-200 cursor-pointer">Inspect Raw CVSS Payload</summary>
+ <pre className="json-box mt-2 text-xs font-mono">{JSON.stringify(data, null, 2)}</pre>
+ </details>
+ </section>
+ );
+}
+
+function CampaignDiffCard({ data }: { data?: Record<string, unknown> }) {
+ if (!data) return null;
+ return (
+ <section className="panel p-4 diff-card">
+ <div className="flex items-center justify-between mb-3">
+ <div>
+ <div className="text-[11px] font-semibold text-zinc-400 uppercase tracking-wider">Delta Analysis</div>
+ <h3 className="text-base font-semibold text-white">Campaign Comparison</h3>
+ </div>
+ <span className="badge badge-low text-xs">Compared</span>
+ </div>
+ <details className="advanced-details" open>
+ <summary className="text-xs text-zinc-400 hover:text-zinc-200 cursor-pointer mb-2">Detailed Delta Metrics</summary>
+ <pre className="json-box text-xs font-mono">{JSON.stringify(data, null, 2)}</pre>
+ </details>
+ </section>
+ );
+}
+
+function DataPanel({
+ title,
+ data,
+ onClear
+}: {
+ title: string;
+ data: unknown;
+ onClear?: () => void;
+}) {
+ const [copied, setCopied] = useState(false);
if (!data) {
return null;
}
const isError = data instanceof Error || data instanceof ApiError;
+ if (isError) {
+ const errorMsg = data instanceof ApiError ? String(data.detail) : data instanceof Error ? data.message : "The request failed.";
+ return (
+ <div className="rounded-lg border border-rose-500/30 bg-rose-500/10 p-3.5 text-xs text-rose-300 flex items-start justify-between gap-3 mb-3">
+ <div className="flex items-start gap-2.5">
+ <AlertTriangle size={16} className="text-rose-400 shrink-0 mt-0.5" />
+ <div>
+ <strong className="font-semibold text-rose-200 block mb-0.5">{title}</strong>
+ <span className="leading-relaxed">{errorMsg}</span>
+ </div>
+ </div>
+ <div className="flex items-center gap-2 shrink-0">
+ {onClear && (
+ <button
+ className="btn btn-compact text-[11px] py-0.5 px-2 flex items-center gap-1 text-rose-300 hover:text-white border-rose-500/30 hover:bg-rose-500/20"
+ onClick={onClear}
+ type="button"
+ title="Dismiss error"
+ >
+ <X size={12} />
+ <span>Dismiss</span>
+ </button>
+ )}
+ <span className="badge badge-high shrink-0 text-[10px] uppercase font-mono">Error</span>
+ </div>
+ </div>
+ );
+ }
+
+ const jsonText = JSON.stringify(serializeError(data), null, 2);
+ const handleCopy = () => {
+ void navigator.clipboard.writeText(jsonText);
+ setCopied(true);
+ setTimeout(() => setCopied(false), 1500);
+ };
+
return (
- <section className="panel detail-panel">
- <SectionHeader
- title={title}
- eyebrow={isError ? "Needs attention" : undefined}
- action={isError ? <span className="badge badge-high">error</span> : <span className="badge">details</span>}
- />
- {isError ? (
- <p className="notice notice-danger">
- <AlertTriangle size={16} />
- {data instanceof ApiError ? String(data.detail) : data instanceof Error ? data.message : "The request failed."}
- </p>
- ) : null}
+ <section className="panel detail-panel mb-3">
+ <div className="flex items-center justify-between mb-2">
+ <div className="flex items-center gap-2">
+ <Database size={14} className="text-zinc-400" />
+ <strong className="text-xs font-semibold text-zinc-200">{title}</strong>
+ </div>
+ <div className="flex items-center gap-2">
+ {onClear && (
+ <button
+ className="btn btn-compact text-[11px] py-0.5 px-2 flex items-center gap-1 text-zinc-400 hover:text-rose-400 hover:border-rose-900/50"
+ onClick={onClear}
+ type="button"
+ title="Clear payload preview"
+ >
+ <X size={12} />
+ <span>Clear</span>
+ </button>
+ )}
+ <button
+ className="btn btn-compact text-[11px] py-0.5 px-2 flex items-center gap-1.5"
+ onClick={handleCopy}
+ type="button"
+ title="Copy payload to clipboard"
+ >
+ {copied ? <CheckCircle2 size={12} className="text-emerald-400" /> : <Copy size={12} />}
+ <span>{copied ? "Copied" : "Copy Payload"}</span>
+ </button>
+ <span className="badge text-[10px] uppercase font-mono">Payload</span>
+ </div>
+ </div>
<details className="advanced-details">
- <summary>Details</summary>
- <pre className="json-box">{JSON.stringify(serializeError(data), null, 2)}</pre>
+ <summary className="text-xs text-zinc-400 hover:text-zinc-200 cursor-pointer">Inspect Payload Details</summary>
+ <pre className="json-box mt-2 text-xs font-mono">{jsonText}</pre>
</details>
</section>
);
@@ -2610,7 +2894,7 @@ function ModuleRunSummary({ result, error }: { result?: Record<string, unknown>;
<div className="flex flex-wrap items-start justify-between gap-2">
<div>
<div className="font-bold">{finding.title ?? `Finding ${index + 1}`}</div>
- <div className="mt-1 text-sm text-slate-600">{String(finding.description ?? "")}</div>
+ <div className="mt-1 text-sm text-zinc-400">{String(finding.description ?? "")}</div>
</div>
<span className={opsecBadge(finding.severity)}>{finding.severity ?? "info"}</span>
</div>
@@ -2620,7 +2904,7 @@ function ModuleRunSummary({ result, error }: { result?: Record<string, unknown>;
{typeof finding.confidence === "number" && <span className="badge">Confidence: {formatRate(finding.confidence)}</span>}
</div>
{finding.remediation ? (
- <p className="mt-2 text-sm text-slate-700">
+ <p className="mt-2 text-sm text-zinc-300">
<strong>Remediation:</strong> {String(finding.remediation)}
</p>
) : null}
@@ -2657,7 +2941,7 @@ function TemplatePlanSummary({ plan }: { plan?: TemplatePlanResponse }) {
<div className="compact-row" key={`${stage.name ?? "stage"}-${index}`}>
<div className="flex flex-wrap items-center justify-between gap-2">
<span className="font-bold">{index + 1}. {stage.name ?? "stage"}</span>
- <span className="text-xs font-semibold text-slate-500">{stage.modules?.length ?? 0} modules</span>
+ <span className="text-xs font-semibold text-zinc-400">{stage.modules?.length ?? 0} modules</span>
</div>
<div className="mt-2 flex flex-wrap gap-1">
{(stage.modules ?? []).map((moduleId) => <span className="badge" key={moduleId}>{moduleId}</span>)}
@@ -2665,12 +2949,13 @@ function TemplatePlanSummary({ plan }: { plan?: TemplatePlanResponse }) {
</div>
))}
</div>
- <p className="mt-3 text-sm text-slate-500">Ready for campaign dry-run structure.</p>
+ <p className="mt-3 text-sm text-zinc-400">Ready for campaign dry-run structure.</p>
</section>
);
}
function CampaignScopeSummary({ campaign, loading }: { campaign?: Campaign; loading?: boolean }) {
+ const [copied, setCopied] = useState(false);
if (loading) {
return (
<div className="detail-summary mt-3">
@@ -2685,14 +2970,32 @@ function CampaignScopeSummary({ campaign, loading }: { campaign?: Campaign; load
}
const targets = campaignTargets(campaign);
const scope = campaignScopeEntries(campaign);
+
+ const copyScope = () => {
+ void navigator.clipboard.writeText(JSON.stringify(campaign, null, 2));
+ setCopied(true);
+ setTimeout(() => setCopied(false), 1500);
+ };
+
return (
<div className="detail-summary mt-3">
<div className="mb-3 flex flex-wrap items-start justify-between gap-3">
<div>
- <h3 className="text-base font-bold">{campaign.name}</h3>
- <p className="text-sm text-slate-600">{campaign.client ?? "No client"} &middot; {campaign.status ?? "created"}</p>
+ <h3 className="text-base font-bold text-white tracking-tight">{campaign.name}</h3>
+ <p className="text-xs text-zinc-400 mt-0.5">{campaign.client ?? "No client"} &middot; <span className="text-emerald-400 uppercase font-mono text-[11px]">{campaign.status ?? "created"}</span></p>
+ </div>
+ <div className="flex items-center gap-2">
+ <button
+ type="button"
+ onClick={copyScope}
+ className="btn btn-compact text-[11px] py-1 px-2.5 flex items-center gap-1.5"
+ title="Copy campaign JSON"
+ >
+ {copied ? <CheckCircle2 size={12} className="text-emerald-400" /> : <Copy size={12} />}
+ <span>{copied ? "Copied" : "Copy Scope"}</span>
+ </button>
+ <span className="badge font-mono text-[11px]">{campaign.operator ?? "operator"}</span>
</div>
- <span className="badge">{campaign.operator ?? "operator"}</span>
</div>
<div className="mini-stat-grid">
<MiniStat title="Targets" value={String(targets.length)} detail={targets.slice(0, 3).join(", ") || "none declared"} />
@@ -2700,6 +3003,10 @@ function CampaignScopeSummary({ campaign, loading }: { campaign?: Campaign; load
<MiniStat title="Noise Profile" value={String(campaign.noise_profile ?? "stealth")} detail="OPSEC guardrail" />
<MiniStat title="Campaign ID" value={campaign.id.slice(0, 8)} detail="API/report key" />
</div>
+ <details className="advanced-details mt-3">
+ <summary className="text-xs text-zinc-400 hover:text-zinc-200 cursor-pointer">Inspect Raw Scope Parameters</summary>
+ <pre className="json-box mt-2 text-xs font-mono">{JSON.stringify(campaign, null, 2)}</pre>
+ </details>
</div>
);
}
@@ -2725,6 +3032,33 @@ function CampaignPicker({
);
}
+function StatusBadge({ status }: { status?: string }) {
+ const normalized = String(status ?? "").toLowerCase();
+ const isOk = ["active", "running", "ready", "restored", "complete", "completed"].some((item) => normalized.includes(item));
+ const isWarn = ["paused", "pending", "draft", "created"].some((item) => normalized.includes(item));
+ const isDanger = ["failed", "deleted", "blocked", "error"].some((item) => normalized.includes(item));
+ const toneClass = isOk ? "badge badge-low" : isDanger ? "badge badge-high" : isWarn ? "badge badge-medium" : "badge";
+ const dotColor = isOk ? "bg-emerald-400" : isDanger ? "bg-rose-400" : isWarn ? "bg-amber-400" : "bg-zinc-400";
+ return (
+ <span className={toneClass}>
+ <span className={`inline-block h-1.5 w-1.5 rounded-full ${dotColor}`} />
+ <span>{status ?? "created"}</span>
+ </span>
+ );
+}
+
+function NoiseProfileBadge({ noise }: { noise?: string }) {
+ const normalized = String(noise ?? "stealth").toLowerCase();
+ const isNoisy = normalized.includes("noisy") || normalized.includes("critical");
+ const isEvasive = normalized.includes("evasive") || normalized.includes("medium");
+ const badgeClass = isNoisy ? "badge badge-high" : isEvasive ? "badge badge-medium" : "badge";
+ return (
+ <span className={`${badgeClass} font-mono text-[11px] uppercase tracking-wider`}>
+ {noise ?? "stealth"}
+ </span>
+ );
+}
+
function CampaignTable({ campaigns }: { campaigns: Campaign[] }) {
return (
<section className="panel table-panel">
@@ -2741,13 +3075,17 @@ function CampaignTable({ campaigns }: { campaigns: Campaign[] }) {
<tr key={campaign.id}>
<td className="muted-cell">#{String(index + 1).padStart(2, "0")}</td>
<td>
- <div className="font-medium text-slate-950">{campaign.name}</div>
- <div className="mt-1 flex items-center gap-1 text-xs text-slate-500"><Eye size={13} /> {campaign.id.slice(0, 12)}</div>
+ <div className="font-semibold text-zinc-100 text-sm tracking-tight">{campaign.name}</div>
+ <div className="mt-1 flex items-center gap-1.5 text-xs">
+ <span className="font-mono text-[11px] text-zinc-400 bg-zinc-900/90 px-1.5 py-0.5 rounded border border-zinc-800/80">
+ {campaign.id.slice(0, 12)}
+ </span>
+ </div>
</td>
- <td>{campaign.client || "Internal"}</td>
- <td><span className={statusBadge(campaign.status)}>{campaign.status ?? "created"}</span></td>
- <td><span className={opsecBadge(campaign.noise_profile)}>{campaign.noise_profile ?? "stealth"}</span></td>
- <td>{campaign.operator || "operator"}</td>
+ <td className="text-zinc-300 text-sm">{campaign.client || "Internal"}</td>
+ <td><StatusBadge status={campaign.status} /></td>
+ <td><NoiseProfileBadge noise={campaign.noise_profile} /></td>
+ <td className="text-zinc-400 text-sm font-mono">{campaign.operator || "operator"}</td>
</tr>
))}
</tbody>
@@ -2775,10 +3113,10 @@ function FindingsTable({ findings }: { findings: any[] }) {
{findings.map((finding, index) => (
<tr key={finding.id ?? index}>
<td><span className={opsecBadge(finding.severity)}>{finding.severity ?? "info"}</span></td>
- <td className="font-medium text-slate-950">{finding.title ?? `Finding ${index + 1}`}</td>
- <td>{finding.module_id ?? "n/a"}</td>
- <td>{finding.mitre_technique ?? "n/a"}</td>
- <td>{finding.host ?? "n/a"}</td>
+ <td className="font-semibold text-zinc-100 text-sm">{finding.title ?? `Finding ${index + 1}`}</td>
+ <td className="text-zinc-300 font-mono text-xs">{finding.module_id ?? "n/a"}</td>
+ <td className="text-zinc-300 font-mono text-xs">{finding.mitre_technique ?? "n/a"}</td>
+ <td className="text-zinc-400 text-sm">{finding.host ?? "n/a"}</td>
</tr>
))}
</tbody>
@@ -2867,9 +3205,9 @@ function ParamForm({
onChange(next);
}}
/>
- {description && <span className="mt-1 block text-xs text-slate-600">{description}</span>}
+ {description && <span className="mt-1 block text-xs text-zinc-400">{description}</span>}
{fieldDefaultHint(field) && (
- <span className="mt-1 block text-xs font-medium text-slate-500">{fieldDefaultHint(field)}</span>
+ <span className="mt-1 block text-xs font-medium text-zinc-400">{fieldDefaultHint(field)}</span>
)}
</label>
);
diff --git a/frontend/src/features/dashboard/DashboardRouter.tsx b/frontend/src/features/dashboard/DashboardRouter.tsx
index 8c55e06..c61f359 100644
--- a/frontend/src/features/dashboard/DashboardRouter.tsx
+++ b/frontend/src/features/dashboard/DashboardRouter.tsx
@@ -1,6 +1,7 @@
import { Loader2 } from "lucide-react";
import { lazy, Suspense } from "react";
-import { Navigate, Route, Routes } from "react-router-dom";
+import { useEffect } from "react";
+import { Navigate, Route, Routes, useNavigate } from "react-router-dom";
import {
CampaignsPage,
DashboardShell,
@@ -20,6 +21,11 @@ const GraphPage = lazy(() => import("../graph/GraphPage"));
function DashboardRoutes() {
const { selectedCampaignId, setSelectedCampaignId } = useDashboardUi();
+ const navigate = useNavigate();
+
+ useEffect(() => {
+ (window as unknown as { __navigate?: typeof navigate }).__navigate = navigate;
+ }, [navigate]);
return (
<Routes>
diff --git a/frontend/src/styles.css b/frontend/src/styles.css
index 7e34c09..fc82563 100644
--- a/frontend/src/styles.css
+++ b/frontend/src/styles.css
@@ -43,6 +43,12 @@ button:disabled {
min-height: 100vh;
grid-template-columns: 248px minmax(0, 1fr);
background: #09090b;
+ animation: appShellFadeIn 0.25s cubic-bezier(0.16, 1, 0.3, 1) both;
+}
+
+@keyframes appShellFadeIn {
+ from { opacity: 0; transform: translateY(4px); }
+ to { opacity: 1; transform: translateY(0); }
}
.app-shell.sidebar-collapsed {
@@ -57,6 +63,8 @@ button:disabled {
.sidebar-collapsed .sidebar-title,
.sidebar-collapsed .sidebar-subtitle,
.sidebar-collapsed .nav-group-label,
+.sidebar-collapsed .sidebar-footer,
+.sidebar-collapsed .nav-count-badge,
.sidebar-collapsed .nav-link span {
display: none;
}
@@ -168,6 +176,52 @@ button:disabled {
content: "";
}
+.nav-count-badge {
+ margin-left: auto;
+ display: inline-flex;
+ align-items: center;
+ justify-content: center;
+ min-width: 1.25rem;
+ height: 1.25rem;
+ padding: 0 0.35rem;
+ border-radius: 999px;
+ background: #1e1e24;
+ border: 1px solid #2e2e38;
+ color: #a1a1aa;
+ font-size: 0.68rem;
+ font-weight: 600;
+}
+
+.sidebar-footer {
+ margin-top: auto;
+ border-top: 1px solid #222227;
+ padding: 0.75rem 0.85rem;
+ background: #0c0c0f;
+}
+
+.sidebar-enclave-badge {
+ display: flex;
+ align-items: center;
+ gap: 0.65rem;
+ padding: 0.5rem 0.65rem;
+ border-radius: 6px;
+ background: #121217;
+ border: 1px solid #222228;
+}
+
+.sidebar-enclave-title {
+ color: #e4e4e7;
+ font-size: 0.68rem;
+ font-weight: 700;
+ letter-spacing: 0.04em;
+}
+
+.sidebar-enclave-sub {
+ color: #71717a;
+ font-size: 0.64rem;
+ margin-top: 0.05rem;
+}
+
.user-chip-avatar,
.profile-avatar-light {
display: inline-flex;
@@ -247,10 +301,54 @@ button:disabled {
font-size: 0.84rem;
}
+.topbar-scope-wrap {
+ display: flex;
+ align-items: center;
+ gap: 0.45rem;
+ border: 1px solid #27272a;
+ border-radius: 6px;
+ background: #121215;
+ padding: 0.35rem 0.65rem;
+ color: #a1a1aa;
+ font-size: 0.8rem;
+}
+
+.topbar-scope-select {
+ border: 0;
+ background: transparent;
+ color: #f4f4f5;
+ font-size: 0.8rem;
+ font-weight: 500;
+ outline: none;
+ cursor: pointer;
+ max-width: 180px;
+}
+
+.topbar-scope-select option {
+ background: #18181b;
+ color: #f4f4f5;
+}
+
.topbar-search input::placeholder {
color: #71717a;
}
+.search-kbd-badge {
+ display: inline-flex;
+ align-items: center;
+ justify-content: center;
+ height: 18px;
+ min-width: 18px;
+ padding: 0 4px;
+ border-radius: 4px;
+ background: #27272a;
+ border: 1px solid #3f3f46;
+ color: #a1a1aa;
+ font-size: 0.68rem;
+ font-weight: 600;
+ font-family: ui-monospace, SFMono-Regular, monospace;
+}
+
.search-results {
position: absolute;
top: calc(100% + 0.4rem);
@@ -440,6 +538,261 @@ button:disabled {
font-weight: 500;
}
+.topbar-status-btn,
+.topbar-heartbeat {
+ display: inline-flex;
+ align-items: center;
+ gap: 0.5rem;
+ border: 1px solid #27272a;
+ border-radius: 6px;
+ background: #141417;
+ padding: 0.28rem 0.65rem;
+ color: #e4e4e7;
+ font-size: 0.74rem;
+ font-weight: 500;
+ cursor: pointer;
+ transition: border-color 120ms ease, background 120ms ease;
+}
+
+.topbar-status-btn:hover,
+.topbar-heartbeat:hover {
+ border-color: #3f3f46;
+ background: #18181e;
+}
+
+.topbar-status-btn .status-dot,
+.heartbeat-dot {
+ height: 6px;
+ width: 6px;
+ border-radius: 50%;
+ flex-shrink: 0;
+}
+
+.topbar-status-btn .status-dot.online,
+.heartbeat-dot.online {
+ background: #10b981;
+ box-shadow: 0 0 0 2px rgba(16, 185, 129, 0.25);
+}
+
+.topbar-status-btn .status-dot.warning,
+.heartbeat-dot.warning {
+ background: #f59e0b;
+ box-shadow: 0 0 0 2px rgba(245, 158, 11, 0.25);
+}
+
+.topbar-status-btn .status-title,
+.heartbeat-text {
+ font-size: 0.73rem;
+ font-weight: 500;
+ color: #e4e4e7;
+}
+
+.topbar-status-btn .status-pill-count,
+.heartbeat-badge {
+ color: #71717a;
+ font-size: 0.68rem;
+ border-left: 1px solid #27272a;
+ padding-left: 0.45rem;
+}
+
+.telemetry-popover {
+ position: absolute;
+ right: 0;
+ top: calc(100% + 0.5rem);
+ z-index: 40;
+ width: min(320px, calc(100vw - 2rem));
+ border: 1px solid #27272a;
+ border-radius: 8px;
+ background: #141417;
+ padding: 0.85rem;
+ box-shadow: 0 20px 40px rgba(0, 0, 0, 0.75);
+}
+
+.telemetry-popover-header {
+ display: flex;
+ align-items: center;
+ justify-content: space-between;
+ margin-bottom: 0.75rem;
+ padding-bottom: 0.5rem;
+ border-bottom: 1px solid #222228;
+}
+
+.telemetry-popover-header strong {
+ font-size: 0.82rem;
+ color: #f4f4f5;
+}
+
+.telemetry-popover-grid {
+ display: grid;
+ grid-template-columns: 1fr 1fr;
+ gap: 0.5rem;
+}
+
+.popover-stat {
+ padding: 0.5rem;
+ border-radius: 6px;
+ background: #18181d;
+ border: 1px solid #222228;
+}
+
+.popover-stat span {
+ display: block;
+ font-size: 0.68rem;
+ color: #71717a;
+}
+
+.popover-stat strong {
+ display: block;
+ font-size: 0.82rem;
+ color: #f4f4f5;
+ font-family: ui-monospace, SFMono-Regular, monospace;
+ margin-top: 0.15rem;
+}
+
+.operator-menu-wrap {
+ position: relative;
+}
+
+.operator-trigger {
+ display: inline-flex;
+ align-items: center;
+ gap: 0.55rem;
+ border: 1px solid #222227;
+ border-radius: 6px;
+ background: #121216;
+ padding: 0.32rem 0.6rem;
+ color: #f4f4f5;
+ cursor: pointer;
+ transition: border-color 120ms ease, background 120ms ease;
+}
+
+.operator-trigger:hover {
+ border-color: #3f3f46;
+ background: #18181e;
+}
+
+.operator-avatar {
+ display: inline-flex;
+ align-items: center;
+ justify-content: center;
+ height: 26px;
+ width: 26px;
+ border-radius: 999px;
+ background: #27272a;
+ border: 1px solid #3f3f46;
+ color: #ffffff;
+ font-size: 0.75rem;
+ font-weight: 700;
+}
+
+.operator-info {
+ text-align: left;
+ line-height: 1.15;
+}
+
+.operator-info strong {
+ display: block;
+ font-size: 0.78rem;
+ color: #f4f4f5;
+}
+
+.operator-info small {
+ display: block;
+ font-size: 0.66rem;
+ color: #71717a;
+ font-weight: 500;
+}
+
+.chevron-indicator {
+ color: #71717a;
+ transition: transform 120ms ease;
+}
+
+.chevron-indicator.open {
+ transform: rotate(180deg);
+}
+
+.operator-dropdown {
+ position: absolute;
+ right: 0;
+ top: calc(100% + 0.45rem);
+ z-index: 45;
+ min-width: 220px;
+ border: 1px solid #27272a;
+ border-radius: 8px;
+ background: #121216;
+ padding: 0.5rem;
+ box-shadow: 0 20px 40px rgba(0, 0, 0, 0.75);
+}
+
+.operator-dropdown-header {
+ padding: 0.5rem 0.65rem 0.65rem;
+ border-bottom: 1px solid #222228;
+}
+
+.operator-dropdown-title {
+ font-size: 0.68rem;
+ font-weight: 600;
+ text-transform: uppercase;
+ letter-spacing: 0.04em;
+ color: #71717a;
+}
+
+.operator-dropdown-badge {
+ display: inline-block;
+ margin-top: 0.35rem;
+ padding: 0.15rem 0.45rem;
+ border-radius: 4px;
+ background: rgba(59, 130, 246, 0.12);
+ border: 1px solid rgba(59, 130, 246, 0.3);
+ color: #93c5fd;
+ font-size: 0.68rem;
+ font-weight: 600;
+}
+
+.operator-dropdown-sub {
+ margin-top: 0.35rem;
+ font-size: 0.72rem;
+ color: #a1a1aa;
+}
+
+.operator-dropdown-actions {
+ display: grid;
+ gap: 0.25rem;
+ padding-top: 0.45rem;
+}
+
+.operator-action-item {
+ display: flex;
+ align-items: center;
+ gap: 0.55rem;
+ width: 100%;
+ border: 0;
+ border-radius: 5px;
+ background: transparent;
+ padding: 0.45rem 0.65rem;
+ color: #e4e4e7;
+ font-size: 0.78rem;
+ font-weight: 500;
+ text-align: left;
+ cursor: pointer;
+ transition: background 100ms ease, color 100ms ease;
+}
+
+.operator-action-item:hover {
+ background: #1e1e24;
+ color: #ffffff;
+}
+
+.operator-action-item.danger {
+ color: #fda4af;
+}
+
+.operator-action-item.danger:hover {
+ background: rgba(244, 63, 94, 0.12);
+ color: #fecdd3;
+}
+
.content-shell {
margin: 0 auto;
width: min(100%, 1500px);
@@ -800,7 +1153,7 @@ textarea.field {
align-items: center;
gap: 0.35rem;
border: 1px solid #27272a;
- border-radius: 999px;
+ border-radius: 4px;
background: #18181b;
color: #a1a1aa;
font-size: 0.72rem;
@@ -810,33 +1163,76 @@ textarea.field {
}
.badge {
- padding: 0.22rem 0.52rem;
+ padding: 0.2rem 0.45rem;
}
.status-pill {
- min-height: 24px;
- padding: 0.26rem 0.56rem;
+ min-height: 22px;
+ padding: 0.22rem 0.5rem;
}
.badge-high,
.status-high {
- border-color: rgba(244, 63, 94, 0.3);
- background: rgba(244, 63, 94, 0.1);
- color: #fda4af;
+ border-color: rgba(244, 63, 94, 0.25);
+ background: rgba(244, 63, 94, 0.08);
+ color: #fb7185;
}
.badge-medium,
.status-medium {
- border-color: rgba(245, 158, 11, 0.3);
- background: rgba(245, 158, 11, 0.1);
- color: #fcd34d;
+ border-color: rgba(245, 158, 11, 0.25);
+ background: rgba(245, 158, 11, 0.08);
+ color: #fbbf24;
}
.badge-low,
.status-low {
- border-color: rgba(16, 185, 129, 0.3);
- background: rgba(16, 185, 129, 0.1);
- color: #6ee7b7;
+ border-color: rgba(16, 185, 129, 0.25);
+ background: rgba(16, 185, 129, 0.08);
+ color: #34d399;
+}
+
+.telemetry-live-status {
+ display: inline-flex;
+ align-items: center;
+ gap: 0.45rem;
+ border: 1px solid #27272a;
+ border-radius: 6px;
+ background: #141417;
+ padding: 0.25rem 0.6rem;
+ font-size: 0.72rem;
+ font-weight: 500;
+ color: #d4d4d8;
+}
+
+.status-indicator-dot {
+ width: 6px;
+ height: 6px;
+ border-radius: 50%;
+ flex-shrink: 0;
+}
+
+.status-indicator-dot.active {
+ background: #10b981;
+ box-shadow: 0 0 0 2px rgba(16, 185, 129, 0.25);
+}
+
+.status-indicator-dot.pending {
+ background: #f59e0b;
+ box-shadow: 0 0 0 2px rgba(245, 158, 11, 0.25);
+}
+
+.status-indicator-text {
+ font-size: 0.72rem;
+ font-weight: 500;
+ color: #e4e4e7;
+}
+
+.status-indicator-time {
+ color: #71717a;
+ font-size: 0.68rem;
+ border-left: 1px solid #27272a;
+ padding-left: 0.45rem;
}
.telemetry-panel {
@@ -1024,32 +1420,36 @@ textarea.field {
}
.highlight-value {
- min-width: 54px;
- border-radius: 999px;
- padding: 0.28rem 0.5rem;
+ min-width: 50px;
+ border-radius: 6px;
+ padding: 0.22rem 0.55rem;
text-align: center;
- font-size: 0.84rem;
- font-weight: 600;
+ font-size: 0.78rem;
+ font-weight: 500;
font-family: ui-monospace, SFMono-Regular, monospace;
}
.highlight-low {
- background: rgba(16, 185, 129, 0.12);
- color: #6ee7b7;
+ border: 1px solid rgba(16, 185, 129, 0.25);
+ background: rgba(16, 185, 129, 0.08);
+ color: #34d399;
}
.highlight-medium {
- background: rgba(245, 158, 11, 0.12);
- color: #fcd34d;
+ border: 1px solid rgba(245, 158, 11, 0.25);
+ background: rgba(245, 158, 11, 0.08);
+ color: #fbbf24;
}
.highlight-high {
- background: rgba(244, 63, 94, 0.12);
- color: #fda4af;
+ border: 1px solid rgba(244, 63, 94, 0.25);
+ background: rgba(244, 63, 94, 0.08);
+ color: #fb7185;
}
.highlight-neutral {
- background: #27272a;
+ border: 1px solid #27272a;
+ background: #18181b;
color: #d4d4d8;
}
@@ -1281,6 +1681,12 @@ textarea.field {
border-radius: 6px;
}
+.cvss-card,
+.diff-card {
+ border: 1px solid #27272a;
+ background: #121216;
+}
+
.entity-card {
display: grid;
grid-template-columns: auto minmax(0, 1fr);
@@ -1773,3 +2179,39 @@ textarea.field {
min-height: 390px;
}
}
+
+/* ==========================================================================
+ Login Page Animations
+ Each animation is motivated — see inline rationale.
+ ========================================================================== */
+
+/* Entry stagger — communicates hierarchy: brand → copy → pillars → card */
+@keyframes loginSlideFade {
+ 0% { opacity: 0; transform: translateY(12px); }
+ 100% { opacity: 1; transform: translateY(0); }
+}
+
+.animate-login-enter {
+ animation: loginSlideFade 0.5s cubic-bezier(0.16, 1, 0.3, 1) both;
+}
+
+/* Status beacon — communicates "live": DAG engine is running, not static */
+@keyframes beaconPulse {
+ 0%, 100% { opacity: 1; transform: scale(1); }
+ 50% { opacity: 0.4; transform: scale(1.2); }
+}
+
+.animate-beacon {
+ animation: beaconPulse 2.4s ease-in-out infinite;
+}
+
+/* Ambient breathe — communicates the system is active, not idle.
+ Slow enough (9s) to be subliminal, not distracting. */
+@keyframes aresBreathe {
+ 0%, 100% { opacity: 0.5; transform: scale(0.96); }
+ 50% { opacity: 1; transform: scale(1.04); }
+}
+
+.animate-ares-breathe {
+ animation: aresBreathe 9s ease-in-out infinite;
+}
diff --git a/skills-lock.json b/skills-lock.json
new file mode 100644
index 0000000..c5795d1
--- /dev/null
+++ b/skills-lock.json
@@ -0,0 +1,11 @@
+{
+ "version": 1,
+ "skills": {
+ "design-taste-frontend": {
+ "source": "Leonxlnx/taste-skill",
+ "sourceType": "github",
+ "skillPath": "skills/taste-skill/SKILL.md",
+ "computedHash": "899b84384f74f540ea5284d9b2e9234e050998b42eacc805410b518d4226c0b3"
+ }
+ }
+}