Claude Skills by stanfish06

All-in-one FASTQ QC and adapter trimming. Auto-detects Illumina adapters, filters low-quality reads, corrects paired-end overlaps, emits HTML+JSON QC in one pass. 3-10x faster than Trim Galore/Trimmomatic. First step before STAR, BWA-MEM2, or Salmon.

Expert-thinking profile for Fermentation Scientist (wet-lab / SmF & SSF R&D / starter cultures / kinetic & metabolic modeling): Reasons from Monod–Luedeking–Piret kinetics, overflow μcrit, OTR/RQ/RAMOS analytics, DoE media optimization, and 13C-MFA/COBRApy flux bounds while treating stuck-ferment ethanol×T synergy, SSF heat/moisture gradients, and OD-as-biomass red herrings as first-class failure modes.

Creates and maintains Figma Code Connect template files that map Figma components to code snippets. Use when the user mentions Code Connect, Figma component mapping, design-to-code translation, or asks to create/update .figma.ts or .figma.js files.

Load this skill before every `create_new_file` tool call. Trigger whenever the user wants a new blank Figma file — a new design, FigJam, or Slides file — or when you need a fresh file before calling `use_figma`. Usage — /figma-create-new-file [editorType] [fileName] (e.g. /figma-create-new-file figjam My Whiteboard, /figma-create-new-file slides Q3 Review)

Use this skill when implementing a Figma design as code (design → code) — the read-FROM-Figma direction. Triggers: 'implement this Figma design', 'build this screen from Figma', 'turn this Figma into code', 'code this up from Figma', 'design to code', or a figma.com design URL provided alongside a codebase. Encodes the workflow for reading a node out of Figma with get_design_context and adapting its reference output to the target project — reusing existing components, tokens, and conventions,...

Use this skill alongside figma-use when the task involves translating an application page, view, or multi-section layout into Figma. Triggers: 'write to Figma', 'create in Figma from code', 'push page to Figma', 'take this app/page and build it in Figma', 'create a screen', 'build a landing page in Figma', 'update the Figma screen to match code', 'convert this modal/dialog/drawer/panel to Figma'. This is the preferred workflow skill whenever the user wants to build or update a full page, moda...

Load this skill BEFORE every `generate_diagram` tool call. Trigger whenever the user asks to create, generate, draw, render, sketch, or build a diagram — flowchart, architecture diagram, sequence diagram, ERD or entity-relationship diagram, state diagram or state machine, gantt chart, or timeline. Also trigger when the user mentions Mermaid syntax or wants a system architecture, decision tree, dependency graph, API call flow, auth handshake, schema, or pipeline visualized in FigJam. Routes to...

Build or update a professional-grade design system in Figma from a codebase. Use when the user wants to create variables/tokens, build component libraries, create individual components with proper variant sets and variable bindings, set up theming (light/dark modes), document foundations, or reconcile gaps between code and Figma. Also use when the user asks to create or generate any component in Figma — even a single one — since components require proper variable foundations, variant states, ...

Translates Figma motion and animations into production-ready application code. Use when implementing animation/motion from a Figma design — user mentions "implement this motion", "add animation from Figma", "animate this component", provides a Figma URL whose node is animated, or when `get_design_context` returns motion data or instructs you to call `get_motion_context`.

SwiftUI ↔ Figma translation. Use whenever the user mentions Swift, SwiftUI, iOS, iPhone, or iPad — in EITHER direction — translating a Figma design into SwiftUI (design → code), or pushing SwiftUI views / screens / tokens back into a Figma file (code → design). Triggers on phrases like 'implement this Figma design in SwiftUI', 'build this screen in Swift', 'push this SwiftUI view to Figma', 'mirror my Swift code in a Figma file', or whenever a Figma URL appears alongside `.swift` files / an `...

This skill helps agents use Figma's use_figma MCP tool in the FigJam context. Can be used alongside figma-use which has foundational context for using the use_figma tool.

Motion / animation context for the `use_figma` MCP tool — animating Figma nodes via manual keyframes, animation styles, easing, and timeline duration. Load alongside figma-use whenever a task involves adding, editing, or inspecting animation on a node.

This skill helps agents use Figma's use_figma MCP tool in the Slides context. Can be used alongside figma-use which has foundational context for using the use_figma tool.

Load this skill before every `use_figma` tool call. Trigger whenever the user wants to perform a write action or a unique read action that requires JavaScript execution in the Figma file context — e.g. create/edit/delete nodes, set up variables or tokens, build components and variants, modify auto-layout or fills, bind variables to properties, or inspect file structure programmatically.

Advises on the design of the three core figures in a technical paper: the Motivated Example (Figure 1), the Solution Overview (Methodology), and the Experimental Results figures. Recommends the right design paradigm, layout, labelling, and tool for each figure type, then runs a quality-control audit. Use when the user asks to 'design a figure', 'draw Figure 1', 'plot experiment results', 'choose the right chart type', 'which figure tool to use', or 'figure looks unprofessional'.

Helps users discover and install agent skills when they ask questions like \"how do I do X\", \"find a skill for X\", \"is there a skill that can...\", or express interest in extending capabilities. Use when the user is looking for functionality that might exist as an installable skill.

Parse-only static analysis that pairs source files with the tests referencing them and emits JSON listing untested files ordered by API surface, each with a suggested_test_path. Roslyn engine for C#/.NET (namespace-aware), tree-sitter engine for polyglot repos (Python, TS/JS, Go, Java, Rust, Ruby). USE FOR: where to write tests next, which files have no tests, find untested code, build a source-to-test pairing map, prioritized test-gap worklist. DO NOT USE FOR: line/branch coverage or CRAP ri...

Use when Codex is already in the finding-discovery phase of a security scan or the user explicitly asks to discover candidate security findings in a repository or code change. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

Expert-thinking profile for Finite Element Analyst (computational / simulation / verification & validation): Reasons from discretization error, element technology, and constraint physics; runs mesh convergence and Richardson studies, Nastran/Abaqus/ANSYS workflows, RBE2/RBE3 and contact discipline, and ASME V&V 10 verification-before- validation reporting on governing QoIs.

Expert-thinking profile for Fire Protection Engineer (design / engineering / performance-based fire modeling): Reasons from NFPA 13 Hazen-Williams hydraulics (K-factor, remote area, hose stream) and NFPA 101 egress (occupant load, travel distance, capacity factors) through NFPA 92 smoke containment/management, ASET/RSET PBD, and FDS/CFAST/CONTAM/PyroSim modeling while treating breached compartmentation, C-factor/fitting...

Autonomous multi-page extraction into structured JSON. Use when the user wants website data matching a schema — pricing tiers, product listings — beyond a single-page scrape.

Bulk-extract many pages from one site or section. Use for "crawl", "everything under /docs", or content spanning linked pages.

Search issues, merged pull requests, READMEs, and documentation. Use when the question is how a library or API behaves, what an error means, or whether a bug was fixed; prefer this over a general web page.

Save a site or section as local files (markdown, screenshots). Use for "download the site", offline docs, or a local copy for reference.

Drive a live browser on a scraped page: click, fill forms, log in, paginate, infinite-scroll. Use when content requires interaction or a scrape failed or returned incomplete content.

Discover and list a site's URLs, with search filtering. Use for "map the site" or "find the URL for" requests — when the user knows the site but not the exact page, or wants site structure.

Alert by webhook/email on web changes — use for "monitor/watch/track/alert me when": recurring checks on known URLs (prefer over repeated one-off scrapes) or web-wide watches for new results (queries + goal).

Convert a local file (PDF, DOCX, XLSX, HTML, …) to markdown, or answer questions about its content. Use whenever the input is a file path, not a URL.

Find the papers that answer a research query in Firecrawl's research paper index — a corpus of paper abstracts whose largest share is biomedical and life-science literature (PubMed, bioRxiv, medRxiv), alongside arXiv preprints in CS, physics, and math — using semantic search, semantic and structural expansion, and in-body verification. Use this skill for literature-finding and paper-retrieval tasks of any kind, including clinical, biomedical, drug, gene, disease, and other life-science questi...

Extract a URL's content as clean markdown, including JS-rendered pages. Use whenever the user provides a URL and wants its content; prefer over WebFetch.

Web search with full page content. Use when no URL is known: finding sources, articles, or news. For papers use firecrawl-research-index; for library, API, error, or bug questions use firecrawl-developer-index.

Any live-web task via the Firecrawl CLI — including ordinary web research: searching the web, reading or extracting pages, gathering sources, discovering site URLs, bulk extraction, downloading a site, change alerts, or pages needing clicks/login — web only; local files route to firecrawl-parse. For papers use firecrawl-research-index; for library, API, error, or bug questions use firecrawl-developer-index.

固件 / IoT 渗透链。从拿到一坨 .bin / .img 开始，闭环走完逆向 → 提取 → 模拟 → 利用。 方法论遵循 OWASP FSTM 九阶段；工具链以 binwalk v3、unblob、EMBA、Firmadyne、AFL++ 为主。 适用场景：路由器/摄像头/智能家居固件审计、固件升级包逆向、IoT CVE 复现、嵌入式 0day 挖掘。 触发关键词：固件、firmware、IoT、binwalk、unblob、UART、JTAG、squashfs、UBI、JFFS2、Firmadyne、QEMU 全系统仿真、EMBA、固件渗透、路由器固件、嵌入式漏洞利用、bootloader、NVRAM、FAT、firmware analysis toolkit。

Expert-thinking profile for Fisheries Scientist (stock assessment / population dynamics / harvest control rules / MSE / reference points (F_MSY, B_lim)): Reasons from recruitment, growth, and natural and fishing mortality through state-space assessment models (SS3, SAM, JABBA), CPUE/GLM standardization, and reference points like F_MSY and B_lim under ICES and Magnuson-Stevens frameworks, while treating hyperstability, retrospective bias (Mohn's rho), unaccounted...

Use when the user explicitly asks to fix and verify a validated or plausible security finding. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.

Expert-thinking profile for Flavor & Fragrance Chemist (aroma chemistry / GC-MS-O analysis / sensory evaluation / formulation / regulatory (IFRA, FEMA GRAS)): Reasons from odor activity values, threshold perception, matrix release, and degradation kinetics through GC-MS with retention indices, GC-O/AEDA, chiral GC authentication, ISO 8586 trained sensory panels, and IFRA/FEMA regulatory limits while treating aldehyde oxidation, citral cyclization, top-note fade, and...

Manage a fleet of Grafana Alloy collectors with Fleet Management — author Alloy pipelines once, target them via attribute matchers (`env="production"`, regex `region=~"us-.*"`), push remotely via OpAMP without restarting collectors. Covers pipeline create / update / matcher RPCs, collector attribute API, `remotecfg` bootstrap block (standalone + Helm), pre-deploy `alloy fmt` validation, the local Alloy UI at port 12345 for component health, and post-deploy `REMOTE_CONFIG_STATUS_APPLIED` verif...

Parse FCS (Flow Cytometry Standard) files v2.0-3.1. Extract events as NumPy arrays, read metadata/channels, convert to CSV/DataFrame, for flow cytometry data preprocessing.

Expert-thinking profile for Fluid Dynamicist (computational CFD / theoretical scaling / experimental validation): Reasons from Navier–Stokes and dimensionless scaling through RANS/LES/DNS selection, mesh/y+ strategy, OpenFOAM/Fluent workflows, and MMS + ASME V&V 20 / PIV validation.

Expert-thinking profile for Fluid Mechanics Engineer (plant hydraulics / piping & pump systems / CFD verification): Reasons from Navier–Stokes reductions through Darcy–Weisbach/Crane TP-410 pipe networks, pump system curves, NPSH/affinity laws, HI turbomachinery selection, and ASME V&V 20 CFD validation when simulation supports design.

Framework for computational fluid dynamics simulations using Python. Use when running fluid dynamics simulations including Navier-Stokes equations (2D/3D), shallow water equations, stratified flows, or when analyzing turbulence, vortex dynamics, or geophysical flows. Provides pseudospectral methods with FFT, HPC support, and comprehensive output analysis.

Expert-thinking profile for Food Chemist (analytical / regulatory food chemistry): Reasons from food matrix effects, aw and lipid oxidation, AOAC-validated HPLC/GC- MS/LC-MS/MS, FoodData Central/FNDDS, and trained sensory panels while treating matrix suppression, accelerated-shelf-life misuse, and untrained-taster data as first-class failure modes.

Expert-thinking profile for Food Engineer (process engineering / thermal & nonthermal processing / HACCP validation / pilot-to-plant scale-up): Reasons from water activity, thermal microbiology, transport-coupled reaction, and rheology through heat- penetration studies, F0/D/z lethality integration, HACCP with prerequisite programs, and CFR Title 21 LACF/acidified-food rules while treating cold-point under-processing, aw and pH drift, post-process...

Expert-thinking profile for Food Microbiologist (QC lab / food safety / spoilage ecology / HACCP / method validation (ISO 16140, BAM)): Reasons from food as a hurdle- governed matrix of water activity, pH, and redox through BAM/ISO reference methods, c/n/m/M sampling plans, PMA-v-qPCR, and ComBase kinetics while treating VBNC and injured cells, post-process contamination, matrix inhibition, and unconfirmed PCR hits as first-class failure modes.

Expert-thinking profile for Food Scientist (product development / process engineering / sensory / food-safety systems): Reasons from a_w and GAB isotherms, Maillard/acrylamide kinetics, HLB emulsions, TPA/rheology, ISO sensory methods, and HACCP/FSMA preventive controls while treating aw–moisture conflation, HLB-only emulsion fixes, and Arrhenius misuse as first-class failure modes.

Expert-thinking profile for Forensic Chemist (accredited crime lab / seized-drug & trace analysis / GC-MS & LC-MS/MS / courtroom reporting (SWGDRUG, ISO/IEC 17025, Daubert/Frye)): Reasons from chain of custody, validated methods, measurement uncertainty, and class-versus-individual characteristics through GC-MS, LC-MS/MS, FTIR, and SWGDRUG-aligned identification under ISO/IEC 17025, while treating carryover contamination, secondary transfer, isomer co-elution, and upgrading equivocal results...

Expert-thinking profile for Forestry Scientist (field / inventory / silviculture / remote sensing / forest carbon): Reasons from silvicultural systems, site index, DGH and DBH increment, and FIA cruise design through FVS/ORGANON calibration, LiDAR area- based inventory with support matching, and IPCC carbon pools while treating site-index misassignment, plot edge effects, and change-of-spatial-support bias as first-class failure...

Expert-thinking profile for Formal Methods Researcher (theoretical / verification / interactive proof & model checking): Reasons from operational semantics and temporal logics through SPIN/TLA+/PRISM, Coq/Lean/Isabelle, Z3/CVC5, refinement and separation logic, vacuity and false-positive diagnosis, and Dafny/F* versus property-based testing boundaries.

Expert-thinking profile for Foundation Engineer (geotechnical design / deep & shallow foundations / soil-structure interaction / LRFD (AASHTO, Eurocode 7) / site investigation): Reasons from effective stress, ULS versus SLS limit states, and construction-altered soil behavior through CPT/SPT logging, triaxial and oedometer testing, LRFD φ-factor checks, and LPILE/PLAXIS analysis while treating liquefaction- driven lateral spread, negative skin friction downdrag, differential settlement, and...