[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79TC308X5CM857MSTXDPB0M":3,"skill-same:01M79TC308X5CM857MSTXDPB0M":53},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":14,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":37,"updatedAt":38,"install":39,"resources":52},"01M79TC308X5CM857MSTXDPB0M","django-architect",null,"Architect-level Django guidance — app boundaries and project layout, ORM and migration discipline, settings\u002Fenvironment split, auth and permissions, DRF API layering, admin as an internal surface, and the queries that make Django slow. Use when designing or reviewing a Django\u002FDRF product.","SriAkhilSJ\u002FPulseAIRepo","SriAkhilSJ","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F206201543?v=4","01M79RWFD1Q09B89SXTTKKJY6Z","Sri Akhil SJ","01M79RWFE26NPG0BZ1FRNX376H",0,"MIT","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fbackend-development-architect\u002Fpython-architect\u002Fdjango-architect\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: django-architect\ndescription: Architect-level Django guidance — app boundaries and project layout, ORM and migration discipline, settings\u002Fenvironment split, auth and permissions, DRF API layering, admin as an internal surface, and the queries that make Django slow. Use when designing or reviewing a Django\u002FDRF product.\nlicense: MIT\ncompatibility: Django 4.2\u002F5.x, Django REST Framework, PostgreSQL\nmetadata:\n  crusor-domain: website-architect\n  crusor-path: website-architect\u002Fbackend-development-architect\u002Fpython-architect\u002Fdjango-architect\n  crusor-origin: original\n  crusor-sources: \"docs.djangoproject.com; www.django-rest-framework.org\"\n  crusor-triggers: \"django, drf, django orm, django migration, django admin, django-rest-framework\"\n  crusor-verified-on: \"2026-10-30\"\n---\n\n# Django Architect\n\nDjango is a **product framework**: it ships the ORM, auth, admin and migrations.\nArchitecture is about respecting its grain — apps as boundaries, the ORM as the\nonly data path — rather than fighting it.\n\n## When to use\n\n- Product web app with users, auth, admin and a relational core.\n- Content\u002Fcatalog\u002FCRM-style domains where CRUD is the bulk of the work.\n- A team that benefits from convention over assembly.\n\n## When NOT to use\n\n- A small service or single-purpose API (see `flask-architect`,\n  `fastapi-architect`).\n- Async-heavy or realtime-first workloads — Django works, but the async story is\n  secondary.\n- A polyglot microservice where the ORM's coupling is unwanted.\n\n## Decision 1 — Apps as bounded contexts\n\n```\nproject\u002F            settings, urls, asgi\u002Fwsgi\n  apps\u002F\u003Ccontext>\u002F   models, services, api, admin, migrations\n    services\u002F       use-cases; transactions live here\n      selectors\u002F    read queries (query objects)\n```\n\n- One app per business context, not per technical layer.\n- Cross-app imports go through a service\u002Fselector, never into another app's\n  models.\n- `core`\u002F`common` stays tiny; a big shared app is coupling with a nicer name.\n\n## Decision 2 — ORM discipline\n\n- Views\u002Fserializers do not build complex queries; selectors do, and they are\n  tested.\n- `select_related`\u002F`prefetch_related` are part of the design, not an optimisation\n  pass — N+1 is the default failure.\n- Write paths use `transaction.atomic()` in the service, not the view.\n- No raw SQL without a documented reason and a parameterised query.\n- Model `save()` stays dumb; side effects belong to services\u002Fsignals you can see.\n\n## Decision 3 — Migrations\n\n- Every schema change is a migration, reviewed like code.\n- Data migrations separate from schema migrations.\n- Backwards-compatible sequence for zero-downtime: add → backfill → switch →\n  remove (never rename in place on a live table).\n- `makemigrations --check` in CI so drift cannot merge.\n\n## Decision 4 — Settings and environments\n\n- `settings\u002Fbase.py` + `dev.py` + `prod.py`; environment-specific values from env\n  vars (`django-environ`\u002F`pydantic-settings`).\n- `DEBUG=False` by default; a missing secret must fail at boot, not fall back.\n- `ALLOWED_HOSTS`, `CSRF_TRUSTED_ORIGINS`, secure cookies and HSTS set explicitly\n  in production.\n- Static\u002Fmedia served by the proxy\u002Fobject store, never by Django in production.\n\n## Decision 5 — API layer (DRF)\n\n- Serializers validate input and shape output; they are not business logic.\n- ViewSets only for genuinely resourceful endpoints; explicit APIViews for\n  actions with rules.\n- Permissions are declared per view and tested; object-level checks in the\n  service or permission class.\n- Pagination, filtering and ordering are global defaults, not per-view\n  reinvention.\n- Throttling at the edge; heavy exports\u002Fimports go to background jobs.\n\n## Decision 6 — Admin and auth\n\n- Admin is an internal operational surface: restrict by staff, audit actions,\n  never expose it as the customer UI.\n- Custom user model from day one (`AUTH_USER_MODEL`) — retrofitting it is a\n  migration project.\n- Session vs token auth chosen per surface; API tokens scoped and revocable.\n\n## Failure modes at scale\n\n- Fat views + fat serializers; no service layer, rules duplicated.\n- N+1 in list endpoints discovered only in production.\n- Migrations locked in a deploy; long transactions blocking the table.\n- Signals causing hidden writes that nobody can trace.\n- Settings drift between environments; prod is the only place it breaks.\n\n## Verification receipts\n\n1. `manage.py check --deploy` clean; `makemigrations --check` in CI.\n2. Query-count test on the hottest list endpoint (`assertNumQueries`).\n3. Permission matrix tests per endpoint (owner \u002F other user \u002F staff \u002F anon).\n4. Migration plan reviewed for a live table change (expand\u002Fcontract).\n5. Load test on the two heaviest read and write paths.\n","# Django Architect\n\nDjango is a **product framework**: it ships the ORM, auth, admin and migrations.\nArchitecture is about respecting its grain — apps as boundaries, the ORM as the\nonly data path — rather than fighting it.\n\n## When to use\n\n- Product web app with users, auth, admin and a relational core.\n- Content\u002Fcatalog\u002FCRM-style domains where CRUD is the bulk of the work.\n- A team that benefits from convention over assembly.\n\n## When NOT to use\n\n- A small service or single-purpose API (see `flask-architect`,\n  `fastapi-architect`).\n- Async-heavy or realtime-first workloads — Django works, but the async story is\n  secondary.\n- A polyglot microservice where the ORM's coupling is unwanted.\n\n## Decision 1 — Apps as bounded contexts\n\n```\nproject\u002F            settings, urls, asgi\u002Fwsgi\n  apps\u002F\u003Ccontext>\u002F   models, services, api, admin, migrations\n    services\u002F       use-cases; transactions live here\n      selectors\u002F    read queries (query objects)\n```\n\n- One app per business context, not per technical layer.\n- Cross-app imports go through a service\u002Fselector, never into another app's\n  models.\n- `core`\u002F`common` stays tiny; a big shared app is coupling with a nicer name.\n\n## Decision 2 — ORM discipline\n\n- Views\u002Fserializers do not build complex queries; selectors do, and they are\n  tested.\n- `select_related`\u002F`prefetch_related` are part of the design, not an optimisation\n  pass — N+1 is the default failure.\n- Write paths use `transaction.atomic()` in the service, not the view.\n- No raw SQL without a documented reason and a parameterised query.\n- Model `save()` stays dumb; side effects belong to services\u002Fsignals you can see.\n\n## Decision 3 — Migrations\n\n- Every schema change is a migration, reviewed like code.\n- Data migrations separate from schema migrations.\n- Backwards-compatible sequence for zero-downtime: add → backfill → switch →\n  remove (never rename in place on a live table).\n- `makemigrations --check` in CI so drift cannot merge.\n\n## Decision 4 — Settings and environments\n\n- `settings\u002Fbase.py` + `dev.py` + `prod.py`; environment-specific values from env\n  vars (`django-environ`\u002F`pydantic-settings`).\n- `DEBUG=False` by default; a missing secret must fail at boot, not fall back.\n- `ALLOWED_HOSTS`, `CSRF_TRUSTED_ORIGINS`, secure cookies and HSTS set explicitly\n  in production.\n- Static\u002Fmedia served by the proxy\u002Fobject store, never by Django in production.\n\n## Decision 5 — API layer (DRF)\n\n- Serializers validate input and shape output; they are not business logic.\n- ViewSets only for genuinely resourceful endpoints; explicit APIViews for\n  actions with rules.\n- Permissions are declared per view and tested; object-level checks in the\n  service or permission class.\n- Pagination, filtering and ordering are global defaults, not per-view\n  reinvention.\n- Throttling at the edge; heavy exports\u002Fimports go to background jobs.\n\n## Decision 6 — Admin and auth\n\n- Admin is an internal operational surface: restrict by staff, audit actions,\n  never expose it as the customer UI.\n- Custom user model from day one (`AUTH_USER_MODEL`) — retrofitting it is a\n  migration project.\n- Session vs token auth chosen per surface; API tokens scoped and revocable.\n\n## Failure modes at scale\n\n- Fat views + fat serializers; no service layer, rules duplicated.\n- N+1 in list endpoints discovered only in production.\n- Migrations locked in a deploy; long transactions blocking the table.\n- Signals causing hidden writes that nobody can trace.\n- Settings drift between environments; prod is the only place it breaks.\n\n## Verification receipts\n\n1. `manage.py check --deploy` clean; `makemigrations --check` in CI.\n2. Query-count test on the hottest list endpoint (`assertNumQueries`).\n3. Permission matrix tests per endpoint (owner \u002F other user \u002F staff \u002F anon).\n4. Migration plan reviewed for a live table change (expand\u002Fcontract).\n5. Load test on the two heaviest read and write paths.\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":31},{"crusor-path":25,"crusor-domain":26,"crusor-origin":27,"crusor-sources":28,"crusor-triggers":29,"crusor-verified-on":30},"website-architect\u002Fbackend-development-architect\u002Fpython-architect\u002Fdjango-architect","website-architect","original","docs.djangoproject.com; www.django-rest-framework.org","django, drf, django orm, django migration, django admin, django-rest-framework","2026-10-30","Django 4.2\u002F5.x, Django REST Framework, PostgreSQL","main","8fa4e240be65b98472c9b2d3a505ade2aea1a5c6","skills\u002Fwebsite-architect\u002Fbackend-development-architect\u002Fpython-architect\u002Fdjango-architect","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ","Studying in CMR institute of Technology\r\n2024 - 2028","2026-11-13 21:02:23",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add SriAkhilSJ\u002FPulseAIRepo --skill django-architect",{"tool":45,"command":46},"bunx","bunx skills add SriAkhilSJ\u002FPulseAIRepo --skill django-architect",{"tool":48,"command":49},"pnpm","pnpm dlx skills add SriAkhilSJ\u002FPulseAIRepo --skill django-architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fbackend-development-architect\u002Fpython-architect\u002Fdjango-architect\u002FSKILL.md",true,[],[54,61,68,75,82,89],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M79TTAJNACCNXCEN3649CMMD","interaction-patterns-architect","Architect-level interaction design in code — choosing established patterns over invented ones, feedback and latency behaviour, destructive-action safeguards, navigation and overlay conventions, and the state model behind every interactive surface. Use when a screen has to behave, not just look.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Finteraction-patterns-architect\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M79TT2ESKB1TKZBYY9KYJHV9","design-system-ops-architect","Architect-level operation of a design system in code — token pipelines and versioning, component API and variant policy, the catalogue as the contract, adoption metrics, and the governance that stops a system from forking into three. Use when a component library must survive several teams.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fdesign-system-ops-architect\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M79TSV0PWGNK3PRX9P4JDR9N","design-handoff-architect","Architect-level design handoff — what must be specified before implementation starts, tokens over raw values, responsive and content-limit contracts, state matrices, and the review loop that catches drift between design and code. Use when a design is about to become code.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fdesign-handoff-architect\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M79TSJS9BFXNP696FMJ9GKDA","content-microcopy-architect","Architect-level UI content — where strings live, voice and terminology consistency, error and empty-state copy as part of the interface, translation-ready authoring, and the content model a product needs before it multiplies screens. Use when the words in the interface matter as much as the pixels.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fcontent-microcopy-architect\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M79TSCNBST3N1M68V1KPH9HQ","ui-ux-implementation-architect","Architect-level direction for turning a design into working UI — the handoff contract, component ownership versus screen-level layout, interaction and state conventions, design QA gates, and the review habits that keep an implementation faithful without frozen pixels. Use before any specific UI implementation skill.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M79TS4N6A4D2QQ433VXS5D0R","test-strategy-architect","Architect-level test strategy — allocating assertions across unit, integration, contract and end-to-end layers, designing for testability through dependency boundaries, fixture and data strategy, and the flake and coverage policies that keep a suite trustworthy. Use when defining how a codebase is tested.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Ftesting-and-deployment-architect\u002Ftest-strategy-architect\u002FSKILL.md",[],[]]