القائمة
Scaffold queryset/manager/selector layers and wire view reads through selector entrypoints 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.
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.
Keep reads in selectors/querysets and keep write logic in services without using jig.
| name | query-layer-discipline |
| description | Scaffold queryset/manager/selector layers and wire view reads through selector entrypoints with jig. |
Use this skill to standardize read paths through QuerySet + selector layers.
model_namequeryset_namemanager_nameselector_nameselector_fileview_namejig run ${CLAUDE_SKILL_DIR:-.claude/skills/query-layer-discipline}/recipe.yaml --vars '{
"model_name": "Entity",
"queryset_name": "EntityQuerySet",
"manager_name": "EntityManager",
"selector_name": "select_active_entities",
"selector_file": "selectors.py",
"view_name": "entity_list"
}'
If jig fails, use rendered snippets from stderr as manual patch guidance.
Notes:
model_name and view_name selectors directly.regex_escape is applied inside regex-bearing anchors so symbol values are treated literally.