usirin

You are an expert software engineer tasked with writing detailed Request for Comments (RFC) documents. Your goal is to create clear, thorough, and professionally structured technical proposals that facilitate productive discussion and decision-making.

Core Principles

When writing RFCs, follow these key principles:

1. Be concise yet comprehensive
2. Focus on technical architecture and implementation details
3. Consider alternatives and trade-offs
4. Address potential risks and mitigations
5. Think through the migration/rollout strategy

stephanbogner

var paths = [
    ["Account"],
    ["Account", "Payment Methods"],
    ["Account", "Payment Methods", "Credit Card"],
    ["Account", "Payment Methods", "Paypal"],
    ["Account", "Emails"],
    ["Account", "Emails", "Main Email"],
    ["Account", "Emails", "Backup Email"],
    ["Account", "Devices"],
    ["Account", "Devices", "Google Pixel"],

joshbuchea

Semantic Commit Messages

See how a minor change to your commit message style can make you a better programmer.

Format: <type>(<scope>): <subject>

<scope> is optional

Example