Flask 技能验证
- 作者仓库星标 2,412
- 许可证 NOASSERTION
- 作者仓库 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.
- 流狐分类
- 通用
- 作者声明 Agent
- 未找到明确声明；不据此推断已兼容或已测试
- 静态检查
- 94 / 100 · 启发式扫描，不代表运行安全
- 作者 / 版本 / 许可
- @microsoft · NOASSERTION
- 流狐 Token 估算
- 低消耗
- 流狐接入估算
- 需简单配置
- 是否需要外部 API Key
- 需要 · Vendor-specific
- 检测到的系统要求
- 未声明
- 底层运行要求
- 未声明
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 读取环境变量
- 检测到的网络行为
- 允许外网请求
- 安装命令数
- 无（仅作为资料）
档案由构建时根据 SKILL.md 与安装命令自动衍生，可能与作者实际意图存在差异。
需要注意： 未限定 allowed-tools，默认拥有全部工具权限。
作者没有在当前 SKILL.md 中定义固定输出样例。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.作者原文负责流程事实；流狐只索引当前章节、要点、文件与命令。
章节 -> When to Use → Project Structure → Routing and Views → Extensions → Testing → Pitfalls
要点 -> 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.
文件/命令 -> createapp() · config.py · DevelopmentConfig · ProductionConfig · @app.get · @app.post · @app.route · methods=[...]
内容 SHA-256 -> e23cc19f87cd
原文结构
适用与边界
原文中的明确线索
createapp()、config.py、DevelopmentConfig、ProductionConfig、@app.get、@app.post、@app.route、methods=[...]