I prefer keeping routes in a separate file. Instead of @app.route('/') def index(): pass I keep a routes array routes = [ ('/',

I prefer keeping routes in a separate file. Instead of @app.route('/') def index(): pass I keep a routes array routes = [ ('/', endpoint='index', view_func=index) ... ] I find it a lot pleasant to look up all routes at the same place rather than guessing or searching. Also, I give an explicit name to all endpoints. I do the same with blueprints. Blueprints have their own urls.py, and blueprints don't specify the url prefix. For eg, a comment blueprint will define '/', rather than '/comments'. I leave the url prefix to the main application. app.register_blueprint(comment, url_prefix='/comment') For migrations, I prefer alembic to sql migrations - https://alembic.readthedocs.org/en/latest/tutorial.html https://alembic.readthedocs.org/en/latest/tutorial.html I find Alembic simpler than SQLAlchemy(without compromising on power). Alembic can autogenerate migrations based on your model definitions. The way I work is I add a new model, and then run alembic to autogenerate the migration. Same goes for altering models. For settings, I maintain setting.py, dev_settings.py, prod_settings.py. settings.py contains all the common settings. If environment is not defined, I do a `from dev_settings import *`, else I do a relevant import for the environment. I also prefer having BEFORE_REQUESTS, AFTER_REQUESTS, MIDDLEWARES, LOG_HANDLERS, TEMPLATE_FILTERS, CONTEXT_PROCESSORS, ERROR_HANDLERS... in settings, and in main.py, call the relevant functions. That way, I don't have to hunt down the codebase. For blueprints, I define the same variables in __init__.py. Model forms are another time saver(use wtforms, or preferably flask-wtform) from flask.ext.wtf import Form from wtforms.ext.sqlalchemy.orm import model_form import models PostForm = model_form(models.Post, models.db.session, Form, field_args = { 'name': {'validators': []}, 'title': {'validators': []}, 'content': {'validators': []}, }) models.Post is flask-sqlalchemy model, models.db.session is sqlalcheymy session. You don't need to list all model fields for your model form. I find keeping models and forms in sync a pain. This way, I only keep the validations in sync(field_args isn't required - that's an example of adding validations). I use flask-debugtoolbar for basic profiling and debugging. flask-webassets is awesome for managing assets and dynamic compilation. flask-script for writing manage.py jobs(python manage.py get_deps, python manage.py db_createall etc etc)