bio-genome-engineering-base-editing-design
Designs cytosine (CBE, C-to-T) and adenine (ABE, A-to-G) base-editor guides by positioning the target base at the activity-peak of the editing window (protospacer positions ~5-7, PAM-distal numbering), minimizing bystander edits for product purity, reading dinucleotide context (APOBEC1 TC favored / GC disfavored), and selecting the editor variant (BE4max, ABEmax, ABE8e, YE1/SECURE, TadCBE, CGBE, SpG/SpRY-BE). Covers knockout by premature stop (CRISPR-STOP/iSTOP) and splice-site disruption, the three off-target classes (Cas-dependent, Cas-independent DNA, RNA), outcome prediction (BE-Hive/DeepBE), and the base-vs-prime-vs-HDR decision. Use when installing a transition mutation without a double-strand break, knocking out a gene without indels, or choosing CBE vs ABE. Generic guide scoring, prime editing, and HDR donors are separate skills.
What this skill does
## Version Compatibility Reference examples tested with: BioPython 1.83+. Before using code patterns, verify installed versions match. If versions differ: - Python: `pip show <package>` then `help(module.function)` to check signatures If code throws ImportError, AttributeError, or TypeError, introspect the installed package and adapt the example to match the actual API rather than retrying. BE-Hive is NOT a pip package -- it is a web tool (crisprbehive.design) plus clone-only repos (`maxwshen/be_predict_efficiency`, `be_predict_bystander`) pinning old dependencies (scikit-learn 0.20.3, BioPython 1.73). Use the web tool for a quick answer, the clone for batch use. Editing windows and outcome predictions are **editor-variant- and cell-type- specific** and are activity gradients, not hard boxes -- record which editor model was used. # Base Editing Design **"Install a transition mutation without a double-strand break"** -> Write the edit as a base-pair change to pick the editor family, find a PAM that lands the target base at the window peak while keeping bystanders out, read sequence context, choose the editor variant, and report the predicted genotype spectrum -- not a lone efficiency number. - Python: window/bystander scan with `Bio.Seq` + `re`; per-base context reading - Web/clone: BE-Hive / DeepBE for the per-base efficiency + bystander genotype spectrum - Web: BE-Designer (guide enumeration), BE-Analyzer / CRISPResso2 (validate from NGS) ## The Single Most Important Modern Insight -- the job is product PURITY, not editing efficiency A base editor produces a *distribution of genotypes at one site*, not a binary cut. "80% editing" can mean 80% of alleles carry the clean intended edit, or 80% carry *some* edit -- a soup where a bystander C/A two positions away is also converted half the time, so the exact desired genotype is only 30% of alleles. Both report as "80% efficient." The number that answers the biology is **precise editing: the fraction of alleles with the target edit AND no bystander edit.** Design is dominated by three coupled levers on one ~5-nt window: **(1) where the target base sits** (set by PAM/guide; drives efficiency), **(2) what else sits in the window** (bystander C's/A's; drives purity), **(3) the local dinucleotide context** of each base (drives which actually edit). The corollary trap: a *more active* editor (ABE8e over ABE7.10) raises headline efficiency while *lowering* purity (higher processivity sweeps more bystanders). Rank guides by the predicted **outcome spectrum**, never by efficiency alone. The second field-defining insight: **base editors have THREE off-target classes, and the two that distinguish CBE from ABE are invisible to every Cas-off-target tool** (below). Most people only think of class 1 (guide-directed); the classes that matter for safety are Cas-independent and guide-invisible. ## Mechanism & the Position-Numbering Convention (get this right) Both families are a **ssDNA deaminase fused to a Cas9 NICKASE (nCas9, D10A)**, guided by an ordinary sgRNA -- **no double-strand break**. When Cas9 binds, the non-target (PAM-containing) strand is displaced as ssDNA in the R-loop; the deaminase edits bases on that displaced strand within the window. **Canonical numbering (Komor 2016): position 1 = PAM-DISTAL (5' end of the spacer), position 20 = PAM-PROXIMAL (next to the PAM at 21-23). The editing window is ~positions 4-8, peak ~5-7.** (This is the opposite of what older tutorials sometimes say.) - **CBE:** cytidine deaminase (rAPOBEC1) C->U, + **UGI** (blocks uracil excision -- the main CBE purity determinant), nCas9 nicks the unedited strand -> resolves to C->T (G->A other strand). - **ABE:** lab-evolved TadA* deaminase A->inosine (read as G) -> resolves to A->G (T->C other strand). No UGI needed (inosine is not efficiently excised) -- a key reason early ABE was intrinsically cleaner than CBE. ## The Window Is a Gradient, Editor-Specific -- not a box Activity inside the "box" is a steep gradient: a target at position 6 edits far better than one at 8; a bystander at 8 edits at a fraction of one at 5. The design move is "how close to the 5-6-7 peak is my target, and how far toward the cold edges can I push the bystanders?" The width is a property of the **editor variant**: ABE8e's high processivity widens it to ~3-11, so a guide that was bystander-clean with ABE7.10 becomes dirty when "upgraded" to ABE8e without re-checking. Carrying a window assumption across an editor switch is the most common silent failure. ## Editor Variant Selection | Editor | Class | When | |--------|-------|------| | **BE4max / AncBE4max** | CBE | default modern CBE (Koblan 2018) | | **ABEmax** | ABE | strong default ABE (Koblan 2018) | | **ABE8e** | ABE | maximum activity (hard targets, screens) -- but WIDER window, MORE bystanders/off-target, LOSES context preference (Richter 2020; Lapinaite 2020) | | YE1 / SECURE-BE3 | CBE | narrowed window / low RNA off-target (Grunewald 2019) | | **TadCBE / TadDE** | CBE / dual | lowest Cas-independent DNA+RNA off-target CBE (Neugebauer 2023) | | CGBE1 | C->G | the only transversion a base editor does well (Kurt 2021) | | A&C-BEmax / SPACE | dual | simultaneous C->T and A->G (niche; adds bystander surface) (Grunewald 2020; Sakata 2020) | | SpG / SpRY base editors | any | when no canonical NGG positions the base (Walton 2020) -- more class-1 off-target | Default BE4max/ABEmax; reach for ABE8e for activity at a purity cost; a SECURE/TadCBE variant when off-target matters; a PAM-flexible editor when no NGG positions the base. The *deaminase* choice (rAPOBEC1 vs APOBEC3A vs eA3A vs evolved TadA) sets window width, context, and off-target far more than the BE3-vs-BE4 generation number. ## The Three Off-Target Classes -- ask "which of the three?" first | Class | Mechanism | Detected by | Mitigation | |-------|-----------|-------------|------------| | **1. Cas-dependent DNA** | guide mismatch-tolerance, like ordinary Cas9 | GUIDE-/CIRCLE-seq; in-silico (-> off-target-prediction) | high-fidelity Cas; guide selection | | **2. Cas-INDEPENDENT DNA** | deaminase edits transiently-exposed genomic ssDNA, **no guide** | GOTI (Zuo 2019); WGS (Jin 2019) | choose a low-activity-deaminase variant (YE1, **TadCBE**) | | **3. RNA** | deaminase edits cellular mRNA, **no guide**, transient | RNA-seq (Grunewald/Rees/Zhou 2019) | **SECURE** variants (rAPOBEC1 R33A; ABE F148A); TadCBE | Classes 2-3 have no protospacer, so they are **invisible to every guide-based predictor** -- the guide cannot be designed to avoid them; only a cleaner editor can. **CBE has historically been the dirtier family on classes 2-3** (Zuo/Jin: CBE >20x background Cas-independent SNVs, mostly C>T in transcribed DNA; early ABE did not) -- a genuine input to the CBE-vs-ABE choice. But this is *variant*-specific, not family-destiny: ABE8e raised it back up; TadCBE pulled CBE's down. Class-3 RNA edits are transient (RNA turns over) -- a real dose/exposure-dependent liability for chronic/AAV/therapeutic use, often tolerable for a transient cell-line transfection. ## Knockout by Base Editing (no DSB) Base editing knocks out a gene without a double-strand break -- no indel lottery, no large deletions/translocations, no p53 response, works in **non-dividing cells**, and safe for **multiplex** (no translocations between simultaneous cut sites). Two routes: - **Premature stop (CRISPR-STOP/iSTOP):** a CBE converts **CAA->TAA, CAG->TAG, CGA->TGA** (sense) or **TGG->stop** via the antisense strand. Only these four codons are reachable; target an **early** stop (before functional domains, NMD-competent). iSTOP precomputed sgRNAs cover 97-99% of genes (Billon 2017; Kuscu 2017). - **Splice-site disruption:** edit the invariant splice-donor **GT** or acceptor **AG** -> mis- splicing / exon skipping (Kluesner 2021). Often the more robust KO (every gene has many junctions; only ~half have a well-placed early stop codon). The quiet failure mode: a ba
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.