flask
- Repo stars 2,412
- License NOASSERTION
- Author repo debugpy
Skill: Flask
Best practices for Flask web development including routing, blueprints, and testing.
When to Use
Apply this skill when building Flask web applications or APIs — routing, blueprints, extensions, and testing.
Project Structure
- Use the application factory pattern (
create_app()) to avoid global state and enable testing. - Organize features into Blueprints; register them in the factory.
- Keep configuration in a
config.pywith classes likeDevelopmentConfig,ProductionConfig.
Routing and Views
- Prefer explicit HTTP method decorators (
@app.get,@app.post) over generic@app.routewithmethods=[...]. - Validate request data early; return 400 errors for malformed input before processing.
- Use
flask.abort()with appropriate HTTP codes rather than returning error responses manually.
Extensions
- Initialize extensions lazily with
ext.init_app(app)inside the factory, not at module level. - Common extensions: Flask-SQLAlchemy, Flask-Migrate, Flask-Login, Flask-WTF, Flask-CORS.
Testing
- Use
app.test_client()for HTTP-level tests andapp.test_request_context()for unit tests. - Use pytest fixtures to create the app and client; scope appropriately (
sessionfor the app,functionfor the client). - Set
TESTING=Trueand use a separate test database.
Pitfalls
- Never use the development server (
app.run()) in production — use Gunicorn or uWSGI. - Avoid storing mutable state on the
appobject; usegfor request-scoped data. - Never hardcode
SECRET_KEY— load from environment variables.
- Fluxly category
- Other
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 94 / 100 · heuristic scan, not runtime safety proof
- Author / version / license
- @microsoft · NOASSERTION
- Fluxly token estimate
- Lean
- Fluxly setup estimate
- Guided setup
- External API key
- Required · Vendor-specific
- Detected OS requirements
- Unspecified
- Runtime requirements
- Unspecified
- Detected file/system behavior
-
- Read-only
- Write / modify
- Env read
- Detected network behavior
- External requests
- Install commands
- None (reference only)
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
The current SKILL.md does not define a fixed output example.Apply this skill when building Flask web applications or APIs — routing, blueprints, extensions, and testing.
Use the application factory pattern (createapp()) to avoid global state and enable testing. Organize features into Blueprints; register them in the factory. Keep configuration in a config.py with classes like DevelopmentConfig, ProductionConfig.
Prefer explicit HTTP method decorators (@app.get, @app.post) over generic @app.route with methods=[...]. Validate request data early; return 400 errors for malformed input before processing. Use flask.abort() with appropriate HTTP codes rather than returning…
Initialize extensions lazily with ext.initapp(app) inside the factory, not at module level. Common extensions: Flask-SQLAlchemy, Flask-Migrate, Flask-Login, Flask-WTF, Flask-CORS.
Use app.testclient() for HTTP-level tests and app.testrequestcontext() for unit tests. Use pytest fixtures to create the app and client; scope appropriately (session for the app, function for the client). Set TESTING=True and use a separate test database.
Never use the development server (app.run()) in production — use Gunicorn or uWSGI. Avoid storing mutable state on the app object; use g for request-scoped data. Never hardcode SECRETKEY — load from environment variables.
# Skill: Flask
Best practices for Flask web development including routing, blueprints, and testing.
## When to Use
Apply this skill when building Flask web applications or APIs — routing, blueprints, extensions, and testing.
## Project Structure
- Use the application factory pattern (`create_app()`) to avoid global state and enable testing.
- Organize features into Blueprints; register them in the factory.
- Keep configuration in a `config.py` with classes like `DevelopmentConfig`, `ProductionConfig`.
## Routing and Views
- Prefer explicit HTTP method decorators (`@app.get`, `@app.post`) over generic `@app.route` with `methods=[...]`.
- Validate request data early; return 400 errors for malformed input before processing.
- Use `flask.abort()` with appropriate HTTP codes rather than returning error responses manually.
## Extensions
- Initialize extensions lazily with `ext.init_app(app)` inside the factory, not at module level.
- Common extensions: Flask-SQLAlchemy, Flask-Migrate, Flask-Login, Flask-WTF, Flask-CORS.
## Testing
- Use `app.test_client()` for HTTP-level tests and `app.test_request_context()` for unit tests.
- Use pytest fixtures to create the app and client; scope appropriately (`session` for the app, `function` for the client).
- Set `TESTING=True` and use a separate test database.
## Pitfalls
- Never use the development server (`app.run()`) in production — use Gunicorn or uWSGI.
- Avoid storing mutable state on the `app` object; use `g` for request-scoped data.
- Never hardcode `SECRET_KEY` — load from environment variables.Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.
sections -> When to Use → Project Structure → Routing and Views → Extensions → Testing → Pitfalls
terms -> Best practices for Flask web development including routing, blueprints, and testing. · Apply this skill when building Flask web applications or APIs — routing, blueprints, extensions, and testing. · - Use the application factory pattern (createapp()) to avoid global state and enable testing. · - Prefer explicit HTTP method decorators (@app.get, @app.post) over generic @app.route with methods=[...]. · - Initialize extensions lazily with ext.initapp(app) inside the factory, not at module level. · - Use app.testclient() for HTTP-level tests and app.testrequestcontext() for unit tests. · - Never use the development server (app.run()) in production — use Gunicorn or uWSGI.
files/cmd -> createapp() · config.py · DevelopmentConfig · ProductionConfig · @app.get · @app.post · @app.route · methods=[...]
body sha256 -> e23cc19f87cd
Decide Fit First
Design Intent
How To Use It
Boundaries And Review