Protein design workflows

What is protein design?

Protein design is the computational creation or optimization of protein sequences and structures for a defined objective. The objective may be a new fold, a sequence compatible with a backbone, catalytic activity, antigen recognition, peptide binding, target-specific protein binding, or improved sequence properties. Different design tasks require different inputs, models, scores, and experimental evidence.

Protein design is an umbrella use case rather than one algorithm. De novo methods generate new structural or sequence space; inverse folding finds sequences for a fixed backbone; enzyme, antibody, peptide, and binder design add functional and molecular-class constraints. Protein sequence design spans both structure-conditioned and sequence-generative approaches.

Choose the narrowest task that matches what you are trying to create. Every workflow should preserve constraints, random seeds, generated candidates, component scores, structures, and rejection reasons. Computational ranking reduces a search space, while synthesis, expression, structural characterization, and functional assays determine whether a design works.

When to use protein design

• Create a new protein candidate. Generate a backbone, sequence, binder, enzyme, antibody, or peptide against an explicit objective.
• Redesign an existing structure. Search sequences compatible with a backbone while preserving fixed functional or structural positions.
• Connect design with validation. Keep generation, sequence assignment, refolding, property review, and experimental handoff in one inspectable record.

Choosing a protein design method

The useful taxonomy follows researcher intent. De novo protein design creates new structures; inverse folding solves sequence for a fixed backbone; enzyme, antibody, peptide, and protein-binder design add distinct functional or molecular constraints; protein sequence design covers broader sequence generation and optimization.

Ligand-conditioned design and stability design remain important methods and objectives, but they fit within enzyme, sequence, or binder workflows here rather than becoming additional maintained spokes without demonstrated search demand.

How to design proteins online

A defensible protein-design workflow begins with a measurable objective and ends with experimental evidence. The software stages should make every assumption, constraint, candidate, and acceptance gate visible.

1. Define the objective. State the desired structure, interaction, reaction, or property and how success will be measured.
2. Prepare constraints. Confirm structures, sequences, motifs, fixed residues, targets, and allowed design space.
3. Generate candidates. Use a method whose documented task and input requirements match the project.
4. Evaluate evidence. Review native scores, refolding, geometry, diversity, stability, solubility, and task-specific evidence.
5. Test experimentally. Select a diverse panel and measure expression, structure, and the intended function.

How to evaluate protein designs

No single score establishes design success. Evaluate constraint satisfaction, structural agreement, local confidence, geometry, sequence diversity, stability, solubility, aggregation, and task-specific evidence separately.

Compare candidates within the same model and settings unless scores are explicitly calibrated across methods. Preserve rejected designs and score distributions to avoid selection based only on attractive visualizations.

Experimental validation for protein design

Expression and folding are early gates, not proof of function. The decisive assay must match the objective: affinity and specificity for binders, catalytic rate and selectivity for enzymes, or structural and biophysical properties for scaffold designs.

Plan controls, replication, and candidate diversity before generation. Export sequences, structures, settings, provenance, and selection logic together for synthesis and laboratory handoff.

Benefits of protein design

• Broader search. Explore structural and sequence possibilities beyond manual mutation.
• Explicit constraints. Encode geometry, residues, targets, and properties as inspectable design requirements.
• Connected evidence. Carry candidates from generation through model review and experimental handoff.

Limitations of protein design

• Model-dependent rankings. Scores are approximations tied to each method and training distribution.
• Incomplete biological context. Dynamics, expression systems, partners, and cellular conditions may be missing.
• Experiments remain decisive. Computational candidates require synthesis, characterization, and functional testing.

How the featured workflow works

The hub workflow compares four sequence-design methods from one backbone; each spoke uses a workflow matched to its specific design task.

1. Define the objective. Choose the protein-design task and acceptance criteria.
2. Prepare the backbone. Clean the PDB and identify chains and fixed residues.
3. Run four methods. Submit the same backbone to four sequence-design models.
4. Compare candidates. Review probabilities, diversity, conserved positions, and method agreement.
5. Validate and export. Refold and screen selected candidates before experimental testing.

Inputs and outputs for the featured workflow

Check formats before running, then inspect and download the result from every workflow step.

Inputs

Design evidence

PDBFASTAJSONTXT

Protein structures, sequences, targets, motifs, fixed residues, and constraints required by the selected design task.

Outputs

Design candidates

PDBFASTACSVJSON

Generated structures and sequences, model-native scores, rankings, logs, and validation files.