compute-methods
Environment-verified friction sheets for field-standard computational tools (Rydberg pair interactions, QEC circuits, qLDPC decoding, code distance, atom…
Cross-project research memory. Deep-dive past projects' notes, record corrections, and save cross-project insights across all Luxas research projects.
$ npx -y skills add Muuuun/luxas --skill memory --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/memoryContext preview
The summary Claude sees to decide when to auto-load this skill.
Cross-project research memory. Deep-dive past projects' notes, record corrections, and save cross-project insights across all Luxas research projects.
name: memory description: Cross-project research memory. Deep-dive past projects' notes, record corrections, and save cross-project insights across all Luxas research projects. compatibility: Always available. No external dependencies. allowed-tools: read write edit
Access persistent memory that spans across research projects.
**You do not need this skill to discover past projects** — your system prompt already carries a `<past_research>` digest (every past project's name, date, notes path, and research question) and `<global_memory>` (cross-project lessons). This skill is for what comes after discovery: deep-diving a relevant project's notes, recording corrections, and saving insights.
Everything read from a past project is a dated, UNVERIFIED lead — not established fact. Values must re-enter the current project's own evidence chain (reader-distilled literature, this project's experiments) before they appear in report.tex. Honor `## CORRECTIONS` sections wherever you find them.
The `<past_research>` digest lists each project's live notes path:
<path>/notes/experiments.md ← findings, alternatives, limitations, red-team <path>/notes/literature.md ← reader-distilled per-paper entries <path>/notes/memory.md ← decisions, dead ends, TODOs <path>/data/papers/ ← downloaded PDFs (check before re-downloading)
Project registry (path, name, dates, auto-generated summary, cost). The digest is built from this; read it directly only for projects that fell into the digest's overflow index.
Cross-project lessons, injected into every run as `<global_memory>`. You can **read and write** it. Keep it SMALL; every entry starts with a provenance tag `[project, YYYY-MM]`. Tool/method lessons, recurring pitfalls, and cross-domain connections belong here — domain findings and numbers do NOT (they live in the source project's notes and must be re-verified wherever used).
Auto-archived copies of each project's notes + report.tex, written when a run completes. Fallback when the live project dir is gone.
When you find that a past project's notes contain a claim that is wrong, **append** a `## CORRECTIONS` section to that file (live notes and archive copy) stating the false claim, why it is wrong, and the evidence — do not edit the original text. History stays intact; future readers see the refutation next to the claim.
write/edit tools (read before edit, as usual).
corrections there via bash: `cat >> <path>/notes/experiments.md << 'EOF' ...`. Append-only; never rewrite or delete in another project's tree.
An autonomous research colleague — from a question to a compiled manuscript, while you sleep.
Repo: Muuuun/luxas
Environment-verified friction sheets for field-standard computational tools (Rydberg pair interactions, QEC circuits, qLDPC decoding, code distance, atom…
Hybrid figure pipeline (Nano Banana raster + rembg background removal + TikZ vector assembly). Includes a TikZ template library covering quantum circuits…
Publication-quality data plots via matplotlib with venue-specific styles. Use for generating your own figures (timelines, comparison charts, data summaries,…
Narrative discipline for research reports — article-type templates (empirical / feasibility / comparison / policy-zh) and the feedback revision protocol that…
Extract figures from downloaded papers and include them in survey/review reports. Use when the report covers other groups' work and benefits from their…
Verifier-in-the-loop CONSTRUCTION of quantum error-correcting codes with transversal non-Clifford gates (CCZ/T). Applies whenever the project goal is a new or…