菜单
Implements all methods of a defined interface, abstract class, or contract with full type safety, error handling, and documentation. Do NOT use for designing interfaces from scratch, API contract design, or generating tests only.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use to implement a REST or GraphQL API endpoint from a specification or description, including request validation, error handling, and accompanying tests. Activate for building a new API route, resolver, or handler end-to-end. Do NOT use for API design/contract creation, documentation generation, or frontend API consumption.
Use to implement background job processing with a queue, worker, retry with exponential backoff, dead letter queue, and monitoring. Activate when the request involves offloading work from the request cycle (emails, reports, data processing). Do NOT use for real-time event streaming, webhook handling, or scheduled cron jobs.
Use to scaffold a new project from scratch — generating directory structure, configuration files, entry points, and a README skeleton. Activate when starting a new project, service, or package and needing a production-ready starting point. Do NOT use for adding features to existing projects, generating tests, or CI/CD configuration.
Use to design and implement a caching layer for data that is expensive to compute or fetch. Activate for cache-aside, write-through, or write-behind patterns, TTL strategy, and cache invalidation logic. Do NOT use for database query optimization, CDN configuration, or HTTP response caching headers.
Use to generate a CI/CD pipeline configuration for building, testing, and deploying an application. Activate for GitHub Actions, GitLab CI, CircleCI, or similar pipeline tools for any tech stack. Do NOT use for infrastructure provisioning, Dockerfile creation, or deployment strategy design.
Use to generate production-ready code for a new feature, function, class, or module from a description. Activate for writing new code from scratch with error handling, inline documentation, and a self-review checklist. Do NOT use for refactoring existing code, code review, or test generation.
| name | interface-contract-implementation |
| description | Implements all methods of a defined interface, abstract class, or contract with full type safety, error handling, and documentation. Do NOT use for designing interfaces from scratch, API contract design, or generating tests only. |
| version | 1.1.0 |
| time_saved | Manual: 1–3 hours | With skill: 10–20 minutes |
| license | Proprietary — Personal Use Only |
| category | coding |
| complexity | Intermediate |
| tokens | ~3000 |
| tags | ["interface","contract","implementation","type-safety","abstraction"] |
| author | vheins |
Implement all methods of a defined contract with full type safety, error handling, and documentation.
| Variable | Type | Req | Description |
|---|---|---|---|
tech_stack | string | Yes | e.g., "TypeScript + Node.js" |
interface_definition | string | Yes | Full definition of the contract |
context | string | Yes | Purpose, dependencies, and constraints |
| Case | Strategy |
|---|---|
| Optional methods | Implement required logic; note skipped overrides. |
| Generics | Apply concrete parameters for the context; note generalization paths. |
| Circular deps | Flag in context; suggest lazy injection or event decoupling. |
flowchart TD
A([Start: Interface Implementation]) --> B[Parse interface definition]
B --> C[Enumerate all methods]
C --> D{Ambiguous
behavior?}
D -- Yes --> E[State assumption explicitly]
D -- No --> F[Design constructor:
inject dependencies]
E --> F
F --> G[Implement methods]
G --> H{External
dependency?}
H -- Yes --> I[Wrap with error boundary,
translate to domain error]
H -- No --> J[Pure logic with guard clauses]
I & J --> K{Uses generics?}
K -- Yes --> L[Apply concrete type params]
K -- No --> M{Optional methods?}
L --> M
M -- Yes --> N[Implement required only,
note optional skipped]
M -- No --> O{Circular dependency?}
N --> O
O -- Yes --> P[Flag it, suggest lazy injection
or event decoupling]
O -- No --> Q[Add doc comment per method]
P --> Q
Q --> R[Write usage example]
R --> S[Document error handling strategy]
S --> T([Output: Complete contract implementation])
@upstash/context7-mcp: Library documentation and examples.| Version | Date | Description |
|---|---|---|
| 1.1.0 | 2026-03-20 | Restructured: moved examples/references, added compatibility/license |
| 1.0.0 | 2026-03-20 | Initial release |