メニュー
Scaffolds the testing infrastructure for a FastAPI (Pydantic V2) backend using Pytest. Configures Dockerized DB, directory structure, and modern pyproject.toml settings.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Provides the single source of truth for brand guidelines, design tokens, technology choices, and voice/tone. Use this skill whenever generating UI components, styling applications, writing copy, or creating user-facing assets to ensure brand consistency.
Generates high-quality, predictable, and efficient .agent/skills/ directories based on user requirements. Use this skill when the user asks to create a new skill.
Reviews code changes for bugs, style issues, and best practices. Use when reviewing PRs or checking code quality.
Generates hexagonal architecture directory structure and boilerplate code for new domains in the FastAPI backend. Use when creating a new backend module, feature, or domain.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
Automates interaction with Google NotebookLM via MCP. Use this skill when the user wants to research topics, manage notebooks, generate content (audio/video overviews, reports), or query existing sources using NotebookLM.
| name | setup-backend-testing |
| description | Scaffolds the testing infrastructure for a FastAPI (Pydantic V2) backend using Pytest. Configures Dockerized DB, directory structure, and modern pyproject.toml settings. |
app/main.py, pyproject.toml, and requirements.txt.pydantic>=2.0).Add the following to requirements-dev or poetry group:
pytest, pytest-covpytest-mock (Wrapper around unittest.mock)pytest-asyncio (Critical for async Pydantic/FastAPI tests) [10]httpx (For API integration tests)polyfactory (Recommended for Pydantic V2) OR factory-boyrespx (For mocking external HTTP services) [5]Create the hierarchy ensuring separation of concerns [11]:
backend/tests/
├── unit/
├── integration/
├── contract/
├── factories/ # Pydantic Model Factories
├── conftest.py # Global fixtures (DB session, AsyncClient)
└── pyproject.toml # Configuration (instead of pytest.ini)
Generate fixtures for:
• Async Client: httpx.AsyncClient with base_url="http://test".
• DB Session: A session strictly bound to the test transaction (rollback strategy).
• Schema Lifecycle: A scope="session" fixture that creates the DB schema (e.g., Base.metadata.create_all(bind=engine)) at start and drops it at finish. This guarantees tests work even if test.db doesn't exist.
• Event Loop: Override default event loop scope to session if using async fixtures.
Inject the following configuration to handle Asyncio and warnings properly:
[tool.pytest.ini_options]
minversion = "6.0"
addopts = "-v --strict-markers --cov=app --cov-report=term-missing"
asyncio_mode = "auto"
testpaths = ["tests"]
markers = [
"unit: Fast tests, no I/O [12]",
"integration: Requires Docker/DB [12]",
"contract: OpenAPI schema validation [12]",
]
filterwarnings = [
"ignore::DeprecationWarning", # Filter noise from third-party libs
]
• tests/unit/test_smoke.py: Verify a Pydantic model uses model_validate correctly. • tests/integration/test_health.py: Full async HTTP request to health endpoint.
• DO NOT use pytest.ini if pyproject.toml exists; consolidate config. • ENSURE asyncio_mode = "auto" is set to avoid decorators on every async test.