[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77SP3AH34TPZDPHNXBNX86P":3,"skill-same:01M77SP3AH34TPZDPHNXBNX86P":55},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":29,"commitSha":30,"skillDirectory":31,"forksCount":13,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M77SP3AH34TPZDPHNXBNX86P","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.","ConcertoNotes\u002Fcodex-plugins","ConcertoNotes","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F249301288?v=4","01M77NJ0BK2KN5YW0D8RHD99TB","01M77NJ0CCEDPATAY3JTXEWNK5",0,"MIT","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcommunity\u002Flvtd-skills\u002Fskills\u002Fdjango-test-data\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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":14,"metadata":23,"description":7,"compatibility":28},{"tags":24,"version":25,"category":26,"displayName":27},"django,testing,test-data,factories,pytest","0.1.0","Django","Django Test Data","Codex, Claude Code, and other Agent Skills-compatible clients.","main","9ba3c9fadff1092395837bf1502e1b8a7f98b1e1","plugins\u002Fcommunity\u002Flvtd-skills\u002Fskills\u002Fdjango-test-data","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins","https:\u002F\u002Fgithub.com\u002FConcertoNotes","2026-06-26 10:13:54",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add ConcertoNotes\u002Fcodex-plugins --skill django-test-data",{"tool":41,"command":42},"bunx","bunx skills add ConcertoNotes\u002Fcodex-plugins --skill django-test-data",{"tool":44,"command":45},"pnpm","pnpm dlx skills add ConcertoNotes\u002Fcodex-plugins --skill django-test-data","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcommunity\u002Flvtd-skills\u002Fskills\u002Fdjango-test-data\u002FSKILL.md",true,[49],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fpatterns.md","REFERENCE","参考文档",2593,"https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcommunity\u002Flvtd-skills\u002Fskills\u002Fdjango-test-data\u002Freferences\u002Fpatterns.md",[56,65,72,80,87,94],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":60,"licenseFileUrl":61,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":18},"01M77YB7WW36DS9AERTWP673E0","android-emulator-qa","Use when validating Android feature flows in an emulator with adb-driven launch, input, UI-tree inspection, screenshots, and logcat capture.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Ftest-android-apps\u002Fskills\u002Fandroid-emulator-qa\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Ftest-android-apps\u002Fskills\u002Fandroid-emulator-qa\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":18},"01M77Y7AA8N45G6NM0WJSS2W9C","supabase-postgres-best-practices","Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Fsupabase\u002Fskills\u002Fsupabase-postgres-best-practices\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":60,"licenseFileUrl":76,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M77Y2W5H5YGSW7MYWEJ8HYXD","sentry","Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Fsentry\u002Fskills\u002Fsentry\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Fsentry\u002Fskills\u002Fsentry\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M77Y06GV1DAME7PN9KBFHWRX","render-workflows","Sets up, develops, tests, and deploys Render Workflows. Covers first-time scaffolding (via CLI or manual), SDK installation (Python or TypeScript), task patterns (retries, subtasks, fan-out), local development, Dashboard deployment, and troubleshooting. Use when a user wants to set up Render Workflows for the first time, scaffold a workflow service, add or modify workflow tasks, test workflows locally, or deploy workflows to Render.","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Frender\u002Fskills\u002Frender-workflows\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":18},"01M77Y01A6RJA8VYT7CZ2TVETF","render-web-services","Configures Render web services—port binding, TLS, health checks, custom domains, auto-deploy, PR previews, persistent disks, and deploy lifecycle. Use when the user needs to set up a web service, fix health check failures, add a custom domain, configure zero-downtime deploys, or troubleshoot port binding issues.","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Frender\u002Fskills\u002Frender-web-services\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":18},"01M77XZW1AZ6B6NZTWWFVY72T3","render-static-sites","Deploys and configures static sites on Render's global CDN—build commands, publish paths, SPA routing, redirects, custom headers, and PR previews. Use when the user needs to deploy a static site, set up a React\u002FVue\u002FHugo\u002FGatsby frontend, configure SPA fallback routing, add redirect rules, customize response headers, or choose between a static site and a web service for their frontend. Trigger terms: static site, CDN, SPA, single-page app, React deploy, Vue deploy, Hugo, Gatsby, Docusaurus, Jekyll, staticPublishPath.","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Frender\u002Fskills\u002Frender-static-sites\u002FSKILL.md",[],[]]