xcpc-jiangly-style（xcpc 江南风格）

XCPC: jiangly C++ Style

Overview

Proven C++ coding style from jiangly's Codeforces submissions. Focuses on safety, maintainability, and modern C++ features for competitive programming.

Core principle: Zero global pollution, zero global arrays, explicit types, modern C++.

When to Use

• Writing C++ solutions for Codeforces, ICPC, AtCoder, etc.
• Creating competitive programming templates
• Reviewing contest solutions
• Teaching competitive programming best practices

Don't use for:

• Production C++ code (different requirements)
• Non-competitive programming projects

MANDATORY WORKFLOW - READ BEFORE WRITING CODE

This skill enforces strict adherence to jiangly's coding style. You MUST follow this workflow:

Step 1: Consult Rules Before Writing

Before writing ANY code, you MUST:

1. Read the relevant rule files in rules/ directory based on your task
2. Check Red Flags table below to avoid common mistakes
3. Reference examples from rule files - they are the source of truth

Step 2: Match Rule Requirements

For each code decision, verify against rules:

Step 3: Verify Against Red Flags

Before finalizing code, check EVERY row in the Red Flags table below.

If any pattern matches, you MUST fix it before output.

Step 4: Self-Correction Checklist

After writing code, verify:

• No using namespace std;
• No global arrays (all in solve())
• Used using i64 = long long;
• Used and/or/not instead of &&/||/!
• Used std:: prefix everywhere
• 4-space indentation, K&R braces
• No line compression (one statement per line)
• Used "\n" not std::endl
• Large temporary arrays in block scopes {}
• Strings preallocated with reserve() when size known
• Used swap() for O(1) variable reuse
• Used push_back() for single characters, not +=
• Symmetric comparison patterns (a[i] <= b[j])
• Uppercase names for temporary count arrays (S, T)
• Use iota + lambda for index-value sorting, not structs
• Loop variables initialized in for header when possible
• Output uses " \n"[i == n - 1] for space-separated values

Rule Files are PRIMARY Reference

The Quick Reference table below is a summary. Rule files contain the complete, authoritative examples. When in doubt, read the rule file.

Code Template

#include <bits/stdc++.h>

using i64 = long long;

void solve() {
    int n;
    std::cin >> n;

    std::vector<int> a(n);
    for (int i = 0; i < n; i++) {
        std::cin >> a[i];
    }

    std::cout << ans << "\n";
}

int main() {
    std::ios::sync_with_stdio(false);
    std::cin.tie(nullptr);

    int t;
    std::cin >> t;

    while (t--) {
        solve();
    }

    return 0;
}

Red Flags - STOP

Full Documentation

For complete details on all rules: AGENTS.md

FINAL CHECKPOINT - BEFORE OUTPUTTING CODE

You MUST verify ALL items below before showing code to user:

□ Read relevant rule files (naming.md, formatting.md, etc.)
□ Checked against Red Flags table
□ No `using namespace std;`
□ No global arrays
□ Used `i64` for long long
□ Used `and`/`or`/`not` keywords
□ Used `std::` prefix throughout
□ 4-space indent, K&R braces
□ No compressed lines
□ Used `"\n"` not `std::endl`
□ Temporary arrays in block scopes
□ String operations use `reserve()` and `swap()`
□ Symmetric comparison patterns
□ Uppercase temp array names (S, T)
□ Use iota + lambda for sorting with indices
□ Loop vars in for header when scope permits
□ Output uses " \n"[i == n - 1] trick

If ANY item fails, fix before output. This is non-negotiable.