'rfc' 검색 결과

设计 API 错误码和错误结构时使用。适用于错误响应规范、调用方错误处理、调试可观测。优先使用 RFC 7807 Problem Details + 业务错误码 + 调用方处理建议。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Spring Boot coding conventions: REST controller design, service layer, dependency injection, configuration, DTO patterns, exception handling, and Bean Validation. Apply on any Spring Boot project. Works alongside spring-boot-plugin:spring-data-jpa for persistence and java-foundation:java-conventions for domain objects. Use this skill to: - Structure REST endpoints with @RestController, proper HTTP semantics, and DTO mapping. - Enforce constructor injection and @ConfigurationProperties over @Value on fields. - Write @Service classes with transactional boundaries at the right layer. - Handle errors consistently with @RestControllerAdvice and ProblemDetail (RFC 9457). Do NOT use this skill for: - JPA entity and repository patterns — see spring-boot-plugin:spring-data-jpa. - Spring Security configuration — see the security phase injection in stack.md. - Build tool configuration — see java-foundation:build-tooling.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

OAuth 2.1, JWT (RFC 8725), encryption, and authentication security expert. Enforces 2026 security standards.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Adopt govctl in an existing project. Discovers undocumented decisions, backfills ADRs/RFCs, annotates source code. Use when: (1) Project has no governance yet, (2) User mentions migrate, adopt, onboard, or brownfield

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Maintain governance artifacts without implementation work. Use when: (1) Accepting or refining ADRs, (2) Clarifying or amending RFCs without code changes, (3) Governance-only docs/check/render updates

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Execute the fast path for trivial changes with minimal governance ceremony. Use when: (1) User invokes /quick, (2) Change is doc-only or non-behavioral, (3) No RFC or ADR work is needed

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Facilitate design discussion — research context, clarify requirements, draft RFC/ADR

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Onderhoudt de inhoud van de roadmap op /roadmap — werkpakketten toevoegen, wijzigen, verplaatsen of verwijderen, onderzoeksvragen schrijven en aan een sectie van het position paper koppelen, en RFC's koppelen die het ontwerp beschrijven. Gebruik dit bij "voeg een werkpakket toe", "verplaats X naar de Hoe-fase", "zet er een onderzoeksvraag bij", of het bijwerken van fases, disciplines en swimlanes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Writing rules for the regelrecht docs site (docs/). Use when writing or editing prose under docs/ — RFCs, guides, component docs, concept pages, and the NL/EN landing copy. Keeps docs prose free of AI-generated tells and consistent with the site's government-technical register. Not for code, commit messages, or PR descriptions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Email marketing operations and automation for B2B SaaS. Use this skill for newsletter strategy, email automation sequences, lifecycle campaigns, nurture workflows, onboarding sequences, deliverability optimization, email copywriting, lead scoring, marketing automation platform setup, and cold-email sending infrastructure — secondary sending domains, SPF/DKIM/DMARC, and domain warmup — plus the contact budget: a cross-channel frequency cap across every sender (marketing, sales sequences, customer success, in-app). Also triggers on: email, newsletter, drip campaign, lifecycle, nurture, onboarding sequence, deliverability, email automation, lead scoring, marketing automation, our emails are going to spam, SPF, DKIM, DMARC, sender reputation, sending domain, cold email domains, domain warmup, mailbox setup, blacklist, bounce rate, BIMI, brand logo in inbox, VMC, Verified Mark Certificate, Common Mark Certificate, transactional email, password reset emails going to spam, DMARCbis, RFC 9989, DMARC pct tag, DMARC t=y test mode, DMARC rollout, move DMARC to reject, frequency cap, email fatigue, customers get too many emails, too many messages, sales and marketing both emailing the same person, communication limits, send frequency safeguard, global frequency capping, quiet period, message precedence, AI email summaries, Apple Intelligence summary replaces preview text, Gmail Gemini summary, Gmail AI Inbox, Apple Mail categories, our emails land in Promotions, writing emails for AI summaries.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Legal, security, privacy, and deliverability requirements every delivered app must satisfy — legal pages, PII/deletion rights, CSP/Trusted-Types/Zod, AI-agent security, RFC7807 errors, email domain auth.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Test horizontal and vertical authorization bypass via session ID swapping between accounts, IDOR through parameter manipulation (invoice=, user=, menuitem=, EventID=), and special header injection (X-Original-URL, X-Rewrite-URL, X-Forwarded-For, X-Remote-IP, X-Client-IP with 127.0.0.1/localhost/RFC1918 values). Tools: Burp Suite with Autorize/AuthMatrix extensions, OWASP ZAP Access Control Testing add-on.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Implement and debug OAuth 2.0 DPoP (RFC 9449) refresh token sender-constraining for WebCrypto, Node.js ES6, and browser runtimes integrating with Google's OAuth platform. Use when configuring non-extractable asymmetric key pairs (P-256), generating DPoP Proof JWTs for authorization code exchange and token refresh, or handling 400 use_dpop_nonce challenge retry loops at oauth2.googleapis.com/token. Don't use for unconstrained OAuth 2.0 flows (where refresh tokens are not bound to a client key pair), or for Google Cloud IAM / service account authentication.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Spring Boot 4 REST API implementation patterns. Use when creating REST controllers, REST endpoints, request validation, exception handlers with ProblemDetail (RFC 9457), API versioning, content negotiation, WebFlux reactive endpoints, HTTP clients with @HttpExchange, JSON serialization with Jackson 3, error handling, or CORS configuration. Covers @RestController patterns, Bean Validation 3.1, global error handling, and declarative HTTP clients.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Doc-first async culture — RFC, status update, async meeting alternative, decision log

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Patterns and architectures for autonomous Claude Code loops — from simple sequential pipelines to RFC-driven multi-agent DAG systems.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Fetch a URL and return clean markdown, for arbitrary external pages (blog, RFC, GitHub issue, vendor doc) not covered by mk:docs-finder. Static-only by default; opt-in JS rendering available.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Serve a markdown file/directory as a calm, book-like reader via a local HTTP server (127.0.0.1 only); good for long-form docs like RFCs and plans. Supports Mermaid, dark/light mode, and a nav sidebar.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Fetch a URL and return clean markdown. Use when the agent needs an arbitrary external page (blog, RFC, GitHub issue, vendor doc) not covered by mk:docs-finder. Triggers on URLs in chat. Static-only by default; opt-in JS rendering available.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Serve any markdown file or directory as a calm, book-like reader via a local HTTP server (127.0.0.1 only). Best for long-form documents — RFCs, runbooks, design docs, plan files — where comfortable in-browser reading matters. Supports Mermaid diagrams, dark/light mode, plan navigation sidebar, and keyboard shortcuts. Requires explicit start and stop lifecycle.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

When co-authoring a PRD, design doc, RFC, decision doc, or technical spec — 3-stage flow (context → section-by-section → reader-test) — even if the user just says 'help me write this spec'.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.