القائمة
Scaffold request/response contracts, view function wiring, URL route, and test updates with jig.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
When the user wants to codify a repeatable code generation pattern into a jig recipe — design variables, choose operations (create/inject/patch/replace), write Jinja templates, and validate the result. Use when someone says "I keep writing this same boilerplate", "make a recipe for X", or wants to turn a manual edit into an automated pattern.
When the user needs to chain multiple jig recipes into a multi-step workflow with conditional execution and shared variables. Use when a pattern spans multiple files that need coordinated creation and modification, like scaffolding an entire endpoint or a full feature slice.
Scaffold queryset/manager/selector layers and wire view reads through selector entrypoints with jig.
Generate two-step rollout-safe Django migrations plus model-field patching using jig.
Insert consistent method/step structured logging lines into target functions using jig.
Write deterministic service tests with stable fixtures and boundary mocks without using jig.
| name | view-contract-enforcer |
| description | Scaffold request/response contracts, view function wiring, URL route, and test updates with jig. |
Use this skill to keep view boundary behavior consistent and mechanical.
view_namehttp_methodrequest_schema_nameresponse_schema_nameservice_symbolurl_pathurl_nametest_nametest_urljig run ${CLAUDE_SKILL_DIR}/recipe.yaml --vars '{
"view_name": "entity_summary",
"http_method": "POST",
"request_schema_name": "EntitySummaryRequest",
"response_schema_name": "EntitySummaryResponse",
"service_symbol": "build_entity_summary",
"url_path": "entities/<int:pk>/summary/",
"url_name": "entity-summary",
"test_name": "test_entity_summary",
"test_url": "/api/entities/1/summary/"
}'
If jig exits non-zero, apply the rendered snippets manually from stderr output.