[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BN4F4KF3FAK81MFT472B92":3,"skill-same:01M7BN4F4KF3FAK81MFT472B92":47},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7BN4F4KF3FAK81MFT472B92","python-project-structure",null,"Python project organization, module architecture, and public API design. Use when setting up new projects, organizing modules, defining public interfaces with __all__, or planning directory layouts.","YYC-Cube\u002FYYC3-Knowledge-Base","YYC-Cube","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235006543?v=4","01M79J2PH4SWD2X0825X6PN748","yyc3","01M79J2PHVK3F6ZBYT8K2SCZCW",1,"MIT","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Agent-智能体\u002FYYC3-Agent-智能体-agents\u002Fplugins\u002Fpython-development\u002Fskills\u002Fpython-project-structure\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: python-project-structure\ndescription: Python project organization, module architecture, and public API design. Use when setting up new projects, organizing modules, defining public interfaces with __all__, or planning directory layouts.\n---\n\n# Python Project Structure & Module Architecture\n\nDesign well-organized Python projects with clear module boundaries, explicit public interfaces, and maintainable directory structures. Good organization makes code discoverable and changes predictable.\n\n## When to Use This Skill\n\n- Starting a new Python project from scratch\n- Reorganizing an existing codebase for clarity\n- Defining module public APIs with `__all__`\n- Deciding between flat and nested directory structures\n- Determining test file placement strategies\n- Creating reusable library packages\n\n## Core Concepts\n\n### 1. Module Cohesion\n\nGroup related code that changes together. A module should have a single, clear purpose.\n\n### 2. Explicit Interfaces\n\nDefine what's public with `__all__`. Everything not listed is an internal implementation detail.\n\n### 3. Flat Hierarchies\n\nPrefer shallow directory structures. Add depth only for genuine sub-domains.\n\n### 4. Consistent Conventions\n\nApply naming and organization patterns uniformly across the project.\n\n## Quick Start\n\n```\nmyproject\u002F\n├── src\u002F\n│   └── myproject\u002F\n│       ├── __init__.py\n│       ├── services\u002F\n│       ├── models\u002F\n│       └── api\u002F\n├── tests\u002F\n├── pyproject.toml\n└── README.md\n```\n\n## Fundamental Patterns\n\n### Pattern 1: One Concept Per File\n\nEach file should focus on a single concept or closely related set of functions. Consider splitting when a file:\n\n- Handles multiple unrelated responsibilities\n- Grows beyond 300-500 lines (varies by complexity)\n- Contains classes that change for different reasons\n\n```python\n# Good: Focused files\n# user_service.py - User business logic\n# user_repository.py - User data access\n# user_models.py - User data structures\n\n# Avoid: Kitchen sink files\n# user.py - Contains service, repository, models, utilities...\n```\n\n### Pattern 2: Explicit Public APIs with `__all__`\n\nDefine the public interface for every module. Unlisted members are internal implementation details.\n\n```python\n# mypackage\u002Fservices\u002F__init__.py\nfrom .user_service import UserService\nfrom .order_service import OrderService\nfrom .exceptions import ServiceError, ValidationError\n\n__all__ = [\n    \"UserService\",\n    \"OrderService\",\n    \"ServiceError\",\n    \"ValidationError\",\n]\n\n# Internal helpers remain private by omission\n# from .internal_helpers import _validate_input  # Not exported\n```\n\n### Pattern 3: Flat Directory Structure\n\nPrefer minimal nesting. Deep hierarchies make imports verbose and navigation difficult.\n\n```\n# Preferred: Flat structure\nproject\u002F\n├── api\u002F\n│   ├── routes.py\n│   └── middleware.py\n├── services\u002F\n│   ├── user_service.py\n│   └── order_service.py\n├── models\u002F\n│   ├── user.py\n│   └── order.py\n└── utils\u002F\n    └── validation.py\n\n# Avoid: Deep nesting\nproject\u002Fcore\u002Finternal\u002Fservices\u002Fimpl\u002Fuser\u002F\n```\n\nAdd sub-packages only when there's a genuine sub-domain requiring isolation.\n\n### Pattern 4: Test File Organization\n\nChoose one approach and apply it consistently throughout the project.\n\n**Option A: Colocated Tests**\n\n```\nsrc\u002F\n├── user_service.py\n├── test_user_service.py\n├── order_service.py\n└── test_order_service.py\n```\n\nBenefits: Tests live next to the code they verify. Easy to see coverage gaps.\n\n**Option B: Parallel Test Directory**\n\n```\nsrc\u002F\n├── services\u002F\n│   ├── user_service.py\n│   └── order_service.py\ntests\u002F\n├── services\u002F\n│   ├── test_user_service.py\n│   └── test_order_service.py\n```\n\nBenefits: Clean separation between production and test code. Standard for larger projects.\n\n## Advanced Patterns\n\n### Pattern 5: Package Initialization\n\nUse `__init__.py` to provide a clean public interface for package consumers.\n\n```python\n# mypackage\u002F__init__.py\n\"\"\"MyPackage - A library for doing useful things.\"\"\"\n\nfrom .core import MainClass, HelperClass\nfrom .exceptions import PackageError, ConfigError\nfrom .config import Settings\n\n__all__ = [\n    \"MainClass\",\n    \"HelperClass\",\n    \"PackageError\",\n    \"ConfigError\",\n    \"Settings\",\n]\n\n__version__ = \"1.0.0\"\n```\n\nConsumers can then import directly from the package:\n\n```python\nfrom mypackage import MainClass, Settings\n```\n\n### Pattern 6: Layered Architecture\n\nOrganize code by architectural layer for clear separation of concerns.\n\n```\nmyapp\u002F\n├── api\u002F           # HTTP handlers, request\u002Fresponse\n│   ├── routes\u002F\n│   └── middleware\u002F\n├── services\u002F      # Business logic\n├── repositories\u002F  # Data access\n├── models\u002F        # Domain entities\n├── schemas\u002F       # API schemas (Pydantic)\n└── config\u002F        # Configuration\n```\n\nEach layer should only depend on layers below it, never above.\n\n### Pattern 7: Domain-Driven Structure\n\nFor complex applications, organize by business domain rather than technical layer.\n\n```\necommerce\u002F\n├── users\u002F\n│   ├── models.py\n│   ├── services.py\n│   ├── repository.py\n│   └── api.py\n├── orders\u002F\n│   ├── models.py\n│   ├── services.py\n│   ├── repository.py\n│   └── api.py\n└── shared\u002F\n    ├── database.py\n    └── exceptions.py\n```\n\n## File and Module Naming\n\n### Conventions\n\n- Use `snake_case` for all file and module names: `user_repository.py`\n- Avoid abbreviations that obscure meaning: `user_repository.py` not `usr_repo.py`\n- Match class names to file names: `UserService` in `user_service.py`\n\n### Import Style\n\nUse absolute imports for clarity and reliability:\n\n```python\n# Preferred: Absolute imports\nfrom myproject.services import UserService\nfrom myproject.models import User\n\n# Avoid: Relative imports\nfrom ..services import UserService\nfrom . import models\n```\n\nRelative imports can break when modules are moved or reorganized.\n\n## Best Practices Summary\n\n1. **Keep files focused** - One concept per file, consider splitting at 300-500 lines (varies by complexity)\n2. **Define `__all__` explicitly** - Make public interfaces clear\n3. **Prefer flat structures** - Add depth only for genuine sub-domains\n4. **Use absolute imports** - More reliable and clearer\n5. **Be consistent** - Apply patterns uniformly across the project\n6. **Match names to content** - File names should describe their purpose\n7. **Separate concerns** - Keep layers distinct and dependencies flowing one direction\n8. **Document your structure** - Include a README explaining the organization\n","# Python Project Structure & Module Architecture\n\nDesign well-organized Python projects with clear module boundaries, explicit public interfaces, and maintainable directory structures. Good organization makes code discoverable and changes predictable.\n\n## When to Use This Skill\n\n- Starting a new Python project from scratch\n- Reorganizing an existing codebase for clarity\n- Defining module public APIs with `__all__`\n- Deciding between flat and nested directory structures\n- Determining test file placement strategies\n- Creating reusable library packages\n\n## Core Concepts\n\n### 1. Module Cohesion\n\nGroup related code that changes together. A module should have a single, clear purpose.\n\n### 2. Explicit Interfaces\n\nDefine what's public with `__all__`. Everything not listed is an internal implementation detail.\n\n### 3. Flat Hierarchies\n\nPrefer shallow directory structures. Add depth only for genuine sub-domains.\n\n### 4. Consistent Conventions\n\nApply naming and organization patterns uniformly across the project.\n\n## Quick Start\n\n```\nmyproject\u002F\n├── src\u002F\n│   └── myproject\u002F\n│       ├── __init__.py\n│       ├── services\u002F\n│       ├── models\u002F\n│       └── api\u002F\n├── tests\u002F\n├── pyproject.toml\n└── README.md\n```\n\n## Fundamental Patterns\n\n### Pattern 1: One Concept Per File\n\nEach file should focus on a single concept or closely related set of functions. Consider splitting when a file:\n\n- Handles multiple unrelated responsibilities\n- Grows beyond 300-500 lines (varies by complexity)\n- Contains classes that change for different reasons\n\n```python\n# Good: Focused files\n# user_service.py - User business logic\n# user_repository.py - User data access\n# user_models.py - User data structures\n\n# Avoid: Kitchen sink files\n# user.py - Contains service, repository, models, utilities...\n```\n\n### Pattern 2: Explicit Public APIs with `__all__`\n\nDefine the public interface for every module. Unlisted members are internal implementation details.\n\n```python\n# mypackage\u002Fservices\u002F__init__.py\nfrom .user_service import UserService\nfrom .order_service import OrderService\nfrom .exceptions import ServiceError, ValidationError\n\n__all__ = [\n    \"UserService\",\n    \"OrderService\",\n    \"ServiceError\",\n    \"ValidationError\",\n]\n\n# Internal helpers remain private by omission\n# from .internal_helpers import _validate_input  # Not exported\n```\n\n### Pattern 3: Flat Directory Structure\n\nPrefer minimal nesting. Deep hierarchies make imports verbose and navigation difficult.\n\n```\n# Preferred: Flat structure\nproject\u002F\n├── api\u002F\n│   ├── routes.py\n│   └── middleware.py\n├── services\u002F\n│   ├── user_service.py\n│   └── order_service.py\n├── models\u002F\n│   ├── user.py\n│   └── order.py\n└── utils\u002F\n    └── validation.py\n\n# Avoid: Deep nesting\nproject\u002Fcore\u002Finternal\u002Fservices\u002Fimpl\u002Fuser\u002F\n```\n\nAdd sub-packages only when there's a genuine sub-domain requiring isolation.\n\n### Pattern 4: Test File Organization\n\nChoose one approach and apply it consistently throughout the project.\n\n**Option A: Colocated Tests**\n\n```\nsrc\u002F\n├── user_service.py\n├── test_user_service.py\n├── order_service.py\n└── test_order_service.py\n```\n\nBenefits: Tests live next to the code they verify. Easy to see coverage gaps.\n\n**Option B: Parallel Test Directory**\n\n```\nsrc\u002F\n├── services\u002F\n│   ├── user_service.py\n│   └── order_service.py\ntests\u002F\n├── services\u002F\n│   ├── test_user_service.py\n│   └── test_order_service.py\n```\n\nBenefits: Clean separation between production and test code. Standard for larger projects.\n\n## Advanced Patterns\n\n### Pattern 5: Package Initialization\n\nUse `__init__.py` to provide a clean public interface for package consumers.\n\n```python\n# mypackage\u002F__init__.py\n\"\"\"MyPackage - A library for doing useful things.\"\"\"\n\nfrom .core import MainClass, HelperClass\nfrom .exceptions import PackageError, ConfigError\nfrom .config import Settings\n\n__all__ = [\n    \"MainClass\",\n    \"HelperClass\",\n    \"PackageError\",\n    \"ConfigError\",\n    \"Settings\",\n]\n\n__version__ = \"1.0.0\"\n```\n\nConsumers can then import directly from the package:\n\n```python\nfrom mypackage import MainClass, Settings\n```\n\n### Pattern 6: Layered Architecture\n\nOrganize code by architectural layer for clear separation of concerns.\n\n```\nmyapp\u002F\n├── api\u002F           # HTTP handlers, request\u002Fresponse\n│   ├── routes\u002F\n│   └── middleware\u002F\n├── services\u002F      # Business logic\n├── repositories\u002F  # Data access\n├── models\u002F        # Domain entities\n├── schemas\u002F       # API schemas (Pydantic)\n└── config\u002F        # Configuration\n```\n\nEach layer should only depend on layers below it, never above.\n\n### Pattern 7: Domain-Driven Structure\n\nFor complex applications, organize by business domain rather than technical layer.\n\n```\necommerce\u002F\n├── users\u002F\n│   ├── models.py\n│   ├── services.py\n│   ├── repository.py\n│   └── api.py\n├── orders\u002F\n│   ├── models.py\n│   ├── services.py\n│   ├── repository.py\n│   └── api.py\n└── shared\u002F\n    ├── database.py\n    └── exceptions.py\n```\n\n## File and Module Naming\n\n### Conventions\n\n- Use `snake_case` for all file and module names: `user_repository.py`\n- Avoid abbreviations that obscure meaning: `user_repository.py` not `usr_repo.py`\n- Match class names to file names: `UserService` in `user_service.py`\n\n### Import Style\n\nUse absolute imports for clarity and reliability:\n\n```python\n# Preferred: Absolute imports\nfrom myproject.services import UserService\nfrom myproject.models import User\n\n# Avoid: Relative imports\nfrom ..services import UserService\nfrom . import models\n```\n\nRelative imports can break when modules are moved or reorganized.\n\n## Best Practices Summary\n\n1. **Keep files focused** - One concept per file, consider splitting at 300-500 lines (varies by complexity)\n2. **Define `__all__` explicitly** - Make public interfaces clear\n3. **Prefer flat structures** - Add depth only for genuine sub-domains\n4. **Use absolute imports** - More reliable and clearer\n5. **Be consistent** - Apply patterns uniformly across the project\n6. **Match names to content** - File names should describe their purpose\n7. **Separate concerns** - Keep layers distinct and dependencies flowing one direction\n8. **Document your structure** - Include a README explaining the organization\n",{"name":5,"description":7},"main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Agent-智能体\u002FYYC3-Agent-智能体-agents\u002Fplugins\u002Fpython-development\u002Fskills\u002Fpython-project-structure",0,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base","https:\u002F\u002Fkb.yyc3.top\u002F","https:\u002F\u002Fgithub.com\u002FYYC-Cube","万象归元于云枢 | 深栈智启新纪元","2026-11-10 10:37:32",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill python-project-structure",{"tool":39,"command":40},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill python-project-structure",{"tool":42,"command":43},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill python-project-structure","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Agent-智能体\u002FYYC3-Agent-智能体-agents\u002Fplugins\u002Fpython-development\u002Fskills\u002Fpython-project-structure\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7CTDWHERCXPQCP0K03A86AS","vercel-sandbox","Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include \"Vercel Sandbox browser\", \"microVM Chrome\", \"agent-browser in sandbox\", \"browser automation on Vercel\", or any task requiring Chrome in a Vercel Sandbox.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fvercel-sandbox\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7CTD8D2BNJY54S65M47HEJA","slack","Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include \"check my Slack\", \"what channels have unreads\", \"send a message to\", \"search Slack for\", \"extract from Slack\", \"find who said\", or any task requiring programmatic Slack interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fslack\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7CTCSSB8ZP3Q58C3YZDZK1W","electron","Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include \"automate Slack app\", \"control VS Code\", \"interact with Discord app\", \"test this Electron app\", \"connect to desktop app\", or any task requiring automation of a native Electron application.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Felectron\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7CTCBJY76688V4DCZGWFHGQ","dogfood","Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to \"dogfood\", \"QA\", \"exploratory test\", \"find issues\", \"bug hunt\", \"test this app\u002Fsite\u002Fplatform\", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fdogfood\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7CTC4H0FFGVEAQR9PA4GA1A","agent-browser","Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to \"open a website\", \"fill out a form\", \"click a button\", \"take a screenshot\", \"scrape data from a page\", \"test this web app\", \"login to a site\", \"automate browser actions\", or any task requiring programmatic web interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fagent-browser\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7CTBKVFYBG78FDSABSDJTTQ","shadcn","Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn\u002Fui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for \"shadcn init\", \"create an app with --preset\", \"switch to --preset\", and for building a design system or applying a DESIGN.md or brand spec to shadcn\u002Fui.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-UI-界面组件\u002FYYC3-UI-界面组件-ui\u002Fskills\u002Fshadcn\u002FSKILL.md",[],[]]