tooluniverse-protein-therapeutic-design
AI-guided de novo protein design — RFdiffusion backbone generation, ProteinMPNN sequence design, structure validation (pLDDT, pTM, MPNN scores). Use for designing therapeutic protein binders, novel scaffolds, enzyme variants, and miniprotein/protein-interface design before experimental validation.
What this skill does
# Therapeutic Protein Designer AI-guided de novo protein design using RFdiffusion backbone generation, ProteinMPNN sequence optimization, and structure validation for therapeutic protein development. **KEY PRINCIPLES**: 1. **Structure-first** - Generate backbone geometry before sequence 2. **Target-guided** - Design binders with target structure in mind 3. **Iterative validation** - Predict structure to validate designs 4. **Developability-aware** - Consider aggregation, immunogenicity, expression 5. **Evidence-graded** - Grade designs by confidence metrics 6. **Actionable output** - Provide sequences ready for experimental testing 7. **English-first queries** - Always use English terms in tool calls Therapeutic protein design starts with the target interaction. What binding surface do you need to cover? A small pocket = nanobody or peptide. A large flat surface = designed protein. Stability, immunogenicity, and manufacturability constrain the design space. ## LOOK UP, DON'T GUESS When uncertain about any scientific fact, SEARCH databases first rather than reasoning from memory. A database-verified answer is always more reliable than a guess. --- ## COMPUTE, DON'T DESCRIBE When analysis requires computation (statistics, data processing, scoring, enrichment), write and run Python code via Bash. Don't describe what you would do — execute it and report actual results. Use ToolUniverse tools to retrieve data, then Python (pandas, scipy, statsmodels, matplotlib) to analyze it. ## When to Use Apply when user asks to: - Design a protein binder, therapeutic protein, or scaffold - Optimize a protein sequence for function - Design a de novo enzyme - Generate protein variants for target binding --- ## Workflow Overview ``` Phase 1: Target Characterization Get structure (PDB, EMDB cryo-EM, AlphaFold), identify binding epitope Phase 2: Backbone Generation (RFdiffusion) Define constraints, generate >= 5 backbones, filter by geometry Phase 3: Sequence Design (ProteinMPNN) Design >= 8 sequences per backbone, sample with temperature control Phase 4: Structure Validation (ESMFold/AlphaFold2) Predict structure, compare to backbone, assess pLDDT/pTM Phase 5: Developability Assessment Aggregation, pI, expression prediction Phase 6: Report Synthesis Ranked candidates, FASTA, experimental recommendations ``` --- ## Critical Requirements ### Report-First Approach (MANDATORY) 1. Create `[TARGET]_protein_design_report.md` first with section headers 2. Progressively update as designs are generated 3. Output `[TARGET]_designed_sequences.fasta` and `[TARGET]_top_candidates.csv` ### Design Documentation (MANDATORY) Every design MUST include: Sequence, Length, Target, Method, and Quality Metrics (pLDDT, pTM, MPNN score, binding prediction). --- ## NVIDIA NIM Tools | Tool | Purpose | Key Parameter | |------|---------|---------------| | `NvidiaNIM_rfdiffusion` *(requires NVIDIA_API_KEY env var; free key at build.nvidia.com)* | Backbone generation | `diffusion_steps` (NOT `num_steps`) | | `NvidiaNIM_proteinmpnn` *(requires NVIDIA_API_KEY env var; free key at build.nvidia.com)* | Sequence design | `pdb_string` (NOT `pdb`) | | `ESMFold_predict_structure` | Fast validation | `sequence` (NOT `seq`) | | `NvidiaNIM_alphafold2` *(requires NVIDIA_API_KEY env var; free key at build.nvidia.com)* | High-accuracy structure inference from sequence | `sequence`, `algorithm` | | `NvidiaNIM_esm2_650m` *(requires NVIDIA_API_KEY env var; free key at build.nvidia.com)* | Sequence embeddings | `sequences`, `format` | ### Common Parameter Mistakes | Tool | Wrong | Correct | |------|-------|---------| | `NvidiaNIM_rfdiffusion` *(requires NVIDIA_API_KEY)* | `num_steps=50` | `diffusion_steps=50` | | `NvidiaNIM_proteinmpnn` *(requires NVIDIA_API_KEY)* | `pdb=content` | `pdb_string=content` | | `ESMFold_predict_structure` | `seq="MVLS..."` | `sequence="MVLS..."` | | `NvidiaNIM_alphafold2` *(requires NVIDIA_API_KEY)* | `seq="MVLS..."` | `sequence="MVLS..."` | ### NVIDIA NIM Requirements - **API Key**: `NVIDIA_API_KEY` environment variable required - **Rate limits**: 40 RPM (1.5 second minimum between calls) - AlphaFold2 may return 202 (polling required); RFdiffusion and ESMFold are synchronous --- ## Supporting Tools | Tool | Purpose | Key Parameters | |------|---------|----------------| | `PDBe_get_uniprot_mappings` | Find PDB structures | `uniprot_id` | | `RCSBData_get_entry` | Download PDB file | `pdb_id` | | `alphafold_get_prediction` | Get AlphaFold DB structure | `accession` | | `EMDB_search_structures` | Search cryo-EM maps | `query` | | `EMDB_get_structure` | Get entry details | `entry_id` | | `UniProt_get_entry_by_accession` | Get target sequence | `accession` | | `InterPro_get_protein_domains` | Get domains | `accession` | --- ## Evidence Grading | Tier | Criteria | |------|----------| | T1 (best) | pLDDT >85, pTM >0.8, low aggregation, neutral pI | | T2 | pLDDT >75, pTM >0.7, acceptable developability | | T3 | pLDDT >70, pTM >0.65, developability concerns | | T4 | Failed validation or major developability issues | --- ## Completeness Checklist - [ ] Target structure obtained (PDB or predicted) - [ ] Binding epitope identified - [ ] >= 5 backbones generated, top 3-5 selected - [ ] >= 8 sequences per backbone, MPNN scores reported - [ ] All sequences validated (ESMFold), pLDDT/pTM reported, >= 3 passing - [ ] Developability assessed (aggregation, pI, expression) - [ ] Ranked candidate list, FASTA file, experimental recommendations --- ## Reference Files - **DESIGN_PROCEDURES.md** - Phase-by-phase code examples, sampling parameters, fallback chains - **TOOLS_REFERENCE.md** - Complete tool documentation with code examples - **EXAMPLES.md** - Sample design workflows and outputs - **CHECKLIST.md** - Detailed phase checklists and quality metrics - **design_templates.md** - Report templates and output format examples
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.