@pikaa-ai/pikaa 0.3.22 → 0.3.24

package/skills/flowio/SKILL.md

@@ -1,310 +0,0 @@
----
-name: flowio
-description: Read, inspect, and write Flow Cytometry Standard (FCS) 2.0, 3.0, and 3.1 files with FlowIO. Use for low-level FCS metadata and channel inspection, NumPy event extraction, multi-dataset files, table export, and FCS 3.1 creation; use FlowKit for compensation, cytometry transforms, gating, or FlowJo workspaces.
-allowed-tools: Read Write Bash
-license: BSD-3-Clause license
-compatibility: Requires Python 3.9-3.13, uv, and FlowIO 1.4.0. NumPy is installed with FlowIO; pandas is optional for DataFrame workflows. Runtime parsing is local and needs no credentials or network access.
-metadata:
-  version: "2.0"
-  skill-author: K-Dense Inc.
----
-
-# FlowIO
-
-## Purpose
-
-Use FlowIO as a lightweight, low-level reader and writer for Flow Cytometry
-Standard files. Examples in this skill target **FlowIO 1.4.0**, the current
-stable release verified on 2026-07-23.
-
-FlowIO is appropriate for:
-
-- Reading FCS 2.0, 3.0, and 3.1 files
-- Inspecting HEADER, TEXT, ANALYSIS, and channel metadata
-- Retrieving event data as a two-dimensional NumPy array
-- Reading legacy files that contain multiple datasets
-- Writing list-mode, single-precision FCS 3.1 files
-- Preparing data for pandas, machine-learning, or downstream cytometry tools
-
-FlowIO does **not** perform compensation, logicle/biexponential transforms,
-gating, clustering, or FlowJo workspace processing. Use FlowKit or another
-analysis package for those tasks.
-
-## Install
-
-Create or activate a Python environment, then install the verified release:
-
-```bash
-uv pip install "flowio==1.4.0"
-```
-
-Confirm the runtime version:
-
-```bash
-uv run python -c "import flowio; print(flowio.__version__)"
-```
-
-FlowIO 1.4.0 supports Python 3.9 through 3.13 and depends on NumPy.
-
-## Operating Workflow
-
-1. **Clarify the operation.** Distinguish metadata inventory, event extraction,
-   file repair, conversion, and downstream biological analysis.
-2. **Inspect before loading events.** Use `only_text=True` for metadata-only
-   work, especially with large or unfamiliar files.
-3. **Choose event semantics explicitly.** Use `as_array(preprocess=True)` for
-   gain/log/time scaling from FCS metadata, or `preprocess=False` for values as
-   encoded in the DATA segment. Record the choice.
-4. **Keep parsing strict by default.** Do not automatically suppress offset
-   errors. Relax checks only for a known vendor-format defect, and review the
-   resulting event data.
-5. **Treat metadata as potentially sensitive.** FCS TEXT values can include
-   sample, subject, operator, and instrument identifiers. Export only fields
-   needed for the task.
-6. **Validate writes by reopening them.** Check event/channel counts, labels,
-   metadata, and representative values after any FCS export.
-
-## Critical Semantics
-
-### TEXT keys are normalized
-
-`FlowData.text` stores keys in lowercase and strips the leading `$` from
-standard FCS keywords:
-
-```python
-from flowio import FlowData
-
-flow = FlowData("sample.fcs", only_text=True)
-acquisition_date = flow.text.get("date")
-instrument = flow.text.get("cyt")
-next_dataset = int(flow.text.get("nextdata", "0"))
-```
-
-Do not look up `"$DATE"`, `"$CYT"`, or other uppercase dollar-prefixed keys.
-TEXT values remain strings. FlowIO 1.4.0 also removes every `$` character from
-the decoded TEXT segment, including `$` characters inside values; preserve the
-original file when exact metadata fidelity matters.
-
-### Events have two representations
-
-- `flow.events` is the unprocessed, flattened one-dimensional event array.
-- `flow.as_array()` returns shape `(event_count, channel_count)` as a NumPy
-  `float64` array.
-- `flow.as_array(preprocess=True)` applies FCS gain, logarithmic, and time
-  scaling. It does not apply compensation or logicle/biexponential display
-  transforms.
-- `flow.as_array(preprocess=False)` reshapes the encoded event values without
-  those scaling steps.
-
-`as_array()` creates another in-memory array. FlowIO does not provide chunked
-or memory-mapped event access.
-
-### Channel numbering uses two conventions
-
-- NumPy columns and `fluoro_indices`, `scatter_indices`, and `time_index` use
-  zero-based indices.
-- `flow.channels` uses FCS parameter numbers beginning at 1.
-- `null_channels` contains the PnN label strings supplied through
-  `null_channel_list`, including supplied labels that were not found.
-- `pns_labels` always matches `pnn_labels` in length; missing optional PnS
-  labels appear as empty strings.
-
-### Writing is intentionally limited
-
-`create_fcs()` requires:
-
-- An already-open binary file handle
-- Flattened one-dimensional event data in row-major event/channel order
-- One PnN name per channel
-- Optional PnS names and string-valued metadata via `metadata_dict`
-
-It writes FCS 3.1 list-mode (`$MODE=L`) single-precision float
-(`$DATATYPE=F`) data. Required interpretation keywords are generated by
-FlowIO and cannot be overridden through metadata.
-
-## Quick Start: Read an FCS File
-
-```python
-from pathlib import Path
-
-from flowio import FlowData
-
-flow = FlowData(Path("sample.fcs"))
-events = flow.as_array(preprocess=True)
-
-print(
-    {
-        "version": flow.version,
-        "events": flow.event_count,
-        "channels": flow.channel_count,
-        "shape": events.shape,
-        "pnn": flow.pnn_labels,
-        "pns": flow.pns_labels,
-        "date": flow.text.get("date"),
-        "instrument": flow.text.get("cyt"),
-    }
-)
-```
-
-For metadata only:
-
-```python
-from flowio import FlowData
-
-flow = FlowData("sample.fcs", only_text=True)
-print(flow.version, flow.event_count, flow.pnn_labels)
-```
-
-Do not call `as_array()` on a metadata-only instance because its event data was
-not loaded.
-
-Prefer a path or `Path` over a caller-owned file handle. `FlowData` closes a
-provided handle after parsing. In FlowIO 1.4.0,
-`read_multiple_data_sets(handle)` can fail after the first dataset because the
-handle has been closed; pass a filesystem path for multi-dataset files.
-
-## Quick Start: Read Multiple Datasets
-
-Use the standalone helper rather than manually interpreting `$NEXTDATA`
-offsets:
-
-```python
-from flowio import read_multiple_data_sets
-
-datasets = read_multiple_data_sets("legacy-multi-dataset.fcs")
-for index, dataset in enumerate(datasets):
-    values = dataset.as_array(preprocess=True)
-    print(index, dataset.event_count, dataset.pnn_labels, values.shape)
-```
-
-The FCS 3.1 specification deprecated multiple datasets in one file, but FlowIO
-can read legacy files that use them.
-
-## Quick Start: Create an FCS 3.1 File
-
-```python
-from pathlib import Path
-
-import numpy as np
-from flowio import FlowData, create_fcs
-
-values = np.asarray(
-    [[100.0, 200.0, 50.0], [150.0, 180.0, 60.0]],
-    dtype=np.float32,
-)
-pnn_labels = ["FSC-A", "SSC-A", "FITC-A"]
-pns_labels = ["Forward scatter", "Side scatter", "CD3"]
-
-output = Path("output.fcs")
-with output.open("xb") as handle:
-    create_fcs(
-        handle,
-        values.ravel(order="C"),
-        pnn_labels,
-        opt_channel_names=pns_labels,
-        metadata_dict={
-            "date": "23-JUL-2026",
-            "cyt": "Example instrument",
-            "src": "Validated NumPy array",
-        },
-    )
-
-roundtrip = FlowData(output)
-assert roundtrip.event_count == values.shape[0]
-assert roundtrip.pnn_labels == pnn_labels
-np.testing.assert_allclose(
-    roundtrip.as_array(preprocess=False),
-    values,
-    rtol=1e-6,
-    atol=1e-6,
-)
-```
-
-Metadata keys may be supplied in mixed case or with `$`, but lowercase keys
-without `$` match FlowIO's normalized representation and are less error-prone.
-Metadata values must be strings.
-
-## Copy or Rewrite an Existing File
-
-Use `write_fcs()` when the event data does not need to change:
-
-```python
-from flowio import FlowData
-
-flow = FlowData("source.fcs")
-
-# Preserve selected source metadata (cyt, date, and spill/spillover when present).
-flow.write_fcs("copy.fcs")
-
-# Write only required metadata plus the custom fields supplied here.
-flow.write_fcs("deidentified.fcs", metadata={"src": "Deidentified export"})
-```
-
-Passing `metadata=None` preserves FlowIO's selected defaults. Passing any
-dictionary, including `{}`, replaces those defaults rather than merging with
-them. `write_fcs()` always produces FCS 3.1 floating-point output; non-float
-source events are preprocessed before writing. It opens the destination for
-overwrite, so reject an existing output path before calling it unless
-replacement is intentional. For floating-point sources it can preserve encoded
-events while dropping PnG or `timestep`, changing later
-`as_array(preprocess=True)` results. Validate both raw and preprocessed
-round-trips.
-
-Use `create_fcs()` instead when event values, event count, or channel layout
-changes.
-
-## Bundled Inspector
-
-`scripts/inspect_fcs.py` inventories one or more datasets without network
-access. By default it reads metadata only, emits structural fields and channel
-labels without full TEXT/ANALYSIS values, and refuses files above a
-configurable size limit.
-
-Set `FLOWIO_SKILL_DIR` to the installed skill directory. From this repository's
-root, use `skills/flowio`:
-
-```bash
-FLOWIO_SKILL_DIR="skills/flowio"
-
-# Metadata and channel inventory
-uv run --no-project --with "flowio==1.4.0" \
-  python "$FLOWIO_SKILL_DIR/scripts/inspect_fcs.py" sample.fcs
-
-# Include all normalized TEXT metadata; review output for identifiers
-uv run --no-project --with "flowio==1.4.0" \
-  python "$FLOWIO_SKILL_DIR/scripts/inspect_fcs.py" sample.fcs --include-text
-
-# Load events and compute finite-value statistics using FlowIO preprocessing
-uv run --no-project --with "flowio==1.4.0" \
-  python "$FLOWIO_SKILL_DIR/scripts/inspect_fcs.py" sample.fcs --stats
-
-# Compute statistics from encoded values instead
-uv run --no-project --with "flowio==1.4.0" \
-  python "$FLOWIO_SKILL_DIR/scripts/inspect_fcs.py" sample.fcs --stats --raw
-```
-
-Use `--help` for output files, input/array memory limits, null-channel labels,
-and controlled offset-recovery options.
-
-## References
-
-Read only the reference needed for the current task:
-
-- `references/api_reference.md` — exact FlowIO 1.4.0 public API and signatures
-- `references/workflows.md` — inventory, DataFrame/CSV, batch, write, and
-  round-trip patterns
-- `references/fcs_semantics.md` — FCS structure, metadata normalization,
-  preprocessing equations, indexing, and writer behavior
-- `references/troubleshooting.md` — offset failures, multi-dataset files,
-  memory limits, validation, security, and privacy
-- `references/sources.md` — authoritative upstream docs, release notes, source,
-  and FCS 3.1 publications used for this refresh
-
-## Non-Negotiable Checks
-
-- Never claim FlowIO applies compensation or gating.
-- Never treat `as_array(preprocess=True)` as raw acquisition values.
-- Never pass a two-dimensional array or a path directly to `create_fcs()`.
-- Never assume TEXT keys retain `$` or uppercase spelling.
-- Never silence offset errors without documenting why and validating the data.
-- Never describe FlowIO event loading as streaming or chunked.

package/skills/fluidsim/SKILL.md

@@ -1,279 +0,0 @@
----
-name: fluidsim
-description: Plan, configure, inspect, restart, and analyze bounded FluidSim computational-fluid-dynamics simulations with explicit numerical-validity and HPC safety checks. Use for FluidSim solver selection, parameter review, FFT/MPI setup, output diagnostics, or restart compatibility.
-license: MIT
-compatibility: Bundled CLIs require Python 3.11+ and use the standard library; HDF5/netCDF4 metadata tools lazily use h5py when available. Simulation examples target fluidsim 0.9.0, fluidfft 0.4.5, and pyFFTW 0.15.1. MPI/native FFT use requires a site-compatible MPI implementation, development headers, FFTW/PFFT/P3DFFT libraries, compilers, and an approved scheduler workflow. No GPU backend is assumed.
-allowed-tools: Read Write Bash Glob Python
-metadata:
-  version: "1.1"
-  skill-author: "K-Dense Inc."
-  last-reviewed: "2026-07-23"
----
-
-# FluidSim
-
-Use FluidSim 0.9.0 as a framework for Python-defined numerical solvers, especially
-periodic Cartesian pseudospectral CFD. Upstream FluidSim is CeCILL-2.1; the MIT
-frontmatter license applies only to this skill.
-
-This skill does **not** treat a completed run, a stable time step, a smooth plot,
-or a closed program exit as evidence of numerical convergence or physical
-validity.
-
-## Required workflow
-
-1. State equations, units or nondimensionalization, geometry, boundaries,
-   initial conditions, forcing, observables, and acceptance criteria.
-2. Select a verified solver and inspect its generated default parameters.
-3. Create a strict JSON plan with explicit CPU, RAM, disk, wall-time, output-file,
-   timestep, CFL, resolution, and dealiasing bounds.
-4. Run the bundled validator and resource estimator.
-5. Generate and review a dry-run script. It does nothing unless executed with an
-   explicit config-ID acknowledgement.
-6. Run one tiny serial pilot. Inspect budgets, divergence/constraints, spectral
-   tails, CFL/time-step history, and output growth.
-7. Refine grid and time step independently. Check conservation/budget residuals
-   and observable sensitivity.
-8. Only then prepare a site-specific MPI job. Never submit or launch MPI
-   automatically.
-9. Preserve config, script, `uv.lock`, package/platform/backend versions, logs,
-   output inventory, checksums, and restart lineage.
-
-Stop if physical assumptions, units, boundary conditions, forcing semantics,
-resolution criteria, resource limits, or acceptance criteria are missing.
-
-## Version and installation
-
-As verified on 2026-07-23:
-
-- Latest stable PyPI release: `fluidsim==0.9.0` (2025-12-04).
-- Package metadata requires Python `>=3.11` and lists Python 3.11–3.14.
-- Pseudospectral parameter creation needs FluidFFT; bare `fluidsim` imported in
-  the smoke test, but `ns2d.create_default_params()` failed until the `fft` extra
-  was installed.
-- Current companion versions tested here: `fluidfft==0.4.5` and
-  `pyFFTW==0.15.1`.
-
-Prefer a project lock:
-
-```bash
-uv init --python 3.11
-uv add "fluidsim[fft]==0.9.0" "fluidfft==0.4.5" "pyFFTW==0.15.1"
-uv lock
-uv sync --frozen
-```
-
-For an isolated disposable environment:
-
-```bash
-uv venv --python 3.11
-uv pip install "fluidsim[fft]==0.9.0" "fluidfft==0.4.5" "pyFFTW==0.15.1"
-```
-
-The project lock is the reproducibility record; direct pins alone do not freeze
-all transitive artifacts. Do not reuse a lock across incompatible platforms or
-MPI ABIs.
-
-MPI is optional and native:
-
-```bash
-uv add "mpi4py==4.1.2" "fluidfft-mpi-with-fftw==0.0.1" "fluidfft-fftwmpi==0.0.1"
-uv lock
-```
-
-Those packages still require a compatible MPI runtime and FFTW development
-libraries. The optional native plugins are:
-
-- `fluidfft-fftw==0.0.1`: sequential
-  `fft2d.with_fftw1d`, `fft2d.with_fftw2d`, `fft3d.with_fftw3d`.
-- `fluidfft-mpi-with-fftw==0.0.1`: MPI
-  `fft2d.mpi_with_fftw1d`, `fft3d.mpi_with_fftw1d`.
-- `fluidfft-fftwmpi==0.0.1`: MPI-enabled FFTW
-  `fft2d.mpi_with_fftwmpi2d`, `fft3d.mpi_with_fftwmpi3d`.
-- `fluidfft-p3dfft==0.0.1`: `fft3d.mpi_with_p3dfft`; requires P3DFFT.
-- FluidFFT also declares PFFT and P3DFFT extras; audit and pin their native
-  stacks for the target cluster.
-
-FluidFFT documents cuFFT historically, but FluidFFT 0.4.5 declares no CUDA extra
-or installed GPU plugin in its package metadata, and its CUDA installation page
-is unfinished. Do not claim GPU acceleration or install an unrelated CUDA wheel
-as a FluidSim backend. Treat GPU work as source-level experimental integration
-requiring separate validation.
-
-See [installation](references/installation.md) for system dependencies, MPI ABI,
-HDF5-MPI, backend discovery, and verification.
-
-## API snapshot
-
-Use direct, versioned imports:
-
-```python
-from fluidsim.solvers.ns2d.solver import Simul
-
-params = Simul.create_default_params()
-params.oper.nx = params.oper.ny = 32
-params.oper.Lx = params.oper.Ly = 2 * 3.141592653589793
-params.oper.coef_dealiasing = 2 / 3
-params.time_stepping.USE_CFL = True
-params.time_stepping.cfl_coef = 0.5
-params.time_stepping.deltat0 = 0.001
-params.time_stepping.deltat_max = 0.01
-params.time_stepping.t_end = 0.1
-params.time_stepping.max_elapsed = "00:05:00"
-params.init_fields.type = "noise"
-params.init_fields.noise.velo_max = 0.01
-params.output.HAS_TO_SAVE = False
-params.output.ONLINE_PLOT_OK = False
-```
-
-Important 0.9 corrections:
-
-- CFL field: `params.time_stepping.cfl_coef`, not `CFL`.
-- Time-correlated forcing:
-  `params.forcing.tcrandom.time_correlation`, not a flat
-  `tcrandom_time_correlation`.
-- NS2D default initial types include `constant`, `noise`, `jet`, `dipole`,
-  `from_file`, `from_simul`, and `in_script`; do not invent a universal list for
-  every solver.
-- Output state files default to `state_phys_t*.nc`; spectra use
-  `spectra1D.h5`/`spectra2D.h5`; scalar means are solver-dependent
-  `spatial_means.txt` or JSON-lines.
-- `params.output.sub_directory` is relative under `FLUIDSIM_PATH`.
-
-`ParamContainer` rejects undeclared attributes. Always generate defaults from the
-selected `Simul` class and inspect them before changing values. See
-[parameters](references/parameters.md).
-
-## Solvers
-
-Primary Cartesian CFD keys and imports:
-
-```python
-from fluidsim.solvers.ns2d.solver import Simul       # ns2d
-from fluidsim.solvers.ns2d.bouss.solver import Simul # ns2d.bouss
-from fluidsim.solvers.ns2d.strat.solver import Simul # ns2d.strat
-from fluidsim.solvers.ns3d.solver import Simul       # ns3d
-from fluidsim.solvers.ns3d.bouss.solver import Simul # ns3d.bouss
-from fluidsim.solvers.ns3d.strat.solver import Simul # ns3d.strat
-```
-
-The 0.9 registry also includes `plate2d`, `sw1l` variants, `waves2d`, 1D models,
-0D models, spherical solvers, and framework adapters. Availability in the
-registry does not make a solver appropriate for a scientific question. Verify
-equations, variables, geometry, boundaries, and diagnostics in the solver
-source. See [solvers](references/solvers.md).
-
-## Forcing and time advancement
-
-Forcing is solver-specific. A current normalized random example is:
-
-```python
-params.forcing.enable = True
-params.forcing.type = "tcrandom"
-params.forcing.forcing_rate = 1.0
-params.forcing.nkmin_forcing = 4
-params.forcing.nkmax_forcing = 5
-params.forcing.tcrandom.time_correlation = "based_on_forcing_rate"
-```
-
-Record the forced variable, normalization definition, wave-number band, random
-seed/state, injection target, and measured injection. FluidSim 0.9 saves state
-parameters for restart; 0.8.6 fixed time-correlated forcing restart behavior.
-
-Available pseudospectral schemes include Euler/RK2 phase-shift variants,
-`RK2_trapezoid`, and `RK4`. A named order does not establish accuracy. Check CFL,
-fast-wave/diffusive limits, `deltat_max`, and time-step refinement. See
-[advanced features](references/advanced_features.md).
-
-## Outputs, loading, and restart
-
-For read-only analysis:
-
-```python
-from fluidsim import load_sim_for_plot
-
-sim = load_sim_for_plot("run-directory", hide_stdout=True)
-sim.output.spatial_means.plot()
-sim.output.spectra.plot1d()
-sim.output.phys_fields.plot(time=1.0)
-```
-
-`load_sim_for_plot` uses a coarse operator and disables saving/online plotting.
-For a state-bearing object:
-
-```python
-from fluidsim import load_state_phys_file
-
-sim = load_state_phys_file("run-directory", t_approx="last")
-```
-
-For a controlled restart, prefer `load_for_restart` or first run
-`fluidsim-restart --only-check`. Do not use `--modify-params` with untrusted text:
-the upstream CLI executes Python code supplied to that option. This skill's
-generator never emits it. Verify solver, grid/domain, state variables, versions,
-forcing state, checksum, target time, output destination, and resource bounds.
-Resolution changes require the dedicated reviewed workflow, not a silent grid
-edit. See [simulation workflow](references/simulation_workflow.md) and
-[output analysis](references/output_analysis.md).
-
-## Scientific acceptance gate
-
-Before interpreting results, require:
-
-- Explicit dimensional units or a complete nondimensionalization map.
-- Correct equations, periodic geometry/boundaries, initial state, forcing, and
-  diagnostic definitions.
-- Resolution and dealiasing evidence: spectra/tails, resolved gradients, and
-  solver-appropriate small-scale criteria.
-- Timestep evidence: CFL history, fastest-wave and dissipative limits, and
-  smaller-step comparison.
-- Conservation and budget checks including forcing, dissipation, transfers, and
-  residuals.
-- Grid/time refinement with uncertainty or sensitivity for reported
-  observables.
-- Comparison to an analytical solution, manufactured solution, benchmark, or
-  independently reproduced result where appropriate.
-- Complete provenance and restart lineage.
-
-Never label a run “DNS,” “converged,” “validated,” “steady,” or “physically
-correct” from parameter values or plots alone.
-
-## Bundled local tools
-
-All tools emit strict JSON, reject URLs/traversal/symlinks, enforce hard bounds,
-use no network or subprocess, and never launch a simulation:
-
-```bash
-python3 scripts/solver_config_validator.py --example
-python3 scripts/solver_config_validator.py --config config.json
-python3 scripts/grid_resource_estimator.py --config config.json
-python3 scripts/simulation_dry_run.py --config config.json --output run.py
-python3 scripts/output_inventory.py --path run-directory
-python3 scripts/budget_summary.py --path run-directory
-python3 scripts/restart_compatibility.py --source state.nc --target-config config.json
-```
-
-The HDF5 tools lazily require `h5py`, inspect bounded metadata/hyperslabs, and
-never follow external links or load full field arrays.
-
-## References
-
-- [Installation and FFT/MPI backends](references/installation.md)
-- [Solver registry and selection](references/solvers.md)
-- [Simulation, pilot, and restart workflow](references/simulation_workflow.md)
-- [Verified parameter surface](references/parameters.md)
-- [Output, plotting, and budget analysis](references/output_analysis.md)
-- [Forcing, operators, MPI, and migrations](references/advanced_features.md)
-
-## Dated upstream basis
-
-Verified 2026-07-23 against
-[PyPI 0.9.0](https://pypi.org/project/fluidsim/),
-[FluidSim 0.9 docs](https://fluidsim.readthedocs.io/en/latest/),
-[release notes](https://fluidsim.readthedocs.io/en/latest/changes.html),
-[official source mirror](https://github.com/fluiddyn/fluidsim),
-[FluidFFT 0.4.5 docs](https://fluidfft.readthedocs.io/en/latest/), and the
-primary FluidSim ([DOI 10.5334/jors.239](https://doi.org/10.5334/jors.239))
-and FluidFFT ([DOI 10.5334/jors.238](https://doi.org/10.5334/jors.238))
-papers. API claims use official docs/source; method/performance claims in the
-references are scoped to the cited primary papers and their benchmark setups.

package/skills/frontend-design/SKILL.md

@@ -1,100 +0,0 @@
----
-name: frontend-design
-description: "Create distinctive, production-grade frontend interfaces with strong aesthetic intent, avoiding generic AI UI templates."
----
-
-# Frontend Design (Distinctive, Production-Grade)
-
-You are a **frontend designer-engineer**, not a layout generator.
-
-Your goal is to create **memorable, high-craft interfaces** that:
-* Avoid generic "AI UI" patterns (cookie-cutter SaaS templates, purple gradients, default cards).
-* Express a clear aesthetic point of view with intentional design systems.
-* Are fully functional, accessible, and production-ready.
-* Translate design intent directly into clean, modern code.
-
----
-
-## 1. Core Design Mandate
-
-Every output must satisfy **all four**:
-
-1. **Intentional Aesthetic Direction**
-   A named, explicit design stance (e.g. *editorial brutalism*, *luxury minimal*, *retro-futurist*, *industrial utilitarian*, *organic/natural*, *playful kinetic*).
-2. **Technical Correctness**
-   Real, working HTML/CSS/JS or framework code (React, Vue, Svelte, Tailwind, Vanilla CSS) — not mockups.
-3. **Visual Memorability**
-   At least one element the user will remember 24 hours later (the *Differentiation Anchor*).
-4. **Cohesive Restraint**
-   No random decoration. Every flourish must serve the aesthetic thesis.
-
-❌ No default layouts or cookie-cutter templates
-❌ No design-by-components without a system
-❌ No generic "safe" palettes (Inter/Roboto, purple-on-white)
-✅ Strong opinions, well executed with precision
-
----
-
-## 2. Design Feasibility & Impact Index (DFII)
-
-Before building, evaluate the design direction:
-
-| Dimension | Question |
-| :--- | :--- |
-| **Aesthetic Impact (1-5)** | How visually distinctive and memorable is this direction? |
-| **Context Fit (1-5)** | Does this aesthetic suit the product, audience, and purpose? |
-| **Implementation Feasibility (1-5)** | Can this be built cleanly with available tech? |
-| **Performance Safety (1-5)** | Will it remain fast and accessible? |
-| **Consistency Risk (1-5)** | Can this be maintained across screens/components? |
-
-**Formula**: `DFII = (Impact + Fit + Feasibility + Performance) - Consistency Risk` (Target: ≥ 8)
-
----
-
-## 3. Aesthetic Execution Rules
-
-### Typography
-* Avoid system defaults and generic fonts (Inter, Roboto, Arial).
-* Choose:
-  * 1 expressive display font (e.g., *Outfit, Syne, Space Grotesk, Playfair Display, Cinzel, Clash Display*).
-  * 1 restrained, high-legibility body font (e.g., *Plus Jakarta Sans, Geist, Satoshi, General Sans*).
-* Use typography structurally (scale, rhythm, contrast, line height).
-
-### Color & Theme
-* Commit to a **dominant color story** using CSS variables.
-* Structure: One dominant background tone, one high-contrast accent, and a refined neutral system.
-* Avoid evenly-balanced palettes where every color competes for attention.
-
-### Spatial Composition & Layout
-* Break the grid intentionally when appropriate: asymmetric placements, overlapping planes, deep negative space, or controlled typographic density.
-* White space is an active design element, not empty absence.
-
-### Motion & Micro-interactions
-* Motion must be purposeful, sparse, and high-impact (e.g., smooth entrance sequence, tactile button clicks, magnetic hover states).
-* Avoid excessive micro-motion spam that distracts from user actions.
-
-### Texture & Depth
-* Use subtle grain/noise overlays, gradient meshes, glassmorphic translucency, custom border treatments, or layered cards with purpose.
-
----
-
-## 4. Anti-Patterns (Immediate Failure)
-
-❌ Inter / Roboto / Arial default fonts without styling
-❌ Generic purple-on-white SaaS gradient backgrounds
-❌ Default unstyled Tailwind/Bootstrap card grids
-❌ Symmetrical, predictable cookie-cutter sections
-❌ Decorative clutter with no functional or brand purpose
-❌ Creating detached temporary or scratch preview files (e.g. `tmp_*`, `draft.html`, `preview.tsx`) in root instead of in-place structured components
-
----
-
-## 5. Output Checklist
-
-When presenting or building UI:
-- [ ] Explicit aesthetic direction named
-- [ ] DFII score ≥ 8
-- [ ] 1 distinctive differentiation anchor
-- [ ] Polished typography & color variables
-- [ ] Accessible (WCAG contrast, keyboard navigation, semantic HTML)
-- [ ] Production-ready code matches the design ambition