[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MC3FFH00ABHRMMKS28W7P5":3,"skill-same:01M6MC3FFH00ABHRMMKS28W7P5":94},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":31,"publishedAt":53,"linkOnly":54,"markdownContent":55,"markdownBody":56,"frontMatter":57,"refName":64,"commitSha":65,"skillDirectory":66,"forksCount":67,"repositoryHtmlUrl":68,"repositoryHomepageUrl":69,"ownerHtmlUrl":70,"ownerBlogUrl":71,"ownerDescription":72,"updatedAt":73,"install":74,"resources":87},"01M6MC3FFH00ABHRMMKS28W7P5","django-test-data",null,"Design faster, clearer Django test data and test structure with factories, setUpTestData, SimpleTestCase\u002FTestCase choices, fixture-file cleanup, query optimization, and unit-vs-integration boundaries. Use when Django tests create too much data, rely on slow fixtures, overuse TransactionTestCase, duplicate setup, or need refactoring for speed without losing coverage.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fdjango-test-data\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52],"test","django test data","data","django","test data","coverage","when","for","unit","fixture","structure","query","pytest","query optimization","testing","refactoring","Optimization","code","create","cleanup","design","2026-11-10 10:12:30",false,"---\nname: django-test-data\ndescription: Design faster, clearer Django test data and test structure with factories, setUpTestData, SimpleTestCase\u002FTestCase choices, fixture-file cleanup, query optimization, and unit-vs-integration boundaries. Use when Django tests create too much data, rely on slow fixtures, overuse TransactionTestCase, duplicate setup, or need refactoring for speed without losing coverage.\nlicense: MIT\ncompatibility: Codex, Claude Code, and other Agent Skills-compatible clients.\nmetadata:\n  version: \"0.1.0\"\n  displayName: Django Test Data\n  category: Django\n  tags: django,testing,test-data,factories,pytest\n---\n\n# Django Test Data\n\nMost slow Django suites spend time building data they do not need or exercising full request\u002Fdatabase paths for behavior that can be tested at a smaller boundary. Use this skill to reduce setup cost while keeping representative integration coverage.\n\n## Refactoring Workflow\n\n1. Map the behavior under test.\n   - Identify the smallest useful boundary: function, form, model method, middleware, command helper, view, or full request path.\n   - Keep a few integration tests for wiring; move detailed cases to unit tests where the boundary is clean.\n\n2. Choose the fastest test base class.\n   - `SimpleTestCase`: no database access.\n   - `TestCase`: ordinary database tests with rollback.\n   - `TransactionTestCase`: committed transaction behavior only.\n   - `LiveServerTestCase`: browser\u002Flive-server tests only.\n\n3. Remove broad fixture data.\n   - Avoid large fixture files and base classes that always create objects.\n   - Build only the data each test or class needs.\n\n4. Use factories deliberately.\n   - Start with small factory functions when the domain is simple.\n   - Use Factory Boy or Model Bakery when relationships and variants become repetitive.\n\n5. Share class-level data with `setUpTestData`.\n   - Use `setUpTestData()` for database objects reused by multiple methods in a `TestCase`.\n   - Avoid mutating shared in-memory objects across methods.\n\n6. Optimize database access in test setup and assertions.\n   - Use `select_related`, `prefetch_related`, or `bulk_create` where setup\u002Fquery cost is the bottleneck.\n   - Assert query counts for hot paths when performance is part of the contract.\n\nRead [patterns.md](references\u002Fpatterns.md) for examples and decision details.\n\n## Decision Rules\n\n- If a test does not need the database, use `SimpleTestCase`.\n- If only some tests need the database, split them into separate classes.\n- If a test requires committed transaction behavior, first check whether `captureOnCommitCallbacks()` or an inner `atomic()` is enough.\n- If many tests share expensive objects, use `setUpTestData` instead of `setUp`.\n- If fixture files are hard to understand or grow over time, replace them with factories.\n- If a test depends on hard-coded auto-increment IDs, fix the assertion rather than enabling `reset_sequences=True`.\n- Combine assertions when they describe one behavior produced by one expensive action.\n\n## Common Mistakes\n\n- Testing form validation only through rendered HTML instead of inspecting form errors directly.\n- Leaving management-command business logic inside `handle()`, forcing tests through `call_command()`.\n- Using `TransactionTestCase` as the default.\n- Putting data in a base `TestCase` that only a few subclasses need.\n- Treating factories as permission to create a large object graph for every test.\n- Mutating objects created by `setUpTestData` and leaking in-memory state to later tests.\n\n## Verification\n\nBefore finishing a refactor:\n\n- The old behavior remains covered at the right level.\n- Database-using and non-database tests are split where useful.\n- Repeated setup moved to `setUpTestData` or factories only where it reduces cost.\n- Relevant tests pass individually and as part of their module\u002Fclass.\n","# Django Test Data\n\nMost slow Django suites spend time building data they do not need or exercising full request\u002Fdatabase paths for behavior that can be tested at a smaller boundary. Use this skill to reduce setup cost while keeping representative integration coverage.\n\n## Refactoring Workflow\n\n1. Map the behavior under test.\n   - Identify the smallest useful boundary: function, form, model method, middleware, command helper, view, or full request path.\n   - Keep a few integration tests for wiring; move detailed cases to unit tests where the boundary is clean.\n\n2. Choose the fastest test base class.\n   - `SimpleTestCase`: no database access.\n   - `TestCase`: ordinary database tests with rollback.\n   - `TransactionTestCase`: committed transaction behavior only.\n   - `LiveServerTestCase`: browser\u002Flive-server tests only.\n\n3. Remove broad fixture data.\n   - Avoid large fixture files and base classes that always create objects.\n   - Build only the data each test or class needs.\n\n4. Use factories deliberately.\n   - Start with small factory functions when the domain is simple.\n   - Use Factory Boy or Model Bakery when relationships and variants become repetitive.\n\n5. Share class-level data with `setUpTestData`.\n   - Use `setUpTestData()` for database objects reused by multiple methods in a `TestCase`.\n   - Avoid mutating shared in-memory objects across methods.\n\n6. Optimize database access in test setup and assertions.\n   - Use `select_related`, `prefetch_related`, or `bulk_create` where setup\u002Fquery cost is the bottleneck.\n   - Assert query counts for hot paths when performance is part of the contract.\n\nRead [patterns.md](references\u002Fpatterns.md) for examples and decision details.\n\n## Decision Rules\n\n- If a test does not need the database, use `SimpleTestCase`.\n- If only some tests need the database, split them into separate classes.\n- If a test requires committed transaction behavior, first check whether `captureOnCommitCallbacks()` or an inner `atomic()` is enough.\n- If many tests share expensive objects, use `setUpTestData` instead of `setUp`.\n- If fixture files are hard to understand or grow over time, replace them with factories.\n- If a test depends on hard-coded auto-increment IDs, fix the assertion rather than enabling `reset_sequences=True`.\n- Combine assertions when they describe one behavior produced by one expensive action.\n\n## Common Mistakes\n\n- Testing form validation only through rendered HTML instead of inspecting form errors directly.\n- Leaving management-command business logic inside `handle()`, forcing tests through `call_command()`.\n- Using `TransactionTestCase` as the default.\n- Putting data in a base `TestCase` that only a few subclasses need.\n- Treating factories as permission to create a large object graph for every test.\n- Mutating objects created by `setUpTestData` and leaking in-memory state to later tests.\n\n## Verification\n\nBefore finishing a refactor:\n\n- The old behavior remains covered at the right level.\n- Database-using and non-database tests are split where useful.\n- Repeated setup moved to `setUpTestData` or factories only where it reduces cost.\n- Relevant tests pass individually and as part of their module\u002Fclass.\n",{"name":5,"license":15,"metadata":58,"description":7,"compatibility":63},{"tags":59,"version":60,"category":61,"displayName":62},"django,testing,test-data,factories,pytest","0.1.0","Django","Django Test Data","Codex, Claude Code, and other Agent Skills-compatible clients.","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fdjango-test-data",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":75,"prompt":85,"zipAvailable":86},[76,79,82],{"tool":77,"command":78},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill django-test-data",{"tool":80,"command":81},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill django-test-data",{"tool":83,"command":84},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill django-test-data","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fdjango-test-data\u002FSKILL.md",true,[88],{"path":89,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Fpatterns.md","REFERENCE","参考文档",2593,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fdjango-test-data\u002Freferences\u002Fpatterns.md",[95,104,112,120,128,136],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":99,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":103},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":108,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":103},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":116,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":103},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":124,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":103},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":132,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":103},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":140,"sourceHtmlUrl":141,"categories":142,"keywords":143,"publishedAt":103},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]