원클릭으로 Manus에서 모든 스킬 실행

python-api-backend

스타2

포크1

업데이트2026년 5월 15일 07:40

Use this skill for Python backend API work, including FastAPI or Flask style endpoints, request and response models, validation, configuration, environment variables, connectors, background jobs, security-sensitive changes, and integration with a Next.js frontend.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

skrylexx

skrylexx/BreachRadar

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Python API Backend

Use this skill for backend work in Python.

Goals

Make safe backend changes with explicit validation and error handling.
Preserve existing architecture and conventions.
Keep API contracts stable when possible.
Avoid leaking secrets or weakening security.

Rules

Inspect the current backend structure before adding new modules.
Reuse existing config, settings, routers, schemas, and helpers.
Validate inputs explicitly.
Return predictable response shapes.
Keep errors actionable but not overly verbose.
Avoid silent failures.
Do not hardcode secrets, URLs, tokens, or credentials.
Prefer environment-based configuration consistent with the repo.
Preserve backward compatibility unless the request says otherwise.

API design

Keep endpoint responsibilities narrow.
Use clear naming for routes and payload fields.
Separate transport concerns from service logic where the codebase already follows that pattern.
If pagination, filtering, or sorting exists elsewhere, mirror the same contract style.

Security

Treat all external data as untrusted.
Sanitize and validate connector inputs.
Avoid exposing stack traces to frontend consumers.
Do not relax auth, CORS, or permission checks without explicit instruction.
Flag risky changes clearly.

Integration with Next.js

Keep response payloads easy for frontend consumption.
Document changed request and response fields briefly.
Do not duplicate frontend formatting logic in the API unless necessary.

Editing style

Change the narrowest possible set of files.
Reuse existing test or example patterns if present.
Avoid broad refactors while implementing one endpoint or connector.

Output style

For backend changes:

State the contract impact.
Implement the smallest safe change.
Note any env vars or migration implications.
Mention verification steps briefly.

이 저장소의 다른 Skills

같은 저장소

cicd-expert

skrylexx/BreachRadar

Specialized expertise in CI/CD pipelines, GitHub Actions, security audits (SCA, secrets), and automated quality checks. Use when modifying or troubleshooting .github/workflows, adding new CI checks, or ensuring repository integrity through automation.

2026-06-012

docs-readme-writer

skrylexx/BreachRadar

Use this skill when the task is to create, rewrite, improve, structure, or update project documentation such as README files, setup guides, runbooks, operating procedures, installation steps, contributor guides, technical documentation, architecture notes, deployment guides, onboarding docs, and troubleshooting documentation in Markdown.

2026-05-182

senior-webapp-cyber-auditor

skrylexx/BreachRadar

Use this skill when the task is to act as a senior full-stack developer and cybersecurity engineer for an existing web application repository, including repository analysis, secure architecture review, authorized web application pentest planning and execution, dependency and package review, version drift analysis, technology watch, upgrade recommendations, and safe remediation planning for Next.js, Tailwind CSS, Python backends, Docker, APIs, and CI/CD.

2026-05-172

frontend-page-builder

skrylexx/BreachRadar

Use this skill for building or finishing frontend pages in an existing product repository, especially dashboard pages, settings screens, admin sections, detail views, empty states, forms, and responsive layouts in Next.js with Tailwind CSS.

2026-05-152

minimal-diff-coder

skrylexx/BreachRadar

Use this skill whenever the task involves editing an existing codebase and the goal is to minimize token usage, reduce code churn, avoid unnecessary refactors, keep patches reviewable, and change only what is strictly required.

2026-05-152

nextjs-app-router

skrylexx/BreachRadar

Use this skill for Next.js App Router development in TypeScript or JavaScript, including app directory architecture, layouts, pages, route handlers, server components, client components, loading states, error boundaries, metadata, environment variables, and safe frontend changes in existing repositories.

2026-05-152

name	python-api-backend
description	Use this skill for Python backend API work, including FastAPI or Flask style endpoints, request and response models, validation, configuration, environment variables, connectors, background jobs, security-sensitive changes, and integration with a Next.js frontend.

Python API Backend

Use this skill for backend work in Python.

Goals

Make safe backend changes with explicit validation and error handling.
Preserve existing architecture and conventions.
Keep API contracts stable when possible.
Avoid leaking secrets or weakening security.

Rules

Inspect the current backend structure before adding new modules.
Reuse existing config, settings, routers, schemas, and helpers.
Validate inputs explicitly.
Return predictable response shapes.
Keep errors actionable but not overly verbose.
Avoid silent failures.
Do not hardcode secrets, URLs, tokens, or credentials.
Prefer environment-based configuration consistent with the repo.
Preserve backward compatibility unless the request says otherwise.

API design

Keep endpoint responsibilities narrow.
Use clear naming for routes and payload fields.
Separate transport concerns from service logic where the codebase already follows that pattern.
If pagination, filtering, or sorting exists elsewhere, mirror the same contract style.

Security

Treat all external data as untrusted.
Sanitize and validate connector inputs.
Avoid exposing stack traces to frontend consumers.
Do not relax auth, CORS, or permission checks without explicit instruction.
Flag risky changes clearly.

Integration with Next.js

Keep response payloads easy for frontend consumption.
Document changed request and response fields briefly.
Do not duplicate frontend formatting logic in the API unless necessary.

Editing style

Change the narrowest possible set of files.
Reuse existing test or example patterns if present.
Avoid broad refactors while implementing one endpoint or connector.

Output style

For backend changes:

State the contract impact.
Implement the smallest safe change.
Note any env vars or migration implications.
Mention verification steps briefly.