[{"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",1566,"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",483,"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-13 02:16:32",{"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,111,118,143,168],{"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":99,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":103},"01M746ZWACVKMZ1BJXJZHYJSSX","migrate-to-e2e","Moves an existing Playwright, Cypress, Selenium, Appium, Detox, Maestro, or TesterArmy suite to e2e one slice at a time, with the old suite running beside the new one until each ported test is proven. Keeps a MIGRATION.md progress file so any later session resumes where the last stopped. Optionally plants a defect to show both suites catch it. Use for \u002Fmigrate-to-e2e, \"migrate our tests to e2e\", \"port these Maestro flows\", \"move our TesterArmy tests\", or when a project has an e2e config and an older suite still running.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fmigrate-to-e2e\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"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":99,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":103},"01M746ZPTAX1Q0FBKAB1CYND7E","e2e","Writes, runs, and debugs end-to-end tests for web and mobile apps with e2e, the agentic test runner, which mixes agent.act goals with exact locator assertions on a Playwright browser or an iOS or Android device. Also drives a project's running app live over the e2e MCP server to look at a screen, check a UI change, take a screenshot or record a video, and try a locator; and runs bug bashes, parallel e2e explore runs with each bug proven by a repro test. Use when a project depends on e2e or has an e2e.config.ts, when asked for end-to-end, browser, mobile, or agentic UI tests, to check a change in the running app, to QA or bug bash an app or branch, or when an e2e run fails.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fe2e\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":99,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":103},"01M746ZJN784HVHMDP9MQGCSGG","create-verification-skill","Generate a project-local verify-\u003Capp> skill on top of e2e, so any coding agent can launch the app, check it is worth driving, exercise a feature the way a user does, keep evidence, and bug bash it. Writes the skill, a feature map with one explore charter per feature, and proves it once. Use for \u002Fcreate-verification-skill, \"make a verification skill for this repo\", or when a project has no scripted way to prove UI behavior.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fcreate-verification-skill\u002FSKILL.md",[],[],{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":99,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":53},"01M716A6ETNB9B1SQ3GXZC75VR","deja-search","deja-vu memory — search the user's past AI coding sessions with the deja CLI. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before you call a change done or ready to merge, before you recommend a tool, library, design or reviewer, before re-debugging an error that may already be solved, when they say 'didn't we fix this before', 'what did we decide about X' or 'I already have that', and before telling them something on this machine does not exist.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-search\u002FSKILL.md",[],[125,126,127,128,129,130,131,132,133,52,134,38,135,136,137,138,139,140,141,142],"search","deja search","never","error","ready","memory","re","decide","fix","debugging","you","done","reviewer","io","change","cli","merge","past",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":99,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":149,"publishedAt":53},"01M716A3J2W5SENSE9VGMXB375","deja-reflect","End-of-session reflection and memory curation with deja-vu. Review what was decided, what commands broke and what repaired them, and record durable project rules or decisions with deja remember so the next session starts with them.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-reflect\u002FSKILL.md",[],[150,151,152,138,153,154,155,156,157,158,159,160,161,162,130,163,164,165,166,167],"deja reflect","reflect","review","with","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":99,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":181,"publishedAt":53},"01M715T3RR4BAYSR57HPPTJ0PF","revid","Make, edit, export and post AI videos with Revid (revid.ai) through the Revid MCP server. Use whenever the user wants a short-form or long-form video made (from an idea, a script, a URL, an article, a PDF, a tweet, a product page, their own clips, or a song), wants to find what is going viral on TikTok, YouTube, Instagram or X before making something, wants to edit or re-export an existing Revid project, generate a standalone AI image or clip, make a series episode, or publish and schedule a finished video to connected social accounts. Covers setup (hosted MCP with OAuth, or an API key), the 36 tools, credits, polling and the rules for publishing. Routes to the more specific revid-* skills when one fits.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftmakersas\u002Frevid-skills\u002Fskills\u002Frevid\u002FSKILL.md",[174,177,178],{"categoryNo":175,"categoryName":176,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":179,"categoryName":180,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[170,182,183,184,185,186,187,164,188,131,189,190,191,192,38,193,194,195,196,197],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api","publish"]