메뉴
Use when explaining, designing, auditing, or extending the mechanics of the Tales of the Old West 2E repo. This skill maps the rules, design space, design logic, integration points, and gameplay logic so new mechanics fit the existing engine and manuscript structure.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Audit and rewrite content to remove AI writing patterns ("AI-isms"). Use this skill when asked to "remove AI-isms," "clean up AI writing," "edit writing for AI patterns," "audit writing for AI tells," or "make this sound less like AI." Supports a detect-only mode, an edit-in-place mode for files, an optional voice profile (casual / professional / technical / warm / blunt), and an iterate-to-convergence pass.
Use when designing, drafting, or revising a tabletop RPG adventure, scenario, campaign chapter, or sandbox opener for any system. System-agnostic. Covers the full architecture: cold open, historical/situational frame, faction wants, NPC casting, rumor seeds, consequence tracks, scene-by-scene branching grammar, dilemma design, distributed clues, combat-encounter blocks, multi-ending reckonings, sandbox exits, and pacing rhythms. Built from the design DNA of robust, replayable, choice-driven adventures that survive contact with players. Triggered by requests to "write an adventure", "design a scenario", "outline a campaign chapter", "draft a sandbox opener", "build an introductory module", or to revise/audit an existing adventure for branching, pacing, or robustness.
Use when drafting, revising, or reviewing manuscript-facing prose for the Tales of the Old West 2E repo, or any gritty realistic western fiction in the McCarthy / McMurtry / Portis / Leonard / Hall / Lansdale / Swarthout / Hansen tradition. Applies the voice, structure, diction, knowledge base, and anti-AI rules so prose reads like native fiction — harsh, clear, physical, atmospheric, and free of generated-text tells. Covers corebook chapters, proposal prose, item and ability descriptions, flavor exposition, examples, and mixed fiction-and-rule bridges, plus standalone short fiction in the same register.
Use when converting a tabletop RPG PDF into clean, structured markdown for `corebook/`, `rpg_projects/`, or similar source-document work. Covers layout-aware extraction, multi-pass cleanup, Tales of the Old West-specific repair rules, and final normalization.
Use when evaluating game balance in tabletop roleplaying games, especially when the task requires deep analytical and psychological analysis of game theory, player expectations, GM expectations, choice pressure, fairness, lethality, spotlight balance, and perceived versus actual balance.
Use when auditing talent combinations, ability stacking, character builds, or any multi-rule interaction for balance-breaking potential. Triggers on questions like "is this combo broken", "what are the strongest builds", "does this talent stack with that ability", "can players exploit this", or any request to stress-test a rule interaction. Also use when designing new talents or abilities that might create unintended synergy with existing content. This skill distinguishes between creative high-risk play (healthy) and one-decision dominant lines (unhealthy).
| name | western-rpg-design |
| description | Use when explaining, designing, auditing, or extending the mechanics of the Tales of the Old West 2E repo. This skill maps the rules, design space, design logic, integration points, and gameplay logic so new mechanics fit the existing engine and manuscript structure. |
Use this skill for rules analysis and design work in the Tales of the Old West 2E repo.
Start with:
corebook/AGENTS.md file if presentIf the task includes manuscript drafting, also use the western-writing skill.
Use it when you need to:
For each mechanic, analyze these layers:
When evaluating new rules, always look at:
When answering a design question, prefer this order:
All NPC and creature statblocks use a fixed 8-column table structure unique to this game. Never use flat wide tables that list attributes as columns.
Header row — attribute name + value, paired across four attribute columns:
| GRIT | <value> | QUICK | <value> | CUNNING | <value> | DOCITY | <value> |
| --- | --- | --- | --- | --- | --- | --- | --- |
Skill rows — abilities are placed under the column of the attribute they belong to. Ability name in the label cell, value in the adjacent value cell. Empty cells fill gaps where no ability applies. Attribute-ability mappings:
Talents line — placed immediately after the closing row of the table as a standalone bold paragraph. Markdown tables do not support colspan, so talents must not be placed inside the table.
Example (Ellis Rockcliffe):
| GRIT | 4 | QUICK | 3 | CUNNING | 5 | DOCITY | 3 |
| ---------- | --- | ----- | --- | ------- | --- | ------ | --- |
| PRESENCE | 3 | | | HAWKEYE | 2 | | |
| RESILIENCE | 1 | | | INSIGHT | 2 | | |
**Talents:** AUTHORITY (Advanced), CHARMING (Advanced), COLD BLOODED (Basic), BUSINESS MINDED (Advanced).
Creature/animal statblocks (wolves, dogs) that don't use the four standard attributes keep a simpler inline table — do not force them into the 8-column format.
When auditing a proposal, explicitly check: