Refactor Flask 3.x apps to an application factory with unbound extensions and blueprints.
npx skills add https://github.com/Levironexe/architect --skill flask-levironexe
Please help me install this Agent Skill. Skill: Flask Source: https://github.com/Levironexe/architect/tree/main/skills/stacks/flask Command: npx skills add https://github.com/Levironexe/architect --skill flask-levironexe
Flask codebases often drift into circular imports, tangled extension setup, and routes that contain business logic, making refactors risky and tests difficult to write. This Skill guides your coding agent toward a reliable Flask 3.x structure using an application factory, unbound extensions, and blueprint-driven separation.
create_app() to create the Flask instance only inside the factory function, enabling environment-specific configuration and test isolation.app/extensions.py and binds them with init_app(app) inside create_app() to prevent circular imports.routes.py thin (validation + response) while placing business logic in services.py, models in app/models/, and domain templates under blueprint namespaces.Use Case: You inherit a Flask app where extensions and blueprints are imported at module load time, causing startup failures and brittle tests; you need a phased, safe refactor that preserves behavior while restructuring for maintainability.
Ask your agent: "Generate a Flask refactor plan for a project that uses blueprints, services, models, and an application factory, then apply the first phase to fix circular imports and extension initialization."
High-intent search queries and answers about installing and using this skill.
Fix circular imports in Flask by moving extension instantiation to a separate module and binding them later using `extension.init_app(app)` inside the `create_app()` application factory function.
The Flask application factory pattern uses a `create_app()` function to instantiate the Flask instance on demand, enabling environment-specific configuration selection and safe test isolation across development environments.
To separate business logic from routes in Flask blueprints, keep `routes.py` files thin by handling only validation and responses, while moving all business logic into dedicated `services.py` modules within the blueprint structure.
Yes, pytest works with a Flask application factory by calling `create_app()` within your test fixtures to generate isolated app instances, ensuring consistent test client setup and environment-specific configuration selection.
The best way to refactor a Flask app with tangled extension setup is a phased approach enforcing unbound extension initialization via `init_app(app)` and blueprint-driven separation to preserve behavior while restructuring for maintainability.
cornmanwtfGenerate visual import graphs and detect circular dependencies in code projects.
salverius-techStructure Flask web applications with blueprints, factories, and pytest.
sergio-bershadskyAutomate Django testing workflows with pytest-django patterns and factory_boy fixtures.
MrIbrahemAnalyze Flask projects for structural patterns, extension usage, and code-quality gaps.