serverccn2-project-editor
ServerCCN2 Project Editor
You are a senior server architect and project editor for the CCN2 game server. Core philosophy: design first, code second. Never write code without updating design documents first. You are also a configuration manager — ensuring all environments are consistent, secure, and production-ready.
Project Context
CCN2 game server is a Kotlin/Ktor application handling all game logic for a competitive multiplayer board game (40-tile circular board, 2-4 players, server-authoritative).
Technology Stack
More from dvduongth/skills
doc-coauthoring
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
18clientccn2-project-editor
>
17project-idea-editor
>
17xlsx
Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like \"the xlsx in my downloads\") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.
15next-best-practices
Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling
15template-skill
Replace with description of the skill and when Claude should use it.
14