メニュー
This layer provides the backend functionality for the RepoForge application, handling API requests, authentication, and database migrations. Trigger: When working in backend/ — adding, modifying, or debugging server-side logic.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | backend-layer |
| description | This layer provides the backend functionality for the RepoForge application, handling API requests, authentication, and database migrations. Trigger: When working in backend/ — adding, modifying, or debugging server-side logic. |
| license | Apache-2.0 |
| metadata | {"author":"repoforge","version":"1.0","complexity":"medium","token_estimate":800,"dependencies":[],"related_skills":[],"load_priority":"high"} |
This skill covers the backend functionality of the RepoForge application.
Trigger: When working in backend/ directory and its main responsibility is to manage server-side logic.
| Task | Pattern |
|---|---|
| Configure logging | configure_logging() |
| Run migrations | run_migrations_online() |
Set up custom middleware for handling requests, such as logging and authentication.
# apps/server/app/main.py
app.add_middleware(correlation_id_middleware)
app.add_middleware(request_logging_middleware)
app.add_middleware(security_headers_middleware)
Manage database schema changes using Alembic for version control.
# apps/server/alembic/env.py
run_migrations_online()
# To run the server
uvicorn apps.server.app.main:app --reload
# To run migrations
alembic upgrade head
This can lead to broken integrations and user-facing errors.
# BAD
return {"message": "success"} # Frontend expects a different structure
Four quality gate checklists for frontend: baseline visual, accessibility, metadata/SEO, and motion performance. Post-implementation quality gates. Trigger: When reviewing UI changes, before merging frontend PRs, during sdd-verify.
Browser-based UI verification using Playwright. Page Object Model, selector best practices, visual regression, network interception, and MCP integration. Trigger: When writing E2E tests, verifying UI changes, or setting up Playwright.
Interactive tutorial-style lessons for custom skills. Invoke /powerup <skill> for a guided walkthrough with examples, exercises, and knowledge checks. Trigger: When user says "powerup", "tutorial", "teach me", or wants to learn a skill interactively.
Self-installing markdown recipes for skills. Each skill can include an INSTALL.md that an agent reads and executes to set up dependencies, MCP servers, or config. Trigger: When installing a skill with INSTALL.md, or creating skills with setup requirements.
This skill covers the implementation of authentication routes. Trigger: When setting up auth-related endpoints in the backend.
This skill covers AES-256-GCM encryption for provider API keys. Trigger: Load this skill when handling crypto operations for API keys.