CATEular/skill

Analog IC Notes

Transform a real paper into structured Analog IC notes that can be re-read, compared, and traced. This skill follows the circuit deep-reading method from the DC-DC Buck Reader, selecting analysis dimensions based on the actual paper type.

Input and Paths

Use a user-supplied PDF, paper link, or an already connected literature tool. First confirm the paper title, authors, year, journal/conference, and DOI. Advisor information should not be included in the author list.

When only an abstract is available, organize only the information within its scope. If the full text or figures are missing, clearly state this; do not speculate on circuit details.

Copy config.example.json to your own config.local.json, filling in the input, notes, and images directories. Alternatively, use the environment variable ANALOG_IC_NOTES_CONFIG to point to another configuration.

{
  "paths": {
    "papers": "./papers",
    "notes": "./notes",
    "images": "./notes/assets"
  },
  "language": "en"
}

Relative paths are resolved relative to the configuration file's directory. Both ~ and absolute paths are supported. Personal configurations must not be included in shared skill packages.

Resolve the actual paths first. If no configuration is provided, use papers/, notes/, and notes/assets/ under the current working directory.

python scripts/paths.py --config config.local.json

Explicit paths specified by the user in the current conversation take precedence. Do not modify the original paper, and do not overwrite existing notes. Before modifying an existing record, review its contents and preserve the user's analysis.

Reading and Organization

• First verify the source, then build the body around the research problem, architecture, key circuits, measurement evidence, and limitations. The template can be trimmed per paper; a fixed number of sections is not mandatory.
• Use the general paper template to store bibliographic information, metrics tables, key figures, personal understanding, and unresolved questions.
• Distinguish between "original paper text", "your own derivation", "simulation results", and "measured results". Reference specific page numbers, figure numbers, table numbers, or equation numbers.
• Quote short essential original passages and include your own explanation. Do not generate fabrication-style English citations when the original sentence is missing, and do not extensively reproduce the main text.
• Record test conditions and definitions for metrics. Write "not reported" for missing items. When comparing across papers, first verify supply voltage, bandwidth, load, die area scope, and FoM definitions.
• Keep each paper independent. Do not actively link to user private PDKs, commercial chips, internal projects, or personal directories. Related literature must have a real source.

Select Analysis Dimensions by Type

Literature Type	Key Records
PMIC / Buck / Charge Pump / LDO	Topology, control, supply and load, switches and drivers, efficiency, ripple, transient response, and reliability
Amplifier / Comparator / Reference	Input/output range, gain and bandwidth, noise and offset, power consumption, stability and PVT conditions
ADC / DAC	Architecture, sampling rate, resolution, linearity, dynamic test conditions, power, and area
PLL / Clock	Architecture, frequency range, phase noise, jitter definition, locking behavior, and power consumption

Only apply dimensions relevant to the paper. Do not force a Buck efficiency table and load-step metrics onto other circuit types.

For Buck papers, you may further refer to the Buck deep-reading template and the PMIC terms reference. Formulas in the reference materials are only analysis clues; the original paper always defines the specific meaning and applicable conditions.

Figures and Formulas

First read the figure extraction instructions, then use scripts/extract_figures.py. Dependencies are listed in requirements.txt.

python scripts/extract_figures.py paper.pdf --config config.local.json --paper-id paper-slug

Prefer extracting image regions based on actual PDF page rendering. Preserve original polarity, color, and scaling; do not invert colors just because the photograph background is dark.

For vector circuit diagrams, use page cropping. Record the original page and figure number. First check that the figure, labels, and caption are complete, then write into the notes.

Place images in a dedicated subdirectory for that paper. Use relative Markdown image links. Use $...$ and $$...$$ for formulas, clearly distinguishing the paper's formulas from your own derivations.

Output Checklist

• Title, authors, year, and DOI match the source. Advisor information is stored separately.
• Every key value and assertion has a locatable source. No fabricated innovations, original quotations, or measurement results.
• Images open correctly, orientation and colors are correct. Formulas and tables are readable.
• No personal absolute paths, account information, private processes, or internal project identifiers.
• The original paper remains unchanged. Related citations are traceable. The body text preserves the user-specified language.

Public release is only done upon explicit user authorization. Exclude config.local.json, local PDFs, and other personal configurations when sharing.